Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:49
From version 143.1
edited by Mengting Qiu
on 2025/06/18 15:53
Change comment: There is no comment for this version
To version 144.12
edited by Mengting Qiu
on 2025/07/03 18:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1013,11 +1013,14 @@
1013 1013  
1014 1014  === **MQTT Protocol:** ===
1015 1015  
1016 -Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1016 +==== **1. HEX-format** ====
1017 1017  
1018 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1019 +
1018 1018  //Example~:// For the S31-CB's uplink interval modification (AT+TDC=900):
1019 1019  
1020 -* HEX format: (% 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 +
1021 1021  * 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 1022  
1023 1023  (% style="color:red" %)**Note:**
... ... @@ -1029,11 +1029,17 @@
1029 1029  (% 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  
1031 1031  
1032 -**Template for Batch Configuration:**
1035 +==== **2. JSON-format ** ====
1033 1033  
1034 -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.
1035 -Template:
1037 +===== **2. 1 JSON format template.** =====
1036 1036  
1039 +All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1040 +
1041 +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.
1042 +Template.
1043 +
1044 +Take the template of DDS75-CB as an example:
1045 +
1037 1037  {
1038 1038  "AT+SERVADDR":"119.91.62.30,1882",
1039 1039  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1046,17 +1046,22 @@
1046 1046  "AT+APN":"NULL",
1047 1047  "AT+5VT":"0",
1048 1048  "AT+PRO":"3,5",
1049 -"AT+TR":"900",
1050 -"AT+NOUD":"0",
1058 +"AT+TR":"15",
1059 +"AT+NOUD":"8",
1051 1051  "AT+CSQTIME":"5",
1052 -"AT+DNSTIMER":"0",
1061 +"AT+GDNS":"0",
1053 1053  "AT+TLSMOD":"0,0",
1054 1054  "AT+MQOS":"0",
1055 -"AT+TEMPALARM1":"0",
1056 -"AT+TEMPALARM2":"10",
1057 -"AT+TEMPALARM3":"0"
1064 +"AT+IPTYPE":"0",
1065 +"AT+GTDC":"0",
1066 +"AT+GNSST":"10",
1067 +"AT+GPS":"0"
1058 1058  }
1059 1059  
1070 +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.
1071 +
1072 +[[image:1751538862245-924.png]]
1073 +
1060 1060  **Instructions for Using the Template:**
1061 1061  
1062 1062  1. Modify the parameters for each AT command in the template as needed.
... ... @@ -1069,6 +1069,15 @@
1069 1069  
1070 1070  
1071 1071  
1086 +===== **2.2 Support sending json format commands separately** =====
1087 +
1088 +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**
1089 +
1090 +//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
1091 +
1092 +
1093 +
1094 +
1072 1072  == 7.4 What if the signal is good but the domain name resolution fails? ==
1073 1073  
1074 1074  
1751538862245-924.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +114.7 KB
Content