Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 229.6
edited by Mengting Qiu
on 2025/06/16 09:13
Change comment: There is no comment for this version
To version 232.2
edited by Mengting Qiu
on 2025/07/03 18:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1043,17 +1043,28 @@
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  
1052 +* HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1050 1050  
1051 -Json：
1054 +[[image:1750035004731-376.png||height="276" width="557"]]
1052 1052  
1053 -The Json format in MQTT mode needs to be configured with all commands.
1054 -If you have configurations that need to be changed, please change them in the template below.
1055 -Template:
1056 1056  
1057 +==== **2. JSON-format ** ====
1058 +
1059 +===== **2. 1 JSON format template.** =====
1060 +
1061 +All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1062 +
1063 +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.
1064 +Template.
1065 +
1066 +Take the template of D2x-CB as an example:
1067 +
1057 1057  {
1058 1058  "AT+SERVADDR":"119.91.62.30,1882",
1059 1059  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1077,18 +1077,33 @@
1077 1077  "AT+TEMPALARM3":"0"
1078 1078  }
1079 1079  
1080 -Hex：
1091 +Explanations of two special commands in the template: AT+TR (set the detection interval: 0 ~~ 255 minutes) and AT+NOUD (set the number of groups) correspond to parameters in AT+CLOCKLOG.
1081 1081  
1082 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1093 +[[image:1751538862245-924.png]]
1083 1083  
1084 -The supported commands are consistent with LoRaWAN's hex commands.
1085 -Please refer to the following link to obtain the hex format:
1086 1086  
1087 -[[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/]]
1096 +**Instructions for Using the Template:**
1088 1088  
1098 +1. Modify the parameters for each AT command in the template as needed.
1099 +1. Send the entire template in one downlink command.
1089 1089  
1090 1090  (% style="color:red" %)**Note:**
1091 1091  
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.
1105 +
1106 +
1107 +
1108 +===== **2.2 Support sending json format commands separately** =====
1109 +
1110 +Some models of nodes support sending json format commands separately：(% style="color:blue" %)**RS485-NB, LDS25-NB, CS01-NB, SDI-12-NB, SW3L-NB, WL03A-NB, PS-NB, LTC2-NB.**
1111 +
1112 +//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
1113 +
1114 +Downlink command:  (% 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 {}.
1115 +
1116 +(% style="color:red" %)**Note:**
1117 +
1092 1092  (% 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.**
1093 1093  
1094 1094  (% 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.**
... ... @@ -1095,9 +1095,7 @@
1095 1095  
1096 1096  (% 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.**
1097 1097  
1098 -[[image:1750035004731-376.png||height="276" width="557"]]
1099 1099  
1100 -
1101 1101  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1102 1102  
1103 1103  
... ... @@ -1158,30 +1158,26 @@
1158 1158  
1159 1159  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:
1160 1160  
1161 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1162 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1163 -**Firmware version**
1164 -
1165 -**(without FDR1 function)**
1166 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1167 -**Firmware version**
1168 -
1169 -**(with FDR1 function)**
1185 +(% border="1" style="background-color:#f2f2f2; width:912px" %)
1186 +|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1187 +**Firmware version (without FDR1 function)**
1188 +)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1189 +**Firmware version (with FDR1 function)**
1170 1170  )))
1171 -|(% style="width:210px" %)(((
1191 +|(% style="width:306px" %)(((
1172 1172  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;
1173 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1174 -|(% style="width:210px" %)(((
1193 +)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1194 +|(% style="width:306px" %)(((
1175 1175  WL03A-NB, SDI-12-NB;
1176 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1196 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1177 1177  After V1.0.8 (including V1.0.2)
1178 1178  )))
1179 -|(% style="width:210px" %)(((
1199 +|(% style="width:306px" %)(((
1180 1180  SW3L-NB, PS-NB;
1181 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1201 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1182 1182  After V1.0.5 (including V1.0.5)
1183 1183  )))
1184 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1204 +|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1185 1185  
1186 1186  === UART connection and firmware update methods ===
1187 1187  
... ... @@ -1239,4 +1239,11 @@
1239 1239  
1240 1240  
1241 1241  
1262 +== 6.8 ==
1263 +
1264 +
1265 +
1266 +
1267 +
1268 +
1242 1242  
1751538862245-924.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +114.7 KB
Content