Release notes

CMi6140 1.5.0

Release date: 2026-04-07

Caution

Valid only for CMi6140 G2 hardware: When changing APN to a manual APN via staging value, the value can be committed to the configuration even if it is invalid. The module will still use previous value (check the actual value used) but the configuration will show the wrong setting.

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.

Note

Message format Combined (ID: 68) has been changed so Forward and Return temperatures are included. This is done to correspond better to the corresponding message format for CMi4140.

Background: Together with the introduction of the new face-lifted HW, CMi6140 G2, a set of new FW features are introduced as well. Note that the FW is compatible on existing CMi6140 HW. Devices already installed in field can be remotely updated to get the new firmware in place. Highlighted features in FW 1.5.0 includes:

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

  • System log capabilities: Thanks to the system log, 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. The system log works independently of the info log, which was introduced in FW 1.3.0.

  • General network related improvements: The FW release includes a package of fixes and solutions to improve the general network-related behavior of the device. This will improve data delivery and overall field performance of the CMi6140.

Configuration changes:

In FW 1.5.0, some changes are made to the default configuration. It is also introducing several new parameters, linked to the new features.

Table 118. Below changes have been made to the default configuration to improve device behavior

Parameter

Old value

New value

Tx Offset

30

125

Tx Delay

240

45

LwM2M Resume Backoff

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

[30-60,60-120]

IOWA Communication Sequence Retry Delay

24h

2h

Table 119. New parameters and default value

Related feature

New parameter(s)

Default value

NFC Autolock

NfcAutoLockEnable

Disabled

NfcAutoLockTimeout

15 min

Remote change of bootstrap server

BootstrapServerURIStaging

Empty (used for remote updates of Bootstrap URI)

System logger

SyslogLevel

INFO

SyslogMqttSnTopic

elvaco/#P/cbor/syslog/#D

SyslogAutoUploadLevel

NOTICE

SyslogAutoUploadAgeLimit

14 days

Push of alarms

AlarmFuncEnableBitmask

0 = OFF

AlarmMaskResetPeriod

0 = OFF

AlarmHysteresis

10 minutes

AlarmAutoResetBitmask

0 = OFF

AlarmTxDelayMax

5 minutes

AlarmMqttSnTopic

elvaco/#P/#E/#T/#D/alarm

Low Battery Voltage threshold

3200 mV

DTLS

DTLS Max Rewinds

10

PLMN

Roam Home Plmn Search

Disabled

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.

Integration considerations:

The following LwM2M objects have new versions:

  • Connectivity Monitoring (v1.0 → v1.3)

    • Updated to new version according to OMA specification

  • MCM Config (v2.4 → v2.14)

    • Removed resources that was marked as obsolete: 26, 27, 28, 29

    • Added resources:

      • Communication settings 59, 60

      • Alarms 61, 62, 63, 64, 65, 66, 67, 75

      • Persistent bootstrap 69, 70

      • NFC Auto lock 71, 72

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

    • Added resource 12 (Current Access Technology)

  • Meter Info (2.0 → 2.4)

    • Clarification of range of resource 2 (Communication status)

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

  • NB-IoT Info (v2.2 → v2.6)

    • Added resources:

      • IMEI 9

      • Power stats 10

  • Elvaco Syslog Config (new, version 1.0)

Implemented changes:

Table 120. Implemented changes

ID

Description

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-8609

Add support for meters MC603M and MC803M

MCM-8541

Add missing registers to Combined message format

MCM-8478

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

MCM-8470

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

MCM-8464

Push of alarms for CMi6140

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-7561

Automatically lock NFC configuration after activation

MCM-7332

Persistent user defined credentials for BS+DM+MDM

MCM-7184

Syslog for NB-IoT devices

MCM-5812

DTLS handshake supervision

MCM-8649

[SOLVED] Data upload during FOTA could cause device restart

MCM-8602

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

MCM-8528

[SOLVED] Values for SNR + ECL sometimes not correct/valid

MCM-8510

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

MCM-8379

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

MCM-8378

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

MCM-8309

[SOLVED] Timestamp included in LwM2M Send not correctly handling UTC time

MCM-8106

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

MCM-7682

[SOLVED] Large NFC writes not being applied

MCM-7489

[SOLVED] No connectivity for ~72h and no historical data transmitted

MCM-7412

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

MCM-7121

[SOLVED] No valid meter time after brown-out, storing the first meter readout wrong

CMi6140 1.3.1

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 fixes an issue related to LwM2M send, detected in the previous firmware release of CMi6140. If not using the LwM2M send feature, devices are operating as they are intended to do. The release also corrects a potential issue if using the newly introduced pulse message format, occasionally falsely sending too big data packages. In addition to adding some other general improvements and fixing some bugs, it also adds the possibility to manually configure PLMN using NFC.

Table 121. 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-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

CMi6140 1.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

  • Added info log enable setting (default off)

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 CMi6140, see list of highlighted implemented features below. Please note that the new firmware name is 1.3.0, replacing 1.0.2. To harmonize the naming of products using the Elvaco NB-IoT platform, the sequentially correct naming, 1.1.0, has been skipped intentionally.

Table 122. Implemented changes

ID

Description

MCM-6182

Object version for MCM Config Object (33906) updated to 2.2

MCM-6123

Operating hours included in Pulse message format

MCM-6016

Transmit meter Info Log data

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-5653

[Solved] Correctly identify module on meter requests, such as when using Kamstrup Meter Tool for meter configuration.

MCM-5403

[Solved] BC66 modem driver misses incoming back-to-back packets

MCM-5352

[Solved] Periodic Vavg measuring active during modem DFOTA upgrade phase.

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.