Last modified by Mengting Qiu on 2025/07/17 10:51
From version 228.4
edited by Mengting Qiu
on 2025/06/16 08:57
on 2025/06/16 08:57
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Xiaoling - Content
-
... ... @@ -1028,29 +1028,42 @@ 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:** 1032 1032 1033 -(% 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.** 1032 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1033 +=== **UDP Protocol:** === 1034 1034 1035 - (%style="color:red"%)**2.**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. 1037 1037 1038 -[[image:1750035 004731-376.png]]1040 +[[image:1750035991532-434.png||height="237" width="495"]] 1039 1039 1040 1040 1041 -(% data-sider-select-id=" bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)1042 -=== ** UDPProtocol:** ===1043 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1044 +=== **MQTT Protocol:** === 1043 1043 1044 - Only supportsvalid **HEX-format**corresponding to AT command1046 +Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands). 1045 1045 1046 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1047 -=== MQTT: === 1048 +//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900): 1048 1048 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 {}. 1049 1049 1050 - Json:1053 +(% style="color:red" %)**Note:** 1051 1051 1052 -The Json format in MQTT mode needs to be configured with all commands. 1053 -If you have configurations that need to be changed, please change them in the template below. 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. 1054 1054 Template: 1055 1055 1056 1056 { ... ... @@ -1076,16 +1076,18 @@ 1076 1076 "AT+TEMPALARM3":"0" 1077 1077 } 1078 1078 1079 - Hex:1092 +**Instructions for Using the Template:** 1080 1080 1081 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported. 1094 +1. Modify the parameters for each AT command in the template as needed. 1095 +1. Send the entire template in one downlink command. 1082 1082 1083 -The supported commands are consistent with LoRaWAN's hex commands. 1084 -Please refer to the following link to obtain the hex format: 1097 +(% style="color:red" %)**Note:** 1085 1085 1086 -[[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/]] 1099 +* The template may vary depending on the device model. 1100 +* **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>>url:https://mailto:support@dragino.com/]] to request the latest downlink template. 1087 1087 1088 1088 1103 + 1089 1089 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) == 1090 1090 1091 1091 ... ... @@ -1146,30 +1146,26 @@ 1146 1146 1147 1147 We are now dividing the **old firmware**(without FDR1 function) with the **new firmware**(with FDR1 function) by whether it contains FDR1 functionality. Please refer to the table: 1148 1148 1149 -(% border="1" style="background-color:#f2f2f2; width:510px" %) 1150 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)((( 1151 -**Firmware version** 1152 - 1153 -**(without FDR1 function)** 1154 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)((( 1155 -**Firmware version** 1156 - 1157 -**(with FDR1 function)** 1164 +(% border="1" style="background-color:#f2f2f2; width:814px" %) 1165 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:313px" %)((( 1166 +**Firmware version (without FDR1 function)** 1167 +)))|(% style="background-color:#4f81bd; color:white; width:286px" %)((( 1168 +**Firmware version (with FDR1 function)** 1158 1158 ))) 1159 1159 |(% style="width:210px" %)((( 1160 1160 CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB, MDS200-NB, SE01-NB, SPH01-NB; 1161 -)))|(% style="width:1 50px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)1172 +)))|(% style="width:313px" %)Before V1.2.1|(% style="width:286px" %)After V1.2.1 (including V1.2.1) 1162 1162 |(% style="width:210px" %)((( 1163 1163 WL03A-NB, SDI-12-NB; 1164 -)))|(% style="width:1 50px" %)Before V1.0.2|(% style="width:150px" %)(((1175 +)))|(% style="width:313px" %)Before V1.0.2|(% style="width:286px" %)((( 1165 1165 After V1.0.8 (including V1.0.2) 1166 1166 ))) 1167 1167 |(% style="width:210px" %)((( 1168 1168 SW3L-NB, PS-NB; 1169 -)))|(% style="width:1 50px" %)Before V1.0.5|(% style="width:150px" %)(((1180 +)))|(% style="width:313px" %)Before V1.0.5|(% style="width:286px" %)((( 1170 1170 After V1.0.5 (including V1.0.5) 1171 1171 ))) 1172 -|(% style="width:210px" %)RS485-NB|(% style="width:1 50px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)1183 +|(% style="width:210px" %)RS485-NB|(% style="width:313px" %)Before V1.0.8|(% style="width:286px" %)After V1.0.8 (including V1.0.8) 1173 1173 1174 1174 === UART connection and firmware update methods === 1175 1175
- 1750035991532-434.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.ting - Size
-
... ... @@ -1,0 +1,1 @@ 1 +54.4 KB - Content