Integration Guide
SMK900 Integration Guide Revision 4
RXAirCmdWrapper
This event message is a wrapper message for any replies from a node transmitted back to the
gateway of a given mesh network (instead of being transmitted to a host locally connected to that
node via serial communication bus), and thus is the corresponding message to TXAirCmdWrapper
(see section 7.2.22 for details).
This reply message is only applicable for transceivers configured as gateways. If a node needs to sniff
another node answer to an air command previously sent by gateway, then that node needs to use the
event marker RXBcastInSnifferAirDataPacket (with proper concomitant configuration register flag
set).
RXAirCmdWrapper
(event wrapping remote reply)
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
0x2D = RXAirCmdWrapper
0x04
Broadcast Phase ID
0x00-0x03 = Received packet Broadcast Phase ID
0x05
RSSI
0x00-0xFF = Received packet strength
0x06
Wrapped Packet
Type
IF Packet Type byte of corresponding air command has its bit 7 set (i.e. if
bit-masking that byte with 0x80 yields a non-zero result), then:
0x??, which is the reply Packet Type byte matching said air command,
with its bit 7 set also
ELSE:
0x??, which is the regular reply Packet Type byte matching said
air command
0x07 -
(0x07+N-1)
Node MAC
Address
IF Packet Type byte of corresponding air command has its bit 7 set (i.e. if
bit-masking that byte with 0x80 yields a non-zero result), then:
N = M bytes, which are the M MAC address bytes for the node
answering said air command
ELSE:
N = 0 bytes
(0x07+N) - …
Wrapped Partial
Payload
Wrapped message, with Start-of-Packet & Length word & Wrapped Packet Type
byte of that wrapped reply message removed
Configuration Registers
There are three configuration parameter banks: the TMP bank (also called RAMBUF), RAM bank, and
EEPROM bank. The EEPROM allows a configuration that must stick through radio module reset or
power-down to be stored in non-volatile memory. The RAM bank is copied from the EEPROM bank at
boot-up, and is the main bank used by the mesh controller itself for its operations within its mesh network.
To control the mesh configuration registers, the SMK900 must be in protocol-formated mode. All three
banks can be read via GetRegister command. Write operations (SetRegister) are only allowed to the TMP
bank, and only to those registers. The proper procedure to change mesh configuration register, containing
critical parameters such as the NwkID or the HopTable are changed, is as follows:
1. Set registers in TMP bank to the desired value (using SetRegister command);
2. Transfer TMP bank to EEPROM bank (using TransferConfig command);
3. Reset the module to activate the changes into RAM bank (using DeviceReset command).
Here is a table summarizing the configuration parameter registers available to the user:
31