Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:49
From version 144.13
edited by Mengting Qiu
on 2025/07/03 18:43
Change comment: There is no comment for this version
To version 144.1
edited by Mengting Qiu
on 2025/07/03 18:34
Change comment: Uploaded new attachment "1751538862245-924.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1019,15 +1019,22 @@
1019 1019  
1020 1020  //Example~:// For the S31-CB's uplink interval modification (AT+TDC=900):
1021 1021  
1022 -Downlink command: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1022 +* HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1023 +* 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 {}.
1023 1023  
1025 +(% style="color:red" %)**Note:**
1024 1024  
1025 -==== **2. JSON-format ** ====
1027 +(% 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.**
1026 1026  
1027 -===== **2. 1 JSON format template.** =====
1029 +(% 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.**
1028 1028  
1029 -All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1031 +(% 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.**
1030 1030  
1033 +
1034 +==== **2. JSON-format ** ====
1035 +
1036 +All -CB nodes support downlink configuration modification using JSON format templates.
1037 +
1031 1031  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.
1032 1032  Template.
1033 1033  
... ... @@ -1057,9 +1057,7 @@
1057 1057  "AT+GPS":"0"
1058 1058  }
1059 1059  
1060 -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.
1061 1061  
1062 -[[image:1751538862245-924.png]]
1063 1063  
1064 1064  **Instructions for Using the Template:**
1065 1065  
... ... @@ -1073,16 +1073,6 @@
1073 1073  
1074 1074  
1075 1075  
1076 -===== **2.2 Support sending json format commands separately** =====
1077 -
1078 -Some models of nodes support sending json format commands separately：(% style="color:blue" %)**RS485-CB, LDS25-CB, CS01-CB, SDI-12-CB, SW3L-CB, WL03A-CB, PS-CB**
1079 -
1080 -//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
1081 -
1082 -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 {}.
1083 -
1084 -
1085 -
1086 1086  == 7.4 What if the signal is good but the domain name resolution fails? ==
1087 1087  
1088 1088