O3 Firmware 4.17 Release Notes

Welcome

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

4.17 firmware continues the regularly scheduled releases based on the same V4 platform shared with Red5 and enteliBUS controllers.

Note: Refer to O3 documentation for more information of supported V4 functionality specific to the O3.

New Features in 4.17

There are no new features for the O3 with 4.17 firmware. 4.17 is a short cycle release primarily targeted for other products in the V4 family.

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.17.  

Seymour Connect

Seymour Connect 1.1 or newer is required for O3 firmware 4.17.

enteliWEB

enteliWEB 4.28 or newer is required for O3 firmware 4.17.

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 build, enteliWEB Firmware Loader can be used to upgrade to V4.17 firmware with the V4.17 .fls file. V2.x firmware must be upgraded via the below online cloud method.

Download the V4.17 O3 firmware .fls file from Delta Controls Support Firmware Downloads

Cloud Firmware Load

V4.17 cannot be directly upgraded from V2.x,. Upgrade to V4.16 via the below cloud method, then use the above enteliWEB firmware Loader method to upgrade from 4.16 → 4.17.

The O3 must have an Internet connection to download firmware via the cloud method.

Cloud upgrading to 4.16

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.xx 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.xx upgrade. Python DLMs replaces Node-Red DLMs for IoT integration in V4.xx firmware. Contact PDS for more details on Python DLMs

 It can take over 1/2hr to update a controller from 2.x to 4.xx, 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 V4.16, enteliWEB Firmware Loader method can be used to upgrade to 4.17 using the .fls firmware file.

Future firmware will support both the online methods (Proviso / BACnet CSV43) and offline enteliWEB Firmware Loader (.fls files).

Downgrading an O3

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

Firmware loader or the cloud CSV43/Proviso can be used to downgrade an O3 from 4.17 to 4.16. See the 4.16 Release notes for more details on loading 4.16 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.17.0.1021: The following notable issues are fixed in version since release 4.16

• General
  • When BACnet IP is enabled, an I-Am packet is sent every 10s , adding unnecessary traffic to the network (SHFW-3923)

Refer to the general V4.17 firmware release notes for additional fixes common to the V4 platform: Red5 and enteliBUS 4.17 Firmware Release Notes.pdf