Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 231.4
edited by Mengting Qiu
on 2025/07/03 18:48
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
... ... @@ -1050,16 +1050,7 @@
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 {}.
1054 1054  
1055 -(% style="color:red" %)**Note:**
1056 -
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.**
1058 -
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.**
1060 -
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 -
1063 1063  [[image:1750035004731-376.png||height="276" width="557"]]
1064 1064  
1065 1065  
... ... @@ -1072,14 +1072,8 @@
1072 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 1073  Template.
1074 1074  
1075 -Take the template of DDS75-CB as an example:
1066 +Take the template of D2x-CB as an example:
1076 1076  
1077 -
1078 -**Template for Batch Configuration:**
1079 -
1080 -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.
1081 -Template:
1082 -
1083 1083  {
1084 1084  "AT+SERVADDR":"119.91.62.30,1882",
1085 1085  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1103,6 +1103,11 @@
1103 1103  "AT+TEMPALARM3":"0"
1104 1104  }
1105 1105  
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 +
1106 1106  **Instructions for Using the Template:**
1107 1107  
1108 1108  1. Modify the parameters for each AT command in the template as needed.
... ... @@ -1115,6 +1115,23 @@
1115 1115  
1116 1116  
1117 1117  
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 +
1118 1118  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1119 1119  
1120 1120  
1751538862245-924.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +114.7 KB
Content