Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 228.5
edited by Mengting Qiu
on 2025/06/16 09:01
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,27 +1024,20 @@
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 -(% style="color:red" %)**Note:**
1039 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1040 +=== UDP: ===
1032 1032  
1033 -(% 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.**
1034 1034  
1035 -(% 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.**
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:
1036 1036  
1037 -(% 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.**
1047 +{AT+TDC=300}
1038 1038  
1039 1039  
1040 -[[image:1750035004731-376.png]]
1041 -
1042 -
1043 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1044 -=== **UDP Protocol:** ===
1045 -
1046 -Only supports valid **HEX-format downlink commands** corresponding to AT command
1047 -
1048 1048  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1049 1049  === MQTT: ===
1050 1050  
... ... @@ -1088,44 +1088,16 @@
1088 1088  [[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/]]
1089 1089  
1090 1090  
1091 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1093 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1092 1092  
1093 1093  
1094 -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.
1096 +* **AT Command: AT** **+GETLOG**
1095 1095  
1098 +This command can be used to query upstream logs of data packets.
1096 1096  
1097 -(% class="lead" %)
1098 -Step1: Use Mobile Phone to connect device
1100 +[[image:image-20240701114700-1.png]]
1099 1099  
1100 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1101 1101  
1102 -
1103 -(% class="lead" %)
1104 -Step2: Get Log by different commands.
1105 -
1106 -Use below three method to generate logs.
1107 -
1108 -* **AT+CFG       ~-~-> Command to show the current configuration**
1109 -* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1110 -* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1111 -
1112 -Above are the output example for about three action:
1113 -
1114 -[[image:image-20250121235119-1.png||height="493" width="455"]]
1115 -
1116 -[[image:image-20240207002129-2.png]]
1117 -
1118 -
1119 -(% class="lead" %)
1120 -Step3: Export Log
1121 -
1122 -[[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"]]
1123 -
1124 -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.
1125 -
1126 -[[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"]]
1127 -
1128 -
1129 1129  == 6.7 How to find the AT Command Password if lost? ==
1130 1130  
1131 1131  
... ... @@ -1143,6 +1143,7 @@
1143 1143  * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1144 1144  * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1145 1145  
1120 +
1146 1146  === Version Confirmation ===
1147 1147  
1148 1148  
... ... @@ -1173,6 +1173,7 @@
1173 1173  )))
1174 1174  |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1175 1175  
1151 +
1176 1176  === UART connection and firmware update methods ===
1177 1177  
1178 1178  
1750035004731-376.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -55.1 KB
Content
image-20250121235119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -145.4 KB
Content