CALL NOW CALL NOW CALL NOW GATEWAY SELECTOR CALL NOW GATEWAY SELECTOR LEARN MORE LEARN MORE PROCEED TO CHECK-OUT SUBSCRIBE TO OUR RSS FEED SEARCH GATEWAYS NOW SEND MESSAGE SUBMIT

FieldServer BACnet Router (Single-Port)

The FieldServer Classic BACnet Router offers a complete BACnet Internetworking solution for BACnet/IP, BACnet Ethernet, and BACnet MS/TP networks.
The BACnet Ethernet driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet Ethernet protocol.
The BACnet Master-Slave/Token-Passing (MSTP) driver implements a data link protocol that uses the services of the RS-485 physical layer.
The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP protocol.
SKU:
FS-ROUTER-BAC1
27-05-14-52_BACnet Router website.png - /2017/nov/27-05-14-52_BACnet Router website.png

Classic BACnet Router

The FieldServer BACnet Router offers a complete BACnet Internetworking solution for BACnet/IP, BACnet Ethernet, and BACnet MS/TP networks.

This is the first standalone BACnet Router that has been certified by BTL to ensure the highest standard for BACnet integration.

The FieldServer BACnet Router is available in two models:

  • The FS-ROUTER-BAC has two RS-485 ports enabling up to 64 BACnet MS/TP devices to be connected to it without the use of additional line drivers. Relative to a single port router, the dual port router halves device response time by distributing devices over the two RS-485 ports.
  • The FS-ROUTER-BAC1 offers a single RS-485 port and is a cost-effective option for configurations of 32 or fewer BACnet MS/TP devices without the need for additional line drivers.

The FieldServer BACnet Router has an easy one page configuration, greatly simplifying the installation process. DeviceFind™, a unique discovery feature, allows the integrator to push a button and discover all the BACnet devices connected to the router, greatly simplifying the commissioning process.

BACnet MSTP

The BACnet Master-Slave/Token-Passing (MS/TP) driver implements a data link protocol that uses the services of the RS-485 physical layer. See the FieldServer BACnet PIC statement for the level of conformance that this driver implements.

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.

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 Analog Input Object is representative of the Objects involved directly with control elements and many of its Properties reflect this.

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

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.

BACnet Ethernet

The BACnet®1suite of drivers is designed to workwith the FieldServer products. One or more driversusing different Data Link Layer options could beconfigured to act as a gateway between BACnetsystems and RTU, SCADA's and PLC’s using a widevariety of protocols.

This is relevant to the following FieldServerDrivers:

  • FS-8700-16 BACnet/PTP
  • FS-8700-73 BACnet/MSTP
  • FS-8700-07 BACnet/ARCnet
  • FS-8704-06 BACnet/IP
  • FS-8704-02 BACnet/Ethernet
BACnet Vendor Name: Sierra Monitor CorporationBACnet Vendor ID: 37 

I'd like to inquire about the FieldServer BACnet Router (Single-Port) FS-ROUTER-BAC1. Please provide me with a quote for this product.

Specifications

Classic BACnet Router

Environment

  • Operating temperature: -40 to 75oC (-40 to 167o
  • Relative humidity: 5-90% RH non-condensing

Power Requirements

  • 9-30VDC or 12-24VAC
  • Current draw @ 12V: 240 mA

Physical Dimensions (HxWxD)

  • 4.5 x 2.9 x 1.6 in. (11.5 x 7.4 x 4.1 cm)
  • 0.4 lbs (0.2 Kg)

Other

  • Configuration/Diagnostic utilities
  • Table, Wall or DIN rail mount

Communication

  • Baud: 4800, 9600, 19200, 38400, 57600, 115200
  • Start Bit: 7, 8
  • Stop Bit: 1, 2
  • Parity: Even, Odd, None

Approvals

  • RoHS Compliant

Block Diagrams

Additional Information

BACnet MSTP to IP

A BACnet Router is used to connect MSTP trunks to BACNetIP systems. The router itself is a device on the IP and on the MSTP side. The router can also act as BBMD device allowing messages to cross from one subnet to another.

BACnet BBMD

BACnet messages cannot cross from one subnet to another except under special circumstances.

Most BACnet sequenc es of messages begin with a broadcast called 'who is'. All devices respond with 'I am'. That is how they are discovered. It is also how many system confirm the device is still there.

Broadcasts can't cross routers (they are blocked) and therefore devices on the other side of a router cannot e discovered.


BBMD is the name of the BACNet technology that resolves these issues. The BACNet ROuter sold by CAS provides BBMD services as do all FieldServer BACNet products when configured as clients.

Logos

imports/logos/Logo bacnet1.jpg
imports/logos/Logo BTL Bacnet Test Lab.jpg
imports/logos/Logo bacnet1.jpg
imports/logos/Logo BTL Bacnet Test Lab.jpg
imports/logos/Logo bacnet1.jpg
imports/logos/Logo BTL Bacnet Test Lab.jpg

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