Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 231.4
edited by Mengting Qiu
on 2025/07/03 18:48
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,60 +1024,28 @@
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):
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 DDS75-CB as an example:
1076 -
1077 -
1078 -**Template for Batch Configuration:**
1079 -
1080 -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.
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.
1081 1081  Template:
1082 1082  
1083 1083  {
... ... @@ -1103,56 +1103,26 @@
1103 1103  "AT+TEMPALARM3":"0"
1104 1104  }
1105 1105  
1106 -**Instructions for Using the Template:**
1083 +Hex：
1107 1107  
1108 -1. Modify the parameters for each AT command in the template as needed.
1109 -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.
1110 1110  
1111 -(% 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:
1112 1112  
1113 -* The template may vary depending on the device model.
1114 -* **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/]]
1115 1115  
1116 1116  
1093 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1117 1117  
1118 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1119 1119  
1096 +* **AT Command: AT** **+GETLOG**
1120 1120  
1121 -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.
1098 +This command can be used to query upstream logs of data packets.
1122 1122  
1100 +[[image:image-20240701114700-1.png]]
1123 1123  
1124 -(% class="lead" %)
1125 -Step1: Use Mobile Phone to connect device
1126 1126  
1127 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1128 -
1129 -
1130 -(% class="lead" %)
1131 -Step2: Get Log by different commands.
1132 -
1133 -Use below three method to generate logs.
1134 -
1135 -* **AT+CFG       ~-~-> Command to show the current configuration**
1136 -* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1137 -* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1138 -
1139 -Above are the output example for about three action:
1140 -
1141 -[[image:image-20250121235119-1.png||height="493" width="455"]]
1142 -
1143 -[[image:image-20240207002129-2.png]]
1144 -
1145 -
1146 -(% class="lead" %)
1147 -Step3: Export Log
1148 -
1149 -[[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"]]
1150 -
1151 -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.
1152 -
1153 -[[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"]]
1154 -
1155 -
1156 1156  == 6.7 How to find the AT Command Password if lost? ==
1157 1157  
1158 1158  
... ... @@ -1170,32 +1170,38 @@
1170 1170  * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1171 1171  * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1172 1172  
1120 +
1173 1173  === Version Confirmation ===
1174 1174  
1175 1175  
1176 1176  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:
1177 1177  
1178 -(% border="1" style="background-color:#f2f2f2; width:912px" %)
1179 -|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1180 -**Firmware version (without FDR1 function)**
1181 -)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1182 -**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)**
1183 1183  )))
1184 -|(% style="width:306px" %)(((
1136 +|(% style="width:210px" %)(((
1185 1185  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;
1186 -)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1187 -|(% 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" %)(((
1188 1188  WL03A-NB, SDI-12-NB;
1189 -)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1141 +)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1190 1190  After V1.0.8 (including V1.0.2)
1191 1191  )))
1192 -|(% style="width:306px" %)(((
1144 +|(% style="width:210px" %)(((
1193 1193  SW3L-NB, PS-NB;
1194 -)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1146 +)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1195 1195  After V1.0.5 (including V1.0.5)
1196 1196  )))
1197 -|(% 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)
1198 1198  
1151 +
1199 1199  === UART connection and firmware update methods ===
1200 1200  
1201 1201  
... ... @@ -1252,11 +1252,4 @@
1252 1252  
1253 1253  
1254 1254  
1255 -== 6.8 ==
1256 -
1257 -
1258 -
1259 -
1260 -
1261 -
1262 1262  
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