Changes for page General Manual for -CB , -CS models
Last modified by Mengting Qiu on 2025/07/03 18:49
From version 143.3
edited by Mengting Qiu
on 2025/07/03 18:27
on 2025/07/03 18:27
Change comment:
There is no comment for this version
To version 146.2
edited by Mengting Qiu
on 2025/07/03 18:48
on 2025/07/03 18:48
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1019,26 +1019,22 @@ 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:**1024 +[[image:1750035004731-376.png||height="276" width="557"]] 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 1028 1029 - (% style="color:red"%)**2.Devices designed with downlink commands can utilize different downlink formats (e.g.,JSONor HEX)forconfiguration. However, regardless of the format,the functionality is strictly limited to the downlink command specifications described in the user manual's AT command explanation.**1027 +==== **2. JSON-format ** ==== 1030 1030 1031 - (% style="color:red"%)**Forexample,theHEX-formatdownlink command correspondingto AT+TDC can only beused to configure TDC and cannot be used for queries. There is no HEX-format downlink command equivalentto AT+TDC=? , so querying TDC via downlink is not supported.**1029 +===== **2. 1 JSON format template.** ===== 1032 1032 1031 +All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.** 1033 1033 1033 +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. 1034 +Template. 1034 1034 1035 - 2. **JSON-format**a1036 +Take the template of DDS75-CB as an example: 1036 1036 1037 -**Template for Batch Configuration:** 1038 - 1039 -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. 1040 -Template: 1041 - 1042 1042 { 1043 1043 "AT+SERVADDR":"119.91.62.30,1882", 1044 1044 "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs", ... ... @@ -1051,17 +1051,22 @@ 1051 1051 "AT+APN":"NULL", 1052 1052 "AT+5VT":"0", 1053 1053 "AT+PRO":"3,5", 1054 -"AT+TR":" 900",1055 -"AT+NOUD":" 0",1050 +"AT+TR":"15", 1051 +"AT+NOUD":"8", 1056 1056 "AT+CSQTIME":"5", 1057 -"AT+DNS TIMER":"0",1053 +"AT+GDNS":"0", 1058 1058 "AT+TLSMOD":"0,0", 1059 1059 "AT+MQOS":"0", 1060 -"AT+TEMPALARM1":"0", 1061 -"AT+TEMPALARM2":"10", 1062 -"AT+TEMPALARM3":"0" 1056 +"AT+IPTYPE":"0", 1057 +"AT+GTDC":"0", 1058 +"AT+GNSST":"10", 1059 +"AT+GPS":"0" 1063 1063 } 1064 1064 1062 +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. 1063 + 1064 +[[image:1751538862245-924.png]] 1065 + 1065 1065 **Instructions for Using the Template:** 1066 1066 1067 1067 1. Modify the parameters for each AT command in the template as needed. ... ... @@ -1074,6 +1074,23 @@ 1074 1074 1075 1075 1076 1076 1078 +===== **2.2 Support sending json format commands separately** ===== 1079 + 1080 +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** 1081 + 1082 +//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900): 1083 + 1084 +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 {}. 1085 + 1086 +(% style="color:red" %)**Note:** 1087 + 1088 +(% 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.** 1089 + 1090 +(% 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.** 1091 + 1092 +(% 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.** 1093 + 1094 + 1077 1077 == 7.4 What if the signal is good but the domain name resolution fails? == 1078 1078 1079 1079
- 1750035004731-376.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.ting - Size
-
... ... @@ -1,0 +1,1 @@ 1 +48.8 KB - Content
- 1751538862245-924.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.ting - Size
-
... ... @@ -1,0 +1,1 @@ 1 +114.7 KB - Content