| Overview
The OTA progress updates is a feature implemented in the ClimaVision system, to improve transparency and progress visualization of Over the Air firmware updates for the hardware devices.
This enhances the message-handling capability between the cloud and CCU, and thus addresses issues like:
- No way to track OTA updates.
- No actual status notifications for the users on updates.
The implementation targets the following aspects:
- Status updates for the OTA initiated from portals in the portal.
- Progress of the update
- Notifying the users of the success and failure of the updates
| OTA Status Updates
As part of the above-mentioned aspects, the following capability is added.
Statuses | Description |
Packet received |
|
Download started. |
|
Update Completed |
|
| OTA Status Update Point
The implementation to achieve the OTA status visibility uses a newly added point OtaStatus, and its respective Enums to provide information about different stages of the OTA update.
Following are the Enumerations used for the point OtaStatus and their descriptions:
Enumeration | Enumeration Description |
0 | OTA_REQUEST_RECEIVED |
1 | OTA_UPDATE_STARTED |
2 | OTA_REQUEST_IN_PROGRESS |
3 | OTA_FIRMWARE_DOWNLOAD_FAILED |
4 | OTA_CCU_TO_CM_FAILED |
5 | OTA_CCU_TO_CM_UPDATE_STARTED |
6 | OTA_CCU_TO_CM_PERCENT_COMPLETED_10 |
7 | OTA_CCU_TO_CM_PERCENT_COMPLETED_50 |
8 | OTA_CCU_TO_CM_PERCENT_COMPLETED_100 |
9 | OTA_CCU_TO_CM_FIRMWARE_RECEIVED |
10 | OTA_CM_TO_DEVICE_PACKET_STARTED |
11 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_10 |
12 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_20 |
13 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_30 |
14 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_40 |
15 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_50 |
16 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_60 |
17 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_70 |
18 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_80 |
19 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_90 |
20 | OTA_CM_TO_DEVICE_PERCENT_COMPLETED_100 |
21 | OTA_SUCCESSED |
22 | OTA_TIMEOUT |
23 | OTA_CM_TO_DEVICE_FAILED |
24 | NODE_STATUS_VALUE_FW_OTA_SUCCESSFUL |
The OTA updates initiated from the portals could fail for various reasons and at two places in the OTA process steps.
- While firmware upgrade packets are being received
- After firmware upgrade packets are received
During these steps of the process, when the CCU application crashes for any reason, the OTA update fails.
During this kind of failure, when the CCU application comes back online, it recognizes an active request for the update is present.
This request for the update can be visualized in the Portal with the failure status message, and the same can be resumed.
| OTA Failure Update
The OtaStatus also provides the status of the failed OTA update.
Following are the Enumerations used for the point OtaStatus and their descriptions on the OTA Update failure statuses.
Enumeration | Enumeration Description |
25 | NODE_STATUS_VALUE_FW_OTA_FAIL_REBOOT_INTERRUPTION |
26 | NODE_STATUS_VALUE_FW_OTA_FAIL_NOT_FOR_ME_DEV_TYPE |
27 | NODE_STATUS_VALUE_FW_OTA_FAIL_NOT_FOR_ME_FW_VERSION |
28 | NODE_STATUS_VALUE_FW_OTA_FAIL_IMAGE_SIZE |
29 | NODE_STATUS_VALUE_FW_OTA_FAIL_EXT_FLASH_ERROR |
30 | NODE_STATUS_VALUE_FW_OTA_FAIL_IMAGE_VERIFICATION |
31 | NODE_STATUS_VALUE_FW_OTA_FAIL_INACTIVITY_TIMEOUT |
32 | NO INFO |
Based on an enum value visualized for the point OtaStaus the user can conclude on the failure status of an OTA update.
| OTA Status Update Visualizations
| Feature Availability Versions
- The OTA progress tracking feature is available from the CM version 3.31 and above.
- The OTA progress tracking feature is available from the CCU version 3.31 and above.
Comments
0 comments
Please sign in to leave a comment.