CALL NOWCALL NOWCALL NOWGATEWAY SELECTORCALL NOWGATEWAY SELECTORLEARN MORELEARN MORE PROCEED TO CHECK-OUT SUBSCRIBE TO OUR RSS FEED SEARCH GATEWAYS NOW SEND MESSAGE NEWSLETTER | SUBSCRIBESUBMIT CALL NOWCALL NOWCALL NOWGATEWAY SELECTORCALL NOWGATEWAY SELECTORLEARN MORELEARN MORE PROCEED TO CHECK-OUT SUBSCRIBE TO OUR RSS FEED SEARCH GATEWAYS NOW SEND MESSAGE NEWSLETTER | SUBSCRIBESUBMIT

EtherNet/IP to BACnet IP Multiport Gateway

A FieldServer protocol Gateway that provides data exchange between BACnet IP and EtherNet/IP. The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP protocol. The Ethernet IP driver allows th...
SKU:
FS-B3510-0436
Max Points
Max Points: 1000, 10000
EtherNet/IP to BACnet IP Multiport Gateway
This product is only available upon request Contact us now for a quote

EtherNet/IP to BACnet IP Multiport Gateway


Multiport Gateway (Serial-Ethernet-LonWorks)

This protocol translator/gateway provides a wealth of features to enable data transfer between different devices and networks utilizing serial, Ethernet or LonWorks ports. The extensive library of FieldServer drivers provides easy interoperability with devices and networks used in building automation, HVAC, fire and process control industries.

The FS-B3510 is one of the FS-X30 Series FieldServers designed to meet the needs of system integrators in designing a complete interoperable system. The FS-B30 Series brings together the powerful FieldServer driver library with state-of-the-art gateway design. This FieldServer includes four serial connections (two RS-232, two RS-485), two Ethernet ports, and a LonWorks port. The multiport design allows for serial-to-serial interfaces or interface from mulitple serial products to an Ethernet or LonWorks network. The two Ethernet ports enable the integrator to connect a PC to download configuration changes without disturbing the system connections and without the additional cost of an external hub.

EtherNet/IP

The Ethernet IP driver allows the FieldServer totransfer data to and from devices over Ethernet usingthe EtherNet/IP protocol. The FieldServer canemulate either a Server or Client.

EtherNet/IP uses CIP (Control and InformationProtocol), the common network, transport andapplication layers also shared by ControlNet andDeviceNet. EtherNet/IP then makes use of standardEthernet and TCP/IP technology to transport CIPcommunications packets. The result is a common,open application layer on top of open and highlypopular Ethernet and TCP/IP protocols.

The Driver is able to read/write using the Data Tablestructure employed by all Logix Series PLC’s.

PCCC support is also provided for legacy devicesthat do not fully support CIP encapsulation. EIPPCCC Encapsulation was tested at the FST factoryusing a PLC5 I785 ENET card. The following datatypes were tested:

  • N
  • F
  • S

The Driver also supports PCCC communication onSLC and MicroLogix (Tested on MicroLogix 1400Device)

Fragmented Services (0x52) is supported fordata_table read and write operations. 

BACnet IP

The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP protocol. The FieldServer can emulate either a Server or Client.

All information in a BACnet system is represented in terms of objects. The Object_Identifier is a 32-bit code that identifies the type of Object (also identified by the Object_Type Property) and its "Instance" number, which together uniquely identify the Object within its BACnet device. Theoretically, a BACnet device could have over four million Objects of a particular type. The Object_Name is a text string, which has a unique capability.

BACnet devices may broadcast queries for devices that contain Objects with a specific Object_Name. This can greatly simplify project setup.

BACnet requires one Device Object to be present in every BACnet device. The Device Object makes information about the device and its capabilities available to other devices on the networks. Before one BACnet device starts control-related communications with another, it needs to obtain some of the information presented by the other device's Device Object. Unlike other Objects, the Device Object's Instance number must be unique across the entire BACnet internetwork because it is used to uniquely identify the BACnet devices. It may be used to conveniently identify the BACnet device from other devices during installation.

Standard object types are used to hold real time data and other information. Each Object Type is referenced by a number, for example 0 represents an Analog Input. See Appendix D.1 for abbreviation list.

Each Object consists of a number of prescribed properties, the main property being the Present_Value. Objects are monitored and controlled through their properties.

The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer.

Block Diagrams

LP Rockwell

Useful Links

Logos

Logo bacnet1
Logo BTL Bacnet Test Lab
Logo Rockwel

Gateway Selector

Select your combination of protocols.
Protocol 1
Protocol 2

Contact Us

Contact us via phone (+1 866-383-1657) or leave a detailed message below for sales, support, or any other needs

*Required Field
I'd like to receive the newsletter. *Check email for confirmation.
*Required Field
Preferred Time To Be Contacted (PST)
8:00am - 12:00pm 12:00pm - 5:00pm