Advertisement
Documentation Center
DTU_CMD
0x03
NOTE
The message length does not contain the header
Example: We will add a polling instruction.
Publish topic:
application/1/device/60c5a8fffe75404b/tx
NOTE
Application ID and Device EUI should be consistent with the settings within the gateway.
To successfully complete this, the JSON data format must be followed.
Content of the uplink:
{
"confirmed":true,
"fPort":129,
"data":"030001000901010300000002C40B"
}
Parameter
"confirmed":true
"fPort":129
"data":"030001000901010300000002C40B"
The content of the data that we will send is:
1. DTU command word
MSER
MDATA_LEN
2Byte
2Byte
Description
This indicates that the downlink to the RAK7431 will be
confirmed for successful receiving.
Defines the port that we want to send the command. (For
more information on the fPort see the
Manual
The data of the task in hexadecimal format.
Figure 23: Data arrangement
TASK_ID
1Byte
for RAK7431)
MDATA
DATA
nByte
sh
sh
AT Command
Advertisement
