This section helps to identify BACnet requirements and to set up the BACnet with respective 75F® CCU. BACnet requires Ethernet connection, USB to Ethernet adapter, CM board, and CCU. BACnet uses Ethernet connection for BACnet protocol communication.
This section is useful for Commissioning Engineers, Installer, and In-Site personnel who have access to CCU setup.
- Ethernet USB adapter must be used to enable the hardware for Ethernet.
- Renatus must use Ethernet for BACnet-IP communication with the existing BMS.
- Wi-Fi must be only used to sync the local haystack data to cloud.
- Ethernet and Wi-Fi must function independently.
Below architecture is followed by BACnet along with 75F systems. CCU is used for enabling the BACnet protocol and acts as BACnet Server. All the objects as per exposed object list will be exposed to BACnet client. In case of more than one CCU, for each CCU BACnet shall be enabled.
- 75F® CCU
- 75F® CM Board
- USB to Ethernet Converter
Supported System Profiles:
- Renatus should expose all the relay points as BACnet objects for all the system profiles.
- For profiles such as Fully Modulating, Hybrid AHU or Staged RTU with VFD Fan, analog outputs are also exposed as BACnet objects.
Supported Terminal Profiles:
- Smart Node:
- VAV, DAB, TI and SSE profiles are supported for BACnet.
- DAB terminals profiles should expose their current temperature (CT), cooling desired temperature (CDT), heating desired temperature (HDT) and damper position as BACnet exposed objects.
- VAV terminals profiles should expose their current temperature (CT), cooling desired temperature (CDT), heating desired temperature (HDT), damper position, Supply Air temp, and Reheat Coil as BACnet exposed objects.
- Temperature Influencing profiles should expose Current Temperature (CT), cooling desired temperature (CDT), and heating desired temperature (HDT)
- SSE profiles should expose Current Temperature (CT), cooling desired temperature (CDT), and heating desired temperature (HDT)
- Smart Stat:
- All smart stat profiles are supported for BACnet i.e. CPU, HPU, 2pFCU and 4pFCU
- CT, CDT, HDT, and all the sensor points are supported for BACnet and will be exposed as BACnet objects.
- Relay points of smart stat should not be exposed as BACnet objects.
- Only building schedule will be supported and all zones should follow building schedule.
- 75F® building schedule should be exposed as BACnet schedule object.
- BACnet client can create single schedule event for a day. Multiple schedule events in a day or overnight schedules are not supported for BACnet.
- BACnet client can modify/extend the existing schedule event.
- BACnet client can delete the existing schedule event.
- Zone schedules are not supported for BACnet.
- 75F® vacations should be exposed as Calendar object.
- BACnet client can create single day vacation (Date).
- BACnet client can create multiple days’ vacation (Date Range).
- BACnet client can modify/extend the existing vacation.
- BACnet client can delete the existing vacation.
- Zone Vacations are not supported for BACnet.
- Current Temperature, CDT, HDT alarms should be supported.
- CCU Battery level alarms should be supported.
- Time Synchronization is supported, in case if there is time difference for BMS client and Renatus.
Trend log objects
- Trend Log Objects should be created for all the BACnet exposed objects of smart node and smart stat profiles (CT, CDT, HDT, Damper Pos, All sensor related points).
- Connect one end of the Ethernet cable to USB-to-Ethernet adapter as shown below.
Note: BACnet over Ethernet allowed building automation systems to transfer data via ethernet across a bus architecture. This worked well initially but with the advent of the internet and the desire to have a single control system across a network of buildings, the need for networks larger than 254 nodes was needed.
2. Connect the USB part of USB-to-Ethernet adapter to CM board USB port as shown below:
3. Connect the other end of Ethernet cable to Wi-Fi router (or) switch as shown below:
4. Confirm the Ethernet connection is active by checking the Ethernet icon on the top-right-side
of notification bar.
- Go to CCU Settings > Installer Operations screen for configuring BACnet.
- Click the Use BACnet toggle to see the. By default, it will be Auto Config. Based on the network type connected, prefix of the IP address will be updated.
For example: If Ethernet is connected, then it will display Ethernet-IP address as shown below:
- Select Manual Config option to update the static IP address.
- Click INITIALISE button to initialize the BACnet objects. On initializing, a message appears as shown.
5. Once BACnet is Initialized, it will start exposing the BACnet objects and any other interoperable
system when configured will be able to read all the exposed objects.