Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 163.1
edited by Bei Jinggeng
on 2024/05/30 18:06
Change comment: There is no comment for this version
To version 219.2
edited by Xiaoling
on 2024/12/12 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
Content
... ... @@ -45,6 +45,10 @@
45 45  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
46 46  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 47  
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" %)
51 +
48 48  == 2.2 Speed Up Network Attach time ==
49 49  
50 50  
... ... @@ -62,6 +62,7 @@
62 62  
63 63  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64 64  
69 +By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
65 65  
66 66  See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
67 67  
... ... @@ -163,6 +163,7 @@
163 163  
164 164  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
165 165  
171 +
166 166  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
167 167  
168 168  
... ... @@ -204,6 +204,7 @@
204 204  
205 205  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
206 206  
213 +
207 207  ==== 3.3.3.2 Uplink Examples ====
208 208  
209 209  
... ... @@ -265,6 +265,7 @@
265 265  |(% 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" %)
266 266  |(% 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" %)
267 267  
275 +
268 268  == 3.4 [[Datacake>>https://datacake.co/]] ==
269 269  
270 270  
... ... @@ -279,10 +279,12 @@
279 279  
280 280  * (% 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.
281 281  
290 +
282 282  === 3.4.1 For device Already has template ===
283 283  
284 284  ==== 3.4.1.1 Create Device ====
285 285  
295 +
286 286  (% style="color:blue" %)**Add Device**(%%) in DataCake.
287 287  
288 288  [[image:image-20230808162301-1.png||height="453" width="952"]]
... ... @@ -353,8 +353,11 @@
353 353  
354 354  **Step6: Please add the decoder at the payload decoder of the device configuration.**
355 355  
356 -**Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
366 +**Decoder location: **[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
357 357  
368 +**Due to version update, please use the following decoder for the new version firmware:**
369 +[[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]
370 +
358 358  [[image:image-20240129172056-7.png||height="457" width="816"]]
359 359  
360 360  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -445,6 +445,7 @@
445 445  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
446 446  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
447 447  
461 +
448 448  == 3.6 ThingsBoard.Cloud (via MQTT) ==
449 449  
450 450  === 3.6.1 Configure ThingsBoard ===
... ... @@ -504,7 +504,6 @@
504 504  
505 505  === 3.6.2 Simulate with MQTT.fx ===
506 506  
507 -
508 508  [[image:image-20230802112413-39.png]]
509 509  
510 510  [[image:image-20230802112413-40.png||height="525" width="980"]]
... ... @@ -536,11 +536,88 @@
536 536  [[image:image-20230802112413-43.png||height="407" width="825"]]
537 537  
538 538  
539 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
552 +== 3.7 ThingsBoard.Cloud (via COAP) ==
540 540  
541 -=== 3.7.1 Create device & Get Credentials ===
554 +=== 3.7.1 Configure ThingsBoard ===
542 542  
556 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
543 543  
558 +
559 +(% style="color:blue" %)**Uplink Converter**
560 +
561 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
562 +
563 +To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
564 +
565 +[[image:image-20240729141300-1.png||height="552" width="1115"]]
566 +
567 +
568 +(% style="color:blue" %)**Downlink Converter**
569 +
570 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
571 +
572 +[[image:image-20240729142505-3.png||height="507" width="1023"]]
573 +
574 +
575 +==== 3.7.1.2 COAP Integration Setup ====
576 +
577 +
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" %);
579 +
580 +[[image:image-20240729144058-4.png||height="506" width="1021"]]
581 +
582 +
583 +The next steps is to add the recently created uplink converters;
584 +
585 +[[image:image-20240729150142-5.png||height="507" width="1023"]]
586 +
587 +
588 +==== 3.7.1.3 Add COAP Integration ====
589 +
590 +
591 +==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
592 +
593 +
594 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
595 +
596 +==== 3.7.2.1 Instruction Description ====
597 +
598 +
599 +* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
600 +* AT+SERVADDR=COAP Server Address,5683
601 +
602 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
603 +
604 +[[image:image-20240729172305-12.png||height="361" width="624"]]
605 +
606 +Note:The port for the COAP protocol has been fixed to 5683
607 +
608 +
609 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
610 +
611 +If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
612 +
613 +e.g.
614 +
615 +* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
616 +
617 +[[image:image-20240729172415-13.png||height="401" width="694"]]
618 +
619 +If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
620 +
621 +e.g.
622 +
623 +* AT+URL1=11, "i"
624 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
625 +
626 +[[image:image-20240729172500-14.png||height="403" width="700"]]
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 +
544 544  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.
545 545  
546 546  [[image:image-20230802112413-44.png]]
... ... @@ -589,7 +589,7 @@
589 589  
590 590  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
591 591  
592 -=== 3.7.2 Simulate with MQTT.fx ===
682 +=== 3.8.2 Simulate with MQTT.fx ===
593 593  
594 594  
595 595  [[image:image-20230802112413-52.png]]
... ... @@ -605,7 +605,7 @@
605 605  [[image:image-20230808105329-3.png]]
606 606  
607 607  
608 -=== 3.7.3 tago data ===
698 +=== 3.8.3 tago data ===
609 609  
610 610  
611 611  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -613,7 +613,7 @@
613 613  [[image:image-20230802112413-51.png||height="184" width="696"]]
614 614  
615 615  
616 -== 3.8 TCP Connection ==
706 +== 3.9 TCP Connection ==
617 617  
618 618  
619 619  (% style="color:blue" %)**AT command:**
... ... @@ -634,12 +634,161 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
727 +== 3.10 AWS Connection ==
637 637  
638 638  
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 +
732 +
733 +== 3.11 ThingsEye (via MQTT) ==
734 +
735 +=== 3.11.1 Configure ThingsEye ===
736 +
737 +==== 3.11.1.1 Create MQTT integration ====
738 +
739 +
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**;
741 +
742 +[[image:image-20241126175509-1.png||height="518" width="1081"]]
743 +
744 +
745 +Next, directly select to create a new Uplink data converter and downlink data converter.
746 +
747 +[[image:image-20241126180135-2.png||height="535" width="1092"]]
748 +
749 +[[image:image-20241126180223-3.png||height="518" width="1093"]]
750 +
751 +
752 +(% style="color:blue" %)**Add a topic filter:**
753 +
754 +Consistent with the theme of the node setting.
755 +
756 +(% style="color:red" %)**Note: Recommended MQTT broker: lns1.thingseye.io 8883, fixed use. Topic can be changed on their own, but it need to be consistent with the node's publish and subscribe topic.**
757 +
758 +You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
759 +
760 +[[image:image-20241126181024-4.png||height="521" width="1081"]]
761 +
762 +
763 +==== 3.11.1.2 Add credentials to the MQTT integration ====
764 +
765 +
766 +Click on the MQTT integration you just created.
767 +
768 +[[image:image-20241126181837-5.png||height="365" width="1079"]]
769 +
770 +
771 +Click the edit icon in the upper right corner to enter the edit mode.
772 +
773 +[[image:image-20241126184523-13.png||height="330" width="1075"]]
774 +
775 +
776 +(% style="color:blue" %)**Add credential files.**
777 +
778 +Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
779 +
780 +[[image:image-20241126183032-8.png||height="757" width="976"]]
781 +
782 +When the addition is complete, save the Settings.
783 +
784 +[[image:image-20241126184303-12.png||height="284" width="975"]]
785 +
786 +[[image:image-20241126184211-11.png||height="161" width="977"]]
787 +
788 +
789 +==== 3.11.1.2 Setup uplink and downlink converters ====
790 +
791 +
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]].
793 +
794 +* (% style="color:blue" %)**Uplink Converter**
795 +
796 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
797 +
798 +Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT uplink converter that was newly created when the integration was created.
799 +
800 +[[image:image-20241126184906-14.png||height="424" width="1100"]]
801 +
802 +Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
803 +
804 +[[image:image-20241126190131-15.png||height="542" width="1103"]]
805 +
806 +
807 +* (% style="color:blue" %)**Downlink Converter**
808 +
809 +Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT downlink converter that was newly created when the integration was created.
810 +
811 +[[image:image-20241126190251-16.png||height="372" width="1113"]]
812 +
813 +Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
814 +
815 +[[image:image-20241126190737-17.png||height="527" width="1114"]]
816 +
817 +
818 +=== 3.11.2 Simulate with MQTT.fx ===
819 +
820 +
821 +[[image:image-20241126191118-18.png||height="605" width="835"]]
822 +
823 +[[image:image-20241126193252-25.png||height="663" width="803"]]
824 +
825 +
826 +=== 3.6.3 Configure -NB node ===
827 +
828 +
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.
830 +
831 +Screenshot of successful certificate configuration:
832 +
833 +* Configuring the CA Certificate
834 +
835 +[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
836 +
837 +* Configure client certificate
838 +
839 +[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
840 +
841 +* Configure client private key
842 +
843 +[[image:image-20241126192415-24.png||height="435" width="737"]]
844 +
845 +
846 +When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
847 +
848 +Then configure the -NB node to connect to the ThingsEye platform:
849 +
850 +(% style="color:blue" %)**AT Commands**
851 +
852 +* (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
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
856 +* (% style="color:#037691" %)**AT+CLIENT=NULL**
857 +* (% style="color:#037691" %)**AT+UNAME=NULL**
858 +* (% style="color:#037691" %)**AT+PWD=NULL**
859 +* (% style="color:#037691" %)**AT+TLSMOD=1,0**
860 +
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 +
863 +[[image:image-20241126193458-26.png||height="375" width="1012"]]
864 +
865 +[[image:image-20241126193609-27.png||height="424" width="1014"]]
866 +
867 +
868 +Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
869 +
870 +[[image:image-20241126194018-28.png||height="318" width="1076"]]
871 +
872 +You can view the data that has just been uplink on the device:
873 +
874 +[[image:image-20241126194123-29.png||height="486" width="1073"]]
875 +
876 +
639 639  = 4. MQTT/UDP/TCP downlink =
640 640  
641 641  == 4.1 MQTT (via MQTT.fx) ==
642 642  
881 +
643 643  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
644 644  
645 645  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -680,11 +680,6 @@
680 680  (% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
681 681  
682 682  
683 -
684 -
685 -
686 -
687 -
688 688  = 5. FAQ =
689 689  
690 690  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -700,10 +700,11 @@
700 700  1. Give more sampling data points.
701 701  1. Increase reliable in transmission. For example. If user set
702 702  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)
703 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
704 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
937 +1*. **AT+NOUD=24**  ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
938 +1*. **AT+TDC=7200**  ~/~/  Uplink every 2 hours.
705 705  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.
706 706  
941 +
707 707  == 5.2 Why the uplink JSON format is not standard? ==
708 708  
709 709  
... ... @@ -714,6 +714,14 @@
714 714  [[image:image-20240229233154-1.png]]
715 715  
716 716  
952 +== 5.3 What is the data consumption for different transfer mode？ ==
953 +
954 +
955 +For the data consumption of NB-IoT End node in different transfer mode, reference link:
956 +
957 +[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
958 +
959 +
717 717  = 6. Trouble Shooting: =
718 718  
719 719  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -795,9 +795,11 @@
795 795  
796 796  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
797 797  
1041 +
798 798  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
799 799  === UDP: ===
800 800  
1045 +
801 801  (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
802 802  Its downlink command is the same as the AT command, but brackets are required.
803 803  Example:
... ... @@ -808,6 +808,7 @@
808 808  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
809 809  === MQTT: ===
810 810  
1056 +
811 811  Json：
812 812  
813 813  The Json format in MQTT mode needs to be configured with all commands.
... ... @@ -846,4 +846,121 @@
846 846  
847 847  [[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/]]
848 848  
1095 +
1096 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1097 +
1098 +
1099 +* **AT Command: AT** **+GETLOG**
1100 +
1101 +This command can be used to query upstream logs of data packets.
1102 +
1103 +[[image:image-20240701114700-1.png]]
1104 +
1105 +
1106 +== 6.7 How to find the AT Command Password if lost? ==
1107 +
1108 +
1109 +=== Why can't the password access AT command after upgrade(-NB)? ===
1110 +
1111 +
1112 +Because the new version of -NB firmware has updated the factory reset function, users can choose to restore all parameters to factory Settings, or keep the password to restore the rest of the parameters to factory Settings.
1113 +
1114 +This update changes the password address of the firmware, so the password will be invalid after the customer upgrades from the old version of firmware (without FDR1 function) to the new version of firmware (with FDR1 function).
1115 +
1116 +Two different restore factory Settings configurations.
1117 +
1118 +(% style="color:blue" %)**AT command:**
1119 +
1120 +* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1121 +* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1122 +
1123 +
1124 +=== Version Confirmation ===
1125 +
1126 +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:
1127 +
1128 +(% border="1" style="background-color:#f2f2f2; width:510px" %)
1129 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1130 +**Firmware version**
1131 +
1132 +**(without FDR1 function)**
1133 +)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1134 +**Firmware version**
1135 +
1136 +**(with FDR1 function)**
1137 +)))
1138 +|(% style="width:210px" %)(((
1139 +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;
1140 +)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1141 +|(% style="width:210px" %)(((
1142 +WL03A-NB, SDI-12-NB;
1143 +)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1144 +After V1.0.8 (including V1.0.2)
1145 +)))
1146 +|(% style="width:210px" %)(((
1147 +SW3L-NB, PS-NB;
1148 +)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1149 +After V1.0.5 (including V1.0.5)
1150 +)))
1151 +|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1152 +
1153 +
1154 +=== UART connection and firmware update methods ===
1155 +
1156 +
1157 +Users can query passwords only using the UART interface via the STM32CubeProgrammer.
1158 +
1159 +See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
1160 +
1161 +update firmware through UART TTL interface :** [[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
1162 +
1163 +
1164 +=== query the password via STM32CubeProgrammer ===
1165 +
1166 +
1167 +Users can use the password address to query the password through STM32CubeProgrammer.
1168 +
1169 +* The password address for old firmware(without FDR1 function) : **0x08019000**
1170 +* The password address for new firmware(with FDR1 function) : **0x08025D00**
1171 +
1172 +(% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1173 +
1174 +
1175 +**Procedure for querying the password(old firmware):**
1176 +
1177 +* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1178 +* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1179 +* Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1180 +* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1181 +
1182 +[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827171901-3.png?width=912&height=528&rev=1.1||alt="image-20240827171901-3.png"]]
1183 +
1184 +
1185 +**Procedure for querying the password(new firmware):**
1186 +
1187 +Refer to [[the old and new firmware division>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#HVersionConfirmation]] above, and run the firmware first after updating the firmware.
1188 +
1189 +* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1190 +* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1191 +* Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1192 +* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1193 +
1194 +[[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"]]
1195 +
1196 +
1197 +
1198 +=== Special case ===
1199 +
1200 +
1201 +If the user has never changed the password manually, the user cannot find the valid password through the above two password addresses. In this case, the valid password is still the original password on the node box label (**AT+PIN**).
1202 +
1203 +Invalid query screenshot example:
1204 +
1205 +
1206 +[[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"]]
1207 +
1208 +[[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"]]
1209 +
1210 +
1211 +
849 849  
image-20240701114700-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +166.8 KB
Content
image-20240729172234-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +57.8 KB
Content
image-20240729172305-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +49.3 KB
Content
image-20240729172415-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +54.3 KB
Content
image-20240729172500-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
image-20241126175509-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +241.0 KB
Content
image-20241126180135-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +192.8 KB
Content
image-20241126180223-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +213.1 KB
Content
image-20241126181024-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +238.8 KB
Content
image-20241126181837-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +106.7 KB
Content
image-20241126182007-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +136.3 KB
Content
image-20241126182135-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +91.3 KB
Content
image-20241126183032-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +111.4 KB
Content
image-20241126183803-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20241126184136-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +15.7 KB
Content
image-20241126184211-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20241126184303-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +81.7 KB
Content
image-20241126184523-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +88.7 KB
Content
image-20241126184906-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +108.0 KB
Content
image-20241126190131-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +267.9 KB
Content
image-20241126190251-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +94.2 KB
Content
image-20241126190737-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +253.7 KB
Content
image-20241126191118-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +61.4 KB
Content
image-20241126192009-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +113.6 KB
Content
image-20241126192122-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +105.2 KB
Content
image-20241126192130-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +105.2 KB
Content
image-20241126192246-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +87.7 KB
Content
image-20241126192315-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.0 KB
Content
image-20241126192415-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +88.2 KB
Content
image-20241126193252-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +64.2 KB
Content
image-20241126193458-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +144.3 KB
Content
image-20241126193609-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +167.5 KB
Content
image-20241126194018-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +63.5 KB
Content
image-20241126194123-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.7 KB
Content