Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 229.14
edited by Mengting Qiu
on 2025/06/16 09:19
Change comment: There is no comment for this version
To version 221.1
edited by Xiaoling
on 2024/12/31 15:51
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,37 +1024,26 @@
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 -Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1047 1047  
1048 -//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1054 +Json：
1049 1049  
1050 -* HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1051 -* 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 {}.
1052 -
1053 -
1054 -
1055 -**Template for Batch Configuration:**
1056 -
1057 -
1058 1058  The Json format in MQTT mode needs to be configured with all commands.
1059 1059  If you have configurations that need to be changed, please change them in the template below.
1060 1060  Template:
... ... @@ -1092,55 +1092,16 @@
1092 1092  [[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/]]
1093 1093  
1094 1094  
1095 -(% style="color:red" %)**Note:**
1093 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1096 1096  
1097 -(% 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.**
1098 1098  
1099 -(% 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.**
1096 +* **AT Command: AT** **+GETLOG**
1100 1100  
1101 -(% 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.**
1098 +This command can be used to query upstream logs of data packets.
1102 1102  
1103 -[[image:1750035004731-376.png||height="276" width="557"]]
1100 +[[image:image-20240701114700-1.png]]
1104 1104  
1105 1105  
1106 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1107 -
1108 -
1109 -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.
1110 -
1111 -
1112 -(% class="lead" %)
1113 -Step1: Use Mobile Phone to connect device
1114 -
1115 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1116 -
1117 -
1118 -(% class="lead" %)
1119 -Step2: Get Log by different commands.
1120 -
1121 -Use below three method to generate logs.
1122 -
1123 -* **AT+CFG       ~-~-> Command to show the current configuration**
1124 -* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1125 -* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1126 -
1127 -Above are the output example for about three action:
1128 -
1129 -[[image:image-20250121235119-1.png||height="493" width="455"]]
1130 -
1131 -[[image:image-20240207002129-2.png]]
1132 -
1133 -
1134 -(% class="lead" %)
1135 -Step3: Export Log
1136 -
1137 -[[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"]]
1138 -
1139 -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.
1140 -
1141 -[[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"]]
1142 -
1143 -
1144 1144  == 6.7 How to find the AT Command Password if lost? ==
1145 1145  
1146 1146  
... ... @@ -1158,6 +1158,7 @@
1158 1158  * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1159 1159  * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1160 1160  
1120 +
1161 1161  === Version Confirmation ===
1162 1162  
1163 1163  
... ... @@ -1188,6 +1188,7 @@
1188 1188  )))
1189 1189  |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1190 1190  
1151 +
1191 1191  === UART connection and firmware update methods ===
1192 1192  
1193 1193  
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