|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|
||
|
|
|
|
|
|
|
|||||||||||
 |
|
|||||||||||
 |
|
|||||||||||
|
|
|||||||||||
 |
|
|||||||||||
Protocol converter The Connex 30 and Connex 60 are designed to allow you to grow from a single centralized site to a system with many IEDs, to several sites networked together. The master gateway node, input and output (I/O) nodes and a router module are the basic elements of the Connex system, but in its simplest configuration, it may be used as a protocol converter for legacy RTUs. Protocol converters integrate newer technology with an older system without having to re-invent the wheel. Perhaps you want to add a new multifunction protection IED but can't justify replacing or upgrading your Front-end Processor that communicates via an older proprietary protocol. The solution? A protocol converter that makes the new device compatible with the old SCADA system. A protocol converter exchanges information with multiple parts of the SCADA system using different message formats and timing, but retains the basic information content as it passes from one communication channel to another. By simply creating and mapping one virtual RTU for each IED, you have a protocol converter that gathers information from the IED and passes it on to the virtual RTU, where the information is then gathered by the master as if it was talking directly to the IED. Protocol conversion is one of the many innovative features of our NTU line. We have a number of protocol options for the master and IED gateways. |
|
|||||||||||
|
|
|||||||||||
|
|
|||||||||||
 |
|
|||||||||||
 |
|
|||||||||||
|
||||||||||||
Contents © 2008 Advanced Control Systems, Inc. All trademarks are the property of their respective owners. This site last updated: 17 July 2008. |