O3 Firmware 2.7 Release Notes

Welcome

Delta Controls is pleased to release O3 firmware 2.7 for the O3 Sense and O3 Edge products. These release notes communicate important technical information about release 2.7.1.

New Features in 2.7

ORS/SUA Object Support

For firmware 2.7 we have added support for the ORS (Object Restriction Setting) and SUA (System User Access) objects.

The ORS is a Delta Controls proprietary object that allows configuring controller based security restrictions on the O3 Edge and Sense database objects using enteliWEB.

Read/Write/Create/Delete/Visible restrictions on objects or object properties can be applied, preventing network changes from enteliWEB or any 3rd party front end. User and password setting to lock and unlock the ORS are configured in a referenced SUA object. The ORS can be used for protecting program intellectual property or prevent others from changing configuration values or modifying settings over the BACnet network, regardless of the front end.

ORS configuration, locking and unlocking of an O3 database requires Delta Controls enteliWEB firmware software 4.27 or higher. For more information, refer to the enteliWEB Object Restriction Settings (ORS) Object help page.

System Requirements

Proviso

Proviso (formerly the O3 Setup App) version 2.9 or newer is required to use all the features of O3 firmware 2.7. 

Seymour Connect

Seymour Connect 1.0 or newer is required for O3 firmware 2.7.

enteliWEB

enteliWEB 4.27 or newer is required for O3 firmware 2.7 to be able to use the ORS/SUA objects.

Installing an O3

To install the O3, follow the Installation Instructions. You can also watch the O3 Installation Tutorial. 

Once installed, devices should be secured, following the O3 Edge Hardening Guide. 

Upgrading an O3

You can upgrade to firmware 2.7 from firmware 1.6.16 or newer.

In firmware 2.6 and newer, FIL200 has been adopted as a default object used to store the Seymour Connect configuration. On upgrade, if FIL200 does not exist, it will be created. If FIL200 already exists on upgrade, the operator will need to delete it post-upgrade and reset the O3. FL200 will be re-created on reset. If after loading an older database the FIL200 object is not created, manually create FIL200 'Seymour Configuration' prior to provisioning.

If you have a build older than 1.6.16 in the device, you must follow a specific upgrade path. Refer to the O3 1.6 Release Notes for upgrade instructions. 

Do not unplug or reboot an O3 during a firmware upgrade. Once an upgrade begins, allow at least 5 minutes for it to complete without interruption. 

To perform the upgrade, follow the Firmware Upgrade Guide.

MQTT Write Priority Level

Firmware 2.2 changed the priority array level used for writes to BACnet objects through MQTT. Previously, MQTT writes would occur at priority 16 (the lowest priority). In firmware 2.2 and beyond, MQTT writes occur at priority 13.

This allows MQTT to have a higher write level than controller algorithms at priority 15, such as EnOcean, allowing MQTT to be used to configure these objects and override them. Existing applications, such as those created in Node-RED, may need to be updated.

Downgrading an O3

If you need to revert to a previous release (e.g. downgrade from release 2.1 to 2.0), you should first enable BACnet/Ethernet. In some cases, the O3 may encounter issues being assigned an IP address after the downgrade. Having BACnet/Ethernet enabled will ensure you can continue to communicate with the O3 should this issue occur. 

Starting in version 2.2, downgrading an O3 will clear its database.  If custom FIL loaded (custom sounds, EnOcean, Node-Red DLM) were used, the related internal files are not all deleted. It is recommended to perform an additional clear database to remove these files.

If an ORS is configured and locked in 2.7, downgraded to 2.6 then later upgraded back to 2.7 you will be unable to unlock the database without knowing the old password. Alternately, factory resetting will clear the lock.

General

AV, BV and MV variable object instances 1-999 are reserved for internal use and must not be created or used for other purposes.

See the following documentation for database objects used in the O3 and the complete list of reserved instances.

• BACnet Objects in the O3
• Reserved Object Instance Ranges

Resolved Issues

The following notable issues are fixed in version 2.7

• General

  • Improved accuracy of clock when NTP is disabled

  • Rarely, loading in database, reboot or factory reset could roll back firmware to previous version

  • Startup optimizations to reduce O3 bootup time

  • AV2xx min/mean/max metrics were not reporting correctly in 2.6 release

  • AV2xxx metrics may not calculate hourly data properly after there is a time change. ie offset 1 hr after DST

  • Random remote references may be added to the ATZ/BTZ/MT objects after a database load

  • Rarely, after a factory reset, the Eth1 port may be disabled. A power cycle or soft reset resolves this issue.

  • Clear database/reboot deletes the last firmware upgrade information in the CVS43 object (SHFW-2345)

  • Rare issue where metrics AVs stopped updating (SHFW-3504)

• Proviso

  • MV50, MV51 (Seymour Provisioning/Configuration Statuses) do not update to BLE Proviso App information

  • Proviso - Improve refresh of diagnostic items when connected BLE.