Field: Protocol/IO Gateways
The field-deployable SYNC solutions come in ruggedized, substation-hardened gateways that are tested to IEC61850-3 specifications for EMI/EMC and Surge and provide the full SYNC suite of protocols.
SYNC 1000: This is a pocket sized field device that can act as a communicable remote monitoring and control node for individual data sources for applications like transformer monitoring, meter reading, retrofitting legacy devices with new protocols, serial to Ethernet/PPP converter, bump-in-the-wire security adapter, 61850 proxy GGIO gateway and M2M Node with VPN and SMS. The device comes with optional built-in wireless modems and digital and analog IO, is built to withstand outdoor conditions and can act as a mini pole-top RTU.
SYNC 2000: Mid-sized field device with up to 6 serial channels, 2 Ethernet channels, optional modem card and IO board for applications like substation protocol converters, data loggers, low end data concentration, multi-protocol mapping, industrial complex meter gateway, building automation with all major open standards as well as select proprietary protocols support.
SYNC 3000: High end field device with upto 16 serial channels, 4 Ethernet channels (FO or Base-T) for large scale protocol conversion/concentration. Supports all features of SYNC2000 with additional processing power, RAM and storage capacities.
SYNC-OEM: OEM offerings provide customers the option to install natively the full range of SYNC protocols and capabilities within legacy and proprietary devices. The solution comes in a SYNC miniature board with the full licensed SYNC firmware and OS that can be integrated through internal TTL ports to present a modern protocol to the outside world available at the legacy device’s communication panel. A customized configuration engine is also provided as a licensed option.
SYNC Gateways support a wide range of open and proprietary protocols. The following code determines the protocol availability:
S - Protocol is supported and operational in the associated product and available at standard prices
R - Protocol is not yet implemented on the associated product, but available at standard prices
C - Protocol is not yet implemented on the associated product and requires special pricing
A - Protocol software and hardware realization services, consulting and training offered
N - Protocol is not yet implemented and is not available on the associated product or as an implementation service
| Protocol | SYNC - OEM | SYNC 1000/2000 | SYNC 3000S4R2 | SYNC 3000S16Rx | Product Realization Service |
|---|---|---|---|---|---|
| IEC | |||||
| IEC 61850 | S | S | S | S | A |
| IEC 60870-5-101 | S | S | S | S | A |
| IEC 60870-5-102 | C | C | C | C | A |
| IEC 60870-5-103 | S | S | S | S | A |
| IEC 60870-5-104 | S | S | S | S | A |
| ICCP / TASE.2 (IEC60870-6) | N | S | S | S | A |
| IEC 61400-25 | N | S | S | S | A |
| IEC 61968 | N | N | N | S | A |
| IEC 61970 | N | N | N | S | A |
| DLMS/COSEM - IEC 62056 | C | C | C | C | A |
| IEEE | |||||
| IEEE C37.118 | S | S | S | S | A |
| IEEE 1344 | N | R | R | R | A |
| DNP3 Org | |||||
| DNP3 Serial | S | S | S | S | A |
| DNP3 Network | S | S | S | S | A |
| SEL | |||||
| SEL 451 | R | R | R | R | A |
| SEL 421 | R | R | R | R | A |
| SEL 311A | R | R | R | R | A |
| SEL 421 | R | R | R | R | A |
| SEL Others | R | R | R | R | A |
| Schneider | |||||
| Modbus RTU - SEPAM | S | S | S | S | A |
| ABB | |||||
| SPA Bus | S | S | S | S | A |
| RP570 | S | S | S | S | A |
| RP571 | S | S | S | S | A |
| Indactic 33/1 | C | C | C | C | A |
| Indactic 33/41 | C | C | C | C | A |
| MicroSCADA CPI API | N | N | R | R | A |
| Areva | |||||
| Courier KBUS | N | S | S | S | A |
| Courier RS485 | S | S | S | S | A |
| Industrial Protocols | |||||
| CANOpen | N | S | S | N | A |
| BACNet IP | S | S | S | S | A |
| Ethernet IP | R | R | R | R | A |
| DH+ | C | C | C | C | A |
| Modbus RTU | S | S | S | S | A |
| Modbus ASCII | R | R | R | R | A |
| Modbus TCP/IP | S | S | S | S | A |
| Profibus DP | R | R | R | R | A |
| DeviceNet | C | C | C | C | A |
| ControlNet | C | C | C | C | A |
| DF1 | R | R | R | R | A |
| OPC DA | S | S | S | S | A |
| Westinghouse | |||||
| Wisp+ | C | C | C | C | A |
| Wisp++ | C | C | C | C | A |
| Others | |||||
| Altus* | N | S | S | S | A |
| RTK | N | N | N | N | A |
| ODBC | N | S | S | S | A |
| CONITEL | C | C | C | C | A |
| GE SRTP | R | R | R | R | A |
| EXCOM | N | S | S | S | A |
| CMC Master | N | S | S | S | A |
| SPORT | N | S | S | S | A |
| Triguard Peer-To-Peer | N | S | S | S | A |
*Subject to Vendor Approval
The gateways require SYNC7000 Configuration and Diagnostics software. Please request a configuration tool download by e-mail to support@kalkitech.com. These tools are easy to use and offer both local and remote access to the gateway configuration, security settings, log files, communication traces, and system statistics.
| Feature | SYNC1000 | SYNC2000 | SYNC3000 | SYNC OEM |
|---|---|---|---|---|
| Processor | ARM9 32-bit CPU, 180 MHz | ARM9 32-bit CPU, 180 MHz | X Scale IXP-425 533Mhz Processor | ARM9 32-bit CPU, 190 MHz |
| System Memory (RAM) | 32 MB SDRAM, 256 MB Flash | 32 MB SDRAM, 256 MB Flash | 128 MB DRAM, 32 MB Flash | 32 MB SDRAM, , 256 MB Flash |
| Serial Ports | COM1 RS-232/RS-485 having full modem support Baud rates from 200 bps to 38.4 Kbps. | COM1 ? COM4 RS-232/RS-485,COM5 ?COM6 RS232 only &Additional console port with RS232 COM1 having full modem support Baud ratesfrom 200 bps to 38.4 Kbps. | COM1 ? COM16 RS-232/RS-422/RS-485 & additional console port with RS232.All ports have 2kV optical isolation protection.Baud rates from 50 bps to 921.6 Kbps. | 4 TTL interfaces with max. 230 Kbps Full modem control on port 1 Debug port with TTL interface |
| Network support | 1Ethernet 10-Base T/100- Base T with 1.5 kV magnetic isolation protection | 2Ethernet 10-Base T/100- Base T with 1.5 kV magnetic isolation protection Optional ? 2 Ethernet 10-Base Fx/100-BaseFx | 4 Ethernet 10-Base T/100-Base T Optional -- Supports optical wavelength of 1300nm and a distance up to 2 kms | 1Ethernet 10-Base T/100- Base T with 1.5 kV magnetic isolation protection |
| LED | Serial (TxD & RxD) X 1 ,Ready X 1, LAN 10/100 x 1 | Serial (TxD & RxD) X 16 ,Ready X 1, LAN 10/100 X 2 | Serial (TxD & RxD) X 16 , Ready X 1, LAN 10/100 X 2 | Ready X 1, LAN 10/100 x 1 |
| Power input | Nominal 24V DC (19V to 29VDC) Power Consumption: 15W | Nominal 24V DC (19V to29VDC) Power Consumption: 15W | 100 to 240 VAC/VDC auto ranging (47 to 63 Hz for AC input) Power consumption: 20W | 3.3 V Power consumption 2 W |
| Dimensions | 250 mm x 140mm x 90mm [9.8 in x 5.5 in x 5.4 in]???? | 165mm (Height) x 70mm(Width) x 135mm (Depth) [6.49 in x 2.75 in x 5.31 in] | Without ears: 440 x 45 x 198 mm (17.32 x 1.77 x 7.80 in)With ears: 480 x 45 x 198 mm (18.90 x 1.77 x 7.80 in) | |
| Mounting | DIN Rail | DIN Rail | Standard 19 inch rack mount | |
| Weight | ??? g | 650 g | 2600 g | |
| Operating temperature | -20 to 70 | -20 to 70 | -10 to 60 | |
| Storage temperature | -20 to 80 | -20 to 80 | -20 to 80 | -40 to 85 |
| Certifications | IEC 61850-3 with Exceptions | IEC 61850-3 withExceptions | UL/cUL (UL60950-1, CSA C22.2 No. 60950-1-03), T |
Parameterization through Pass-Through (Transparent) Channel
This software module in the SYNC protocol converters enables users to parameterize relays or IEDs with the manufacturer-provided specific configuration software for the relay/IED. The transparent channel (pass-through) routes the frames directly from the input (server) port to the output(client) port and in the reverse direction. The Transparent Peer protocol can be associated to either any of the serial communication port of the SYNC device or a TCP/IP client port. The SYNC models must be loaded with the license and firmware supporting Transparent Peer interface module, and the configuration file containing all the specific information for the communication. The detailed block diagram is
PPP Support
SYNC devices support PPP connections for enabling GSM/PSTN/CDMA connections. The PPP configuration is handled through an additional module in SYNC7000.
Redundancy and High Availability Support
SYNC devices have several options to create redundant configuration solutions. The redundancy mechanism is basically a hot/standby mechanism. The hot device will poll the devices and communicate with the control center as if it was a stand-alone system. However in Hot/Standby mode the hot and standby devices are connected together through a dedicated link that is used to synchronize the two devices together. Integrated link options supported by SYNC devices include Serial, TCP, Serial+TCP and Dual TCP links. Out of these integrated link mechanisms, the latter two provide a redundancy for the integrated link also.
Types of Switchover
-
Externally Triggered Switchover
In this mode, the SYNC by itself will not take a switchover decision on its on. The switchover is triggered by an explicit command received from an external master. To assist in making a decision, the external master can monitor the gateway status via some default status points. Based on this information, the external master can change the gateway state.
-
Self Switchover
Self switchover mechanisms extend the functionality of external trigger switchover, by providing provision for making switchover decision from the gateway itself. The gateway monitors the status of all the connected channels, as well as the status of the other gateway (via an integrated link). In this mode, when the warm gateway detects a failure of the hot gateway, it changes its own state to hot. Also, a communication failure in active channels of the hot gateway will result in the warm gateway switching to hot
-
Redundant Configuration with IP Swapping
In this mode, the hot and warm gateways share two public IP addresses. One IP address is permanently designated as the HOT IP address and the other one as the WARM IP address. The gateways ensure that the currently HOT gateway will always respond to the HOT IP address and the currently standby gateway will respond to the WARM IP. To do this the two gateways switch IP addresses dynamically at each switchover. Because of this, the control center can connect to the hot gateway using a fixed address. This ensures that no special network configuration is needed at the control center; in fact when the control center connects to the known IP-address it has no indication which gateway is hot and which one is warm. The warm gateway can also always be accessed with its public IP address, for maintenance purposes.
-
Redundant Configuration with Alias IP sharing
In this mode, each gateway has its own private IP address. Also, both gateways share a public IP address to which the control center can connect. This IP address is set as an Alias IP address for the interface. This ensures that no special network configuration is needed at the control center. When the control center connects to the alias IP-address, it will always connect to the hot gateway. The hot and warm gateways can be accessed with their private IP addresses also, for maintenance purposes.
-
Redundant Configuration with No IP Switching
In this configuration, each gateway has its own private IP address only. This will require special network configuration on the part of the control center. The control centre needs to detect the hot gateway, and it should ensure that the correct gateway is being connected after a switchover.
-
VPN Support
SYNC series have option of loading GPRS/ EDGE units which allows the users to extend the Ethernet over wireless networks. SYNC devices additionally provide built-in VPN Server/Client functionality that allows users to create a virtual private network across an intrinsically unsecure public network. SYNC3000 and SYNC4000 can typically be configured as VPN Servers (M2MGateways) while SYNC2000 and SYNC1000 devices can be distributed across the field and act as VPN Clients (M2MNodes). The VPN is essentially hosted at the M2Mgateway which will be equipped with a static IP address and the VPN is extended to all M2MNodes that are configured to participate in the VPN. Data between two ends are encrypted before transmission, making it highly secured. The M2M node acting as VPN client connects to the VPN server (M2M Gateway) using its public IP. The client and server exchange and validate their secret keys to establish the connection. After the successful connection establishment, the M2M Gateway assigns an IP address (VPN IP address) to each client gateway. The IP address given to the client Gateways can be pre-configured using the configuration utility. The client can securely communicate with the server using this IP address. A typical network configuration is shown below:
