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 219.1
edited by Kilight Cao
on 2024/12/11 17:24
Change comment: There is no comment for this version

Summary

Details

Page properties
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: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" %)
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" %)
51 51  
52 52  == 2.2 Speed Up Network Attach time ==
53 53  
... ... @@ -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**;
... ... @@ -568,12 +568,13 @@
568 568  
569 569  === 3.6.2 Simulate with MQTT.fx ===
570 570  
516 +
571 571  [[image:image-20230802112413-39.png]]
572 572  
573 573  [[image:image-20230802112413-40.png||height="525" width="980"]]
574 574  
575 575  
576 -=== 3.7.3 Configure NB-IoT Sensor ===
522 +=== 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) ==
548 +== 3.7 ThingsBoard.Cloud (via COAP) ==
603 603  
604 -=== 3.8.1 Configure ThingsBoard ===
550 +=== 3.7.1 Configure ThingsBoard ===
605 605  
606 -==== 3.8.1.1 Create Uplink & Downlink Converter ====
552 +==== 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 ====
571 +==== 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,16 +635,15 @@
635 635  [[image:image-20240729150142-5.png||height="507" width="1023"]]
636 636  
637 637  
638 -==== 3.8.1.3 Add COAP Integration ====
584 +==== 3.7.1.3 Add COAP Integration ====
639 639  
640 640  
641 -(% class="wikigeneratedid" id="H" %)
642 -[[image:image-20240729161543-9.png||height="500" width="1009"]]
587 +==== [[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)
... ... @@ -657,22 +657,31 @@
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  
671 -== 3.9 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
617 +e.g.
672 672  
673 -=== 3.9.1 Create device & Get Credentials ===
619 +* AT+URL1=11, "i"
620 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
674 674  
622 +[[image:image-20240729172500-14.png||height="403" width="700"]]
675 675  
624 +
625 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
626 +
627 +=== 3.8.1 Create device & Get Credentials ===
628 +
629 +
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.
677 677  
678 678  [[image:image-20230802112413-44.png]]
... ... @@ -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 ===
678 +=== 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 ===
694 +=== 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 ==
702 +== 3.9 TCP Connection ==
749 749  
750 750  
751 751  (% style="color:blue" %)**AT command:**
... ... @@ -766,19 +766,20 @@
766 766  [[image:image-20230807233631-2.png]]
767 767  
768 768  
769 -== 3.11 AWS Connection ==
723 +== 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) ==
729 +== 3.11 ThingsEye (via MQTT) ==
776 776  
777 -=== 3.12.1 Configure ThingsEye ===
731 +=== 3.11.1 Configure ThingsEye ===
778 778  
779 -==== 3.12.1.1 Create MQTT integration ====
780 780  
734 +==== 3.11.1.1 Create MQTT integration ====
781 781  
736 +
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**;
783 783  
784 784  [[image:image-20241126175509-1.png||height="518" width="1081"]]
... ... @@ -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 ====
760 +==== 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 ====
786 +==== 3.11.1.2 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 ===
815 +=== 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 ===
823 +=== 3.6.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.
... ... @@ -874,10 +874,8 @@
874 874  
875 875  * Configuring the CA Certificate
876 876  
877 -[[image:image-20241126192009-19.png||height="431" width="697"]]
832 +[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
878 878  
879 -[[image:image-20241126192130-21.png||height="426" width="694"]]
880 -
881 881  * Configure client certificate
882 882  
883 883  [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
... ... @@ -895,12 +895,12 @@
895 895  
896 896  * (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
897 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
851 +* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
852 +* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
900 900  * (% style="color:#037691" %)**AT+CLIENT=NULL**
901 901  * (% style="color:#037691" %)**AT+UNAME=NULL**
902 902  * (% style="color:#037691" %)**AT+PWD=NULL**
903 -* (% style="color:#037691" %)**AT+TLSMOD=1,2**
856 +* (% style="color:#037691" %)**AT+TLSMOD=1,0**
904 904  
905 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:
906 906  
... ... @@ -918,6 +918,7 @@
918 918  [[image:image-20241126194123-29.png||height="486" width="1073"]]
919 919  
920 920  
874 +
921 921  = 4. MQTT/UDP/TCP downlink =
922 922  
923 923  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -978,8 +978,8 @@
978 978  1. Give more sampling data points.
979 979  1. Increase reliable in transmission. For example. If user set
980 980  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)
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.
935 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
936 +1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
983 983  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.
984 984  
985 985  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -992,7 +992,7 @@
992 992  [[image:image-20240229233154-1.png]]
993 993  
994 994  
995 -== 5.3 What is the data consumption for different transfer mode？ ==
949 +== 5.3 What is the data consumption for different transfer mode？ ==
996 996  
997 997  
998 998  For the data consumption of NB-IoT End node in different transfer mode, reference link:
... ... @@ -999,7 +999,6 @@
999 999  
1000 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 1001  
1002 -
1003 1003  = 6. Trouble Shooting: =
1004 1004  
1005 1005  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -1079,47 +1079,27 @@
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? ==
1035 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1083 1083  
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:** ===
1038 +=== UDP: ===
1089 1089  
1090 -Only supports valid **HEX-format downlink commands** corresponding to AT command.
1040 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1041 +Its downlink command is the same as the AT command, but brackets are required.
1042 +Example:
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.
1044 +{AT+TDC=300}
1094 1094  
1095 -[[image:1750035991532-434.png||height="237" width="495"]]
1096 1096  
1097 -
1098 1098  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1099 -=== **MQTT Protocol:** ===
1048 +=== MQTT: ===
1100 1100  
1101 -==== **1. HEX-format** ====
1050 +Json：
1102 1102  
1103 -Supports **HEX-format** downlink commands (corresponding to AT commands).
1052 +The Json format in MQTT mode needs to be configured with all commands.
1053 +If you have configurations that need to be changed, please change them in the template below.
1054 +Template:
1104 1104  
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 -
1123 1123  {
1124 1124  "AT+SERVADDR":"119.91.62.30,1882",
1125 1125  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1143,78 +1143,26 @@
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.
1079 +Hex：
1147 1147  
1148 -[[image:1751538862245-924.png]]
1081 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1149 1149  
1083 +The supported commands are consistent with LoRaWAN's hex commands.
1084 +Please refer to the following link to obtain the hex format:
1150 1150  
1151 -**Instructions for Using the Template:**
1086 +[[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:**
1089 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1157 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 1160  
1092 +* **AT Command: AT** **+GETLOG**
1161 1161  
1094 +This command can be used to query upstream logs of data packets.
1162 1162  
1163 -===== **2.2 Support sending json format commands separately** =====
1096 +[[image:image-20240701114700-1.png]]
1164 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 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 -== (% 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 -
1218 1218  == 6.7 How to find the AT Command Password if lost? ==
1219 1219  
1220 1220  
... ... @@ -1234,29 +1234,32 @@
1234 1234  
1235 1235  === Version Confirmation ===
1236 1236  
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)**
1120 +(% border="1" style="background-color:#f2f2f2; width:510px" %)
1121 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1122 +**Firmware version**
1123 +
1124 +**(without FDR1 function)**
1125 +)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1126 +**Firmware version**
1127 +
1128 +**(with FDR1 function)**
1245 1245  )))
1246 -|(% style="width:306px" %)(((
1130 +|(% 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" %)(((
1132 +)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1133 +|(% style="width:210px" %)(((
1250 1250  WL03A-NB, SDI-12-NB;
1251 -)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1135 +)))|(% 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" %)(((
1138 +|(% style="width:210px" %)(((
1255 1255  SW3L-NB, PS-NB;
1256 -)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1140 +)))|(% 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)
1143 +|(% 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  
... ... @@ -1301,6 +1301,7 @@
1301 1301  [[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"]]
1302 1302  
1303 1303  
1188 +
1304 1304  === Special case ===
1305 1305  
1306 1306  
... ... @@ -1308,6 +1308,7 @@
1308 1308  
1309 1309  Invalid query screenshot example:
1310 1310  
1196 +
1311 1311  [[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"]]
1312 1312  
1313 1313  [[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"]]
... ... @@ -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
image-20250121235119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -145.4 KB
Content