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

Last modified by Kilight Cao on 2025/07/23 16:27

From 231.4 to 231.5

From version 231.5

edited by Mengting Qiu
on 2025/07/03 18:50

Change comment: There is no comment for this version

To version 236.1

edited by Kilight Cao
on 2025/07/23 16:27

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 4 added, 0 removed)

Details

Page properties

Author

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

Content

@@ -394,11 +394,66 @@
  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
--== 3.5 Node-Red (via MQTT) ==
++== 3.5 Telemetry2U ==
--=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
++=== Configuring the Dragino NB Sensor Settings ===
++
++(% style="color:blue" %)**AT+SERVADDR=telemetry2u.com,4483**(%%) – Sets the server address and port for sending data to the Telemetry2U IoT platform.
++
++(% style="color:blue" %)**AT+APN=simbase**(%%) – Sets the APN required for LTE-M connectivity using a Simbase global SIM card.
++
++(% style="color:blue" %)**ATZ**(%%) – Reboots the device to apply the changes. It won’t transmit to Telemetry2U until added and configured on the platform.
++
++(% style="color:blue" %)**AT+CFG**(%%) – Displays the current configuration. Take note of the 8-byte (HEX) **DEUI**, which you’ll need in the next setup step.
++
++And that’s it! These simple steps will get your device up and running on our Telemetry2U servers in no time.
++
++
++**Step 1: Log in Telemetry2U**
++
++
++Users can register a Telemetry2U account for their first use
++
++**[[https:~~/~~/telemetry2u.com/Identity/Account/Register>>https://telemetry2u.com/Identity/Account/Register]]**
++
++
++**Step 2: Add the device**
++
++[[image:1753258256594-216.png||height="686" width="1382"]]
++
++
++**1. Select Network provide:**Users need to select Telemetry2U NB-IoT over UDP in order to connect to the platform
++
++**2. Select device type:**Select the template you need to use
++
++**3. Fill in Description:**Fill in the unique description
++
++4. **Fill in IMEI:**The IMEI corresponds to the IME of the device
++
++After completion, click "**Greate**"
++
++[[image:1753258480811-335.png||height="789" width="1380"]]
++
++
++**Step 3: Check the data**
++
++
++[[image:1753258821265-310.png||height="681" width="1365"]]
++
++
++
++For more information, please refer to the user manual on the Telemetry2U official website:
++
++**[[https:~~/~~/telemetry2u.com/Documentation/dragino-lte-m-nb-iot-sensors-iot-platform-integration>>https://telemetry2u.com/Documentation/dragino-lte-m-nb-iot-sensors-iot-platform-integration]]**
++
++
++== 3.6 Node-Red (via MQTT) ==
++
++=== 3.6.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
++
++
  Take S31-NB UDP protocol as an example.
  Dragino provides input flow examples for the sensors.
@@ -434,7 +434,7 @@
  [[image:image-20230809174053-9.png]]
--=== 3.5.2 Simulate Connection ===
++=== 3.6.2 Simulate Connection ===
  We have completed the configuration of UDP. We can try sending packets to node red.
@@ -444,7 +444,7 @@
  [[image:image-20230810084048-2.png||height="535" width="1052"]]
--=== 3.5.3 Configure NB-IoT Sensors ===
++=== 3.6.3 Configure NB-IoT Sensors ===
  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)   **~/~/ hex format or json format**
@@ -454,11 +454,11 @@
  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
--== 3.6 ThingsBoard.Cloud (via MQTT) ==
++== 3.7 ThingsBoard.Cloud (via MQTT) ==
--=== 3.6.1 Configure ThingsBoard ===
++=== 3.7.1 Configure ThingsBoard ===
--==== 3.6.1.1 Create Device ====
++==== 3.7.1.1 Create Device ====
  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
@@ -466,7 +466,7 @@
  [[image:image-20230802112413-32.png||height="583" width="1066"]]
--==== 3.6.1.2 Create Uplink & Downlink Converter ====
++==== 3.7.1.2 Create Uplink & Downlink Converter ====
  (% style="color:blue" %)**Uplink Converter**
@@ -487,7 +487,7 @@
  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
--==== 3.6.1.3 MQTT Integration Setup ====
++==== 3.7.1.3 MQTT Integration Setup ====
  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”**(%%), select type (% style="color:blue" %)**MQTT**;
@@ -518,7 +518,7 @@
  [[image:image-20230802112413-40.png||height="525" width="980"]]
--=== 3.6.3 Configure NB-IoT Sensor ===
++=== 3.7.3 Configure NB-IoT Sensor ===
  (% style="color:blue" %)**AT Commands**
@@ -544,11 +544,11 @@
  [[image:image-20230802112413-43.png||height="407" width="825"]]
--== 3.7 ThingsBoard.Cloud (via COAP) ==
++== 3.8 ThingsBoard.Cloud (via COAP) ==
--=== 3.7.1 Configure ThingsBoard ===
++=== 3.8.1 Configure ThingsBoard ===
--==== 3.7.1.1 Create Uplink & Downlink Converter ====
++==== 3.8.1.1 Create Uplink & Downlink Converter ====
  (% style="color:blue" %)**Uplink Converter**
@@ -567,7 +567,7 @@
  [[image:image-20240729142505-3.png||height="507" width="1023"]]
--==== 3.7.1.2 COAP Integration Setup ====
++==== 3.8.1.2 COAP Integration Setup ====
  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" %)**“CoAP Integration”**(%%), select type **COAP    **(% style="color:blue" %);
@@ -580,7 +580,7 @@
  [[image:image-20240729150142-5.png||height="507" width="1023"]]
--==== 3.7.1.3 Add COAP Integration ====
++==== 3.8.1.3 Add COAP Integration ====
  (% class="wikigeneratedid" id="H" %)
@@ -587,9 +587,9 @@
  [[image:image-20240729161543-9.png||height="500" width="1009"]]
--=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
++=== 3.8.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
--==== 3.7.2.1 Instruction Description ====
++==== 3.8.2.1 Instruction Description ====
  * AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
@@ -613,9 +613,9 @@
  [[image:image-20240729172415-13.png||height="401" width="694"]]
--== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
++== 3.9 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
--=== 3.8.1 Create device & Get Credentials ===
++=== 3.9.1 Create device & Get Credentials ===
  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
@@ -666,7 +666,7 @@
  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
--=== 3.8.2 Simulate with MQTT.fx ===
++=== 3.9.2 Simulate with MQTT.fx ===
  [[image:image-20230802112413-52.png]]
@@ -682,7 +682,7 @@
  [[image:image-20230808105329-3.png]]
--=== 3.8.3 tago data ===
++=== 3.9.3 tago data ===
  [[image:image-20230802112413-50.png||height="242" width="1037"]]
@@ -690,7 +690,7 @@
  [[image:image-20230802112413-51.png||height="184" width="696"]]
--== 3.9 TCP Connection ==
++== 3.10 TCP Connection ==
  (% style="color:blue" %)**AT command:**
@@ -711,17 +711,17 @@
  [[image:image-20230807233631-2.png]]
--== 3.10 AWS Connection ==
++== 3.11 AWS Connection ==
  Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
--== 3.11 ThingsEye (via MQTT) ==
++== 3.12 ThingsEye (via MQTT) ==
--=== 3.11.1 Configure ThingsEye ===
++=== 3.12.1 Configure ThingsEye ===
--==== 3.11.1.1 Create MQTT integration ====
++==== 3.12.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**;
@@ -747,7 +747,7 @@
  [[image:image-20241126181024-4.png||height="521" width="1081"]]
--==== 3.11.1.2 Add credentials to the MQTT integration ====
++==== 3.12.1.2 Add credentials to the MQTT integration ====
  Click on the MQTT integration you just created.
@@ -773,7 +773,7 @@
  [[image:image-20241126184211-11.png||height="161" width="977"]]
--==== 3.11.1.3 Setup uplink and downlink converters ====
++==== 3.12.1.3 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]].
@@ -802,7 +802,7 @@
  [[image:image-20241126190737-17.png||height="527" width="1114"]]
--=== 3.11.2 Simulate with MQTT.fx ===
++=== 3.12.2 Simulate with MQTT.fx ===
  [[image:image-20241126191118-18.png||height="605" width="835"]]
@@ -810,7 +810,7 @@
  [[image:image-20241126193252-25.png||height="663" width="803"]]
--=== 3.11.3 Configure -NB node ===
++=== 3.12.3 Configure -NB node ===
  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.
@@ -1049,17 +1049,8 @@
  //Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
--* 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 {}.
++Downlink command:  (% style="color:blue" %)**01000384**(%%)                    ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
--(% 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"]]
@@ -1067,12 +1067,12 @@
  ===== **2. 1 JSON format template.** =====
--All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
++All -NB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
  We can 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.
  Template.
--Take the template of D2x-CB as an example:
++Take the template of D2x-NB as an example:
  {
  "AT+SERVADDR":"119.91.62.30,1882",
@@ -1097,6 +1097,11 @@
  "AT+TEMPALARM3":"0"
  }
++Explanations of two special commands in the template: AT+TR (set the detection interval: 0 ~~ 255 minutes) and AT+NOUD (set the number of groups) correspond to parameters in AT+CLOCKLOG.
++
++[[image:1751538862245-924.png]]
++
++
  **Instructions for Using the Template:**
 . Modify the parameters for each AT command in the template as needed.
@@ -1107,17 +1107,18 @@
  * 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>>url:https://mailto:support@dragino.com/]] to request the latest downlink template.
++
++
  ===== **2.2 Support sending json format commands separately** =====
--Some models of nodes support sending json format commands separately：**RS485-CB, LDS25-CB, CS01-CB, SDI-12-CB, SW3L-CB, WL03A-CB, PS-CB**
++Some models of nodes support sending json format commands separately：(% style="color:blue" %)**RS485-NB, LDS25-NB, CS01-NB, SDI-12-NB, SW3L-NB, WL03A-NB, PS-NB, LTC2-NB.**
--//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
++//Example~:// For the PS-NB's uplink interval modification (AT+TDC=900):
--Downlink command:  **{AT+TDC=900}       **~/~/ The correct format is  **{AT Command}**. No extra characters other than valid AT commands can be added within {}.
++Downlink command:  (% 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.**
@@ -1125,7 +1125,6 @@
  (% 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.**
--
  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==

1751538862245-924.png

Author

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

Size

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

Content

1753258256594-216.png

Author

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

Size

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

Content

1753258480811-335.png

Author

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

Size

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

Content

1753258821265-310.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation