Last modified by Kilight Cao on 2025/07/23 16:27
From version 231.5
edited by Mengting Qiu
on 2025/07/03 18:50
on 2025/07/03 18:50
Change comment:
There is no comment for this version
To version 235.1
edited by Kilight Cao
on 2025/07/23 16:25
on 2025/07/23 16:25
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 4 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Kilight - Content
-
... ... @@ -394,6 +394,61 @@ 394 394 (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445** 395 395 396 396 397 +== 3.5 Telemetry2U == 398 + 399 + 400 +=== Configuring the Dragino NB Sensor Settings === 401 + 402 + 403 +(% style="color:blue" %)**AT+SERVADDR=telemetry2u.com,4483**(%%) – Sets the server address and port for sending data to the Telemetry2U IoT platform. 404 + 405 +(% style="color:blue" %)**AT+APN=simbase**(%%) – Sets the APN required for LTE-M connectivity using a Simbase global SIM card. 406 + 407 +(% style="color:blue" %)**ATZ**(%%) – Reboots the device to apply the changes. It won’t transmit to Telemetry2U until added and configured on the platform. 408 + 409 +(% 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. 410 + 411 +And that’s it! These simple steps will get your device up and running on our Telemetry2U servers in no time. 412 + 413 + 414 +**Step 1: Log in Telemetry2U** 415 + 416 + 417 +Users can register a Telemetry2U account for their first use 418 + 419 +**[[https:~~/~~/telemetry2u.com/Identity/Account/Register>>https://telemetry2u.com/Identity/Account/Register]]** 420 + 421 + 422 +**Step 2: Add the device** 423 + 424 +[[image:1753258256594-216.png||height="686" width="1382"]] 425 + 426 + 427 +**1. Select Network provide:**Users need to select Telemetry2U NB-IoT over UDP in order to connect to the platform 428 + 429 +**2. Select device type:**Select the template you need to use 430 + 431 +**3. Fill in Description:**Fill in the unique description 432 + 433 +4. **Fill in IMEI:**The IMEI corresponds to the IME of the device 434 + 435 +After completion, click "**Greate**" 436 + 437 +[[image:1753258480811-335.png||height="789" width="1380"]] 438 + 439 + 440 +**Step 3: Check the data** 441 + 442 + 443 +[[image:1753258821265-310.png||height="681" width="1365"]] 444 + 445 + 446 + 447 +For more information, please refer to the user manual on the Telemetry2U official website: 448 + 449 +**[[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]]** 450 + 451 + 397 397 == 3.5 Node-Red (via MQTT) == 398 398 399 399 === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] === ... ... @@ -1049,17 +1049,8 @@ 1049 1049 1050 1050 //Example~:// For the S31-NB's uplink interval modification (AT+TDC=900): 1051 1051 1052 -* HEX format: (% style="color:blue" %)**01000384**(%%) ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds. 1053 -* 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 {}. 1107 +Downlink command: (% style="color:blue" %)**01000384**(%%) ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds. 1054 1054 1055 -(% style="color:red" %)**Note:** 1056 - 1057 -(% 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.** 1058 - 1059 -(% 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.** 1060 - 1061 -(% 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.** 1062 - 1063 1063 [[image:1750035004731-376.png||height="276" width="557"]] 1064 1064 1065 1065 ... ... @@ -1067,12 +1067,12 @@ 1067 1067 1068 1068 ===== **2. 1 JSON format template.** ===== 1069 1069 1070 -All - CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**1116 +All -NB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.** 1071 1071 1072 1072 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. 1073 1073 Template. 1074 1074 1075 -Take the template of D2x- CB as an example:1121 +Take the template of D2x-NB as an example: 1076 1076 1077 1077 { 1078 1078 "AT+SERVADDR":"119.91.62.30,1882", ... ... @@ -1097,6 +1097,11 @@ 1097 1097 "AT+TEMPALARM3":"0" 1098 1098 } 1099 1099 1146 +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. 1147 + 1148 +[[image:1751538862245-924.png]] 1149 + 1150 + 1100 1100 **Instructions for Using the Template:** 1101 1101 1102 1102 1. Modify the parameters for each AT command in the template as needed. ... ... @@ -1107,17 +1107,18 @@ 1107 1107 * The template may vary depending on the device model. 1108 1108 * **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. 1109 1109 1161 + 1162 + 1110 1110 ===== **2.2 Support sending json format commands separately** ===== 1111 1111 1112 -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**1165 +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.** 1113 1113 1114 -//Example~:// For the PS- CB's uplink interval modification (AT+TDC=900):1167 +//Example~:// For the PS-NB's uplink interval modification (AT+TDC=900): 1115 1115 1116 -Downlink command: **{AT+TDC=900} **~/~/ The correct format is **{AT Command}**. No extra characters other than valid AT commands can be added within {}. 1169 +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 {}. 1117 1117 1118 1118 (% style="color:red" %)**Note:** 1119 1119 1120 - 1121 1121 (% 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.** 1122 1122 1123 1123 (% 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 @@ 1125 1125 (% 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.** 1126 1126 1127 1127 1128 - 1129 1129 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) == 1130 1130 1131 1131
- 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