Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 231.5
edited by Mengting Qiu
on 2025/07/03 18:50
Change comment: There is no comment for this version
To version 220.2
edited by Xiaoling
on 2024/12/31 15:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -602,17 +602,26 @@
602 602  Note:The port for the COAP protocol has been fixed to 5683
603 603  
604 604  
605 -* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
605 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
606 606  
607 --NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
607 +If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
608 608  
609 609  e.g.
610 610  
611 -* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
611 +* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 612  
613 613  [[image:image-20240729172415-13.png||height="401" width="694"]]
614 614  
615 +If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
615 615  
617 +e.g.
618 +
619 +* AT+URL1=11, "i"
620 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
621 +
622 +[[image:image-20240729172500-14.png||height="403" width="700"]]
623 +
624 +
616 616  == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
617 617  
618 618  === 3.8.1 Create device & Get Credentials ===
... ... @@ -845,7 +845,7 @@
845 845  * (% style="color:#037691" %)**AT+CLIENT=NULL**
846 846  * (% style="color:#037691" %)**AT+UNAME=NULL**
847 847  * (% style="color:#037691" %)**AT+PWD=NULL**
848 -* (% style="color:#037691" %)**AT+TLSMOD=1,2**
857 +* (% style="color:#037691" %)**AT+TLSMOD=1,0**
849 849  
850 850  Test Uplink by click the button for 1~~3 seconds, the MQTT integration in ThingsEye allows you to view the data upstream from the device:
851 851  
... ... @@ -1024,56 +1024,30 @@
1024 1024  [[image:image-20240226111928-1.png]]
1025 1025  
1026 1026  
1027 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1036 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1028 1028  
1029 1029  
1030 -Firstly, it is recommended that users upgrade the firmware of the -NB node to the latest version, as the processing method for downlink commands varies depending on the firmware version. Below, we will introduce the latest downlink command format.
1031 -
1032 1032  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1033 -=== **UDP Protocol:** ===
1040 +=== UDP: ===
1034 1034  
1035 -Only supports valid **HEX-format downlink commands** corresponding to AT command.
1036 1036  
1037 -Take the AT+TDC command of S31-NB as an example, that is, only the valid HEX format downstream command corresponding to the AT+TDC command can be used:
1038 -Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1043 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1044 +Its downlink command is the same as the AT command, but brackets are required.
1045 +Example:
1039 1039  
1040 -[[image:1750035991532-434.png||height="237" width="495"]]
1047 +{AT+TDC=300}
1041 1041  
1042 1042  
1043 1043  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1044 -=== **MQTT Protocol:** ===
1051 +=== MQTT: ===
1045 1045  
1046 -==== **1. HEX-format** ====
1047 1047  
1048 -Supports **HEX-format** downlink commands (corresponding to AT commands).
1054 +Json：
1049 1049  
1050 -//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1056 +The Json format in MQTT mode needs to be configured with all commands.
1057 +If you have configurations that need to be changed, please change them in the template below.
1058 +Template:
1051 1051  
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 -
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 -[[image:1750035004731-376.png||height="276" width="557"]]
1064 -
1065 -
1066 -==== **2. JSON-format ** ====
1067 -
1068 -===== **2. 1 JSON format template.** =====
1069 -
1070 -All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1071 -
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 -Template.
1074 -
1075 -Take the template of D2x-CB as an example:
1076 -
1077 1077  {
1078 1078  "AT+SERVADDR":"119.91.62.30,1882",
1079 1079  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1097,73 +1097,26 @@
1097 1097  "AT+TEMPALARM3":"0"
1098 1098  }
1099 1099  
1100 -**Instructions for Using the Template:**
1083 +Hex：
1101 1101  
1102 -1. Modify the parameters for each AT command in the template as needed.
1103 -1. Send the entire template in one downlink command.
1085 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1104 1104  
1105 -(% style="color:red" %)**Note:**
1087 +The supported commands are consistent with LoRaWAN's hex commands.
1088 +Please refer to the following link to obtain the hex format:
1106 1106  
1107 -* The template may vary depending on the device model.
1108 -* **Currently, each specific template is being updated and tested**. If you need a template for your specific device, please contact **Dragino Technical Support** at [[support@dragino.com>>url:https://mailto:support@dragino.com/]] to request the latest downlink template.
1090 +[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
1109 1109  
1110 -===== **2.2 Support sending json format commands separately** =====
1111 1111  
1112 -Some models of nodes support sending json format commands separately：**RS485-CB, LDS25-CB, CS01-CB, SDI-12-CB, SW3L-CB, WL03A-CB, PS-CB**
1093 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1113 1113  
1114 -//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
1115 1115  
1116 -Downlink command:  **{AT+TDC=900}       **~/~/ The correct format is **{AT Command}**. No extra characters other than valid AT commands can be added within {}.
1096 +* **AT Command: AT** **+GETLOG**
1117 1117  
1118 -(% style="color:red" %)**Note:**
1098 +This command can be used to query upstream logs of data packets.
1119 1119  
1100 +[[image:image-20240701114700-1.png]]
1120 1120  
1121 -(% 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.**
1122 1122  
1123 -(% 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.**
1124 -
1125 -(% 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.**
1126 -
1127 -
1128 -
1129 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1130 -
1131 -
1132 -If user is not able to solve the connection issue, user can use below method and get the device log and send to Dragino (Support@dragino.cc) for further analyze.
1133 -
1134 -
1135 -(% class="lead" %)
1136 -Step1: Use Mobile Phone to connect device
1137 -
1138 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1139 -
1140 -
1141 -(% class="lead" %)
1142 -Step2: Get Log by different commands.
1143 -
1144 -Use below three method to generate logs.
1145 -
1146 -* **AT+CFG       ~-~-> Command to show the current configuration**
1147 -* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1148 -* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1149 -
1150 -Above are the output example for about three action:
1151 -
1152 -[[image:image-20250121235119-1.png||height="493" width="455"]]
1153 -
1154 -[[image:image-20240207002129-2.png]]
1155 -
1156 -
1157 -(% class="lead" %)
1158 -Step3: Export Log
1159 -
1160 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155425-16.png?width=330&height=85&rev=1.1||alt="image-20241230155425-16.png" height="85" width="330"]]
1161 -
1162 -select the log you want to export, then click the share icon on the far right to enter the document that comes with your phone and choose to export it.
1163 -
1164 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155528-17.png?width=327&height=324&rev=1.1||alt="image-20241230155528-17.png" height="324" width="327"]]
1165 -
1166 -
1167 1167  == 6.7 How to find the AT Command Password if lost? ==
1168 1168  
1169 1169  
... ... @@ -1181,32 +1181,38 @@
1181 1181  * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1182 1182  * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1183 1183  
1120 +
1184 1184  === Version Confirmation ===
1185 1185  
1186 1186  
1187 1187  We are now dividing the **old firmware**(without FDR1 function) with the **new firmware**(with FDR1 function) by whether it contains FDR1 functionality. Please refer to the table:
1188 1188  
1189 -(% border="1" style="background-color:#f2f2f2; width:912px" %)
1190 -|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1191 -**Firmware version (without FDR1 function)**
1192 -)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1193 -**Firmware version (with FDR1 function)**
1126 +(% border="1" style="background-color:#f2f2f2; width:510px" %)
1127 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1128 +**Firmware version**
1129 +
1130 +**(without FDR1 function)**
1131 +)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1132 +**Firmware version**
1133 +
1134 +**(with FDR1 function)**
1194 1194  )))
1195 -|(% style="width:306px" %)(((
1136 +|(% style="width:210px" %)(((
1196 1196  CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB,  MDS200-NB, SE01-NB, SPH01-NB;
1197 -)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1198 -|(% style="width:306px" %)(((
1138 +)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1139 +|(% style="width:210px" %)(((
1199 1199  WL03A-NB, SDI-12-NB;
1200 -)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1141 +)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1201 1201  After V1.0.8 (including V1.0.2)
1202 1202  )))
1203 -|(% style="width:306px" %)(((
1144 +|(% style="width:210px" %)(((
1204 1204  SW3L-NB, PS-NB;
1205 -)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1146 +)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1206 1206  After V1.0.5 (including V1.0.5)
1207 1207  )))
1208 -|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1149 +|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1209 1209  
1151 +
1210 1210  === UART connection and firmware update methods ===
1211 1211  
1212 1212  
... ... @@ -1263,11 +1263,4 @@
1263 1263  
1264 1264  
1265 1265  
1266 -== 6.8 ==
1267 -
1268 -
1269 -
1270 -
1271 -
1272 -
1273 1273  
1750035004731-376.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -55.1 KB
Content
1750035991532-434.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.4 KB
Content
image-20250121235119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -145.4 KB
Content