Last modified by Mengting Qiu on 2025/07/17 10:51
From version 229.16
edited by Mengting Qiu
on 2025/06/16 09:25
on 2025/06/16 09:25
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
-
... ... @@ -168,6 +168,7 @@ 168 168 169 169 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 170 170 171 + 171 171 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 172 172 173 173 ... ... @@ -209,6 +209,7 @@ 209 209 210 210 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 211 211 213 + 212 212 ==== 3.3.3.2 Uplink Examples ==== 213 213 214 214 ... ... @@ -270,6 +270,7 @@ 270 270 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %) 271 271 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %) 272 272 275 + 273 273 == 3.4 [[Datacake>>https://datacake.co/]] == 274 274 275 275 ... ... @@ -284,6 +284,7 @@ 284 284 285 285 * (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction. 286 286 290 + 287 287 === 3.4.1 For device Already has template === 288 288 289 289 ==== 3.4.1.1 Create Device ==== ... ... @@ -454,6 +454,7 @@ 454 454 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 455 455 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 456 456 461 + 457 457 == 3.6 ThingsBoard.Cloud (via MQTT) == 458 458 459 459 === 3.6.1 Configure ThingsBoard === ... ... @@ -583,8 +583,7 @@ 583 583 ==== 3.7.1.3 Add COAP Integration ==== 584 584 585 585 586 -(% class="wikigeneratedid" id="H" %) 587 -[[image:image-20240729161543-9.png||height="500" width="1009"]] 591 +==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ==== 588 588 589 589 590 590 === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) === ... ... @@ -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",609 +* 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.611 +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"615 +* 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 619 +If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands, 615 615 621 +e.g. 622 + 623 +* AT+URL1=11, "i" 624 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858" 625 + 626 +[[image:image-20240729172500-14.png||height="403" width="700"]] 627 + 628 + 616 616 == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == 617 617 618 618 === 3.8.1 Create device & Get Credentials === ... ... @@ -773,7 +773,7 @@ 773 773 [[image:image-20241126184211-11.png||height="161" width="977"]] 774 774 775 775 776 -==== 3.11.1. 3Setup uplink and downlink converters ====789 +==== 3.11.1.2 Setup uplink and downlink converters ==== 777 777 778 778 779 779 First, you need to download the [[**MQTT uplink/downlink JS** **code**>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]]. ... ... @@ -810,7 +810,7 @@ 810 810 [[image:image-20241126193252-25.png||height="663" width="803"]] 811 811 812 812 813 -=== 3. 11.3 Configure -NB node ===826 +=== 3.6.3 Configure -NB node === 814 814 815 815 816 816 First you need to configure the certificate to the -NB node. Follow the instructions in this **[[link>>https://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H4.1.2Configurecertificate]]** to configure the certificate. ... ... @@ -819,10 +819,8 @@ 819 819 820 820 * Configuring the CA Certificate 821 821 822 -[[image:image-20241126192009-19.png||height="431" width="697"]] 835 +[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]] 823 823 824 -[[image:image-20241126192130-21.png||height="426" width="694"]] 825 - 826 826 * Configure client certificate 827 827 828 828 [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]] ... ... @@ -840,12 +840,12 @@ 840 840 841 841 * (% style="color:#037691" %)**AT+PRO=3,5 **(%%)** **~/~/ Use MQTT Connection & Json Payload 842 842 * (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883** 843 -* (% style="color:#037691" %)**AT+SUBTOPIC=8899 **(%%)~/~/ 844 -* (% style="color:#037691" %)**AT+PUBTOPIC=8899 **(%%)~/~/ 854 +* (% style="color:#037691" %)**AT+SUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye 855 +* (% style="color:#037691" %)**AT+PUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye 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**859 +* (% 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 ... ... @@ -927,6 +927,7 @@ 927 927 1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 928 928 1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost. 929 929 941 + 930 930 == 5.2 Why the uplink JSON format is not standard? == 931 931 932 932 ... ... @@ -1024,39 +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 CommandFormatforNBDevices? ==1039 +== (% 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:**===1043 +=== 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. 1046 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %) 1047 +Its downlink command is the same as the AT command, but brackets are required. 1048 +Example: 1039 1039 1040 - [[image:1750035991532-434.png||height="237" width="495"]]1050 +{AT+TDC=300} 1041 1041 1042 1042 1043 1043 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1044 -=== **MQTTProtocol:**===1054 +=== 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'suplink interval modification(AT+TDC=900):1057 +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 -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. 1058 - 1059 - 1059 +The Json format in MQTT mode needs to be configured with all commands. 1060 +If you have configurations that need to be changed, please change them in the template below. 1060 1060 Template: 1061 1061 1062 1062 { ... ... @@ -1082,62 +1082,26 @@ 1082 1082 "AT+TEMPALARM3":"0" 1083 1083 } 1084 1084 1085 - **Instructions for Using theTemplate:**1086 +Hex: 1086 1086 1087 -1. Modify the parameters for each AT command in the template as needed. 1088 -1. Send the entire template in one downlink command. 1088 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported. 1089 1089 1090 +The supported commands are consistent with LoRaWAN's hex commands. 1091 +Please refer to the following link to obtain the hex format: 1090 1090 1093 +[[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/]] 1091 1091 1092 -(% style="color:red" %)**Note:** 1093 1093 1094 - (% style="color:red"%)**1.Only when the correct andvalid download command isusedand theformat iscorrectcan thedeviceconfiguredthrough thedownloadcommand.Invalid downloadcontent cannotbe processedbythedeviceand will be automatically restarted.**1096 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) == 1095 1095 1096 -(% 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.** 1097 1097 1098 - (%style="color:red" %)**For example, the HEX-format downlink command corresponding toAT+TDCcan only be used to configure TDCand cannot be used for queries. There is no HEX-format downlink commandequivalent toAT+TDC=? , so querying TDC via downlink is not supported.**1099 +* **AT Command: AT** **+GETLOG** 1099 1099 1100 - [[image:1750035004731-376.png||height="276"width="557"]]1101 +This command can be used to query upstream logs of data packets. 1101 1101 1103 +[[image:image-20240701114700-1.png]] 1102 1102 1103 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) == 1104 1104 1105 - 1106 -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. 1107 - 1108 - 1109 -(% class="lead" %) 1110 -Step1: Use Mobile Phone to connect device 1111 - 1112 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]** 1113 - 1114 - 1115 -(% class="lead" %) 1116 -Step2: Get Log by different commands. 1117 - 1118 -Use below three method to generate logs. 1119 - 1120 -* **AT+CFG ~-~-> Command to show the current configuration** 1121 -* **AT** **+GETLOG ~-~-> Command to get the previous upstream log** 1122 -* **press the toggle button for 1 ~~2 seconds ~-~-> Trigger a uplink** 1123 - 1124 -Above are the output example for about three action: 1125 - 1126 -[[image:image-20250121235119-1.png||height="493" width="455"]] 1127 - 1128 -[[image:image-20240207002129-2.png]] 1129 - 1130 - 1131 -(% class="lead" %) 1132 -Step3: Export Log 1133 - 1134 -[[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"]] 1135 - 1136 -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. 1137 - 1138 -[[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"]] 1139 - 1140 - 1141 1141 == 6.7 How to find the AT Command Password if lost? == 1142 1142 1143 1143 ... ... @@ -1155,9 +1155,9 @@ 1155 1155 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. 1156 1156 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values except for passwords.(new) 1157 1157 1123 + 1158 1158 === Version Confirmation === 1159 1159 1160 - 1161 1161 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: 1162 1162 1163 1163 (% border="1" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -1185,6 +1185,7 @@ 1185 1185 ))) 1186 1186 |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8) 1187 1187 1153 + 1188 1188 === UART connection and firmware update methods === 1189 1189 1190 1190 ... ... @@ -1228,6 +1228,7 @@ 1228 1228 [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827180414-1.png?width=910&height=527&rev=1.1||alt="image-20240827180414-1.png"]] 1229 1229 1230 1230 1197 + 1231 1231 === Special case === 1232 1232 1233 1233 ... ... @@ -1235,6 +1235,7 @@ 1235 1235 1236 1236 Invalid query screenshot example: 1237 1237 1205 + 1238 1238 [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181447-4.png?width=889&height=519&rev=1.1||alt="image-20240827181447-4.png"]] 1239 1239 1240 1240 [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181431-3.png?width=892&height=515&rev=1.1||alt="image-20240827181431-3.png"]]
- 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