Last modified by Kilight Cao on 2025/07/23 16:27
From version 231.3
edited by Mengting Qiu
on 2025/07/03 18:47
on 2025/07/03 18:47
Change comment:
There is no comment for this version
To version 228.5
edited by Mengting Qiu
on 2025/06/16 09:01
on 2025/06/16 09:01
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1028,30 +1028,6 @@ 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 - 1032 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1033 -=== **UDP Protocol:** === 1034 - 1035 -Only supports valid **HEX-format downlink commands** corresponding to AT command. 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 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1044 -=== **MQTT Protocol:** === 1045 - 1046 -==== **1. HEX-format** ==== 1047 - 1048 -Supports **HEX-format** downlink commands (corresponding to AT commands). 1049 - 1050 -//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900): 1051 - 1052 -* HEX format: (% style="color:blue" %)**01000384**(%%) ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds. 1053 -* 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 {}. 1054 - 1055 1055 (% style="color:red" %)**Note:** 1056 1056 1057 1057 (% 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.** ... ... @@ -1060,14 +1060,23 @@ 1060 1060 1061 1061 (% 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.** 1062 1062 1063 -[[image:1750035004731-376.png||height="276" width="557"]] 1064 1064 1040 +[[image:1750035004731-376.png]] 1065 1065 1066 1066 1043 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1044 +=== **UDP Protocol:** === 1067 1067 1068 -** TemplateforBatch Configuration:**1046 +Only supports valid **HEX-format downlink commands** corresponding to AT command 1069 1069 1070 -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. 1048 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1049 +=== MQTT: === 1050 + 1051 + 1052 +Json: 1053 + 1054 +The Json format in MQTT mode needs to be configured with all commands. 1055 +If you have configurations that need to be changed, please change them in the template below. 1071 1071 Template: 1072 1072 1073 1073 { ... ... @@ -1093,18 +1093,16 @@ 1093 1093 "AT+TEMPALARM3":"0" 1094 1094 } 1095 1095 1096 - **Instructions for Using theTemplate:**1081 +Hex: 1097 1097 1098 -1. Modify the parameters for each AT command in the template as needed. 1099 -1. Send the entire template in one downlink command. 1083 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported. 1100 1100 1101 -(% style="color:red" %)**Note:** 1085 +The supported commands are consistent with LoRaWAN's hex commands. 1086 +Please refer to the following link to obtain the hex format: 1102 1102 1103 -* The template may vary depending on the device model. 1104 -* **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. 1088 +[[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/]] 1105 1105 1106 1106 1107 - 1108 1108 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) == 1109 1109 1110 1110 ... ... @@ -1165,26 +1165,30 @@ 1165 1165 1166 1166 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: 1167 1167 1168 -(% border="1" style="background-color:#f2f2f2; width:912px" %) 1169 -|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)((( 1170 -**Firmware version (without FDR1 function)** 1171 -)))|(% style="background-color:#4f81bd; color:white; width:289px" %)((( 1172 -**Firmware version (with FDR1 function)** 1151 +(% border="1" style="background-color:#f2f2f2; width:510px" %) 1152 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)((( 1153 +**Firmware version** 1154 + 1155 +**(without FDR1 function)** 1156 +)))|(% style="background-color:#4f81bd; color:white; width:150px" %)((( 1157 +**Firmware version** 1158 + 1159 +**(with FDR1 function)** 1173 1173 ))) 1174 -|(% style="width: 306px" %)(((1161 +|(% style="width:210px" %)((( 1175 1175 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; 1176 -)))|(% style="width: 311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)1177 -|(% style="width: 306px" %)(((1163 +)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1) 1164 +|(% style="width:210px" %)((( 1178 1178 WL03A-NB, SDI-12-NB; 1179 -)))|(% style="width: 311px" %)Before V1.0.2|(% style="width:289px" %)(((1166 +)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)((( 1180 1180 After V1.0.8 (including V1.0.2) 1181 1181 ))) 1182 -|(% style="width: 306px" %)(((1169 +|(% style="width:210px" %)((( 1183 1183 SW3L-NB, PS-NB; 1184 -)))|(% style="width: 311px" %)Before V1.0.5|(% style="width:289px" %)(((1171 +)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)((( 1185 1185 After V1.0.5 (including V1.0.5) 1186 1186 ))) 1187 -|(% style="width: 306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)1174 +|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8) 1188 1188 1189 1189 === UART connection and firmware update methods === 1190 1190 ... ... @@ -1242,11 +1242,4 @@ 1242 1242 1243 1243 1244 1244 1245 -== 6.8 == 1246 - 1247 - 1248 - 1249 - 1250 - 1251 - 1252 1252
- 1750035991532-434.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -54.4 KB - Content