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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.ting
Content
... ... @@ -394,61 +394,6 @@
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 -
452 452  == 3.5 Node-Red (via MQTT) ==
453 453  
454 454  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
... ... @@ -657,17 +657,26 @@
657 657  Note:The port for the COAP protocol has been fixed to 5683
658 658  
659 659  
660 -* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
605 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
661 661  
662 --NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
607 +If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
663 663  
664 664  e.g.
665 665  
666 -* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
611 +* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
667 667  
668 668  [[image:image-20240729172415-13.png||height="401" width="694"]]
669 669  
615 +If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
670 670  
617 +e.g.
618 +
619 +* AT+URL1=11, "i"
620 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
621 +
622 +[[image:image-20240729172500-14.png||height="403" width="700"]]
623 +
624 +
671 671  == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
672 672  
673 673  === 3.8.1 Create device & Get Credentials ===
... ... @@ -1079,47 +1079,30 @@
1079 1079  [[image:image-20240226111928-1.png]]
1080 1080  
1081 1081  
1082 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1036 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1083 1083  
1084 1084  
1085 -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.
1086 -
1087 1087  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1088 -=== **UDP Protocol:** ===
1040 +=== UDP: ===
1089 1089  
1090 -Only supports valid **HEX-format downlink commands** corresponding to AT command.
1091 1091  
1092 -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:
1093 -Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1043 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1044 +Its downlink command is the same as the AT command, but brackets are required.
1045 +Example:
1094 1094  
1095 -[[image:1750035991532-434.png||height="237" width="495"]]
1047 +{AT+TDC=300}
1096 1096  
1097 1097  
1098 1098  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1099 -=== **MQTT Protocol:** ===
1051 +=== MQTT: ===
1100 1100  
1101 -==== **1. HEX-format** ====
1102 1102  
1103 -Supports **HEX-format** downlink commands (corresponding to AT commands).
1054 +Json：
1104 1104  
1105 -//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1056 +The Json format in MQTT mode needs to be configured with all commands.
1057 +If you have configurations that need to be changed, please change them in the template below.
1058 +Template:
1106 1106  
1107 -Downlink command:  (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1108 -
1109 -[[image:1750035004731-376.png||height="276" width="557"]]
1110 -
1111 -
1112 -==== **2. JSON-format ** ====
1113 -
1114 -===== **2. 1 JSON format template.** =====
1115 -
1116 -All -NB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1117 -
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 -
1123 1123  {
1124 1124  "AT+SERVADDR":"119.91.62.30,1882",
1125 1125  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1143,40 +1143,16 @@
1143 1143  "AT+TEMPALARM3":"0"
1144 1144  }
1145 1145  
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.
1083 +Hex：
1147 1147  
1148 -[[image:1751538862245-924.png]]
1085 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1149 1149  
1087 +The supported commands are consistent with LoRaWAN's hex commands.
1088 +Please refer to the following link to obtain the hex format:
1150 1150  
1151 -**Instructions for Using the Template:**
1090 +[[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/]]
1152 1152  
1153 -1. Modify the parameters for each AT command in the template as needed.
1154 -1. Send the entire template in one downlink command.
1155 1155  
1156 -(% style="color:red" %)**Note:**
1157 -
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 -
1173 -(% 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.**
1174 -
1175 -(% 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.**
1176 -
1177 -(% 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.**
1178 -
1179 -
1180 1180  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1181 1181  
1182 1182  
... ... @@ -1237,26 +1237,30 @@
1237 1237  
1238 1238  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:
1239 1239  
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)**
1153 +(% border="1" style="background-color:#f2f2f2; width:510px" %)
1154 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1155 +**Firmware version**
1156 +
1157 +**(without FDR1 function)**
1158 +)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1159 +**Firmware version**
1160 +
1161 +**(with FDR1 function)**
1245 1245  )))
1246 -|(% style="width:306px" %)(((
1163 +|(% style="width:210px" %)(((
1247 1247  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;
1248 -)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1249 -|(% style="width:306px" %)(((
1165 +)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1166 +|(% style="width:210px" %)(((
1250 1250  WL03A-NB, SDI-12-NB;
1251 -)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1168 +)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1252 1252  After V1.0.8 (including V1.0.2)
1253 1253  )))
1254 -|(% style="width:306px" %)(((
1171 +|(% style="width:210px" %)(((
1255 1255  SW3L-NB, PS-NB;
1256 -)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1173 +)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1257 1257  After V1.0.5 (including V1.0.5)
1258 1258  )))
1259 -|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1176 +|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1260 1260  
1261 1261  === UART connection and firmware update methods ===
1262 1262  
... ... @@ -1314,11 +1314,4 @@
1314 1314  
1315 1315  
1316 1316  
1317 -== 6.8 ==
1318 -
1319 -
1320 -
1321 -
1322 -
1323 -
1324 1324  
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
1751538862245-924.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -114.7 KB
Content
1753258256594-216.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -153.1 KB
Content
1753258480811-335.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -110.5 KB
Content
1753258821265-310.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -189.0 KB
Content