Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 229.14
edited by Mengting Qiu
on 2025/06/16 09:19
Change comment: There is no comment for this version
To version 235.1
edited by Kilight Cao
on 2025/07/23 16:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +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/]] ===
... ... @@ -1043,22 +1043,28 @@
1043 1043  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1044 1044  === **MQTT Protocol:** ===
1045 1045  
1046 -Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1101 +==== **1. HEX-format** ====
1047 1047  
1103 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1104 +
1048 1048  //Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
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 {}.
1107 +Downlink command:  (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1052 1052  
1109 +[[image:1750035004731-376.png||height="276" width="557"]]
1053 1053  
1054 1054  
1055 -**Template for Batch Configuration:**
1112 +==== **2. JSON-format ** ====
1056 1056  
1114 +===== **2. 1 JSON format template.** =====
1057 1057  
1058 -The Json format in MQTT mode needs to be configured with all commands.
1059 -If you have configurations that need to be changed, please change them in the template below.
1060 -Template:
1116 +All -NB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1061 1061  
1118 +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.
1119 +Template.
1120 +
1121 +Take the template of D2x-NB as an example:
1122 +
1062 1062  {
1063 1063  "AT+SERVADDR":"119.91.62.30,1882",
1064 1064  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1082,18 +1082,33 @@
1082 1082  "AT+TEMPALARM3":"0"
1083 1083  }
1084 1084  
1085 -Hex：
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.
1086 1086  
1087 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1148 +[[image:1751538862245-924.png]]
1088 1088  
1089 -The supported commands are consistent with LoRaWAN's hex commands.
1090 -Please refer to the following link to obtain the hex format:
1091 1091  
1092 -[[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/]]
1151 +**Instructions for Using the Template:**
1093 1093  
1153 +1. Modify the parameters for each AT command in the template as needed.
1154 +1. Send the entire template in one downlink command.
1094 1094  
1095 1095  (% style="color:red" %)**Note:**
1096 1096  
1158 +* The template may vary depending on the device model.
1159 +* **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.
1160 +
1161 +
1162 +
1163 +===== **2.2 Support sending json format commands separately** =====
1164 +
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.**
1166 +
1167 +//Example~:// For the PS-NB's uplink interval modification (AT+TDC=900):
1168 +
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 {}.
1170 +
1171 +(% style="color:red" %)**Note:**
1172 +
1097 1097  (% 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.**
1098 1098  
1099 1099  (% 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.**
... ... @@ -1100,9 +1100,7 @@
1100 1100  
1101 1101  (% 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.**
1102 1102  
1103 -[[image:1750035004731-376.png||height="276" width="557"]]
1104 1104  
1105 -
1106 1106  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1107 1107  
1108 1108  
... ... @@ -1163,30 +1163,26 @@
1163 1163  
1164 1164  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:
1165 1165  
1166 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1167 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1168 -**Firmware version**
1169 -
1170 -**(without FDR1 function)**
1171 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1172 -**Firmware version**
1173 -
1174 -**(with FDR1 function)**
1240 +(% border="1" style="background-color:#f2f2f2; width:912px" %)
1241 +|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1242 +**Firmware version (without FDR1 function)**
1243 +)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1244 +**Firmware version (with FDR1 function)**
1175 1175  )))
1176 -|(% style="width:210px" %)(((
1246 +|(% style="width:306px" %)(((
1177 1177  CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB,  MDS200-NB, SE01-NB, SPH01-NB;
1178 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1179 -|(% style="width:210px" %)(((
1248 +)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1249 +|(% style="width:306px" %)(((
1180 1180  WL03A-NB, SDI-12-NB;
1181 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1251 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1182 1182  After V1.0.8 (including V1.0.2)
1183 1183  )))
1184 -|(% style="width:210px" %)(((
1254 +|(% style="width:306px" %)(((
1185 1185  SW3L-NB, PS-NB;
1186 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1256 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1187 1187  After V1.0.5 (including V1.0.5)
1188 1188  )))
1189 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1259 +|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1190 1190  
1191 1191  === UART connection and firmware update methods ===
1192 1192  
... ... @@ -1244,4 +1244,11 @@
1244 1244  
1245 1245  
1246 1246  
1317 +== 6.8 ==
1318 +
1319 +
1320 +
1321 +
1322 +
1323 +
1247 1247  
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