Funk-Electronic Piciorgros GmbH
TGW-100/TGW-100R
V2.71 - Page 50 of 59
4.2.1
Modbus RTU
As the Modbus RTU protocol can be used either for internal device access or for
communication with an external device, care should be taken when sharing out the
Modbus addresses. Under no circumstances, an external device should have the same
Modbus address as the TGW-100.
4.2.2
ROC protocol
The ROC protocol has the same basic data structure for the address byte location and
data packet detection than MODBUS, so MODBUS and ROC protocol shares the same
protocol setting in the configuration.
4.2.3
DNP3
Using the Link Address out of the DNP3 protocol, the routing to the outstation can be
calculated. In case of transmitting multiple DMP3-Data Segments while the timeout
period is not considered, each data segment will be transmitted individually.
Outstations can send data at any time to the master device (unsolicited messaging)
Serial DNP3 was tested with the TGW-100 simultaneously with the HART protocol.
The DNP3 was communicating over the COM port while HART was transferred via
AUX. In that application the TGW-100G Serial-to-Tetra Gateway was used with an
ETELM switch and Infrastructure.
4.2.4
IEC 60870-5-101
The routing for this protocol is similar to the DMP3. Also in this case it may be that
multiple data segments are sent, to complete one message.
4.2.5
PakBus
Pak bus is a much unknown protocol, but it is fully supported by the TGW-100
4.2.6
BSAP
The TGW-100 detects the difference between the normal and the extended messages in
BSAP protocol and extracts the address information accordingly. The node address
contains 7 bit, so the address range which can be used for routing here is 0-127.
As any device can also act itself as a router, you may enable a master-to-master
communication for the used serial port.
Any node can then itself contain a routing table for a retransmission of information to
other nodes (which is not possible when acting in slave mode)
