To set up the O3 through BACnet, using enteliWEB, you must have enteliWEB 4.20 or newer. You can also use enteliCLOUD to set up the O3 through BACnet.
Configuring the Network
The O3 supports both BACnet over Ethernet (BACnet/Ethernet) and BACnet over UDP/IP (BACnet/IP). By default, the BACnet protocol type is set to BACnet/Ethernet. To change the protocol type, connect to the device over BACnet/Ethernet and configure the BACnet/IP settings.
If you are using both Ethernet ports, note the following: you must unplug both cables or reboot your O3 device to get a new IP address from a DHCP server.
To configure BACnet/IP settings in enteliWEB:
- Open object NP6 (Ethernet1 - IP1).
- Clear the Out Of Service checkbox.
- Leave the UDP Port number as the default value (47808) unless you want to create independent groups of BACnet devices on the same IP subnet.
- Set IP Mode to Foreign if you want the O3 to join a BACnet/IP network with a different IP subnet address. Otherwise, leave it as Normal.
- If IP Mode is set to Foreign, in the BBMD Address field, enter the IP address of the BACnet Broadcast Management Device (BBMD) that you want to register with, then enter the Subscription Lifetime (Time-To-Live) value. This is the interval at which the O3 must re-register with the BBMD to keep participating on the BACnet/IP network.
- Click Save. The message "Changes Pending" appears at the top of the page.
- Return to the object list page and click Device Actions > Activate Network Change.
- Open object NP5 (Ethernet1 - BACnet) and select the Out of Service checkbox to disable BACnet/Ethernet.
The O3 does not route and cannot function as a BBMD. As such, it does not require a BACnet network number to be set for any of its ports (Ethernet, UDP/IP, or Secure Connect). See FAQ for a detailed explanation.
Calibrating the Occupant Temperature
The O3 models the room temperature at occupant height using its internal temperature sensors and IR temperature sensor. Because each room is different (due to air flow, heating sources, height of the ceiling, etc.), the O3's initial prediction is likely to be slightly off. This difference can be calibrated out by measuring the current room temperature and sending that value to the O3. The offset is calculated automatically.
For best results, observe the following guidelines:
- Try to get the room temperature as close to your setpoint as reasonably possible. The calibration should hold within ± 5°C, but the closer you are to the control point the better it will be.
- Make sure the temperature in the space has been reasonably stable for at least 15 minutes. That is, don’t go from 10°C to 20°C and then calibrate the reading as soon as you reach 20°C. Hold at approximately 20°C for 15 minutes and then calibrate.
- Try to calibrate within the O3’s IR envelope, but also make sure it isn’t directly next to a heating or cooling source.
- Calibrate at approximately 1 m (3 ft) off the floor.
Normally, the occupant temperature is calibrated using the O3 Setup mobile app. However, you can also update the calibration value over BACnet.
To update the calibration value:
- Open object AI3 (Occupant Temperature).
- Set the object to manual mode.
- Enter the new calibration value in the Calibration field and save your changes.
If AI3 is not set to manual mode, the entered value will be discarded and the previous calibration value will be shown after a refresh.
Security Settings
Changing the BLE PIN
The BLE PIN is a 6-digit code used to authenticate Bluetooth-enabled mobile devices. To secure writes to the O3 via Bluetooth, you must change the BLE PIN after the initial configuration with the O3 Setup app is complete.
The BLE PIN must consist of digits between 0 and 9 and must be exactly 6 digits in length. The new PIN cannot be 000000.
To change the PIN:
- Create object CSV45 with the name "BLE PIN."
- Command the object to manual mode and enter the new PIN as the object value.
Note: Immediately after commanding the object to a manual value, the value is stored in non-volatile memory, the object is reset and the present value is cleared.
3. Restart the O3. If you're using enteliWEB, on the object list page, click Device Actions > Reset.
The CSV45 object value should clear after the new PIN is entered. If it doesn't clear, the PIN was not accepted. Check the PIN length and try again.
Disabling Bluetooth
Another way to secure writes to the O3 via Bluetooth is to disable Bluetooth LE communication.
To disable Bluetooth:
- Command object BV31 (Enable BLE) to manual mode and set the object value to Off.
- Restart the O3. If you're using enteliWEB, on the object list page, click Device Actions > Reset.
Enabling the Internal MQTT Broker
The O3 has an internal MQTT broker that allows you to write directly to the device's configuration file. The broker is disabled by default.
To enable the internal MQTT broker:
- Command object BV48 (Internal MQTT Broker Enable) to manual mode and set the object value to On, then click Save.
Changing the Internal MQTT Broker Password
The default username/password to access the internal MQTT broker is user
/admin
. To secure writes to the broker, you must change this password.
The MQTT broker password is case-sensitive and must be 5 to 31 characters in length. Special characters are allowed.
To change the password:
- Create object CSV46 with the name "MQTT Password".
- Command the object to manual mode and enter the new password as the object value.
Note: Immediately after commanding the object to a manual value, the value is stored in non-volatile memory, the object is reset and the present value is cleared. - Restart the O3. If you're using enteliWEB, on the object list page, click Device Actions > Reset.
The CSV46 object value should clear after the new password is entered. If it doesn't clear, the password was not accepted. Check the password length and try again.
Other Tasks
If NTP is enabled manually, changes (add, remove, modify) to server addresses will not take effect until NTP is disabled and then enabled again, or after a device reset.
Disabling NTP
Network Time Protocol (NTP) service is enabled by default, which allows the O3 to synchronize with Coordinated Universal Time (UTC) time when connected to the internet.
Time zone offsets are not currently supported by the firmware. If you are using enteliWEB, you cannot enable the time zone setting in the DEV object.
If you want the O3 to get its time from another BACnet device or from enteliWEB, you must disable the NTP service.
To disable NTP:
- For firmware 2.3 and older: Command object BV42 (NTP Enable) to manual mode and set the object value to Off.
- For firmware 2.4 and newer: NTP can be enabled or disabled using the Enable NTP Time Sync checkbox in the DEV object.
Frequently Asked Questions
Refer to the FAQ section of Provisioning using Proviso for common Provisioning questions.
Comments
0 comments
Please sign in to leave a comment.