Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Last modified by Mengting Qiu on 2025/07/17 10:51

From 222.1 to 221.1 From 229.19 to 229.18

From version 229.18

edited by Mengting Qiu
on 2025/06/16 09:27

Change comment: There is no comment for this version

To version 222.1

edited by Edwin Chen
on 2025/01/21 23:51

Change comment: Uploaded new attachment "image-20250121235119-1.png", version {1}

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 2 removed)
- 1750035004731-376.png
- 1750035991532-434.png

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.ting
++XWiki.Edwin

Content

@@ -602,17 +602,26 @@
  Note:The port for the COAP protocol has been fixed to 5683
--* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
++* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
---NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
++If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
  e.g.
--* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
++* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
  [[image:image-20240729172415-13.png||height="401" width="694"]]
++If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
++e.g.
++
++* AT+URL1=11, "i"
++* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
++
++[[image:image-20240729172500-14.png||height="403" width="700"]]
++
++
  == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
  === 3.8.1 Create device & Get Credentials ===
@@ -845,7 +845,7 @@
  * (% style="color:#037691" %)**AT+CLIENT=NULL**
  * (% style="color:#037691" %)**AT+UNAME=NULL**
  * (% style="color:#037691" %)**AT+PWD=NULL**
--* (% style="color:#037691" %)**AT+TLSMOD=1,2**
++* (% style="color:#037691" %)**AT+TLSMOD=1,0**
  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:
@@ -1024,46 +1024,28 @@
  [[image:image-20240226111928-1.png]]
--== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
++== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
--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.
--
  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
--=== **UDP Protocol:** ===
++=== UDP: ===
--Only supports valid **HEX-format downlink commands** corresponding to AT command.
--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:
--Downward format: (% style="color:blue" %)**01000384**(%%)   ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
++(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
++Its downlink command is the same as the AT command, but brackets are required.
++Example:
--[[image:1750035991532-434.png||height="237" width="495"]]
++{AT+TDC=300}
  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
--=== **MQTT Protocol:** ===
++=== MQTT: ===
--Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
--//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
++Json：
--* HEX format: (% style="color:blue" %)**01000384**(%%)                    ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
--* 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 {}.
--
--(% style="color:red" %)**Note:**
--
--(% 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.**
--
--(% 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.**
--
--(% 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.**
--
--[[image:1750035004731-376.png||height="276" width="557"]]
--
--
--**Template for Batch Configuration:**
--
--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.
++The Json format in MQTT mode needs to be configured with all commands.
++If you have configurations that need to be changed, please change them in the template below.
  Template:
  {
@@ -1089,59 +1089,26 @@
  "AT+TEMPALARM3":"0"
  }
--**Instructions for Using the Template:**
++Hex：
--1. Modify the parameters for each AT command in the template as needed.
--1. Send the entire template in one downlink command.
++MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
--(% style="color:red" %)**Note:**
++The supported commands are consistent with LoRaWAN's hex commands.
++Please refer to the following link to obtain the hex format:
--**Note:**
++[[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/]]
--* The template may vary depending on the device model.
--* 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 to request the latest downlink template.
++== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
++* **AT Command: AT** **+GETLOG**
--== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
++This command can be used to query upstream logs of data packets.
++[[image:image-20240701114700-1.png]]
--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.
--
--(% class="lead" %)
--Step1: Use Mobile Phone to connect device
--
--See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
--
--
--(% class="lead" %)
--Step2: Get Log by different commands.
--
--Use below three method to generate logs.
--
--* **AT+CFG       ~-~-> Command to show the current configuration**
--* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
--* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
--
--Above are the output example for about three action:
--
--[[image:image-20250121235119-1.png||height="493" width="455"]]
--
--[[image:image-20240207002129-2.png]]
--
--
--(% class="lead" %)
--Step3: Export Log
--
--[[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"]]
--
--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.
--
--[[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"]]
--
--
  == 6.7 How to find the AT Command Password if lost? ==
@@ -1159,6 +1159,7 @@
  * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
  * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
++
  === Version Confirmation ===
@@ -1189,6 +1189,7 @@
  )))
  |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
++
  === UART connection and firmware update methods ===

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

Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Summary

Details

Applications

Navigation