Last modified by Kilight Cao on 2025/07/23 16:27

From version 215.1
edited by Mengting Qiu
on 2024/11/26 19:41
Change comment: Uploaded new attachment "image-20241126194123-29.png", version {1}
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
... ... @@ -46,8 +46,8 @@
46 46  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 47  
48 48  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
49 -|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
50 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net/xxx|(% style="width:474px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
49 +|(% style="background-color:#4f81bd; color:white; width:152px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:169px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:427px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
50 +|(% style="width:152px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:169px" %)iot.1nce.net/xxx|(% style="width:427px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
51 51  
52 52  == 2.2 Speed Up Network Attach time ==
53 53  
... ... @@ -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**;
... ... @@ -513,13 +513,12 @@
513 513  
514 514  === 3.6.2 Simulate with MQTT.fx ===
515 515  
516 -
517 517  [[image:image-20230802112413-39.png]]
518 518  
519 519  [[image:image-20230802112413-40.png||height="525" width="980"]]
520 520  
521 521  
522 -=== 3.6.3 Configure NB-IoT Sensor ===
576 +=== 3.7.3 Configure NB-IoT Sensor ===
523 523  
524 524  
525 525  (% style="color:blue" %)**AT Commands**
... ... @@ -545,11 +545,11 @@
545 545  [[image:image-20230802112413-43.png||height="407" width="825"]]
546 546  
547 547  
548 -== 3.7 ThingsBoard.Cloud (via COAP) ==
602 +== 3.8 ThingsBoard.Cloud (via COAP) ==
549 549  
550 -=== 3.7.1 Configure ThingsBoard ===
604 +=== 3.8.1 Configure ThingsBoard ===
551 551  
552 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
606 +==== 3.8.1.1 Create Uplink & Downlink Converter ====
553 553  
554 554  
555 555  (% style="color:blue" %)**Uplink Converter**
... ... @@ -568,7 +568,7 @@
568 568  [[image:image-20240729142505-3.png||height="507" width="1023"]]
569 569  
570 570  
571 -==== 3.7.1.2 COAP Integration Setup ====
625 +==== 3.8.1.2 COAP Integration Setup ====
572 572  
573 573  
574 574  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" %);
... ... @@ -581,15 +581,16 @@
581 581  [[image:image-20240729150142-5.png||height="507" width="1023"]]
582 582  
583 583  
584 -==== 3.7.1.3 Add COAP Integration ====
638 +==== 3.8.1.3 Add COAP Integration ====
585 585  
586 586  
587 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
641 +(% class="wikigeneratedid" id="H" %)
642 +[[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)
... ... @@ -602,31 +602,22 @@
602 602  Note:The port for the COAP protocol has been fixed to 5683
603 603  
604 604  
605 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
660 +* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
606 606  
607 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
662 +-NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
608 608  
609 609  e.g.
610 610  
611 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
666 +* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 612  
613 613  [[image:image-20240729172415-13.png||height="401" width="694"]]
614 614  
615 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
616 616  
617 -e.g.
671 +== 3.9 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
618 618  
619 -* AT+URL1=11, "i"
620 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
673 +=== 3.9.1 Create device & Get Credentials ===
621 621  
622 -[[image:image-20240729172500-14.png||height="403" width="700"]]
623 623  
624 -
625 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
626 -
627 -=== 3.8.1 Create device & Get Credentials ===
628 -
629 -
630 630  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.
631 631  
632 632  [[image:image-20230802112413-44.png]]
... ... @@ -675,7 +675,7 @@
675 675  
676 676  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
677 677  
678 -=== 3.8.2 Simulate with MQTT.fx ===
724 +=== 3.9.2 Simulate with MQTT.fx ===
679 679  
680 680  
681 681  [[image:image-20230802112413-52.png]]
... ... @@ -691,7 +691,7 @@
691 691  [[image:image-20230808105329-3.png]]
692 692  
693 693  
694 -=== 3.8.3 tago data ===
740 +=== 3.9.3 tago data ===
695 695  
696 696  
697 697  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -699,7 +699,7 @@
699 699  [[image:image-20230802112413-51.png||height="184" width="696"]]
700 700  
701 701  
702 -== 3.9 TCP Connection ==
748 +== 3.10 TCP Connection ==
703 703  
704 704  
705 705  (% style="color:blue" %)**AT command:**
... ... @@ -720,24 +720,21 @@
720 720  [[image:image-20230807233631-2.png]]
721 721  
722 722  
723 -== 3.10 AWS Connection ==
769 +== 3.11 AWS Connection ==
724 724  
725 725  
726 726  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]]
727 727  
728 728  
729 -== 3.11 ThingsEye (via MQTT) ==
775 +== 3.12 ThingsEye (via MQTT) ==
730 730  
731 -(% class="wikigeneratedid" %)
732 -=== 3.11.1 Configure ThingsEye ===
777 +=== 3.12.1 Configure ThingsEye ===
733 733  
779 +==== 3.12.1.1 Create MQTT integration ====
734 734  
735 -==== 3.11.1.1 Create MQTT integration ====
736 736  
737 -
738 738  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**;
739 739  
740 -
741 741  [[image:image-20241126175509-1.png||height="518" width="1081"]]
742 742  
743 743  
... ... @@ -759,7 +759,7 @@
759 759  [[image:image-20241126181024-4.png||height="521" width="1081"]]
760 760  
761 761  
762 -==== 3.11.1.2 Add credentials to the MQTT integration ====
805 +==== 3.12.1.2 Add credentials to the MQTT integration ====
763 763  
764 764  
765 765  Click on the MQTT integration you just created.
... ... @@ -774,7 +774,7 @@
774 774  
775 775  (% style="color:blue" %)**Add credential files.**
776 776  
777 -Click this link to download the certificates.
820 +Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
778 778  
779 779  [[image:image-20241126183032-8.png||height="757" width="976"]]
780 780  
... ... @@ -785,10 +785,10 @@
785 785  [[image:image-20241126184211-11.png||height="161" width="977"]]
786 786  
787 787  
788 -==== 3.11.1.2 Setup uplink and downlink converters ====
831 +==== 3.12.1.3 Setup uplink and downlink converters ====
789 789  
790 790  
791 -First, you need to download the **MQTT uplink/downlink JS** **code**.
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]].
792 792  
793 793  * (% style="color:blue" %)**Uplink Converter**
794 794  
... ... @@ -814,44 +814,67 @@
814 814  [[image:image-20241126190737-17.png||height="527" width="1114"]]
815 815  
816 816  
817 -=== 3.6.2 Simulate with MQTT.fx ===
860 +=== 3.12.2 Simulate with MQTT.fx ===
818 818  
819 819  
820 -[[image:image-20230802112413-39.png]]
863 +[[image:image-20241126191118-18.png||height="605" width="835"]]
821 821  
822 -[[image:image-20230802112413-40.png||height="525" width="980"]]
865 +[[image:image-20241126193252-25.png||height="663" width="803"]]
823 823  
824 824  
825 -=== 3.6.3 Configure NB-IoT Sensor ===
868 +=== 3.12.3 Configure -NB node ===
826 826  
827 827  
828 -(% style="color:blue" %)**AT Commands**
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.
829 829  
830 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT tconnect to ThingsBoard. Payload Type set to 3.
873 +Screenshot of successful certificate configuration:
831 831  
832 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
875 +* Configuring the CA Certificate
833 833  
834 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
877 +[[image:image-20241126192009-19.png||height="431" width="697"]]
835 835  
836 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
879 +[[image:image-20241126192130-21.png||height="426" width="694"]]
837 837  
838 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
881 +* Configure client certificate
839 839  
840 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
883 +[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
841 841  
842 -Test Uplink by click the button for 1 second
885 +* Configure client private key
843 843  
844 -[[image:image-20230802112413-41.png||height="496" width="828"]]
887 +[[image:image-20241126192415-24.png||height="435" width="737"]]
845 845  
846 -[[image:image-20230802112413-42.png]]
847 847  
848 -[[image:image-20230802112413-43.png||height="407" width="825"]]
890 +When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
849 849  
892 +Then configure the -NB node to connect to the ThingsEye platform:
850 850  
894 +(% style="color:blue" %)**AT Commands**
851 851  
896 +* (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
897 +* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
898 +* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
899 +* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
900 +* (% style="color:#037691" %)**AT+CLIENT=NULL**
901 +* (% style="color:#037691" %)**AT+UNAME=NULL**
902 +* (% style="color:#037691" %)**AT+PWD=NULL**
903 +* (% style="color:#037691" %)**AT+TLSMOD=1,2**
852 852  
905 +Test Uplink by click the button for 1~~3 seconds, the MQTT integration in ThingsEye allows you to view the data upstream from the device:
853 853  
907 +[[image:image-20241126193458-26.png||height="375" width="1012"]]
854 854  
909 +[[image:image-20241126193609-27.png||height="424" width="1014"]]
910 +
911 +
912 +Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
913 +
914 +[[image:image-20241126194018-28.png||height="318" width="1076"]]
915 +
916 +You can view the data that has just been uplink on the device:
917 +
918 +[[image:image-20241126194123-29.png||height="486" width="1073"]]
919 +
920 +
855 855  = 4. MQTT/UDP/TCP downlink =
856 856  
857 857  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -912,8 +912,8 @@
912 912  1. Give more sampling data points.
913 913  1. Increase reliable in transmission. For example. If user set
914 914  1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
915 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
916 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
981 +1*. **AT+NOUD=24**  ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
982 +1*. **AT+TDC=7200**  ~/~/  Uplink every 2 hours.
917 917  1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
918 918  
919 919  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -926,6 +926,14 @@
926 926  [[image:image-20240229233154-1.png]]
927 927  
928 928  
995 +== 5.3 What is the data consumption for different transfer mode? ==
996 +
997 +
998 +For the data consumption of NB-IoT End node in different transfer mode, reference link:
999 +
1000 +[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
1001 +
1002 +
929 929  = 6. Trouble Shooting: =
930 930  
931 931  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -1005,27 +1005,47 @@
1005 1005  [[image:image-20240226111928-1.png]]
1006 1006  
1007 1007  
1008 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1082 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1009 1009  
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 +
1010 1010  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1011 -=== UDP: ===
1088 +=== **UDP Protocol:** ===
1012 1012  
1013 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1014 -Its downlink command is the same as the AT command, but brackets are required.
1015 -Example:
1090 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
1016 1016  
1017 -{AT+TDC=300}
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.
1018 1018  
1095 +[[image:1750035991532-434.png||height="237" width="495"]]
1019 1019  
1097 +
1020 1020  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1021 -=== MQTT: ===
1099 +=== **MQTT Protocol:** ===
1022 1022  
1023 -Json:
1101 +==== **1. HEX-format** ====
1024 1024  
1025 -The Json format in MQTT mode needs to be configured with all commands.
1026 -If you have configurations that need to be changed, please change them in the template below.
1027 -Template:
1103 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1028 1028  
1105 +//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
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 +
1029 1029  {
1030 1030  "AT+SERVADDR":"119.91.62.30,1882",
1031 1031  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1049,26 +1049,78 @@
1049 1049  "AT+TEMPALARM3":"0"
1050 1050  }
1051 1051  
1052 -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.
1053 1053  
1054 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1148 +[[image:1751538862245-924.png]]
1055 1055  
1056 -The supported commands are consistent with LoRaWAN's hex commands.
1057 -Please refer to the following link to obtain the hex format:
1058 1058  
1059 -[[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:**
1060 1060  
1153 +1. Modify the parameters for each AT command in the template as needed.
1154 +1. Send the entire template in one downlink command.
1061 1061  
1062 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1156 +(% style="color:red" %)**Note:**
1063 1063  
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.
1064 1064  
1065 -* **AT Command: AT** **+GETLOG**
1066 1066  
1067 -This command can be used to query upstream logs of data packets.
1068 1068  
1069 -[[image:image-20240701114700-1.png]]
1163 +===== **2.2 Support sending json format commands separately** =====
1070 1070  
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.**
1071 1071  
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 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1181 +
1182 +
1183 +If user is not able to solve the connection issue, user can use below method and get the device log and send to Dragino (Support@dragino.cc) for further analyze.
1184 +
1185 +
1186 +(% class="lead" %)
1187 +Step1: Use Mobile Phone to connect device
1188 +
1189 +See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1190 +
1191 +
1192 +(% class="lead" %)
1193 +Step2: Get Log by different commands.
1194 +
1195 +Use below three method to generate logs.
1196 +
1197 +* **AT+CFG       ~-~-> Command to show the current configuration**
1198 +* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1199 +* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1200 +
1201 +Above are the output example for about three action:
1202 +
1203 +[[image:image-20250121235119-1.png||height="493" width="455"]]
1204 +
1205 +[[image:image-20240207002129-2.png]]
1206 +
1207 +
1208 +(% class="lead" %)
1209 +Step3: Export Log
1210 +
1211 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155425-16.png?width=330&height=85&rev=1.1||alt="image-20241230155425-16.png" height="85" width="330"]]
1212 +
1213 +select the log you want to export, then click the share icon on the far right to enter the document that comes with your phone and choose to export it.
1214 +
1215 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155528-17.png?width=327&height=324&rev=1.1||alt="image-20241230155528-17.png" height="324" width="327"]]
1216 +
1217 +
1072 1072  == 6.7 How to find the AT Command Password if lost? ==
1073 1073  
1074 1074  
... ... @@ -1088,32 +1088,29 @@
1088 1088  
1089 1089  === Version Confirmation ===
1090 1090  
1237 +
1091 1091  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:
1092 1092  
1093 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1094 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1095 -**Firmware version**
1096 -
1097 -**(without FDR1 function)**
1098 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1099 -**Firmware version**
1100 -
1101 -**(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)**
1102 1102  )))
1103 -|(% style="width:210px" %)(((
1246 +|(% style="width:306px" %)(((
1104 1104  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;
1105 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1106 -|(% 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" %)(((
1107 1107  WL03A-NB, SDI-12-NB;
1108 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1251 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1109 1109  After V1.0.8 (including V1.0.2)
1110 1110  )))
1111 -|(% style="width:210px" %)(((
1254 +|(% style="width:306px" %)(((
1112 1112  SW3L-NB, PS-NB;
1113 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1256 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1114 1114  After V1.0.5 (including V1.0.5)
1115 1115  )))
1116 -|(% 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)
1117 1117  
1118 1118  === UART connection and firmware update methods ===
1119 1119  
... ... @@ -1158,7 +1158,6 @@
1158 1158  [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827180414-1.png?width=910&height=527&rev=1.1||alt="image-20240827180414-1.png"]]
1159 1159  
1160 1160  
1161 -
1162 1162  === Special case ===
1163 1163  
1164 1164  
... ... @@ -1166,7 +1166,6 @@
1166 1166  
1167 1167  Invalid query screenshot example:
1168 1168  
1169 -
1170 1170  [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181447-4.png?width=889&height=519&rev=1.1||alt="image-20240827181447-4.png"]]
1171 1171  
1172 1172  [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181431-3.png?width=892&height=515&rev=1.1||alt="image-20240827181431-3.png"]]
... ... @@ -1173,4 +1173,11 @@
1173 1173  
1174 1174  
1175 1175  
1317 +== 6.8 ==
1318 +
1319 +
1320 +
1321 +
1322 +
1323 +
1176 1176  
1750035004731-376.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +55.1 KB
Content
1750035991532-434.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.4 KB
Content
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
image-20250121235119-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +145.4 KB
Content