• This gateway can read BACnet data from your BACnet IP devices and publish it as SNMP data.
• It can also write to the BACnet IP devices.
• This gateway can also do the reverse, read SNMP data and publish it as BACnet IP data.
• It can also write to the SNMP devices.

SNMP Traps:

-The gateway can send and receive traps

In summary, this gateway can act as:

• Master on the BACnet IP network: Hence it is capable of reading data from the various BACnet slave devices and writing data to them if required.
• Slave on the BACnet IP network: You can use the gateway in this mode if you have a BACnet IP master on the network which would be reading data from the gateway.
• Client/Master on the SNMP network: Hence it is capable of reading data from the various SNMP devices and writing data to them if required.
• Server/Slave on the SNMP network: The gateway can be configured to be a server of data values, hence another SNMP client can read data from the gateway and write data into the gateway.

QuickServer Key Features:

• BACnet Testing Laboratory (BTL) Mark
• Ability to interface up to 250 points of common BAS protocols
• Multi-configuration capability; specific configurations selectable via DIP switches or software
• Flat panel mount standard, DIN rail mount option
• DIP switches to select baud rate or node ID on the fly

BACnet/IP driver:

• Driver type: Client or Server
• Data Link layer: BACnet IP, (Annex J)
• Connection type: BACnet/IP Internet Protocol (IP), 10/100BaseT, BBMD supported
• BACnet COV support for fast data communication while reducing traffic over a BACnet network
• Data types supported:
  • AI - Analog Input Object
  • AO - Analog Output Object
  • AV - Analog Value Object
  • BI - Binary Input Object
  • BO - Binary Output Object
  • BV - Binary Value Object
  • MI - Multi-state Input Object
  • MO - Multi-state Output Object
  • MV - Multi-state Value Object

SNMP driver:

• The client can be configured to read values specified by their SNMP Object Identifiers (OID's), which are defined in the MIB file (Management Information Base) of the target device. The FieldServer MIB file sets out the OID's to use. The FieldServer Enterprise ID is 6347. MIB files are generated automatically from the FieldServer configuration files. A selection of standarad MIB-2 OID's are supported to allow interaction with popular Network Management packages.
• When acting as a SNMP Agent (server) the SNMP driver allows SNMP Get and Set commands to access Data Arrays using the Integer type. The SNMP v1 protocol does not make provision for Floats
• Driver type: Client or Server
• Connection type: Ethernet 10Base-T, 100Base-T
• Data types supported:
  • INTEGER
  • OCTET_STREAM
  • TIMER_TICKS
  • STRING

• BACnet is a trademark of ASHRAE

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:

                Node ids of the slave devices

                IP addresses/device address of the slave devices

                Baud rate, parity, stop bits for serial communication

                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