Tested Devices

Veeder Root TLS 350/450 Gateway Converter

A great solution to interconnect Veeder Root TLS 350/450 panels on other protocol Networks like BACnet, Modbus, Lonworks, SNMP, Metasys N2 and others.

 		  

              The Veeder-Root Serial Driver allows the FieldServer to transfer data to and from devices over either RS-232 or RS-485 ports using Veeder-Root protocol. This gateway can only act as a client on the fieldserver device. FieldServer Veeder Root TLS 350/450 panels Gateways - a great solution to enable two way communication between:

1.     Between a Veeder Root TLS 350/450 panels and a different protocol network like BACnet, Modbus, Lonworks, SNMP, Metasys N2.

  • FieldServer Veeder Root TLS 350/450 panels Gateway models have multiple RS-485 ports, Ethernet ports and Lonworks ports (depending on the model). Hence it is possible to interconnect devices on different serial, Ethernet and Lonworks protocols together.

FieldServer Hardware platforms supporting VeederRoot protocol

Device type

RS 485/232 ports

Lonworks Ports

Available Ethernet ports

Base Point count capacity

Extended Point count capacity

QuickServer

2

0

1

250

1000

QuickServer Lonworks

1

1

1

250

1000

Enhanced QuickServer

2

0

1

500

1000

Enhanced QuickServer Lonworks

1

1

1

500

1000


 

How to configure the FieldServer Gateway?

  • We will configure the Gateway for you based on your requirement and support you during commissioning of the Gateway, so you do not have to worry about configuring the FieldServer Gateway.
  • However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals with be provided completely free of cost with your purchase.
  • Configuration of the FieldServer is done using a '.csv' file. This file can be edited using any text editor (example Microsoft excel).
  • In this file we need to enter information for the Client and Server side interfaces of the FieldServer. This includes but is not limited to:

a.                     Node ids of the slave devices

b.                     MSTP addresses/device address of the slave devices

c.                     Baud rate, parity, stop bits for serial communication

d.                     Scan rates

  • And finally we need to create an internal mapping that would map each data value read on the client side to a data value on the server side.
  • For detailed information on configuration please get in touch with us and review the configuration manual on top of this page  .