BACnet Data Client/Logger (discontinued)

Chipkin™ BACnet® IP/MSTP Data Client/Logger is a device that connects to BACnet® IP/MSTP devices, and reads and stores the data.
Every QuickServer includes browser-based tools for quick set-up and to perform diagnostics including determination of status, network settings, node information, map descriptors and more.
The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP protocol.
The BACnet Master-Slave/Token-Passing (MSTP) driver implements a data link protocol that uses the services of the RS-485 physical layer.
SKU:
CAS-DC-2010-002
QS-2xx0 QuickServer - QS-2xx0 - Single Ethernet Gateway Picture

Chipkin™ BACnet® IP and MSTP Data Client (aka Data Logger, Data Recorder) is a device that connects to BACnet® IP devices, and reads and stores the data. It also connects to BACnet MSTP Devices as a Slave and Master and reads and stores the data. The data client operates by reading data from the configured registers and stores the values in an internal database. These values can then be logged to an archive file or can be accessed via the data clients REST API as XML, JSON, or CSV data using HTTP Get requests. Log files can be accessed by a Web Browser or FTP client.

The device requires minimal configuration.

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 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.

Quickserver Gateway (Serial-Ethernet)

The QuickServer is a high performance, fully configurable, cost effective Building and Industrial Automation gateway for integrators to easily interface devices to networks in commercial buildings and industrial plants.

System integrators world-wide have benefitted from the value of the powerful line of interoperability gateways offered by FieldServer. Now, QuickServer adds to that value by running the same robust FieldServer protocol conversion software on a highly cost effective platform backed by the experience, engineering expertise and proven technical support that integrators have come to expect from FieldServer.

QuickServer (Serial-Ethernet) is available in two series:

The QuickServer FS-QS-2X10 series is available at four different point capacities. Each QuickServer is preloaded with two drivers (serial and/or Ethernet) from a customer’s choice of 140 different drivers, E.G. Modbus, BACnet, SNMP, EtherNet/IP and many more.

The FS-QS-2010 with 2 RS485 and 1 ethernet port can support up to 250 points. The FS-QS-2210 can support up to 500 points. The FS-QS-2310 can support up to 3,000 points. The FS-QS-2410 can support up to 5,000 points.

Equivalently the FS-QS-2020 with 1 RS485, 1 RS232 and 1 ethernet port can support up to 250 points. The FS-QS-2220 can support up to 500 points. The FS-QS-2320 can support up to 3,000 points. The FS-QS-2420 can support up to 5,000 points.

Every QuickServer includes browser-based tools to make it easy to set-up QuickServer and perform diagnostics including determination of status, network settings, node information, map descriptors and more. The USB flash drive also includes the Discovery utility to determine what FieldServers are on a network.

BTL Mark is registered to the MSA BACnet Driver for MSA QuickServer line of products

I'd like to inquire about the BACnet Data Client/Logger (discontinued) CAS-DC-2010-002. Please provide me with a quote for this product.

Specifications

Quickserver Gateway (Serial-Ethernet)
QuickServer Specs: FS-QS-2XX0

Environment
  • Operating Temperature: -20 to 70°C (-4 to 158oF)
  • Relative Humidity: 10-95% RH non-condensing
Power Requirements
  • Intput: 24VAC 0.125A, 12-24VDC 0.25A @12 VDC
  • Max Power: 3W


Physical Dimensions
  • Dimensions (WxDxH): 4 x 1.1 x 2.7 in (10.16 x 2.8 x 6.8cm)
  • Weight: 0.4 lbs (0.2 Kg)
Other

Web configuration
On-board diagnostics
DIN rail mount included

  • Capacity: 250 points FS-QS-20XX, 500 points FS-QS-22XX, 3000 points FS-QS-23XX, 5000 points FS-QS-24XX
Communication

FS-QS-2XX0

  • Baud: 9600, 19200, 34800, 57600, 76800
  • Serial (Galvanic Isolation) Ports: 1 x RS485, 1 x RS232/RS485
  • Ethernet Port: 10/100baseT, MDIX, DHCP

Approvals
  • UL 60950
  • IC Canada
  • RoHS Compliant
  • WEEE compliant
  • RoHS compliant
  • CE and FCC class B and C part 15

Block Diagrams

CAS2500-04 BACnet IP Data CLient Block DiagramBACnet Combined Block Diagram

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 BTL Bacnet Test Lab
Logo bacnet1

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
*Required Field
I'd like to receive the newsletter. *Check email for confirmation.
*Required Field
8:00am - 12:00pm 12:00pm - 5:00pm