Polysense Technologies Co. Ltd. WXS8000 User Manual
User Guide
Revision 0.1
Revision 0.1
XXX-XXXX
Polysense WxS8000 User Guide
Rev 2.3, Mar 26, 2018
Polysense WxS8000 User Guide
Rev 2.3, Mar 26, 2018
Polysense, Inc. Confidential
Page 10
4. WxS8000 Interface with LoRa Server
This chapter defines Polysense WxS8000 interface with LoRa server over the air, the interfaces
include WxS8000 configurations initiated from LoRa server, sensor data report initiated from
WxS8000. The configurations or sensor data report is named as Polysense proprietary messages
which is filled into the FRMPayload in LoRa frame as shown below:
The sensor data in FRMPayload is in binary format
4.1.
Downlink Message
The downlink messages initiated from LoRa server are used to configure WxS8000, including
WxS8000 LoRa mote specific configurations, WxS8000 sensor configurations, etc. All the downlink
messages are unconfirmed even though some messages request WxS8000 to give response.
The message type (MType) in MAC header can be 0x03 (Unconfirmed Data Down) or 0x05
(Confirmed Data Down) depending on LoRa server demand
The FPort in the MACPayload is 251 (reserved FPort in LoRa spec)
For the field in FRMPayload, if its length is 2-byte or 4-byte, then it is in little endian, if its length
is 8-byte (APP_EUI and DEVICE_EUI), then it is in big endian. For example,
o For SCHEDULING_CYCLE whose length is 2-byte, if user wants to configure it as 0x0A, then
in FRMPayload, it must be set as 0A00
o For APP_EUI whose length is 8-byte, if user wants to configure it as 0x11223344, then in
FRMPayload, it must be set as 0000000011223344 (the prefixed zeroes are necessary)
The basic formats of downlink message:
o Format#1
Size (bytes)
1
FRMPayload
CID
o Format#2
Size (bytes)
1
1/4/6/200
FRMPayload
CID
Value
o Format#3
Size (bytes)
1
1
1
0..N
FRMPayload
CID
Attribute
ValueLength
Value