Supported device types and versions
Communication line configuration
Communication station configuration
Station protocol parameters
I/O tag configuration
Literature
Changes and modifications
Document revisions

Supported device types and versions


This protocol implements the server-side of Telegyr TG809 standard. There is supported a configuration in both line and system redundant configurations.

Communication line configuration


Communication station configuration


Station protocol parameters


Configuration dialog window - tab "Protocol parameters".
They influence some optional parameters of the protocol.

Table 1

ParameterMeaningUnitDefault value
Communication LineA number from range 0-255 defining the "Communication number" parameter in the protocol telegrams.-0
Line Alive TimeoutTimeout for detection of failure of the master side of communication.
After elapsing the timeout since receiving the last sign, the communication line is considered to be nonfunctional. If all lines did not work (relates to the redundant lines), all stations switch to the status of communication error StCOMERR, and after elapsing another such interval, switch to StHARDERR status.
sec7
Read Wait TimeoutThe delay between reading data from the communication line.ss.mss00.050
MOXA TimeoutTimeout for detection of failure of one communication line on the redundant lines. After elapsing the timeout since receiving the last character, the communication is redirected to another communication line, i.e. reading/writing will be done via secondary/backup device.mi:ss00:10
Max Data SizeThe maximum number of data bytes in a single packet. This parameter defines the approximate value (can be exceeded by a data size of one output I/O tag). The standard defines maximum data size equal to 255 bytes but decreasing the packet size practically solved a particular packet fragmentation problem in WAN communication.-210
System Redundancy: Manages A Status AddressHW address of output I/O tag with the status of system redundancy. The format of the HW address is Rack.Chassis.Slot.Point or Rack-Chassis-Slot-Point, for example, "0-2-15-1".
This parameter is useful for Serial System&Line Redundant and SerialOverUDP System&Line Redundant lines, which enable the communication with two independent control systems (e.g. main dispatching SED in Žilina and backup dispatching SED in Bratislava).
The parameter enables to ignore values that are received from the control system, which is inactive just now, providing that the application knows which one is active or inactive. It can know it e.g. based on the value of input I/O tag with a defined value.
This feature (information about active control system) will work providing that output I/O tag of Dout type with the same HW address as defined in this parameter is on the station and the application must write True into it if "System A" is active, or False if "System B", configured on the system redundant line, is active.
-
Is SubstationOn every line, there should be only one station (called the main station) that has this parameter set to False. All other stations (called substations) should have this parameter set to True. This emulates the situation when there may be several substations behind the main station. Requests from the master which do not contain the station number, are related to the main station.-False
Scan-only ModeIn scan-only mode, data is being read and analyzed, but no data is sent. Combined with the parameter Full Debug this parameter enables the KOM process to be used as an analyzer of TG809 communication.-False
No Point No AnswerIf the I/O tag with an address that is in the request from the TG809 server is not found, the KOM process will not send any response.
This behavior is not according to the standard but it can be used, for example, to simulate unconfirmed commands.
-False
Full DebugEnables detailed listings about sending and receiving values.-False

I/O tag configuration


Possible I/O tags: Ai,Ao,Di,Dout,QI,Ci,Co

Address of I/O tags: either software or hardware address

For I/O tags of Ai and Ci type, you must define the minimum and maximum range - Min and Max. The values will be calculated for this range (from range -32000 … 32000 supported by protocol).
For I/O tags of Ao and Co, you must define the minimum and maximum range - Min and Max. Same as for input I/O tags but in addition the values out of defined range will be sent as the values -32000 or 32000.

I/O tags of Dout type have supplementary options:


Literature


-

Changes and modifications


-

Document revisions


Communication protocols