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

Summary

Details

Page properties
Content
... ... @@ -1043,21 +1043,37 @@
1043 1043  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1044 1044  === **MQTT Protocol:** ===
1045 1045  
1046 -Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1046 +==== **1. HEX-format** ====
1047 1047  
1048 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1049 +
1048 1048  //Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
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:
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 {}.
1052 1052  
1055 +(% style="color:red" %)**Note:**
1053 1053  
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.**
1054 1054  
1055 -Json：
1059 +(% 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.**
1056 1056  
1057 -The Json format in MQTT mode needs to be configured with all commands.
1058 -If you have configurations that need to be changed, please change them in the template below.
1059 -Template:
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.**
1060 1060  
1063 +[[image:1750035004731-376.png||height="276" width="557"]]
1064 +
1065 +
1066 +==== **2. JSON-format ** ====
1067 +
1068 +===== **2. 1 JSON format template.** =====
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 +
1061 1061  {
1062 1062  "AT+SERVADDR":"119.91.62.30,1882",
1063 1063  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1081,18 +1081,27 @@
1081 1081  "AT+TEMPALARM3":"0"
1082 1082  }
1083 1083  
1084 -Hex：
1100 +**Instructions for Using the Template:**
1085 1085  
1086 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1102 +1. Modify the parameters for each AT command in the template as needed.
1103 +1. Send the entire template in one downlink command.
1087 1087  
1088 -The supported commands are consistent with LoRaWAN's hex commands.
1089 -Please refer to the following link to obtain the hex format:
1105 +(% style="color:red" %)**Note:**
1090 1090  
1091 -[[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/]]
1107 +* The template may vary depending on the device model.
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.
1092 1092  
1110 +===== **2.2 Support sending json format commands separately** =====
1093 1093  
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 +
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 +
1094 1094  (% style="color:red" %)**Note:**
1095 1095  
1120 +
1096 1096  (% 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.**
1097 1097  
1098 1098  (% 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.**
... ... @@ -1099,7 +1099,6 @@
1099 1099  
1100 1100  (% 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.**
1101 1101  
1102 -[[image:1750035004731-376.png||height="276" width="557"]]
1103 1103  
1104 1104  
1105 1105  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
... ... @@ -1162,30 +1162,26 @@
1162 1162  
1163 1163  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:
1164 1164  
1165 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1166 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1167 -**Firmware version**
1168 -
1169 -**(without FDR1 function)**
1170 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1171 -**Firmware version**
1172 -
1173 -**(with FDR1 function)**
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)**
1174 1174  )))
1175 -|(% style="width:210px" %)(((
1195 +|(% style="width:306px" %)(((
1176 1176  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;
1177 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1178 -|(% style="width:210px" %)(((
1197 +)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1198 +|(% style="width:306px" %)(((
1179 1179  WL03A-NB, SDI-12-NB;
1180 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1200 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1181 1181  After V1.0.8 (including V1.0.2)
1182 1182  )))
1183 -|(% style="width:210px" %)(((
1203 +|(% style="width:306px" %)(((
1184 1184  SW3L-NB, PS-NB;
1185 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1205 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1186 1186  After V1.0.5 (including V1.0.5)
1187 1187  )))
1188 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1208 +|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1189 1189  
1190 1190  === UART connection and firmware update methods ===
1191 1191  
... ... @@ -1243,4 +1243,11 @@
1243 1243  
1244 1244  
1245 1245  
1266 +== 6.8 ==
1267 +
1268 +
1269 +
1270 +
1271 +
1272 +
1246 1246