O3 Firmware 4.16 Release Notes

Welcome

Delta Controls is pleased to release O3 firmware V4.16 for the O3 Sense and O3 Edge products. These release notes communicate important technical information about release 4.16.0.2100. This build replaces previous release build 4.16.0.2098 and should be used to upgrade from existing O3 2.x firmware to V4.16. Existing 4.16.0.2098 do not need to be updated to this build.

V4.16 firmware is the first O3 release based on the same V4 platform that the Red5 product line is using. Going forward, the O3 will now sync with Red5 V4 releases.

New Features in 4.16

V4.x Platform Support

4.16 is the first O3 release under the V4.x umbrella, providing regular scheduled updates and feature improvements that follow the same schedule as Red5 and V4 eBUS firmware releases.

Embedded Web Support

O3 V4.16 firmware supports an embedded web page that can be used to

• Set time, date parameters
• Set Network parameters, connect to a BACnet/SC hub
• Save/Load O3 databases
  • Note, the embedded webserver can only load database from the same version. Use Proviso or eWEB if an existing 2.x database is being loaded into a 4.16 O3.
• Firmware update

See Accessing Embedded Web for details on how to connect to the O3 embedded web.

BDE Support

The O3 Edge/Sense now support Bulk Data Exchange, a Delta proprietary data exchange for efficiently sending multiple values one to many or one to one. For more information on the BDE object, see the enteliWEB Bulk Data Exchange (BDE) online help page.

Removed O3-Edge PG limits

The O3-Edge is no longer restricted to 5 PGs .The O3-Sense does not support PG programming.

 enteliWEB Firmware loader support:

O3 2.x firmware relied on an O3 internet connection to download and install firmware. Once an O3 has been upgraded to 4.16 beta firmware or newer, subsequent firmware can be loaded via enteliWEB firmware loader. This includes the eWEB 4.28 ability to download firmware to the O3 and deploy at a later time.

NP Object Support

BLE and MQTT enable and password settings are now included in NP settings. Existing passwords configured in 2.x will be retained and migrated to the NP properties.

NP10 ‘Bluetooth’

• BV31 “Enable BLE” is no longer used and can be deleted if upgrading a database. Enable or disable BLE via NP10 ‘Bluetooth’ instead.
• CSV45 ‘BLE PIN’ remains for 3rd party BACnet front ends but the PIN can also be set via NP10 (enteliWEB 4.28+).

NP13 'MQTT Broker'

• BV48 ‘Internal MQTT Broker Enable’ is no longer used and can be deleted if upgrading a database. Enable or disable MQTT via NP13 ‘MQTT Broker’ instead.
• CSV46 'MQTT Password’ remains for 3rd party BACnet front ends but the password can also be set via NP13 (enteliWEB 4.28+)

Python DLM

• 4.16 firmware supports PDS created custom Python DLMs. Python DLMs can be used to integrate to other IoT applications. Contact the Delta Controls Professional Development Services (PDS) team for more info.

System Requirements

Proviso

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

Seymour Connect

Seymour Connect 1.1 or newer is required for O3 firmware 4.16

enteliWEB

enteliWEB 4.28 or newer is required for O3 firmware 4.16.

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

Firmware Loader

If the O3 has previously been upgraded to a V4.16 Beta build, enteliWEB Firmware Loader can be used to upgrade to V4.16 release firmware with the V4.16 .fls file. V2.x firmware must be upgraded via the below online cloud method.SHFW-3860

Cloud Firmware Load

Cloud firmware upgrade is supported on all versions of O3 firmware. The O3 must have an Internet connection to download firmware.

Upgrade to firmware V4.16 from O3 firmware V2.5.3 and newer. While limited testing has been performed upgrading earlier 2.x versions, it is highly recommended to first upgrade to at least 2.5.3 firmware prior to upgrading to 4.16. Refer to the upgrade section of the 2.x release notes for further information on upgrading to that version.

Upgrading from O3 V2.x firmware to V4.16 is a one way procedure, it is not possible to downgrade back to V2.x firmware. It is recommended to test upgrading a single O3 prior to upgrading a network of O3's.

Node-Red is not supported in V2.x firmware. Any Node-Red DLM modules installed in V2.x firmware will be lost on a V4.16 upgrade. Python DLMs replaces Node-Red DLMs for IoT integration in V4.16 firmware. Contact PDS for more details on Python DLMs

 It can take over 1/2hr to update a controller from 2.x to 4.16, depending on its database size.  Do not unplug or reboot an O3 during a firmware upgrade. Once an upgrade begins, allow it to complete without interruption.  Do not command reset an O3 for at least 5mins after upgrading.

To perform the upgrade, follow the Firmware Upgrade Guide.

Note: Proviso will not display the 4.16 firmware in the list of available firmware versions. It must be manually entered to prevent accidentally updating a V2.x O3 to V4.16 without understanding the warnings above.

Proviso

• Use Manual Version: 4.16.0.2100

BACnet

• BACnet method, manually command CSV43 value to: {"version":"4.16.0.2100"}
• CSV43 description field will be updated with progress

Once upgraded to 4.16, subsequent firmware can be upgraded with enteliWEB Firmware Loader offline method (.fls files) or continue to use existing online methods (Proviso / BACnet CSV43).

Downgrading an O3

It is not possible to downgrade an O3 from version 4.16 back to 2.x firmware

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

Release 4.16.0.2100: The following notable issues are fixed in version since beta build 4.16.0.2098

• internal improvement to upgrade process when upgrading from 2.x to 4.16 (SHFW-3969)
  • No functional change, existing O3s at 4.16.0.2098 do not need to be upgraded to 4.16.0.2100

Release 4.16.0.2098: The following notable issues are fixed in version since beta build 4.16.0.1052

• General
  • The O3 time will not apply UTC offset correctly after a power cycle - loss of power, not soft reset (SHFW-3764)
  • The NP8 ‘Hostname’ MDNS address, based on model name and MAC address, used to open the embedded webserver is incorrect (SHFW-3577)
    • See more info on this feature in the Accessing Embedded Web help
  • An O3 will go offline if IPv4 is disabled and IPv6 is left enabled while BACnet Ethernet is enabled (SHFW-3830)
  • Metrics: Sensor mean calculation may incorrectly calculated to a negative value (SHFW-3594)

Beta 4.16.0.1052: The following notable issues are fixed in version since release 2.7.1

• General
  • Rarely, bnserver may crash and restart. The O3 recovers automatically, but performance may be affected (SHFW-3357)
  • When the O3 is connected to Secure Connect (NP9) and BACnet - Ethernet (NP5) and a database gets loaded from a file, BACnet Ethernet (NP5) may be disabled (SHFW-3128)
  • Firmware upgrade from production cloud gets "Unable to reach download server" through Proviso or CSV43 (SHFW-3706)
  • If DHCP server is started after an O3 is powered up, the O3 may not communicate on BACnet/IP
• Seymour
  • FIL200, used for storing Seymour connect configuration, sometimes is not auto created after loading an old database (SHFW-3590)
  • Authentication failed error may occur when connecting to a provisioned O3 if the O3 UTC is disabled (SHFW-3662)
• Proviso
  • Ethernet status does not update correctly and will always showing “Up and Running” (SHFW-3505)
  • Date and Time and/or BACnet UDP/IP on Diagnostics page gets errors after writing NTP or local date and time from Setting page - resolved with Proviso 2.11+ (SH-3944)