Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 230.2
edited by Xiaoling
on 2025/06/17 15:10
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -1043,29 +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  
1050 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 {}.
1052 1052  
1053 -(% style="color:red" %)**Note:**
1054 +[[image:1750035004731-376.png||height="276" width="557"]]
1054 1054  
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 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.**
1057 +==== **2. JSON-format ** ====
1058 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.**
1059 +===== **2. 1 JSON format template.** =====
1060 1060  
1061 -[[image:1750035004731-376.png||height="276" width="557"]]
1061 +All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1062 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.
1063 1063  
1064 -**Template for Batch Configuration:**
1066 +Take the template of D2x-CB as an example:
1065 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.
1067 -Template:
1068 -
1069 1069  {
1070 1070  "AT+SERVADDR":"119.91.62.30,1882",
1071 1071  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1089,6 +1089,11 @@
1089 1089  "AT+TEMPALARM3":"0"
1090 1090  }
1091 1091  
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.
1092 +
1093 +[[image:1751538862245-924.png]]
1094 +
1095 +
1092 1092  **Instructions for Using the Template:**
1093 1093  
1094 1094  1. Modify the parameters for each AT command in the template as needed.
... ... @@ -1101,6 +1101,23 @@
1101 1101  
1102 1102  
1103 1103  
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 +
1118 +(% 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.**
1119 +
1120 +(% 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.**
1121 +
1122 +(% 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.**
1123 +
1124 +
1104 1104  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1105 1105  
1106 1106  
... ... @@ -1161,26 +1161,26 @@
1161 1161  
1162 1162  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:
1163 1163  
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" %)(((
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" %)(((
1166 1166  **Firmware version (without FDR1 function)**
1167 -)))|(% style="background-color:#4f81bd; color:white; width:286px" %)(((
1188 +)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1168 1168  **Firmware version (with FDR1 function)**
1169 1169  )))
1170 -|(% style="width:210px" %)(((
1191 +|(% style="width:306px" %)(((
1171 1171  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;
1172 -)))|(% style="width:313px" %)Before V1.2.1|(% style="width:286px" %)After V1.2.1 (including V1.2.1)
1173 -|(% 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" %)(((
1174 1174  WL03A-NB, SDI-12-NB;
1175 -)))|(% style="width:313px" %)Before V1.0.2|(% style="width:286px" %)(((
1196 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1176 1176  After V1.0.8 (including V1.0.2)
1177 1177  )))
1178 -|(% style="width:210px" %)(((
1199 +|(% style="width:306px" %)(((
1179 1179  SW3L-NB, PS-NB;
1180 -)))|(% style="width:313px" %)Before V1.0.5|(% style="width:286px" %)(((
1201 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1181 1181  After V1.0.5 (including V1.0.5)
1182 1182  )))
1183 -|(% style="width:210px" %)RS485-NB|(% style="width:313px" %)Before V1.0.8|(% style="width:286px" %)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)
1184 1184  
1185 1185  === UART connection and firmware update methods ===
1186 1186  
... ... @@ -1238,4 +1238,11 @@
1238 1238  
1239 1239  
1240 1240  
1262 +== 6.8 ==
1263 +
1264 +
1265 +
1266 +
1267 +
1268 +
1241 1241  
1751538862245-924.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +114.7 KB
Content