Page 2
It is therefore recommended to contact Elvaco AB for the latest product information before purchasing the product. The documentation and product are provided on an “as is” basis only and may contain deficiencies or inadequacies.
This manual covers information needed to mount, install, configure, and use the product. It is intended for installers and system integrators. To download the latest version of this User manual, visit the Elvaco website, https://www.elvaco.com. There you will also find information about Elvaco’s other products and services.
Failure to comply with these precautions violates safety standards of design, manufacture and intended use of the product. Elvaco AB assumes no liability for customer’s failure to comply with these precautions.
With Elvaco’s One-Touch Commissioning (OTC), deployment, configuration and key transferring can be performed in a secure and flexible way. Use the Elvaco OTC App to enter your desired settings and place your phone next to the meter. New settings will be applied via NFC.
CMi4140 3.4. Parts overview Pulse inputs In A and In B (allowing to connect adjacent pulse meters) Power connector MCX antenna connector Note The MCX antenna connector is used for connecting either an internal or an external antenna.
4. Installation 4.1. Mounting the product CMi4140 can be used in either a Kamstrup MULTICAL® 403, MULTICAL® 603, or a MULTICAL® 803 heat/cooling meter. If the module is not mounted in the meter upon delivery, it is easily inserted and installed: Grab the device by the outer edges.
4.5. Reading the module status via meter display In addition to the Elvaco OTC App, the current status of the module can be read via the meter display. To retrieve the status of the module via the meter display, enter the tech loop of the meter display and request the status information of the module.
Page 10
Table 1. Module status indication on meter display Character, MSB -> lsb Status 53 = Module identification number (CMi4140) 1 = All following characters are set to “1” 0 = One or more of the following characters are set to “0”...
5. Operation 5.1. Configuration CMi4140 can be configured in two ways, either via the Elvaco OTC App, or via downlink commands. Configuration via the Elvaco OTC App is highly flexible, and all configuration options available in the module can be set. In contrast, donwlink configuration comes with some limitations, where all options are not available.
The module relies on the meter’s clock for keeping time. Time in the meter is assumed to be in standard local time (no DST). When synchronizing time in the meter using the Elvaco OTC App, local standard time is always used, even if DST is in effect. The timestamped meter data sent from the module can...
If the meter is set to used DST this is ignored by the module and the standard time is used. Thus, the time on the meter’s display may not match the time in the telegram or in the Elvaco OTC App.
Go to Apply mode. Choose switch off and apply changes. Note This function is restricted to registered owner of the product in Elvaco OTC app and will not be visible/available for other users. 5.8. Meter communication error messages The payloads using M-Bus encoded data uses the Function field of the DIF to indicate errors. In this case it is set to “value during error state”...
6.1. Elvaco OTC App configuration options Below table list all settings that can be made using the Elvaco OTC App. If the device is locked, and the app user does not have access to the PAK key, available settings are only readable.
CMi4140 6.2. Downlink configuration options Below table list what settings that can be made using the LoRaWAN® downlink commands. Table 5. Downlink commands Field name Number of Configuration Example bytes in configuration Configuration 0x05 0x01 0x00 = Locked 0x00050101 lock...
CMi4140 6.3. Message formats To allow a flexible output from the device, CMi4140 has several message formats. Some of them are scheduled, meaning the meter is read on top of every hour, and sending a clock message once per day, Scheduled message formats [20].
Page 18
CMi4140 Field Size Data type Description Heat energy 6-7 bytes INT32 Energy consumption (Wh, J, Cal) E1 / Cooling energy E3 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh...
Page 19
CMi4140 Field Size Data type Description Rt temp 4 bytes INT16 Return temperature (°C) 025Cxxxx = xxxx * 0.001 °C 025Dxxxx = xxxx * 0.01 °C 025Exxxx = xxxx * 0.1 °C 025Fxxxx = xxxx °C Meter ID 6 bytes...
CMi4140 6.3.1.3. JSON For message format JSON, the data is presented in a plain text format, instead of M-Bus, as the other message formats. Below table contains a description of all fields included in the JSON telegram. Table 9. Payload, message format JSON [0x17]...
Page 21
CMi4140 Table 12. Transmit interval options Parameter Values Unit Transmit interval 60, 120, 180, 240, 360, 480, 720, 1440 Minutes 6.3.2.1. Scheduled Daily Redundant Message format Scheduled Daily Redundant contains an accumulated daily energy field, which is updated at 24:00 each day. In other words, depending on transmit interval settings and data rate, the field will be included in between 1-24 telegrams per day.
Page 22
CMi4140 Field Size Data type Description Info bits 7 bytes INT32 Error and warning flags 04FD17xxxxxxxx For further information about Info bits please refer to the meter’s manual Meter date/ 6 bytes INT32 Meter date and time (YY-MM-DD HH:MM) time...
Page 23
CMi4140 6.3.2.2. Scheduled Extended The data message format Scheduled Extended contains all the data fields from message format Stand- ard. In addition to these, it also includes the meter date/time to transmit messages on the full hour. As for all scheduled message formats, the transmit interval can only be set to the values included in Table 12, “Transmit interval options ”...
Page 24
CMi4140 Field Size Data type Description Meter ID / Info 11 bytes INT96 Byte 0-2 = DIF/VIF codes, 0x07FF21 bits Byte 3-6 = Info bits (lsByte -> msByte) Byte 7-10 = Meter ID (lsByte -> msByte)* *Sent in binary format...
Page 25
CMi4140 Field Size Data type Description Heat energy 6-7 bytes INT32 Energy consumption (Wh, J, Cal) 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh 0405xxxxxxxx = xxxxxxxx * 100 Wh...
Page 26
CMi4140 Field Size Data type Description Rt temp 4 bytes INT16 Return temperature (°C) 025Cxxxx = xxxx * 0.001 °C 025Dxxxx = xxxx * 0.01 °C 025Exxxx = xxxx * 0.1 °C 025Fxxxx = xxxx °C Meter ID 6 bytes...
Page 27
CMi4140 Field Size Data type Description Cooling 8-9 bytes INT32 Energy consumption (Wh, J, Cal) energy E3 0480 FF02xxxxxxxx = xxxxxxxx,xxx Wh 0481 FF02xxxxxxxx = xxxxxxxx,xx Wh 0482 FF02xxxxxxxx = xxxxxxxx,x Wh 0483FF02xxxxxxxx = xxxxxxxx Wh 0484FF02xxxxxxxx = xxxxxxxx * 10 Wh...
Page 28
CMi4140 Field Size Data type Description Heat energy 6-7 bytes INT32 Energy consumption (Wh, J, Cal) E1 / Cooling energy E3 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh...
Page 30
CMi4140 Field Size Data type Description Meter date/ 6 bytes INT32 Meter date and time (YY-MM-DD HH:MM) time 046Dxxxxxxxx Bit 31-28 = Year-high* Bit 27-24 = Month Bit 23-21 = Year-low* Bit 20-16 = Day Bit 15 = Summertime flag**...
Page 31
CMi4140 Table 20. Telegram 2 - Payload, message format Pulse [0x1D] Field Size (bytes) Data type Description Message ID UINT8 Always 0x1C Date and time INT32 Date and Time (M-Bus Type F) Example: 046Dxxxxxxxx Meter ID BCD8 According to M-Bus EN13757-3 identification field...
Page 32
CMi4140 Field Size (bytes) Data type Description Rt temp INT16 Example: 025Exxxx Info codes INT32 Error and warning flags Example: 04FD17xxxx Note that this field is always 32 bits, even when using MultiCal 403 which only reports 16 bits. Table 22. Telegram 2 - Payload, message format Pulse [0x1D]...
OTAA or ABP Data rate DR0 - DR5 (250 bit/s-5470 bit/s) User interface Value Push button Start-up / reboot / switch off module Configuration NFC via Elvaco OTC app or downlink data Approvals Value LoRa Alliance® LoRaWAN Certified EN 301489-1, EN 301489-3...
CMi4140 9. Document history Table 23. Versions Version Date Description 2019-03 PoC version 2019-10 Evaluation samples version 2019-12 Commercial release version 2020-06 Commercial release v1.1 2021-05 Commercial release v1.2 2021-11 Commercial release v1.3 2023-12 Minor layout changes were made. 2024-09 Adaptation to release of FW 1.0.4.
Page 36
Manufacturer: Elvaco AB / Kabelgatan 2T / 434 37 Kungsbacka / SWEDEN info@elvaco.com Support: support.elvaco.com support@elvaco.se...
Need help?
Do you have a question about the CMi4140 and is the answer not in the manual?
Questions and answers