Release notes
Warning
There's a known bug in the FW 1.3.2 making devices being unreachable in case of doing a firmware over the air update to this firmware in case using manual APN. Thus, Elvaco strongly advises to not do FOTA till FW 1.3.2. Devices successfully updated to 1.3.2 will operate normally.
Release date: 2025-03-04
Configuration changes: This release includes two changes in the default settings.
Note
Pay extra attention to MCM-7113 where the default settings have been updated. Change details:
Tx Offset: 30 min → 45 min
Tx Delay: 240 min → 125 min
These settings will improve the delivery of meter data occurring on top the hour.
Note
Pay extra attention to MCM-7070 where the default settings have been updated. Change details:
Message format: Tariff → Standard
By convenience, the default message format has been changed to Standard.
Integration considerations: Two new parameters have been added:
-
DTLS max rewind: 10 - Limits the number of restarts of DTLS handshake in case of server errors
-
Home PLMN search: 0b10 (feature turned off) - The home PLMN search will search for the SIM home network periodically. This is detrimental to battery lifetime and therefore turned off by default.
The MCM Config object increased version 2.4 → 2.8 with the two added parameters above.
Background: The main feature of this release is the automatic activation at flow feature, allowing the module to automatically active when enough water has flowed through the meter. This allows a more efficient yet battery friendly installation procedure.
Table 103. Implemented changes
|
Change ID |
Description |
|---|---|
|
MCM-7113 |
Change default transmit offset/delay to improve delivery performance |
|
MCM-7070 |
Factory default message format set to Standard |
|
MCM-6950 |
Read power source from meter |
|
MCM-6829 |
Upgrade LwM2M stack (IOWA) to 2023-09.2 |
|
MCM-6358 |
Product activation at detection of water flow |
|
MCM-5812 |
DTLS handshake supervision |
|
MCM-2769 |
Send additional readout only when time sync moves time past planned readout |
|
MCM-6716 |
[SOLVED] L4 Auto PLMN issue |
|
MCM-6343 |
[SOLVED] Handle error code 03 on MQTT-SN Publish |
|
MCM-6299 |
[SOLVED] Process PLMN code as per the 3GPP standard (leading zeroes considered as significant) |
Release date: 2024-03-18
Configuration changes: No changed configuration parameters.
Integration considerations: Object versions for 33905 and 33906 changed due to changes in definitions/descriptions, see ID MCM-6359 and MCM-6214 below.
Background: This release mainly fixes an issue related to LwM2M send, detected in the previous firmware release of CMi6160. If not using the LwM2M send feature, devices are operating as they are intended to do. In addition to adding some general improvements and fixing some bugs, it also adds the possibility to manually configure PLMN using NFC.
Table 104. Implemented changes
|
ID |
Description |
|---|---|
|
MCM-6367 |
Possibility to manually configure PLMN via NFC added |
|
MCM-6406 |
[SOLVED] Value sometimes sent with wrong timestamp in CBOR payload |
|
MCM-6381 |
[SOLVED] Previous manual PLMN configuration could lead to lost network connection |
|
MCM-6359 |
[SOLVED] LwM2M resource 33906/0/57 defined as bool instead of integer |
|
MCM-6308 |
[SOLVED] Possible error when reading entire object 33906 (MCM Config) if having resource(s) not implemented within the object |
|
MCM-6277 |
[SOLVED] LwM2M Send transmitted at the same time as Reg Update fails |
|
MCM-6214 |
[SOLVED] Misleading information in LwM2M XML for objects 33905 and 33906. Range for /33905/../2 updated to 0..3 to match implementation. Object versions incremented to indicate change. |
|
MCM-5924 |
[SOLVED] Device could send zero energy value if unable to read meter |
Release date: 2024-01-05
Configuration changes:
-
Added Bootstrap URI as alternative to bootstrap IP
-
Added Manual PLMN with staging for setting PLMN in device
-
Added MQTT keep alive timeout (was previously hard coded to ~18h)
-
Added LwM2M force queue mode setting to control if queue mode is used.
Notes New LwM2M object version set for /33906/x/x/ (MCM Config)
Background: This new firmware comes with several new features improving the overall performance of the CMi6160, see list of implemented features below. Please note that the new firmware name is 1.3.0, replacing 1.1.0. To harmonize the naming of products using the Elvaco NB-IoT platform, the sequentially correct naming, 1.2.0, has been skipped intentionally.
Table 105. Implemented changes
|
ID |
Description |
|---|---|
|
MCM-6182 |
Object version for MCM Config Object (33906) updated to 2.2 |
|
MCM-5610 |
Added configuration to manually select network (PLMN) |
|
MCM-5608 |
RTC timestamp is used for LwM2M Send |
|
MCM-5580 |
Configure client usage of LwM2M Queue Mode |
|
MCM-5554 |
Modem IMSI is now readable in production |
|
MCM-5372 |
DTLS Connection ID (53->54) updated according to DTLS 1.2 (RFC 9146) |
|
MCM-5102 |
Added Release Assistance Indication (RAI) support for LwM2M |
|
MCM-4735 |
Possible to configure bootstrap server using URI |
|
MCM-3871 |
MQTT-SN Compliant timeout is now configurable |
|
MCM-6099 |
[Solved] Allow correct maximum values for T3412 and T3324 according to 3GPP TS 24.008 |
|
MCM-6047 |
[Solved] Bad range/description for XML resource /33906/0/51 Enable RAI |
|
MCM-5922 |
[Solved] MD Upload via LwM2M does not work when same Tx Interval and DM Lifetime |
|
MCM-5403 |
[Solved] BC66 modem driver misses incoming back-to-back packets |
|
MCM-5119 |
[Solved] Resource changes from DM not always applied in device |
|
MCM-4759 |
[Solved] Readouts and uploads can be accidentally started via NFC in inactive mode, leading to unplanned meter readouts and higher power consumption |
|
MCM-4533 |
[Solved] Registation Uptime resource (/33909/0/6) is reset by PSM |
|
MCM-4356 |
[Solved] Trigger sending of readouts using LwM2M in Queue mode not working |
|
MCM-3916 |
[Solved] Factory reset via LwM2M not supported |
|
MCM-3736 |
[Solved] MDM Uploads stopped working in Compliant mode |
|
MCM-3735 |
[Solved] MQTT-SN Compliant mode not working |
|
MCM-3697 |
[Solved] In conversion from BTU to Wh, large BTU values causes overflow to negative Wh values |
Kommentarer (0 kommentarer)