Needs
Investments in BMS systems are long term investments. Control systems often run for multiple decades before they are replaced. On the other hand, facilities are often extended, or adapted to a different use across their lifetime, requiring extension or adaptation of the installed control systems, possibly using more modern solutions such as BACnet based controllers. Finally, the customer may desire additional functionality which was not available at the time the control system was installed, like e.g. web access to the system.
Such features should be addable without requiring to fully replace the existing control solution.
The more flexibly a modern BMS solution supports legacy integration scenarios, the better the investment of the client is prote
Scenario |
Solution |
A supervisor should be added to stand alone CBUS system | Connect the CBUS system to the CentraLine ARENA BMS supervisor. Installation of the CBUS driver makes sure that the supervisor functions such as trending, alarming, graphic frontends, web access, etc. work with the installed CBUS controllers. |
A CBUS system should be web enabled | Depending on the size, connect the CBUS system either to the CentraLine ARENA BMS supervisor (larger systems) or to the CentraLine HAWK (small systems up to 32 controllers). The integrated web server in those devices in combination with the CBUS driver enables web access to all essential functions such as schedule and point access, trending, alarming, graphics, Parameters, etc. |
Facility is extended with a new area in which a BACnet control system should be installed. The CBUS installations in the existing areas should be kept, but both systems should be managed by a single supervisor in a consistent view | Connect both, the BACnet and the CBUS systems to the CentraLine AREAN BMS supervisor. Installation of the corresponding drivers in the supervisor makes sure that the protocols are handled consistently. |
Part of the facility is refurbished with a modern BACnet control system. This system needs to get information from the CBUS system and vice versa. A typical example is exchanging demand information (heat / cool demand), setpoints, status information etc. | Connect both, the BACnet and the CBUS systems to either the CentraLine ARENA BMS supervisor or a HAWK. Installation of the corresponding drivers makes sure that data point information can be exchanged between the BACnet and the CBUS systems. |
Products
CLAXDRCBUS
C-Bus Driver Unlimited Points
Supporting CLIF / BNA Version 1, 2 and 3 as C-Bus interface C-Bus Driver is fully supporting the CentraLine C-Bus History and grants full access to: Alarming (Critical, Non Critical and System Alarms), Schedules, Datapoints with all properties, Parameters with import of CARE reference.txt files
CLAXDRCBUS500
C-Bus Driver limited to 500 Points
Supporting CLIF / BNA Version 1, 2 and 3 as C-Bus interface C-Bus Driver is fully supporting the CentraLine C-Bus History and grants full access to: Alarming (Critical, Non Critical and System Alarms), Schedules, Datapoints with all properties, Parameters with import of CARE reference.txt files
Insights
The CBUS migration scenario covers “physical CBUS installations”, running on an RS
Following C-Bus Controllers will be supported by the C-Bus Driver.
XL50 / PANTHER, XL100, XL500, XL800 / LION, Elink and MVC-80