Direct IEC-101 to IEC-104 Translation: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
[[Pilt:IEC101-104_direct.png]]<br /> | [[Pilt:IEC101-104_direct.png]]<br /> | ||
In this example, lower level device is configured to Port1 (serial master), using IEC101 protocol. | |||
The uplink is configured to Port14 (TCP/IP slave), using IEC 104 protocol. | |||
By pairing the two ports together in GWS (Common->Direct IEC-101 to IEC104), the IEC101 protocol is translated to IEC104 protocol. | |||
Objects of Device1 are not defined in GWS "Objects" tab.All the data is directly translated to IEC104 channel without intermediate database. | |||
Note: Direct IEC-101 to IEC-104 Translation frature should not be used together with "Redundant Connections" feature. | |||
Revision as of 09:22, 25 February 2015
Determine groups of ports (up to 2 ports in each group) for direct protocol translation (without intermediate database) from IEC 60870-5-101 to IEC 60870-5-104 and vice versa. Lower lewel device still has to be configured in GWS to determine communication parameters: address, address length etc.
In this example, lower level device is configured to Port1 (serial master), using IEC101 protocol. The uplink is configured to Port14 (TCP/IP slave), using IEC 104 protocol. By pairing the two ports together in GWS (Common->Direct IEC-101 to IEC104), the IEC101 protocol is translated to IEC104 protocol. Objects of Device1 are not defined in GWS "Objects" tab.All the data is directly translated to IEC104 channel without intermediate database.
Note: Direct IEC-101 to IEC-104 Translation frature should not be used together with "Redundant Connections" feature.