Release notes

CMi6110 2.5.0

Release date: 2025-06-08

Note

Upgrading from FW versions prior to 2.5.0 will delete all stored meter data. So before starting a remote update, ensure that all data needed has been collected from the device.

Background: Firmware 2.5.0 is the first FW made available for the new hardware, CMi6110 G3. The release introduces several major features that improve commissioning efficiency, operational visibility, and flexibility in how meter data is collected and transmitted

Highlighted features:

  • Dynamic message format: Freely choose what to send from a list of available meter registers.

  • Threshold alarms: New alarms have been added to the push of alarm feature.

  • Automatic activation at flow: Reduce installation time and battery use during installation by letting the module be activated once the meter registers flow.

Note

Firmware 2.5.0 is available for CMi6110 G2 as well, but there's a separate firmware file for each version. The functional content is the same.

Configuration changes: The list of configuration changes of existing parameters is quite extensive as the default configuration has been changed from being optimized for mains powered devices. The updated default configuration from 2.5.0 is optimized for battery-operated devices. In addition, there are several new parameters to serve the new features

Table 51. Changed parameters

Parameter

Old value

New value

NbIotTimer3412

252000

144000

NbIotTimer3324

10800

120

NbIotEdrx

0x73 (115)

0x13 (19)

LwM2MQueueMode

0

1

NbIotTxOffset

5

125

NbIotTxDelay

50

45

NbIotIowaCommRetryCount

3

1

NbIotIowaCommSeqRetryDelay

43200

7200

NbIotNwkSearchPeriod

7200

21600

NbIotMdmReconnectBackoff

[0-0, 60-60, 180-180, 720-720]

[0-0, 60-60, 360-360, 1380-1380]

NbIotLwM2MResumeBackoff

[0-5, 60-120, 1300-1600]

[30-60, 60-120]

PowerSource

PowerSourcePsu (1)

PowerSourceBattery (0)

TxInterval

60

1440

Table 52. New parameters

Parameter

Old value

New value

MeterCustomMask

N/A

{0xF9,0x01,0x08,0}

CMi6110BackflowPercent

N/A

-3

CMi6110MaxflowPercent

N/A

200

CMi6110LowBatteryVoltage

N/A

2300

Integration considerations: Several objects have been updated, with added and removed resources:

  • Elvaco MCM Config (33906): v2.12 → v2.16

    • 26: MQTT-SN Register Timeout - removed

    • 27: MQTT-SN Register Attempts - removed

    • 28: MQTT-SN Publish Timeout - removed

    • 29: MQTT-SN Publish Attempts - removed

    • 68: Measurement mode - changed description

    • 73: Max flow percent - added; Maximum flow percent which will trigger a max flow alarm - 0 for disabled (UH50 meter only)

    • 74: Back flow percent - added; Back flow percent which will trigger a back flow alarm - 0 for disabled (UH50 meter only)

    • 75: Low battery voltage - added; Voltage threshold for battery operated devices for triggering low battery alarm.

    • 76: Custom format transmit fields - added; Bitmask defining which data fields are included in payload of measurement mode custom.

  • Elvaco NB-IoT info (33909): v2.2 → v2.6

    • 9: IMEI - added

    • 10: Power Stats - added

  • Elvaco syslog config (33918): v1.0 → v1.2

    • 4: Historical syslog readout trigger - added; Trigger historical syslog readout. Execute arguments: 0=<from unix timestamp>, 1=<to unix timestamp>, 2=<minimum log level (0..6)>.

Table 53. Implemented changes

ID

Description

MCM-8796

Add measurement mode Custom

MCM-8782

Change default tx offset and delay

MCM-8763

Adapt configuration to improve recovery time in case of network reconfigurations

MCM-8712

Upgrade LwM2M object 4 Connectivity Monitoring to v1.3

MCM-8478

Change default value for TAU time (T3412) to 40h

MCM-8470

Update external modules for MQTT/DTLS/RTOS to latest versions

MCM-8429

Use 32 bit extended error codes for CMi6110

MCM-7780

Add backflow and maxflow alarms

MCM-7779

Add support for conditional observations on power source voltage level via LwM2M

MCM-7777

Default configuration for battery operation

MCM-8649

[SOLVED] Data upload during FOTA could cause device restart

MCM-8602

[SOLVED] Multiple concurrent write requests over LwM2M causes lost communication

MCM-8584

[SOLVED] Syslog level of connection handler events may get wrong

MCM-8510

[SOLVED] Reading LwM2M APN Connection Profile object gives wrong validity

MCM-8506

[SOLVED] Manual PLMN lost when upgrading from earlier FW version

MCM-8434

[SOLVED] Fixed syslog entries with "invalid time" not sent to server

MCM-8379

[SOLVED] MQTT-SN compliance mode sends unnecessary CONNECT when Tx interval is low

CMi6110 2.4.1

Release date: 2025-12-22

Background: The only change in this firmware is that the default setting for the NFC automatic configuration lock has been changed from enabled to disabled. This adjustment was made because the automatic activation of the NFC configuration lock has caused issues in certain field installations (where end users do not have possession of the PAK). No other changes are made.

Configuration changes:

Parameter

Old value

New value

NfcAutoLockEnable

Enabled

Disabled

Table 54. Implemented changes

ID

Description

MCM-8466

Disable NFC Auto lock feature by default for CMi6110

CMi6110 2.4.0

Warning

There's a known issue un this FW, where manual PLMN get lost when upgrading (FW over the air) from earlier FW versions. To avoid losing network connection to devices using manual PLMN, it must be secured it’s functioning also on automatic PLMN.

A fix for this issue will be implemented in FW 2.5.0.

Note

Upgrading from previous versions of the FW will delete all stored meter data. So, before starting a remote update, ensure that all data has been collected to avoid losing it.

Release date: 2025-11-26

Background: This FW introduces several new features, focusing on improving the device and meter monitoring. The firmware is also adapted to make CMi6110 G2 RED Cyber Security compliant. Highlighted features:

Push of alarms: Having this feature enabled, the device can push alarms appearing in the meter. This enables quick response to issues in field.

Syslog capabilities: Thanks to the syslog, events over the lifetime of the module and meter can be traced. The feature can be helpful when assessing the overall performance/health of the device.

Improved bootstrapping: This change comes with a set of features, e,g. enabling remotely changing bootstrap server (in case the device cannot attach to the new server, it will roll-back to the existing one).

Automatic configuration lock: To improve the security and access control to the device, the NFC configuration lock is automatically applied after activation. This prevents unauthorized access to the device.

Note

The automatic configuration lock is enabled by default with a 15 min timeout counting down from activation. To get access to the device once locked, local access requires possession of the product access key (PAK).

Configuration changes: No changes to the default configuration have been made, but several new configurations are possible. Default value within ():

Note

The parameters to control what bootstrap to connect to have been updated in the Elvaco OTC App. Instead of defining BS port + BS IP (or BS hostname) + BS security, all of this is now given in a complete BS URI. Previous settings will become obsolete.

  • NFC Autolock

    • NfcAutoLockEnable (Enabled)

    • NfcAutoLockTimeout (15 minutes)

  • BootstrapServerURIStaging (empty)

    • Used for remote updates of Bootstrap URI

  • NbIotDtlsMaxRewinds (10)

    • New protection against excess DTLS rewinding

  • MeasurementMode (Preset mode)

    • Preparation for FW 2.5.0 with dynamic message format

  • RoamHomePlmnSearch (0b10: overrideLrplmnsi enable, HPPlmnSearch disable)

    • Preparation for CMi6110G3, not used in CMi6110G2

  • System logger

    • SyslogLevel (INFO)

    • SyslogMqttSnTopic (elvaco/#P/cbor/syslog/#D)

    • SyslogAutoUploadLevel (NOTICE)

    • SyslogAutoUploadAgeLimit (14 days)

  • Alarm functionality

    • AlarmFuncEnableBitmask (0)

    • AlarmMaskResetPeriod (0 = OFF)

    • AlarmHysteresis (10 minutes)

    • AlarmAutoResetBitmask (0)

    • AlarmTxDelayMax (5 minutes)

    • AlarmMqttSnTopic (elvaco/#P/#E/#T/#D/alarm)

Integration considerations:

  • MCM Config (33906 v2.4 → v2.12)

    • New resources added for supporting new functionality (resource 59 - 72)

  • Elvaco Meter Info (33908 v2.0 → v2.4)

    • Additional resource 4 for Extended Error Codes (used in conjunction with Alarm)

  • Elvaco NB-IoT Status (33907 v2.0 → v2.4)

    • Additional resource 12

  • Elvaco syslog config (33918 v1.0)

    • New object

Table 55. Implemented changes

ID

Description

MCM-8373

Mask out Activation at Flow bits from errorcode

MCM-8221

Remove DFOTA for modem for BC66NA due to non-compliance to RED 3.3

MCM-8090

Expose modem IMEI via NFC & LwM2M

MCM-7960

Factory reset deletes meter data, syslog and credentials

MCM-7959

Factory reset resumption after interruption

MCM-7629

CMi6110 Push of Alarms

MCM-7332

Persistent user defined credentials for BS+DM+MDM

MCM-7302

Support observations based on value changes

MCM-7184

Syslog for CMi6110

MCM-5812

DTLS handshake supervision

MCM-5126

Add NFC command to force DM Registration Update

MCM-3733

Change bootstrap server via DM

MCM-3477

Set user defined credentials via NFC for BS+DM+MDM

MCM-2769

Send additional readout only when time sync moves time past planned readout

MCM-8378

[SOLVED] Staging manual PLMN is not committed after successful DM registration

MCM-8106

[SOLVED] NFC write to UTC offset is very slow when no meter is attached

MCM-7682

[SOLVED] Fix large NFC writes not being applied

MCM-7542

[SOLVED] Config not applied in device even if DM receive write response 2.04 changed

MCM-7412

[SOLVED] Refresh data model gives error on Meter Data object 33911

MCM-7395

[SOLVED] Fix disconnect from MQTT-SN server not handled correctly

MCM-7354

[SOLVED] RSRP not scaled correctly in LwM2M Connectivity Monitoring object

MCM-7335

[SOLVED] NFC write of MQTT-SN topic not working

MCM-7121

[SOLVED] No valid meter time after brown-out and stores the first readout wrong

MCM-6463

[SOLVED] Improve Bootstrap URI string validation

CMi6110 2.3.1

Release date: 2024-03-18

Configuration changes: No changes in 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 CMi6110. 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 56. Implemented changes

ID

Description

MCM-6367

Possibility to manually configure PLMN via NFC added

MCM-6474

[SOLVED] Too large data packages could cause device falsely sending zeros in M-Bus 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.

CMi6110 2.3.0

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 CMi6110, see list of implemented features below.

Table 57. 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-&gt;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-5931

[Solved] CMi6110G2 - New power source not detected if switch is made fast enough

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

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Articles in this section

Comments (0 comments)

Article is closed for comments.