Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 231.5
edited by Mengting Qiu
on 2025/07/03 18:50
Change comment: There is no comment for this version
To version 230.1
edited by Mengting Qiu
on 2025/06/16 09:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1043,14 +1043,12 @@
1043 1043  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1044 1044  === **MQTT Protocol:** ===
1045 1045  
1046 -==== **1. HEX-format** ====
1046 +Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1047 1047  
1048 -Supports **HEX-format** downlink commands (corresponding to AT commands).
1049 -
1050 1050  //Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1051 1051  
1052 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 {}.
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 {}.
1054 1054  
1055 1055  (% style="color:red" %)**Note:**
1056 1056  
... ... @@ -1063,17 +1063,11 @@
1063 1063  [[image:1750035004731-376.png||height="276" width="557"]]
1064 1064  
1065 1065  
1066 -==== **2. JSON-format ** ====
1064 +**Template for Batch Configuration:**
1067 1067  
1068 -===== **2. 1 JSON format template.** =====
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.
1067 +Template:
1069 1069  
1070 -All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1071 -
1072 -We can 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.
1073 -Template.
1074 -
1075 -Take the template of D2x-CB as an example:
1076 -
1077 1077  {
1078 1078  "AT+SERVADDR":"119.91.62.30,1882",
1079 1079  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1107,25 +1107,8 @@
1107 1107  * The template may vary depending on the device model.
1108 1108  * **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.
1109 1109  
1110 -===== **2.2 Support sending json format commands separately** =====
1111 1111  
1112 -Some models of nodes support sending json format commands separately：**RS485-CB, LDS25-CB, CS01-CB, SDI-12-CB, SW3L-CB, WL03A-CB, PS-CB**
1113 1113  
1114 -//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
1115 -
1116 -Downlink command:  **{AT+TDC=900}       **~/~/ The correct format is **{AT Command}**. No extra characters other than valid AT commands can be added within {}.
1117 -
1118 -(% style="color:red" %)**Note:**
1119 -
1120 -
1121 -(% 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.**
1122 -
1123 -(% 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.**
1124 -
1125 -(% 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.**
1126 -
1127 -
1128 -
1129 1129  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1130 1130  
1131 1131  
... ... @@ -1186,26 +1186,30 @@
1186 1186  
1187 1187  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:
1188 1188  
1189 -(% border="1" style="background-color:#f2f2f2; width:912px" %)
1190 -|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1191 -**Firmware version (without FDR1 function)**
1192 -)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1193 -**Firmware version (with FDR1 function)**
1164 +(% border="1" style="background-color:#f2f2f2; width:510px" %)
1165 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1166 +**Firmware version**
1167 +
1168 +**(without FDR1 function)**
1169 +)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1170 +**Firmware version**
1171 +
1172 +**(with FDR1 function)**
1194 1194  )))
1195 -|(% style="width:306px" %)(((
1174 +|(% style="width:210px" %)(((
1196 1196  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;
1197 -)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1198 -|(% style="width:306px" %)(((
1176 +)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1177 +|(% style="width:210px" %)(((
1199 1199  WL03A-NB, SDI-12-NB;
1200 -)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1179 +)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1201 1201  After V1.0.8 (including V1.0.2)
1202 1202  )))
1203 -|(% style="width:306px" %)(((
1182 +|(% style="width:210px" %)(((
1204 1204  SW3L-NB, PS-NB;
1205 -)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1184 +)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1206 1206  After V1.0.5 (including V1.0.5)
1207 1207  )))
1208 -|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1187 +|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1209 1209  
1210 1210  === UART connection and firmware update methods ===
1211 1211  
... ... @@ -1263,11 +1263,4 @@
1263 1263  
1264 1264  
1265 1265  
1266 -== 6.8 ==
1267 -
1268 -
1269 -
1270 -
1271 -
1272 -
1273 1273