Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 229.11
edited by Mengting Qiu
on 2025/06/16 09:14
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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Kilight
Content
... ... @@ -394,11 +394,66 @@
394 394  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
395 395  
396 396  
397 -== 3.5 Node-Red (via MQTT) ==
397 +== 3.5 Telemetry2U ==
398 398  
399 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
400 400  
400 +=== Configuring the Dragino NB Sensor Settings ===
401 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 +== 3.6 Node-Red (via MQTT) ==
453 +
454 +=== 3.6.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
455 +
456 +
402 402  Take S31-NB UDP protocol as an example.
403 403  
404 404  Dragino provides input flow examples for the sensors.
... ... @@ -434,7 +434,7 @@
434 434  [[image:image-20230809174053-9.png]]
435 435  
436 436  
437 -=== 3.5.2 Simulate Connection ===
492 +=== 3.6.2 Simulate Connection ===
438 438  
439 439  
440 440  We have completed the configuration of UDP. We can try sending packets to node red.
... ... @@ -444,7 +444,7 @@
444 444  [[image:image-20230810084048-2.png||height="535" width="1052"]]
445 445  
446 446  
447 -=== 3.5.3 Configure NB-IoT Sensors ===
502 +=== 3.6.3 Configure NB-IoT Sensors ===
448 448  
449 449  
450 450  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -454,11 +454,11 @@
454 454  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
455 455  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
456 456  
457 -== 3.6 ThingsBoard.Cloud (via MQTT) ==
512 +== 3.7 ThingsBoard.Cloud (via MQTT) ==
458 458  
459 -=== 3.6.1 Configure ThingsBoard ===
514 +=== 3.7.1 Configure ThingsBoard ===
460 460  
461 -==== 3.6.1.1 Create Device ====
516 +==== 3.7.1.1 Create Device ====
462 462  
463 463  
464 464  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
... ... @@ -466,7 +466,7 @@
466 466  [[image:image-20230802112413-32.png||height="583" width="1066"]]
467 467  
468 468  
469 -==== 3.6.1.2 Create Uplink & Downlink Converter ====
524 +==== 3.7.1.2 Create Uplink & Downlink Converter ====
470 470  
471 471  
472 472  (% style="color:blue" %)**Uplink Converter**
... ... @@ -487,7 +487,7 @@
487 487  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
488 488  
489 489  
490 -==== 3.6.1.3 MQTT Integration Setup ====
545 +==== 3.7.1.3 MQTT Integration Setup ====
491 491  
492 492  
493 493  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 @@
518 518  [[image:image-20230802112413-40.png||height="525" width="980"]]
519 519  
520 520  
521 -=== 3.6.3 Configure NB-IoT Sensor ===
576 +=== 3.7.3 Configure NB-IoT Sensor ===
522 522  
523 523  
524 524  (% style="color:blue" %)**AT Commands**
... ... @@ -544,11 +544,11 @@
544 544  [[image:image-20230802112413-43.png||height="407" width="825"]]
545 545  
546 546  
547 -== 3.7 ThingsBoard.Cloud (via COAP) ==
602 +== 3.8 ThingsBoard.Cloud (via COAP) ==
548 548  
549 -=== 3.7.1 Configure ThingsBoard ===
604 +=== 3.8.1 Configure ThingsBoard ===
550 550  
551 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
606 +==== 3.8.1.1 Create Uplink & Downlink Converter ====
552 552  
553 553  
554 554  (% style="color:blue" %)**Uplink Converter**
... ... @@ -567,7 +567,7 @@
567 567  [[image:image-20240729142505-3.png||height="507" width="1023"]]
568 568  
569 569  
570 -==== 3.7.1.2 COAP Integration Setup ====
625 +==== 3.8.1.2 COAP Integration Setup ====
571 571  
572 572  
573 573  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 @@
580 580  [[image:image-20240729150142-5.png||height="507" width="1023"]]
581 581  
582 582  
583 -==== 3.7.1.3 Add COAP Integration ====
638 +==== 3.8.1.3 Add COAP Integration ====
584 584  
585 585  
586 586  (% class="wikigeneratedid" id="H" %)
... ... @@ -587,9 +587,9 @@
587 587  [[image:image-20240729161543-9.png||height="500" width="1009"]]
588 588  
589 589  
590 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
645 +=== 3.8.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
591 591  
592 -==== 3.7.2.1 Instruction Description ====
647 +==== 3.8.2.1 Instruction Description ====
593 593  
594 594  
595 595  * AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
... ... @@ -613,9 +613,9 @@
613 613  [[image:image-20240729172415-13.png||height="401" width="694"]]
614 614  
615 615  
616 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
671 +== 3.9 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
617 617  
618 -=== 3.8.1 Create device & Get Credentials ===
673 +=== 3.9.1 Create device & Get Credentials ===
619 619  
620 620  
621 621  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 @@
666 666  
667 667  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
668 668  
669 -=== 3.8.2 Simulate with MQTT.fx ===
724 +=== 3.9.2 Simulate with MQTT.fx ===
670 670  
671 671  
672 672  [[image:image-20230802112413-52.png]]
... ... @@ -682,7 +682,7 @@
682 682  [[image:image-20230808105329-3.png]]
683 683  
684 684  
685 -=== 3.8.3 tago data ===
740 +=== 3.9.3 tago data ===
686 686  
687 687  
688 688  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -690,7 +690,7 @@
690 690  [[image:image-20230802112413-51.png||height="184" width="696"]]
691 691  
692 692  
693 -== 3.9 TCP Connection ==
748 +== 3.10 TCP Connection ==
694 694  
695 695  
696 696  (% style="color:blue" %)**AT command:**
... ... @@ -711,17 +711,17 @@
711 711  [[image:image-20230807233631-2.png]]
712 712  
713 713  
714 -== 3.10 AWS Connection ==
769 +== 3.11 AWS Connection ==
715 715  
716 716  
717 717  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]]
718 718  
719 719  
720 -== 3.11 ThingsEye (via MQTT) ==
775 +== 3.12 ThingsEye (via MQTT) ==
721 721  
722 -=== 3.11.1 Configure ThingsEye ===
777 +=== 3.12.1 Configure ThingsEye ===
723 723  
724 -==== 3.11.1.1 Create MQTT integration ====
779 +==== 3.12.1.1 Create MQTT integration ====
725 725  
726 726  
727 727  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 @@
747 747  [[image:image-20241126181024-4.png||height="521" width="1081"]]
748 748  
749 749  
750 -==== 3.11.1.2 Add credentials to the MQTT integration ====
805 +==== 3.12.1.2 Add credentials to the MQTT integration ====
751 751  
752 752  
753 753  Click on the MQTT integration you just created.
... ... @@ -773,7 +773,7 @@
773 773  [[image:image-20241126184211-11.png||height="161" width="977"]]
774 774  
775 775  
776 -==== 3.11.1.3 Setup uplink and downlink converters ====
831 +==== 3.12.1.3 Setup uplink and downlink converters ====
777 777  
778 778  
779 779  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 @@
802 802  [[image:image-20241126190737-17.png||height="527" width="1114"]]
803 803  
804 804  
805 -=== 3.11.2 Simulate with MQTT.fx ===
860 +=== 3.12.2 Simulate with MQTT.fx ===
806 806  
807 807  
808 808  [[image:image-20241126191118-18.png||height="605" width="835"]]
... ... @@ -810,7 +810,7 @@
810 810  [[image:image-20241126193252-25.png||height="663" width="803"]]
811 811  
812 812  
813 -=== 3.11.3 Configure -NB node ===
868 +=== 3.12.3 Configure -NB node ===
814 814  
815 815  
816 816  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.
... ... @@ -1043,21 +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}**
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 -Json：
1112 +==== **2. JSON-format ** ====
1056 1056  
1057 -The Json format in MQTT mode needs to be configured with all commands.
1058 -If you have configurations that need to be changed, please change them in the template below.
1059 -Template:
1114 +===== **2. 1 JSON format template.** =====
1060 1060  
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 +
1061 1061  {
1062 1062  "AT+SERVADDR":"119.91.62.30,1882",
1063 1063  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1081,18 +1081,33 @@
1081 1081  "AT+TEMPALARM3":"0"
1082 1082  }
1083 1083  
1084 -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.
1085 1085  
1086 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1148 +[[image:1751538862245-924.png]]
1087 1087  
1088 -The supported commands are consistent with LoRaWAN's hex commands.
1089 -Please refer to the following link to obtain the hex format:
1090 1090  
1091 -[[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:**
1092 1092  
1153 +1. Modify the parameters for each AT command in the template as needed.
1154 +1. Send the entire template in one downlink command.
1093 1093  
1094 1094  (% style="color:red" %)**Note:**
1095 1095  
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 +
1096 1096  (% 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.**
1097 1097  
1098 1098  (% 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.**
... ... @@ -1099,9 +1099,7 @@
1099 1099  
1100 1100  (% 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.**
1101 1101  
1102 -[[image:1750035004731-376.png||height="276" width="557"]]
1103 1103  
1104 -
1105 1105  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1106 1106  
1107 1107  
... ... @@ -1162,30 +1162,26 @@
1162 1162  
1163 1163  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:
1164 1164  
1165 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1166 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1167 -**Firmware version**
1168 -
1169 -**(without FDR1 function)**
1170 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1171 -**Firmware version**
1172 -
1173 -**(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)**
1174 1174  )))
1175 -|(% style="width:210px" %)(((
1246 +|(% style="width:306px" %)(((
1176 1176  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;
1177 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1178 -|(% 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" %)(((
1179 1179  WL03A-NB, SDI-12-NB;
1180 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1251 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1181 1181  After V1.0.8 (including V1.0.2)
1182 1182  )))
1183 -|(% style="width:210px" %)(((
1254 +|(% style="width:306px" %)(((
1184 1184  SW3L-NB, PS-NB;
1185 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1256 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1186 1186  After V1.0.5 (including V1.0.5)
1187 1187  )))
1188 -|(% 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)
1189 1189  
1190 1190  === UART connection and firmware update methods ===
1191 1191  
... ... @@ -1243,4 +1243,11 @@
1243 1243  
1244 1244  
1245 1245  
1317 +== 6.8 ==
1318 +
1319 +
1320 +
1321 +
1322 +
1323 +
1246 1246  
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