Integration Guide

SMK900 Integration Guide Revision 4
are in said air command, which directly correlates with the current number of Broadcast In Phases of
the network (parameter B
I
, see section 2.2).
Note that although is in effect theoretically possible for a node to extrapolate this information by
retrieving the network dynamic configuration parameters, in order to get parameter B
I
instead on
relying on the Phase In Count parameter of this event message, it is not a recommended practice.
Indeed, it would be possible for a network to dynamically change its current dynamic configuration
after the sniffed message arrives, but before the request for fetching the dynamic configuration is sent
(by reading RAM bank register dyn; see section 7.3), thereby creating the low-level equivalent of a
"concurrency atomicity problem". Thus, the Phase In Count parameter is provided to user in order
to ensure atomicity when reading the current Broadcast In Phase count within the dynamic
configuration parameters of the mesh network.
RXBcastOutSnifferAirCmd (event)
Byte offset
Field
Description
0x00
Start-of-Packet
0xFB = Indicates start of protocol formatted message
0x01 - 0x02
Length
0x?? 0x?? = Number of bytes in message following this byte (Little-Endian)
0x03
Packet Type
0x2C = RXBcastOutSnifferAirCmd
0x04
Broadcast Phase ID
0x00-0x03 = Received packet Broadcast Phase ID
0x05
RSSI
0x00-0xFF = Received packet strength
0x06
Phase In Count
0x01-0x04 = Number of Broadcast In Phases at sniffed message reception
0x07 - …
Payload
Up to 20 bytes of data at 50kbit/sec, 72 bytes of data at 100kbit/sec
DynConfig
This is the main command for changing the dynamic configuration of a network, and can only be
sent to a transceiver set as a gateway. After this command is sent, a reply will acknowledge the
change request immediately if said request is valid (via a DynConfigReply message), and those
changes will be applied to the gateway mesh configuration at the beginning of the next broadcast
cycle (see section 2.2 for details about broadcast cycles, and for details about the DYN parameters),
or will return an error event message if the set of DYN parameters is deemed invalid. Note that the
new set of DYN parameters are then subsequently flooded to the whole of the mesh network via a
gateway broadcast out packet.
DynConfig (command)
Byte offset
Field
Description
0x00
Start-of-Packet
0xFB = Indicates start of protocol formatted message
0x01 - 0x02
Length
0x07 0x00 = Number of bytes in message following this byte (Little-Endian)
0x03
Packet Type
0x0A = DynConfig
0x04
Phase Out Count
0x01-0x04 = Number of Broadcast Out Phases
0x05
Phase In Count
0x01-0x04 = Number of Broadcast In Phases
0x06
NumSeq
0x01-0x1F = Number of sequence slots (repeater hop count for mesh network)
0x07
NumSeqRedux
0x01 = Numer of sequence slots for redux phase (for the current firmware
version, only 1 value is supported)
0x08
ReduxEnableFlag
0x00-0x01 = Redux phase enable flag
0x09
DutyCycleDiv
0x01, 0x02, 0x05, 0x0A, 0x014, 0x28, 0x50 = Duty Cycle inverted
DynConfigReply
This is the reply message corresponding to gateway command DynConfig, and is sent from gateway
transceiver back to its host if the requested DYN configuration changes are deemed valid.
DynConfigReply (reply)
Byte offset
Field
Description
27