.INI File Format

The INI file consumed by dtCyber has the following general format:

[ <config_name> ]

; this is a comment

; there are three types of statements

<keyword> = <value>
<config.group> = <section.name>
<declaration> = <declaration parameters>

; =============================
; there are five possible configuration groups:
;   deadstart
;   equipment
;   helpers
;   npuConnections
;   operator

[<equipment.section.name>]
; This section contains all of the equipment
; definitions that are associated with the
; equipment.section.name configuration.

[<deadstart.section.name>]

; This section contains a representation of
; deadstart panel settings that are associated
; with the deadstart.section.name configuration.

[<helpers.section.name>]

; This section contains a list of pathnames
; of scripts that start/stop helper programs
; that are associated with the
; helpers.section.name configuration.

[<npuConnections.section.name>]

; This section contains definitions of data
; communication features that are associated
; with the npuConnections.section.name
; configuration.

[<operator.section.name>]

; This section contains a list of DtCyber
; operator commands associated with the
; operator.section.name configuration.

dtCyber accepts two parameters on the command line:

section_name is the identifier of the section within the configuration file to be used when dtCyber starts. The default is cyber

file_name is the name of the configuration file that contains the definition statements. The default filename is cyber.ini which is sought in the current working directory in which the command is invoked.

dtCyber initialization occurs in 5 phases

1. Read Configuration Section from the .ini file
2. (If present) Read the overlay from the corresponding overlay file (<ini_filename>.ini ← <ini_filename>.ovl)
3. Load the Deadstart configuration
4. Interpret Equipment Declarations
5. Configure the Operator Interface
6. Start up “Helpers”

Proceed to Configuration Section