Within each section, you define parameters using a 'key' followed by the "=" sign and followed by one or more alpha-numeric arguments. Parameters within the section may be arranged in any order. Multiple arguments must be separated by spaces, a dot, or a comma. A comment line starts with "/". The following keys are defined at the moment: Section: [PORT]
Sets the COM port used.|
The COM may be any serial port or TCP or UDP .
TCP and UDP use port 20000
|BAUDS||Communication speed. Only applies to serial communications ports||SPEED=19200|
|PARITY||0=NONE, 1=ODD, 2=EVEN 3=MARK 4=SPACE. Only applies to serial communications ports||PARITY=2|
|STOP||Stop bits. 1 or 2. Only applies to serial communications ports||STOP=1|
|DATA||Data bits. 7 or 8. Only applies to serial communications ports||DATA=8|
Accepts a string of the form baud=9600 parity=N data=8.||parity=E data=8 stops=1|
The identifier for this IPS on the UDP (UNET) network.||NODE=1|
The index of the register in the data table that will be used for remote reset. Writing to this register causes the IPS to be re-read the configuration file.||None. No reset register.|
The time in milliseconds that this station will wait for a response
before trying again.
. The default value is 250.
Specifies the IP of a remote micro-server used to communicate with the OPTOMUX station when using TCP or UDP. Each remote is defined by 5 decimal numbers. The first number is the OPTOMUX address. The next 4 are the IP of the micro-server.
Micro-servers must be listening on port 504
You may include up to 64 "REMOTE" lines in the file.
|GET||Defines a cluster of 16-bit values to be received from a remote SYMAX address. Each "GET" definition consists of 5 numbers.You may include up to 64 "GET" definitions in the file.
FIRST, QTY, NODE, POS, ALERT
Defines a cluster of 16-bit valuess to be sent to a remote
station. Each "SEND" definition consists of 6 numbers. You may include
up to 64 "SEND" definitions in the file.
FIRST, QTY, NODE, POS, ALERT,ENABLE
|ROUTE||Defines a station ID. Each station is identified by a route that consists of up to 8 drops. You may include up to 64 "ROUTE" definitions in the file. Each route is defined by a ROUTE cluster as follows : ID, NUMBER OF DROPS, DROP#1, DROP#2, .... , DROP#8 For instance the route for station #3 consists of 5 drops : 10,3,6,8,120. The route for this station is defined by the following cluster: 3,5,10,3,6,8,120,0,0,0 Note : if the station id used in the GET or SEND clusterS is not found in a ROUTE cluster, the route defaults to 3 drops : 30,130,1|