Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 229.14
edited by Mengting Qiu
on 2025/06/16 09:19
Change comment: There is no comment for this version
To version 228.1
edited by Mengting Qiu
on 2025/06/16 08:50
Change comment: Uploaded new attachment "1750035004731-376.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1028,33 +1028,19 @@
1028 1028  
1029 1029  
1030 1030  Firstly, it is recommended that users upgrade the firmware of the -NB node to the latest version, as the processing method for downlink commands varies depending on the firmware version. Below, we will introduce the latest downlink command format.
1031 +(% style="color:red" %)**Note: **
1031 1031  
1032 1032  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1033 1033  === **UDP Protocol:** ===
1034 1034  
1035 -Only supports valid **HEX-format downlink commands** corresponding to AT command.
1036 +Only supports valid **HEX-format downlink commands** corresponding to AT command
1036 1036  
1037 -Take the AT+TDC command of S31-NB as an example, that is, only the valid HEX format downstream command corresponding to the AT+TDC command can be used:
1038 -Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1039 -
1040 -[[image:1750035991532-434.png||height="237" width="495"]]
1041 -
1042 -
1043 1043  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1044 -=== **MQTT Protocol:** ===
1039 +=== MQTT: ===
1045 1045  
1046 -Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1047 1047  
1048 -//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1042 +Json：
1049 1049  
1050 -* HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1051 -* JSON format: (% style="color:blue" %)**{AT+TDC=900}  **(%%)~/~/ The correct format is (% style="color:blue" %)**{AT Command}**(%%). No extra characters other than valid AT commands can be added within {}.
1052 -
1053 -
1054 -
1055 -**Template for Batch Configuration:**
1056 -
1057 -
1058 1058  The Json format in MQTT mode needs to be configured with all commands.
1059 1059  If you have configurations that need to be changed, please change them in the template below.
1060 1060  Template:
... ... @@ -1092,17 +1092,6 @@
1092 1092  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
1093 1093  
1094 1094  
1095 -(% style="color:red" %)**Note:**
1096 -
1097 -(% style="color:red" %)**1. Only when the correct and valid download command is used and the format is correct can the device be configured through the download command. Invalid download content cannot be processed by the device and will be automatically restarted.**
1098 -
1099 -(% style="color:red" %)**2. Devices designed with downlink commands can utilize different downlink formats (e.g., JSON or HEX) for configuration. However, regardless of the format, the functionality is strictly limited to the downlink command specifications described in the user manual's AT command explanation.**
1100 -
1101 -(% style="color:red" %)**For example, the HEX-format downlink command corresponding to AT+TDC can only be used to configure TDC and cannot be used for queries. There is no HEX-format downlink command equivalent to AT+TDC=? , so querying TDC via downlink is not supported.**
1102 -
1103 -[[image:1750035004731-376.png||height="276" width="557"]]
1104 -
1105 -
1106 1106  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1107 1107  
1108 1108  
1750035991532-434.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.4 KB
Content