Decoding data from the Eastron SDM630MCT-LoRa
Identifying your meter
The Eastron SDM630MCT-LoRa is a three-phase DIN rail mounted electricity meter that communicates over LoRaWAN. As illustrated by the image (left) below it will say SDM630MCT-LoRa directly to the right of the Eastron logo. The Serial Number (SN) is located below and to the right of the backlit display as displayed in the image (right).
Connecting your meter to a LoRaWAN Network Server
The SDM630MCT-LoRa can be connected to any LoRaWAN Network Server (LNS) including TTN, TTI, Chirpstack and Loriot amongst others. cThings Cloud provide an end-to-end in-built LNS with pre-configured decoders to facilitate connecting the SDM630MCT-LoRa to your existing system. Contact us to find out more.
The SDM630MCT-LoRa must be setup as a Class-C device
Decoding the default data received from the SDM630MCT-LoRa
All SDM630-LoRa meters come with a default configuration pre-installed. If a custom configuration has been requested, see the section below on custom configurations.
By default, data will be sent from the SDM630MCT-LoRa every 30 minutes. Below is an example hex encoded payload that could be sent from a default configured meter (it has been conveniently separated into chunks to match the decode in the table below).
001435FC 01 14 443A424E 40E7A876 42C5DA1D 439449DB 43AEC439 3B B2
The meter will send the data in a single payload with the 5 default parameters. The below table shows how to decode the payload and parameters.
|Message Fragment Number (always 1 for default configuration)
|Number of Parameter Bytes in this Payload (always 20 for default configuration)
|Total Power Factor
|Maximum Total System Power Demand
Your SDM630MCT-LoRa may have been configured to send different parameters in a different order. If this is the case, you should have received more information about your custom configuration when you ordered your meter.
By default, the SDM630MCT-LoRa will send 5 parameters in a single payload (one message fragment). For non-standard configurations more parameters may be sent in which case the payload may be fragmented across multiple LoRaWAN payloads. Each parameter will always be 4 bytes in length, starting from byte 6 (0-based) and the final 2 bytes of the message will always be a 2 byte Modbus Checksum.
001435FC 01 18 443A424E 40E7A876 42C5DA1D 284F
001435FC 02 18 439449DB 43AEC439 00000000 D821
Updated on: 05/06/2023