Last modified by Mengting Qiu on 2025/07/17 10:51

From version 229.18
edited by Mengting Qiu
on 2025/06/16 09:27
Change comment: There is no comment for this version
To version 226.1
edited by Mengting Qiu
on 2025/03/08 11:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1024,46 +1024,28 @@
1024 1024  [[image:image-20240226111928-1.png]]
1025 1025  
1026 1026  
1027 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1027 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1028 1028  
1029 1029  
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 -
1032 1032  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1033 -=== **UDP Protocol:** ===
1031 +=== UDP: ===
1034 1034  
1035 -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.
1034 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1035 +Its downlink command is the same as the AT command, but brackets are required.
1036 +Example:
1039 1039  
1040 -[[image:1750035991532-434.png||height="237" width="495"]]
1038 +{AT+TDC=300}
1041 1041  
1042 1042  
1043 1043  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1044 -=== **MQTT Protocol:** ===
1042 +=== 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):
1045 +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 -(% style="color:red" %)**Note:**
1054 -
1055 -(% 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.**
1056 -
1057 -(% 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.**
1058 -
1059 -(% 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.**
1060 -
1061 -[[image:1750035004731-376.png||height="276" width="557"]]
1062 -
1063 -
1064 -**Template for Batch Configuration:**
1065 -
1066 -We can also use templates to configure multiple commands AT once. Users only need to modify the parameters of the required AT commands in the correct template for each device.
1047 +The Json format in MQTT mode needs to be configured with all commands.
1048 +If you have configurations that need to be changed, please change them in the template below.
1067 1067  Template:
1068 1068  
1069 1069  {
... ... @@ -1089,21 +1089,16 @@
1089 1089  "AT+TEMPALARM3":"0"
1090 1090  }
1091 1091  
1092 -**Instructions for Using the Template:**
1074 +Hex:
1093 1093  
1094 -1. Modify the parameters for each AT command in the template as needed.
1095 -1. Send the entire template in one downlink command.
1076 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1096 1096  
1097 -(% style="color:red" %)**Note:**
1078 +The supported commands are consistent with LoRaWAN's hex commands.
1079 +Please refer to the following link to obtain the hex format:
1098 1098  
1099 -**Note:**
1081 +[[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/]]
1100 1100  
1101 -* The template may vary depending on the device model.
1102 -* Currently, each specific template is being updated and tested. If you need a template for your specific device, please contact Dragino Technical Support at support@dragino.com to request the latest downlink template.
1103 1103  
1104 -
1105 -
1106 -
1107 1107  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1108 1108  
1109 1109  
1750035004731-376.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -55.1 KB
Content
1750035991532-434.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.4 KB
Content