Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 220.1
edited by Xiaoling
on 2024/12/12 11:41
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.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -168,7 +168,6 @@
168 168  
169 169  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
170 170  
171 -
172 172  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
173 173  
174 174  
... ... @@ -210,7 +210,6 @@
210 210  
211 211  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
212 212  
213 -
214 214  ==== 3.3.3.2 Uplink Examples ====
215 215  
216 216  
... ... @@ -272,7 +272,6 @@
272 272  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
273 273  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
274 274  
275 -
276 276  == 3.4 [[Datacake>>https://datacake.co/]] ==
277 277  
278 278  
... ... @@ -287,7 +287,6 @@
287 287  
288 288  * (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
289 289  
290 -
291 291  === 3.4.1 For device Already has template ===
292 292  
293 293  ==== 3.4.1.1 Create Device ====
... ... @@ -398,11 +398,66 @@
398 398  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
399 399  
400 400  
401 -== 3.5 Node-Red (via MQTT) ==
397 +== 3.5 Telemetry2U ==
402 402  
403 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
404 404  
400 +=== Configuring the Dragino NB Sensor Settings ===
405 405  
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 +
406 406  Take S31-NB UDP protocol as an example.
407 407  
408 408  Dragino provides input flow examples for the sensors.
... ... @@ -438,7 +438,7 @@
438 438  [[image:image-20230809174053-9.png]]
439 439  
440 440  
441 -=== 3.5.2 Simulate Connection ===
492 +=== 3.6.2 Simulate Connection ===
442 442  
443 443  
444 444  We have completed the configuration of UDP. We can try sending packets to node red.
... ... @@ -448,7 +448,7 @@
448 448  [[image:image-20230810084048-2.png||height="535" width="1052"]]
449 449  
450 450  
451 -=== 3.5.3 Configure NB-IoT Sensors ===
502 +=== 3.6.3 Configure NB-IoT Sensors ===
452 452  
453 453  
454 454  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -458,20 +458,19 @@
458 458  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
459 459  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
460 460  
512 +== 3.7 ThingsBoard.Cloud (via MQTT) ==
461 461  
462 -== 3.6 ThingsBoard.Cloud (via MQTT) ==
514 +=== 3.7.1 Configure ThingsBoard ===
463 463  
464 -=== 3.6.1 Configure ThingsBoard ===
516 +==== 3.7.1.1 Create Device ====
465 465  
466 -==== 3.6.1.1 Create Device ====
467 467  
468 -
469 469  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
470 470  
471 471  [[image:image-20230802112413-32.png||height="583" width="1066"]]
472 472  
473 473  
474 -==== 3.6.1.2 Create Uplink & Downlink Converter ====
524 +==== 3.7.1.2 Create Uplink & Downlink Converter ====
475 475  
476 476  
477 477  (% style="color:blue" %)**Uplink Converter**
... ... @@ -492,7 +492,7 @@
492 492  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
493 493  
494 494  
495 -==== 3.6.1.3 MQTT Integration Setup ====
545 +==== 3.7.1.3 MQTT Integration Setup ====
496 496  
497 497  
498 498  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**;
... ... @@ -523,7 +523,7 @@
523 523  [[image:image-20230802112413-40.png||height="525" width="980"]]
524 524  
525 525  
526 -=== 3.6.3 Configure NB-IoT Sensor ===
576 +=== 3.7.3 Configure NB-IoT Sensor ===
527 527  
528 528  
529 529  (% style="color:blue" %)**AT Commands**
... ... @@ -549,11 +549,11 @@
549 549  [[image:image-20230802112413-43.png||height="407" width="825"]]
550 550  
551 551  
552 -== 3.7 ThingsBoard.Cloud (via COAP) ==
602 +== 3.8 ThingsBoard.Cloud (via COAP) ==
553 553  
554 -=== 3.7.1 Configure ThingsBoard ===
604 +=== 3.8.1 Configure ThingsBoard ===
555 555  
556 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
606 +==== 3.8.1.1 Create Uplink & Downlink Converter ====
557 557  
558 558  
559 559  (% style="color:blue" %)**Uplink Converter**
... ... @@ -572,7 +572,7 @@
572 572  [[image:image-20240729142505-3.png||height="507" width="1023"]]
573 573  
574 574  
575 -==== 3.7.1.2 COAP Integration Setup ====
625 +==== 3.8.1.2 COAP Integration Setup ====
576 576  
577 577  
578 578  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" %);
... ... @@ -585,15 +585,16 @@
585 585  [[image:image-20240729150142-5.png||height="507" width="1023"]]
586 586  
587 587  
588 -==== 3.7.1.3 Add COAP Integration ====
638 +==== 3.8.1.3 Add COAP Integration ====
589 589  
590 590  
591 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
641 +(% class="wikigeneratedid" id="H" %)
642 +[[image:image-20240729161543-9.png||height="500" width="1009"]]
592 592  
593 593  
594 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
645 +=== 3.8.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
595 595  
596 -==== 3.7.2.1 Instruction Description ====
647 +==== 3.8.2.1 Instruction Description ====
597 597  
598 598  
599 599  * AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
... ... @@ -606,31 +606,22 @@
606 606  Note:The port for the COAP protocol has been fixed to 5683
607 607  
608 608  
609 -* 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",
610 610  
611 -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.
612 612  
613 613  e.g.
614 614  
615 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
666 +* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
616 616  
617 617  [[image:image-20240729172415-13.png||height="401" width="694"]]
618 618  
619 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
620 620  
621 -e.g.
671 +== 3.9 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
622 622  
623 -* AT+URL1=11, "i"
624 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
673 +=== 3.9.1 Create device & Get Credentials ===
625 625  
626 -[[image:image-20240729172500-14.png||height="403" width="700"]]
627 627  
628 -
629 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
630 -
631 -=== 3.8.1 Create device & Get Credentials ===
632 -
633 -
634 634  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.
635 635  
636 636  [[image:image-20230802112413-44.png]]
... ... @@ -679,7 +679,7 @@
679 679  
680 680  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
681 681  
682 -=== 3.8.2 Simulate with MQTT.fx ===
724 +=== 3.9.2 Simulate with MQTT.fx ===
683 683  
684 684  
685 685  [[image:image-20230802112413-52.png]]
... ... @@ -695,7 +695,7 @@
695 695  [[image:image-20230808105329-3.png]]
696 696  
697 697  
698 -=== 3.8.3 tago data ===
740 +=== 3.9.3 tago data ===
699 699  
700 700  
701 701  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -703,7 +703,7 @@
703 703  [[image:image-20230802112413-51.png||height="184" width="696"]]
704 704  
705 705  
706 -== 3.9 TCP Connection ==
748 +== 3.10 TCP Connection ==
707 707  
708 708  
709 709  (% style="color:blue" %)**AT command:**
... ... @@ -724,17 +724,17 @@
724 724  [[image:image-20230807233631-2.png]]
725 725  
726 726  
727 -== 3.10 AWS Connection ==
769 +== 3.11 AWS Connection ==
728 728  
729 729  
730 730  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]]
731 731  
732 732  
733 -== 3.11 ThingsEye (via MQTT) ==
775 +== 3.12 ThingsEye (via MQTT) ==
734 734  
735 -=== 3.11.1 Configure ThingsEye ===
777 +=== 3.12.1 Configure ThingsEye ===
736 736  
737 -==== 3.11.1.1 Create MQTT integration ====
779 +==== 3.12.1.1 Create MQTT integration ====
738 738  
739 739  
740 740  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**;
... ... @@ -760,7 +760,7 @@
760 760  [[image:image-20241126181024-4.png||height="521" width="1081"]]
761 761  
762 762  
763 -==== 3.11.1.2 Add credentials to the MQTT integration ====
805 +==== 3.12.1.2 Add credentials to the MQTT integration ====
764 764  
765 765  
766 766  Click on the MQTT integration you just created.
... ... @@ -786,7 +786,7 @@
786 786  [[image:image-20241126184211-11.png||height="161" width="977"]]
787 787  
788 788  
789 -==== 3.11.1.2 Setup uplink and downlink converters ====
831 +==== 3.12.1.3 Setup uplink and downlink converters ====
790 790  
791 791  
792 792  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]].
... ... @@ -815,7 +815,7 @@
815 815  [[image:image-20241126190737-17.png||height="527" width="1114"]]
816 816  
817 817  
818 -=== 3.11.2 Simulate with MQTT.fx ===
860 +=== 3.12.2 Simulate with MQTT.fx ===
819 819  
820 820  
821 821  [[image:image-20241126191118-18.png||height="605" width="835"]]
... ... @@ -823,7 +823,7 @@
823 823  [[image:image-20241126193252-25.png||height="663" width="803"]]
824 824  
825 825  
826 -=== 3.6.3 Configure -NB node ===
868 +=== 3.12.3 Configure -NB node ===
827 827  
828 828  
829 829  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.
... ... @@ -832,8 +832,10 @@
832 832  
833 833  * Configuring the CA Certificate
834 834  
835 -[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
877 +[[image:image-20241126192009-19.png||height="431" width="697"]]
836 836  
879 +[[image:image-20241126192130-21.png||height="426" width="694"]]
880 +
837 837  * Configure client certificate
838 838  
839 839  [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
... ... @@ -851,12 +851,12 @@
851 851  
852 852  * (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
853 853  * (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
854 -* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
855 -* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
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
856 856  * (% style="color:#037691" %)**AT+CLIENT=NULL**
857 857  * (% style="color:#037691" %)**AT+UNAME=NULL**
858 858  * (% style="color:#037691" %)**AT+PWD=NULL**
859 -* (% style="color:#037691" %)**AT+TLSMOD=1,0**
903 +* (% style="color:#037691" %)**AT+TLSMOD=1,2**
860 860  
861 861  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:
862 862  
... ... @@ -938,7 +938,6 @@
938 938  1*. **AT+TDC=7200**  ~/~/  Uplink every 2 hours.
939 939  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.
940 940  
941 -
942 942  == 5.2 Why the uplink JSON format is not standard? ==
943 943  
944 944  
... ... @@ -1036,30 +1036,47 @@
1036 1036  [[image:image-20240226111928-1.png]]
1037 1037  
1038 1038  
1039 -== (% 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? ==
1040 1040  
1041 1041  
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 +
1042 1042  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1043 -=== UDP: ===
1088 +=== **UDP Protocol:** ===
1044 1044  
1090 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
1045 1045  
1046 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1047 -Its downlink command is the same as the AT command, but brackets are required.
1048 -Example:
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.
1049 1049  
1050 -{AT+TDC=300}
1095 +[[image:1750035991532-434.png||height="237" width="495"]]
1051 1051  
1052 1052  
1053 1053  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1054 -=== MQTT: ===
1099 +=== **MQTT Protocol:** ===
1055 1055  
1101 +==== **1. HEX-format** ====
1056 1056  
1057 -Json：
1103 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1058 1058  
1059 -The Json format in MQTT mode needs to be configured with all commands.
1060 -If you have configurations that need to be changed, please change them in the template below.
1061 -Template:
1105 +//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1062 1062  
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 +
1063 1063  {
1064 1064  "AT+SERVADDR":"119.91.62.30,1882",
1065 1065  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1083,26 +1083,78 @@
1083 1083  "AT+TEMPALARM3":"0"
1084 1084  }
1085 1085  
1086 -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.
1087 1087  
1088 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1148 +[[image:1751538862245-924.png]]
1089 1089  
1090 -The supported commands are consistent with LoRaWAN's hex commands.
1091 -Please refer to the following link to obtain the hex format:
1092 1092  
1093 -[[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:**
1094 1094  
1153 +1. Modify the parameters for each AT command in the template as needed.
1154 +1. Send the entire template in one downlink command.
1095 1095  
1096 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1156 +(% style="color:red" %)**Note:**
1097 1097  
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.
1098 1098  
1099 -* **AT Command: AT** **+GETLOG**
1100 1100  
1101 -This command can be used to query upstream logs of data packets.
1102 1102  
1103 -[[image:image-20240701114700-1.png]]
1163 +===== **2.2 Support sending json format commands separately** =====
1104 1104  
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.**
1105 1105  
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 +
1106 1106  == 6.7 How to find the AT Command Password if lost? ==
1107 1107  
1108 1108  
... ... @@ -1120,38 +1120,32 @@
1120 1120  * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1121 1121  * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1122 1122  
1123 -
1124 1124  === Version Confirmation ===
1125 1125  
1126 1126  
1127 1127  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:
1128 1128  
1129 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1130 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1131 -**Firmware version**
1132 -
1133 -**(without FDR1 function)**
1134 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1135 -**Firmware version**
1136 -
1137 -**(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)**
1138 1138  )))
1139 -|(% style="width:210px" %)(((
1246 +|(% style="width:306px" %)(((
1140 1140  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;
1141 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1142 -|(% 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" %)(((
1143 1143  WL03A-NB, SDI-12-NB;
1144 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1251 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1145 1145  After V1.0.8 (including V1.0.2)
1146 1146  )))
1147 -|(% style="width:210px" %)(((
1254 +|(% style="width:306px" %)(((
1148 1148  SW3L-NB, PS-NB;
1149 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1256 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1150 1150  After V1.0.5 (including V1.0.5)
1151 1151  )))
1152 -|(% 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)
1153 1153  
1154 -
1155 1155  === UART connection and firmware update methods ===
1156 1156  
1157 1157  
... ... @@ -1208,4 +1208,11 @@
1208 1208  
1209 1209  
1210 1210  
1317 +== 6.8 ==
1318 +
1319 +
1320 +
1321 +
1322 +
1323 +
1211 1211  
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