| Overview
The Connect module can now be paired as a zone in the 75F CCU. Currently, custom sequences created in the Site sequencer tool are downloaded and manually transferred to Connect Modules via WebUSB.
With this implementation, we have enabled Over-The-Air (OTA) delivery of sequences and firmware updates to Connect Modules via CCU, eliminating manual intervention. Users can directly push the custom sequences to the desired zone paired using a connect module in the CCU.
| Version Requirements
- CCU version 3.7.1
- CM version 3.66
- Connect Module Version 1.11
| Wiring
| Configuration Steps
To pair a Connect module as a zone in the CCU.
From the CCU Floor layout screen.
- Add a zone to pair the connect module as a zone.
- Click Pair Module.
The select device type screen displays
- Click CN Connect Module device type.
The pairing steps screen displays.
| Setting the Connect Module to Connect as Zone Mode.
To set the Connect Module device to connect as zone mode.
- Navigate to the Installer Options screen in the Connect module device.
- Press the down arrow button to access the options.
- Navigate to the Configure mode option.
- Press the right arrow button to access the mode selection.
- Press the down arrow button to modify the mode.
- Press the right arrow button to set the mode selection to connect as a zone.
Confirmation screen displays.
- Press the right arrow button to confirm the mode selection to connect as a zone.
Device resets and the connect is set to the connect as a zone mode.
| Setting the Connect Module to Pairing Mode
To set the Connect Module device to connect as zone mode.
- Navigate to the Installer Options screen in the Connect module device.
- Press the down arrow button to access the options.
- Navigate to the Pair with CCU option.
The device mac address broadcasting message screen displays.
| Pairing Steps
- Click Pair on the pairing steps screen.
- Click on the device with mac address broadcasted.
- Alternatively, click Connect Manually, to pair the device manually.
For more information on manual pairing refer to Alternate or Manual Pairing of Connect Module
- Enter the PIN displayed on the connect module device.
- Click Save to finish the Pairing.
The Device gets paired,d and the same is reflected in the floor layout screen.
The Connect Module, paired as a zone, successfully displays.
| Device Configuration in Site Sequencer
Access site sequencer from the internal portal.
- Click Device to access the site sequencer for Low code/ device.
For more information on low code refer to Sequencer for Edge
The Site sequencer screen for the device displays.
- Drag and drop the Run sequence on start-up block.
- Drag and drop the model selection block within the startup block
Note: The model selection block should always be placed with the Run Sequence on Startup block.
- Create the required sequence steps under the startup block.
- Drag and drop the Run sequence Continuously block
- Create the required sequence steps within the 'Run continuously' block.
- Click Save to save the Sequence.
The sequence saved successfully message displays.
-
Click Push to Devices to push the sequence to the device paired Via CCU.
The zone created for the site, paired with a connect module, displays.
- Select the zone to which you need to push the sequence.
- Click Apply Sequence.
The sequence is applied successfully message displays.
The sequence is pushed to the connect module paired as a zone with the CCU.
- Click the profile to access the profile.
The applied model reflects as the zone paired, as shown below.
- Enable the required parameters to display in the UI
- Click Save to save the configuration.
The configuration saved successfully message displays.
The paired zone is reflected in the zone as shown below.
Meanwhile in the device once the sequence is downloaded to the CM and sent to the device, the device restarts and starts running the sequence. The same is demonstrated below.
The home screen is updated with the sequence updates as shown below.
The universal inputs on the device reflect the information from the sequence as shown below.
The values can be monitored from the CCU as shown below.
In the portals, the zone details can be visualized from the zone widget screen as shown below.
| Sequence OTA enumeration
The implementation to achieve the OTA status visibility uses a Sequence OtaStatus, and its respective Enums to provide information about different stages of the OTA update.
The following are the Enumerations used for the Sequence OtaStatus and their descriptions:
| Enumeration | Enumeration Description |
| 0 | SEQ Request Received |
| 1 | SEQ Update Started |
| 2 | SEQ Request In Progress |
| 3 | SEQ Download Failed |
| 4 | SEQ CCU CM Failed |
| 5 | SEQ CCU CM Update Started |
| 6 | SEQ CCU To CM 10 Percent Completed |
| 7 | SEQ CCU To CM 50 Percent Completed |
| 8 | SEQ CCU To CM 100 Percent Completed |
| 9 | SEQ CCU To CM Firmware Received |
| 10 | SEQ CM Device Packet Started |
| 11 | SEQ CM To Device 10 Percent Completed |
| 12 | SEQ CM To Device 20 Percent Completed |
| 13 | SEQ CM To Device 30 Percent Completed |
| 14 | SEQ CM To Device 40 Percent Completed |
| 15 | SEQ CM To Device 50 Percent Completed |
| 16 | SEQ CM To Device 60 Percent Completed |
| 17 | SEQ CM To Device 70 Percent Completed |
| 18 | SEQ CM To Device 80 Percent Completed |
| 19 | SEQ CM To Device 90 Percent Completed |
| 20 | SEQ CM To Device 100 Percent Completed |
| 21 | SEQ Succeeded |
| 22 | SEQ Timeout |
| 23 | SEQ CM Device Failed |
| 24 | Node Status Value FW OTA Successful |
| OTA Failure Handling
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 the 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 that 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.
| Enumeration | Enumeration Description |
| 25 | Node Status Value FW OTA Reboot Interruption |
| 26 | Node Status Value FW OTA Not For Me Dev Type |
| 27 | Node Status Value FW OTA Not For Me FW Version |
| 28 | Node Status Value FW OTA Image Size |
| 29 | Node Status Value FW OTA Ext Flash Error |
| 30 | Node Status Value FW OTA Image Verification |
| 31 | Node Status Value FW OTA Inactivity Timeout |
| 32 | No Info |
| 33 | SEQ Update Failed |
| 34 | SEQ Update Cancelled |
| Device OTA Enumeration
The implementation to achieve the OTA status visibility uses a Firmware device OtaStatus, and its respective Enums to provide information about different stages of the OTA update.
The following are the Enumerations used for the Firmware devices 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 CM Failed |
| 5 | OTA CCU CM Update Started |
| 6 | OTA CCU To CM 10 Percent Completed |
| 7 | OTA CCU To CM 50 Percent Completed |
| 8 | OTA CCU To CM 100 Percent Completed |
| 9 | OTA CCU To CM Firmware Received |
| 10 | OTA CM Device Packet Started |
| 11 | OTA CM To Device 10 Percent Completed |
| 12 | OTA CM To Device 20 Percent Completed |
| 13 | OTA CM To Device 30 Percent Completed |
| 14 | OTA CM To Device 40 Percent Completed |
| 15 | OTA CM To Device 50 Percent Completed |
| 16 | OTA CM To Device 60 Percent Completed |
| 17 | OTA CM To Device 70 Percent Completed |
| 18 | OTA CM To Device 80 Percent Completed |
| 19 | OTA CM To Device 90 Percent Completed |
| 20 | OTA CM To Device 100 Percent Completed |
| 21 | OTA Succeeded |
| 22 | OTA Timeout |
| 23 | OTA CM Device Failed |
| 24 | Node Status Value FW OTA Successful |
| OTA Failure Handling
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 the 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 that 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.
| Enumeration | Enumeration Description |
| 25 | Node Status Value FW OTA Reboot Interruption |
| 26 | Node Status Value FW OTA Not For Me Dev Type |
| 27 | Node Status Value FW OTA Not For Me FW Version |
| 28 | Node Status Value FW OTA Image Size |
| 29 | Node Status Value FW OTA Ext Flash Error |
| 30 | Node Status Value FW OTA Image Verification |
| 31 | Node Status Value FW OTA Inactivity Timeout |
Comments
0 comments
Please sign in to leave a comment.