CMi4160
– LoRaWAN
®
Module
9
02/2021
Field
name
(Abbr.)
Description
Default value
Device
access
Locked device
& correct
Product Access
Key
or
Open device
Device
access
No
Product
Access
Key
Downlink
LoRaWAN
®
settings
Device EUI
Unique module
identification number.
Not configurable.
Device-unique
64-bit number
Readable
Readable
N/A
Activation
type
Sets the way the
device joins the
LoRaWAN
®
network.
OTAA
Readable /
Writeable
Readable
N/A
Network
join
Displays whether the
module has joined the
LoRaWAN
®
network
or not.
N/A
Readable
Readable
N/A
Join EUI
Application ID that
determines where data
ends up.
0x 94 19 3A 03
03 00 00 01
(internal
antenna
version)
0x 94 19 3A 03
04 00 00 01
(external
antenna
version)
Readable /
Writeable
Readable
N/A
Device
address
32-bit address used by
the module to identify
itself on the
LoRaWAN
®
network.
N/A
Readable /
Writeable
N/A
N/A
Current
data rate
The current data rate
used for the module.
N/A
Readable
Readable
N/A
Table 2: Configuration options
6.4
TIME HANDLING
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 OTC App, local standard
time is always used, even if DST is in effect. The timestamped meter data sent from the module can
be adjusted to be sent in UTC by specifying the “UTC offset” configuration parameter. The UTC offset
will be subtracted from the timestamp prior to transmission. If the meter is in Sweden, which uses
CET (Central European Time), it should have UTC offset set to +60 (+1h). In this case at time 12:00
a telegram is sent with timestamp 11:00 as this is the corresponding UTC time. A meter in New York
(USA) should have a UTC offset of -300 (-5h) etc. A UTC offset of 0 means the meter time is used as-
is.
6.5
ADAPTIVE DATA RATE (ADR)
CMi4160 supports Adaptive Data Rate (ADR), part of the
LoRaWAN
®
standard, where the network
server determines the optimal rate of communication for the module based on current signal
conditions. In the best radio conditions, the module will use its highest data rate (DR5) in order to be
as energy efficient as possible. When signal conditions are poor, the network server will incrementally
lower the data rate until it is able to receive the message. When the data rate is low, the energy
consumption per telegram will increase.