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

Last modified by Mengting Qiu on 2025/03/08 11:33

From version < 223.1 >

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

To version < 215.1 >

edited by Mengting Qiu
on 2024/11/26 19:41

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

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- image-20250121235119-1.png

Details

Page properties

Author

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

Content

@@ -46,8 +46,8 @@
  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
--|(% style="background-color:#4f81bd; color:white; width:152px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:169px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:427px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
--|(% style="width:152px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:169px" %)iot.1nce.net/xxx|(% style="width:427px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
++|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
++|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net/xxx|(% style="width:474px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
  == 2.2 Speed Up Network Attach time ==
@@ -513,6 +513,7 @@
  === 3.6.2 Simulate with MQTT.fx ===
++
  [[image:image-20230802112413-39.png]]
  [[image:image-20230802112413-40.png||height="525" width="980"]]
@@ -583,8 +583,7 @@
  ==== 3.7.1.3 Add COAP Integration ====
--(% class="wikigeneratedid" id="H" %)
--[[image:image-20240729161543-9.png||height="500" width="1009"]]
++==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
  === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
@@ -728,13 +728,16 @@
  == 3.11 ThingsEye (via MQTT) ==
++(% class="wikigeneratedid" %)
  === 3.11.1 Configure ThingsEye ===
++
  ==== 3.11.1.1 Create MQTT integration ====
  Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration_NB”**(%%), select type (% style="color:blue" %)**MQTT**;
++
  [[image:image-20241126175509-1.png||height="518" width="1081"]]
@@ -771,7 +771,7 @@
  (% style="color:blue" %)**Add credential files.**
--Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
++Click this link to download the certificates.
  [[image:image-20241126183032-8.png||height="757" width="976"]]
@@ -782,10 +782,10 @@
  [[image:image-20241126184211-11.png||height="161" width="977"]]
--==== 3.11.1.3 Setup uplink and downlink converters ====
++==== 3.11.1.2 Setup uplink and downlink converters ====
--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]].
++First, you need to download the **MQTT uplink/downlink JS** **code**.
  * (% style="color:blue" %)**Uplink Converter**
@@ -811,67 +811,44 @@
  [[image:image-20241126190737-17.png||height="527" width="1114"]]
--=== 3.11.2 Simulate with MQTT.fx ===
++=== 3.6.2 Simulate with MQTT.fx ===
--[[image:image-20241126191118-18.png||height="605" width="835"]]
++[[image:image-20230802112413-39.png]]
--[[image:image-20241126193252-25.png||height="663" width="803"]]
++[[image:image-20230802112413-40.png||height="525" width="980"]]
--=== 3.11.3 Configure -NB node ===
++=== 3.6.3 Configure NB-IoT Sensor ===
--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.
++(% style="color:blue" %)**AT Commands**
--Screenshot of successful certificate configuration:
++* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)**  **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
--* Configuring the CA Certificate
++* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
--[[image:image-20241126192009-19.png||height="431" width="697"]]
++* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
--[[image:image-20241126192130-21.png||height="426" width="694"]]
++* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
--* Configure client certificate
++* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
--[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
++* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
--* Configure client private key
++Test Uplink by click the button for 1 second
--[[image:image-20241126192415-24.png||height="435" width="737"]]
++[[image:image-20230802112413-41.png||height="496" width="828"]]
++[[image:image-20230802112413-42.png]]
--When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
++[[image:image-20230802112413-43.png||height="407" width="825"]]
--Then configure the -NB node to connect to the ThingsEye platform:
--(% style="color:blue" %)**AT Commands**
--* (% style="color:#037691" %)**AT+PRO=3,5  **(%%)**    **~/~/ Use MQTT Connection & Json Payload
--* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
--* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
--* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
--* (% style="color:#037691" %)**AT+CLIENT=NULL**
--* (% style="color:#037691" %)**AT+UNAME=NULL**
--* (% style="color:#037691" %)**AT+PWD=NULL**
--* (% 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:
--[[image:image-20241126193458-26.png||height="375" width="1012"]]
--[[image:image-20241126193609-27.png||height="424" width="1014"]]
--
--
--Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
--
--[[image:image-20241126194018-28.png||height="318" width="1076"]]
--
--You can view the data that has just been uplink on the device:
--
--[[image:image-20241126194123-29.png||height="486" width="1073"]]
--
--
  = 4. MQTT/UDP/TCP downlink =
  == 4.1 MQTT (via MQTT.fx) ==
@@ -932,8 +932,8 @@
 . Give more sampling data points.
 . Increase reliable in transmission. For example. If user set
 *. **AT+TR=1800**        ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
--1*. **AT+NOUD=24**     ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
--1*. **AT+TDC=7200**     ~/~/  Uplink every 2 hours.
++1*. **AT+NOUD=24**    ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
++1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
 *. 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.
  == 5.2 Why the uplink JSON format is not standard? ==
@@ -946,14 +946,6 @@
  [[image:image-20240229233154-1.png]]
--== 5.3 What is the data consumption for different transfer mode？ ==
--
--
--For the data consumption of NB-IoT End node in different transfer mode, reference link:
--
--[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
--
--
  = 6. Trouble Shooting: =
  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
@@ -1035,11 +1035,9 @@
  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
--
  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
  === UDP: ===
--
  (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
  Its downlink command is the same as the AT command, but brackets are required.
  Example:
@@ -1050,7 +1050,6 @@
  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
  === MQTT: ===
--
  Json：
  The Json format in MQTT mode needs to be configured with all commands.
@@ -1090,45 +1090,16 @@
  [[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/]]
--== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
++== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
--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.
++* **AT Command: AT** **+GETLOG**
++This command can be used to query upstream logs of data packets.
--(% class="lead" %)
--Step1: Use Mobile Phone to connect device
++[[image:image-20240701114700-1.png]]
--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? ==
@@ -1148,7 +1148,6 @@
  === Version Confirmation ===
--
  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:
  (% border="1" style="background-color:#f2f2f2; width:510px" %)
@@ -1219,6 +1219,7 @@
  [[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"]]
++
  === Special case ===
@@ -1226,6 +1226,7 @@
  Invalid query screenshot example:
++
  [[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"]]
  [[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"]]

image-20250121235119-1.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-145.4 KB

Content

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

Summary

Details

Applications

Navigation