This Gateway Supports:
Modbus RTU on RS485 & RS232 – Telnet Gateway
Modbus TCP/IP – Telnet Gateway
BACnet MSTP on RS485 – Telnet Gateway
BACnet IP – Telnet Gateway
SNMP (v1 & v2c) – Telnet Gateway
Please click on the below link to download the Datasheet:
Modbus / BACnet / SNMP to Telnet Gateway
PG-100-101-102-103-104-110 is an embedded remote monitoring and control solution for Telnet devices. This unit can connect with Telnet based field slave devices (on RS485 or Ethernet) and provide the data on Modbus RTU or BACnet MSTP devices.
PG-100-101-102-103-104-110 will read the data from Telnet devices and publish this data on BACnet IP or Modbus TCP/IP devices over Ethernet.
Also, PG-100-101-102-103-104-110 will acquire the data from Telnet and serve on SNMP (v1 & v2c) devices.
For more information please contact us at email@example.com
On a metro station there are plenty of lights connected to central Lighting Controller which works with Telnet On RS-485 port to monitor and control those lights through Scada or BMS which works either on Modbus / BACnet Protocols.
Lighting Controllers provide data on Telnet protocol. The site has a BMS which works on BACnet / Modbus protocols that needs the data from Light Controller that works on Telnet Protocol.
Since the Lighting Controller provide data output on Telnet & the BMS understands BACnet/Modbus protocol, a direct exchange is not possible.
ProtoConvert ’s Telnet to Modbus / BACnet Converter will be an excellent solution for this requirement.
For an instance,
If you want to “Turn off/on the lights”, converter will get the command from BMS (Which works on Modbus / BACnet Protocol) and convert into Telnet and serve or post that command to the lighting controller which only understands Telnet. Thereby, the controller will take an action on that command.
If you want to check the status of the lights; BMS will raise a query from Modbus/ BACnet and post it on Converter and Converter will post that command on Lighting Controller and Controller will response with Status of the lights. Thereby, the controller will post the action as “on” or “off” to the BMS via Converter.
In a theatre there is range of Amplifiers that works with Telnet on Ethernet port to monitor and control the sound system through SCADA or BMS that works on SNMP Protocol.
Amplifiers provide data output on Telnet Protocol; whereas BMS understand SNMP Protocol. Since Amplifiers and BMS do not work on the same protocol, a direct exchange of data is not possible.
ProtoConvert ‘S Telnet to SNMP Converter will be an excellent solution for this requirement.
For an instance, “If you want to check the status of an Amplifier”; converter will get the command from BMS (which works on SNMP) and convert it into Telnet and post that command to the Amplifier which only understands Telnet. Thereby, Amplifier will response on that query and post the action to converter and converter will convert that data from Telnet to back into SNMP (v1 or v2c) and post to the BMS. If status of Amplifier changes than converter will get that update and post on BMS (SNMP).