Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 236.1
edited by Kilight Cao
on 2025/07/23 16:27
Change comment: There is no comment for this version
To version 231.2
edited by Mengting Qiu
on 2025/06/19 14:35
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,66 +394,11 @@
394 394  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
395 395  
396 396  
397 -== 3.5 Telemetry2U ==
397 +== 3.5 Node-Red (via MQTT) ==
398 398  
399 +=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
399 399  
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 -
457 457  Take S31-NB UDP protocol as an example.
458 458  
459 459  Dragino provides input flow examples for the sensors.
... ... @@ -489,7 +489,7 @@
489 489  [[image:image-20230809174053-9.png]]
490 490  
491 491  
492 -=== 3.6.2 Simulate Connection ===
437 +=== 3.5.2 Simulate Connection ===
493 493  
494 494  
495 495  We have completed the configuration of UDP. We can try sending packets to node red.
... ... @@ -499,7 +499,7 @@
499 499  [[image:image-20230810084048-2.png||height="535" width="1052"]]
500 500  
501 501  
502 -=== 3.6.3 Configure NB-IoT Sensors ===
447 +=== 3.5.3 Configure NB-IoT Sensors ===
503 503  
504 504  
505 505  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -509,11 +509,11 @@
509 509  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
510 510  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
511 511  
512 -== 3.7 ThingsBoard.Cloud (via MQTT) ==
457 +== 3.6 ThingsBoard.Cloud (via MQTT) ==
513 513  
514 -=== 3.7.1 Configure ThingsBoard ===
459 +=== 3.6.1 Configure ThingsBoard ===
515 515  
516 -==== 3.7.1.1 Create Device ====
461 +==== 3.6.1.1 Create Device ====
517 517  
518 518  
519 519  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
... ... @@ -521,7 +521,7 @@
521 521  [[image:image-20230802112413-32.png||height="583" width="1066"]]
522 522  
523 523  
524 -==== 3.7.1.2 Create Uplink & Downlink Converter ====
469 +==== 3.6.1.2 Create Uplink & Downlink Converter ====
525 525  
526 526  
527 527  (% style="color:blue" %)**Uplink Converter**
... ... @@ -542,7 +542,7 @@
542 542  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
543 543  
544 544  
545 -==== 3.7.1.3 MQTT Integration Setup ====
490 +==== 3.6.1.3 MQTT Integration Setup ====
546 546  
547 547  
548 548  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**;
... ... @@ -573,7 +573,7 @@
573 573  [[image:image-20230802112413-40.png||height="525" width="980"]]
574 574  
575 575  
576 -=== 3.7.3 Configure NB-IoT Sensor ===
521 +=== 3.6.3 Configure NB-IoT Sensor ===
577 577  
578 578  
579 579  (% style="color:blue" %)**AT Commands**
... ... @@ -599,11 +599,11 @@
599 599  [[image:image-20230802112413-43.png||height="407" width="825"]]
600 600  
601 601  
602 -== 3.8 ThingsBoard.Cloud (via COAP) ==
547 +== 3.7 ThingsBoard.Cloud (via COAP) ==
603 603  
604 -=== 3.8.1 Configure ThingsBoard ===
549 +=== 3.7.1 Configure ThingsBoard ===
605 605  
606 -==== 3.8.1.1 Create Uplink & Downlink Converter ====
551 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
607 607  
608 608  
609 609  (% style="color:blue" %)**Uplink Converter**
... ... @@ -622,7 +622,7 @@
622 622  [[image:image-20240729142505-3.png||height="507" width="1023"]]
623 623  
624 624  
625 -==== 3.8.1.2 COAP Integration Setup ====
570 +==== 3.7.1.2 COAP Integration Setup ====
626 626  
627 627  
628 628  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" %);
... ... @@ -635,7 +635,7 @@
635 635  [[image:image-20240729150142-5.png||height="507" width="1023"]]
636 636  
637 637  
638 -==== 3.8.1.3 Add COAP Integration ====
583 +==== 3.7.1.3 Add COAP Integration ====
639 639  
640 640  
641 641  (% class="wikigeneratedid" id="H" %)
... ... @@ -642,9 +642,9 @@
642 642  [[image:image-20240729161543-9.png||height="500" width="1009"]]
643 643  
644 644  
645 -=== 3.8.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
590 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
646 646  
647 -==== 3.8.2.1 Instruction Description ====
592 +==== 3.7.2.1 Instruction Description ====
648 648  
649 649  
650 650  * AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
... ... @@ -668,9 +668,9 @@
668 668  [[image:image-20240729172415-13.png||height="401" width="694"]]
669 669  
670 670  
671 -== 3.9 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
616 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
672 672  
673 -=== 3.9.1 Create device & Get Credentials ===
618 +=== 3.8.1 Create device & Get Credentials ===
674 674  
675 675  
676 676  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.
... ... @@ -721,7 +721,7 @@
721 721  
722 722  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
723 723  
724 -=== 3.9.2 Simulate with MQTT.fx ===
669 +=== 3.8.2 Simulate with MQTT.fx ===
725 725  
726 726  
727 727  [[image:image-20230802112413-52.png]]
... ... @@ -737,7 +737,7 @@
737 737  [[image:image-20230808105329-3.png]]
738 738  
739 739  
740 -=== 3.9.3 tago data ===
685 +=== 3.8.3 tago data ===
741 741  
742 742  
743 743  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -745,7 +745,7 @@
745 745  [[image:image-20230802112413-51.png||height="184" width="696"]]
746 746  
747 747  
748 -== 3.10 TCP Connection ==
693 +== 3.9 TCP Connection ==
749 749  
750 750  
751 751  (% style="color:blue" %)**AT command:**
... ... @@ -766,17 +766,17 @@
766 766  [[image:image-20230807233631-2.png]]
767 767  
768 768  
769 -== 3.11 AWS Connection ==
714 +== 3.10 AWS Connection ==
770 770  
771 771  
772 772  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]]
773 773  
774 774  
775 -== 3.12 ThingsEye (via MQTT) ==
720 +== 3.11 ThingsEye (via MQTT) ==
776 776  
777 -=== 3.12.1 Configure ThingsEye ===
722 +=== 3.11.1 Configure ThingsEye ===
778 778  
779 -==== 3.12.1.1 Create MQTT integration ====
724 +==== 3.11.1.1 Create MQTT integration ====
780 780  
781 781  
782 782  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**;
... ... @@ -802,7 +802,7 @@
802 802  [[image:image-20241126181024-4.png||height="521" width="1081"]]
803 803  
804 804  
805 -==== 3.12.1.2 Add credentials to the MQTT integration ====
750 +==== 3.11.1.2 Add credentials to the MQTT integration ====
806 806  
807 807  
808 808  Click on the MQTT integration you just created.
... ... @@ -828,7 +828,7 @@
828 828  [[image:image-20241126184211-11.png||height="161" width="977"]]
829 829  
830 830  
831 -==== 3.12.1.3 Setup uplink and downlink converters ====
776 +==== 3.11.1.3 Setup uplink and downlink converters ====
832 832  
833 833  
834 834  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]].
... ... @@ -857,7 +857,7 @@
857 857  [[image:image-20241126190737-17.png||height="527" width="1114"]]
858 858  
859 859  
860 -=== 3.12.2 Simulate with MQTT.fx ===
805 +=== 3.11.2 Simulate with MQTT.fx ===
861 861  
862 862  
863 863  [[image:image-20241126191118-18.png||height="605" width="835"]]
... ... @@ -865,7 +865,7 @@
865 865  [[image:image-20241126193252-25.png||height="663" width="803"]]
866 866  
867 867  
868 -=== 3.12.3 Configure -NB node ===
813 +=== 3.11.3 Configure -NB node ===
869 869  
870 870  
871 871  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.
... ... @@ -1098,28 +1098,29 @@
1098 1098  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1099 1099  === **MQTT Protocol:** ===
1100 1100  
1101 -==== **1. HEX-format** ====
1046 +Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1102 1102  
1103 -Supports **HEX-format** downlink commands (corresponding to AT commands).
1104 -
1105 1105  //Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1106 1106  
1107 -Downlink command:  (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
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 {}.
1108 1108  
1109 -[[image:1750035004731-376.png||height="276" width="557"]]
1053 +(% style="color:red" %)**Note:**
1110 1110  
1055 +(% 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.**
1111 1111  
1112 -==== **2. JSON-format ** ====
1057 +(% 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.**
1113 1113  
1114 -===== **2. 1 JSON format template.** =====
1059 +(% 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.**
1115 1115  
1116 -All -NB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1061 +[[image:1750035004731-376.png||height="276" width="557"]]
1117 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 1120  
1121 -Take the template of D2x-NB as an example:
1064 +**Template for Batch Configuration:**
1122 1122  
1066 +We can also 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.
1067 +Template:
1068 +
1123 1123  {
1124 1124  "AT+SERVADDR":"119.91.62.30,1882",
1125 1125  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1143,11 +1143,6 @@
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.
1147 -
1148 -[[image:1751538862245-924.png]]
1149 -
1150 -
1151 1151  **Instructions for Using the Template:**
1152 1152  
1153 1153  1. Modify the parameters for each AT command in the template as needed.
... ... @@ -1160,23 +1160,6 @@
1160 1160  
1161 1161  
1162 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  
... ... @@ -1314,7 +1314,7 @@
1314 1314  
1315 1315  
1316 1316  
1317 -== 6.8 ==
1241 +== 6.8 ==
1318 1318  
1319 1319  
1320 1320  
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