Byte 0
Byte 1
Byte 2
Byte 3
WSN802G Protocol Identifier = 0x52464D49
Opcode = 0x0012
Transaction ID = varies
Length
Bank
Location
Value
Figure 4.12.1
The fields specific to this datagram are:
Length:
Total length of the following bank, register and value sections, in bytes
Bank:
Target register bank
Location:
Target register location
Value:
Target register value
IMPORTANT NOTE: The register value must be entered in Little-Endian order, least significant byte first.
The module responds to a CFG_WRITE with a CFG_WRITE_REPLY. Note that the module must be
awake in order to receive and process this command.
4.13 CFG Write Reply
A CFG_WRITE_REPLY datagram is sent by the module to confirm the receipt of a CFG_WRITE
datagram.
Byte 0
Byte 1
Byte 2
Byte 3
WSN802G Protocol Identifier = 0x52464D49
Opcode = 0x0013
Transaction ID = varies
Length
Status
Figure 4.13.1
The fields specific to this datagram are:
Length:
Length of the remainder of the packet in bytes
Status:
Status code: 0 = successful, 1 = failed
4.14 Configuration Parameters
The parameters that can be accessed through the CFG series API commands are detailed below, orga-
nized by bank and location. The default values in Tables 4.14.1 through 4.14.8 are shown as they would
be sent using CFG_WRITE or received using CFG_READ. All numerical values in the tables are in
Little-
Endian
byte order, starting with the least significant byte on the left. ASCII strings holding a representa-
tion of a numerical value, such as the
AutoReportInterval
in Bank 1, Location 2 below, use Little-Endian
byte order. Strings holding text, such as the
SensorName
in Bank 1, Location 1 below, are in reading byte
order, first character on the left, last character on the right.
©2009-2015 by Murata Electronics N.A., Inc.
HN-210D/X, HN-214 D/X Rev. 2.0 01-16-15
Page 24 of 101
www.murata.com
