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

KNX to BACnet EZ Gateway (500 point)

The EZ Gateway KNX to BACnet (FS-EZX-KNX-BAC) is an easy-to-use, high performance building and industrial automation protocol gateway.
The BACnet Master-Slave/Token-Passing (MSTP) driver implements a data link protocol that uses the services of the RS-485 physical layer.
The KNX driver allows the FieldServer to transfer data to and from devices using KNX protocol.
The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP protocol.
SKU:
FS-EZ1-KNX-BAC
Max Points: 500, 1000
22-14-37-31_EZ_Gateway_knx_bac.png - /2017/jun/22-14-37-31_EZ_Gateway_knx_bac.png

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.

KNX

The KNX driver allows the FieldServer to transfer data to and from devices using KNX protocol. The Fieldbus connection is included with the FieldServer. The FieldServer can emulate a Passive Client.

The KNX driver enables data access from KNX networks to other FieldServer protocols. Most KNX data point types are supported, allowing communication to almost any kind of KNX device in the installation, such as temperature sensors, shutters, light switches, actuators, alarms etc. This allows BMS systems to access a KNX network using direct read and write of KNX configured groups. This setup does not require the use of ETS4 to configure the QuickServer KNX gateway.

The KNX protocol is a connectionless protocol and therefore supports multiple clients and multiple servers.

The QuickServer is intended to act as a Passive Client on the KNX bus and make information available to other protocols. 

EZ Gateway (KNX to BACnet)

The EZ Gateway KNX to BACnet (FS-EZX-KNX-BAC) is an easy-to-use, high-performance building and industrial automation protocol gateway for integrators to interface KNX certified products to BACnet management systems in commercial buildings, campuses, and industrial facilities. KNX-certified products encompass a wide range of applications such as lighting control, heating, ventilation and air conditioning control, shutter/blind and shading control, alarm monitoring, energy, gas, and water metering, and audio and video distribution. The EZ Gateway KNX to BACnet integrates such KNX-based devices and systems to BACnet-based management systems over BACnet MS/TP or BACnet/IP protocols.

The EZ Gateway KNX to BACnet combines field-hardened KNX and BACnet protocol drivers with an easy to use configuration interface. The EZ Gateway’s KNX interface is compatible with all KNX-certified products, while the EZ Gateway’s BACnet interface has been certified by BACnet Test Laboratory (BTL), at Version 12. The intuitive web-based interface allows configurations to be built in the field or in the office, thereby simplifying the commissioning and integration process.

Sierra Monitor’s unique FieldServer DeviceProxy™ feature allows each KNX device to be presented as a corresponding virtual BACnet device within the EZ Gateway, thereby providing granular visibility and control over each KNX device from within a BACnet management framework. For example, offline/online status is visible at the individual KNX device.

With the EZ Gateway KNX to BACnet, the integrator or contractor does not need to be a protocol expert and can minimize configuration and commissioning time, while also reducing ongoing operating and maintenance costs.  

Specifications

EZ Gateway (KNX to BACnet)

Environment
  • Operating Temperature: -40 to 75oC (-40 to 167oF)
  • Relative Humidity: 5-90% RH non-condensing
Power Requirements

9-30V DC or 12-24V AC
Current draw: @ 12V

  • FS-QS-1010, FS-QS-12X0: 240 mA
Physical Dimensions
  • Dimensions (WxDxH): 4.5x2.9x1.6 in. (11.5x7.4x4.1cm
  • Weight: 0.4 lbs (0.2 Kg)
  • Input voltage: 24 V DC nominal: 10-30V DC
Other

Configuration/Diagnostic utilities

  • Capacity: 500 points FS-EZ1-KNX-BAC. (1,000 points FS-EZ2-KNX-BAC)
  • Table, Wall or DIN rail mount
Communication
  • Baud: 4800, 9600, 19200, 38400, 57600, 115200
  • Start Bit: 8
  • Stop Bit: 1
  • Parity: Odd
  • Ethernet: 10/100 BaseT MDIX
Approvals
  • TUV Approved: to UL 916, EN 60950-1, EN 50491-3 and CSA C22.2 standards
  • BTL Mark:
  • RoHS Compliant
  • GOST-R Certified
  • CE and FCC


Block Diagrams

imports/blockDiagrams/LP KNX.jpg

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