Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:49
From version 144.9
edited by Mengting Qiu
on 2025/07/03 18:37
Change comment: There is no comment for this version
To version 145.1
edited by Mengting Qiu
on 2025/07/03 18:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1019,21 +1019,12 @@
1019 1019  
1020 1020  //Example~:// For the S31-CB's uplink interval modification (AT+TDC=900):
1021 1021  
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 {}.
1022 +Downlink command: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1024 1024  
1025 -(% style="color:red" %)**Note:**
1026 1026  
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.**
1028 -
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.**
1030 -
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.**
1032 -
1033 -
1034 1034  ==== **2. JSON-format ** ====
1035 1035  
1036 -**2.**
1027 +===== **2. 1 JSON format template.** =====
1037 1037  
1038 1038  All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1039 1039  
... ... @@ -1082,12 +1082,23 @@
1082 1082  
1083 1083  
1084 1084  
1076 +===== **2.2 Support sending json format commands separately** =====
1085 1085  
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**
1086 1086  
1080 +//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
1087 1087  
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 {}.
1088 1088  
1084 +(% style="color:red" %)**Note:**
1089 1089  
1086 +(% 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.**
1090 1090  
1088 +(% 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.**
1089 +
1090 +(% 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.**
1091 +
1092 +
1091 1091  == 7.4 What if the signal is good but the domain name resolution fails? ==
1092 1092  
1093 1093