Last modified by Mengting Qiu on 2025/07/03 18:55
From version 229.3
edited by Mengting Qiu
on 2025/06/16 09:07
on 2025/06/16 09:07
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +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+UR I1=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/NSproductsusethe(% 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+UR I1=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,20 +1024,18 @@ 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 CommandFormatforNBDevices? ==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 -=== **UDPProtocol:**===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 -01 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" %) ... ... @@ -1083,55 +1083,16 @@ 1083 1083 [[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/]] 1084 1084 1085 1085 1086 -(% style="color:red" %)**Note:**1093 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) == 1087 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 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'sATcommandexplanation.**1096 +* **AT Command: AT** **+GETLOG** 1091 1091 1092 - (% style="color:red" %)**For example, the HEX-format downlinkcommand corresponding to AT+TDC canonlybe used toconfigureTDC and cannot be used forqueries. ThereisnoHEX-formatdownlink command equivalentto AT+TDC=? , so querying TDC viadownlinkis notupported.**1098 +This command can be used to query upstream logs of data packets. 1093 1093 1094 -[[image: 1750035004731-376.png||height="276" width="557"]]1100 +[[image:image-20240701114700-1.png]] 1095 1095 1096 1096 1097 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) == 1098 - 1099 - 1100 -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. 1101 - 1102 - 1103 -(% class="lead" %) 1104 -Step1: Use Mobile Phone to connect device 1105 - 1106 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]** 1107 - 1108 - 1109 -(% class="lead" %) 1110 -Step2: Get Log by different commands. 1111 - 1112 -Use below three method to generate logs. 1113 - 1114 -* **AT+CFG ~-~-> Command to show the current configuration** 1115 -* **AT** **+GETLOG ~-~-> Command to get the previous upstream log** 1116 -* **press the toggle button for 1 ~~2 seconds ~-~-> Trigger a uplink** 1117 - 1118 -Above are the output example for about three action: 1119 - 1120 -[[image:image-20250121235119-1.png||height="493" width="455"]] 1121 - 1122 -[[image:image-20240207002129-2.png]] 1123 - 1124 - 1125 -(% class="lead" %) 1126 -Step3: Export Log 1127 - 1128 -[[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"]] 1129 - 1130 -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. 1131 - 1132 -[[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"]] 1133 - 1134 - 1135 1135 == 6.7 How to find the AT Command Password if lost? == 1136 1136 1137 1137 ... ... @@ -1149,6 +1149,7 @@ 1149 1149 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. 1150 1150 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values except for passwords.(new) 1151 1151 1120 + 1152 1152 === Version Confirmation === 1153 1153 1154 1154 ... ... @@ -1179,6 +1179,7 @@ 1179 1179 ))) 1180 1180 |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8) 1181 1181 1151 + 1182 1182 === UART connection and firmware update methods === 1183 1183 1184 1184
- 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