Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 184.1
edited by Bei Jinggeng
on 2024/09/20 18:03
Change comment: There is no comment for this version
To version 153.1
edited by Mengting Qiu
on 2024/04/17 18:07
Change comment: Uploaded new attachment "image-20240417180737-3.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.ting
Content
... ... @@ -40,16 +40,11 @@
40 40  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
41 41  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
42 42  
43 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
44 -)))|(% style="width:135px" %)UK: Band20
43 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
44 +)))|(% style="width:135px" %)
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 -
49 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
50 -|(% 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**
51 -|(% 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" %)
52 -
53 53  == 2.2 Speed Up Network Attach time ==
54 54  
55 55  
... ... @@ -67,7 +67,6 @@
67 67  
68 68  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
69 69  
70 -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.
71 71  
72 72  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/]]**
73 73  
... ... @@ -289,7 +289,6 @@
289 289  
290 290  ==== 3.4.1.1 Create Device ====
291 291  
292 -
293 293  (% style="color:blue" %)**Add Device**(%%) in DataCake.
294 294  
295 295  [[image:image-20230808162301-1.png||height="453" width="952"]]
... ... @@ -360,11 +360,8 @@
360 360  
361 361  **Step6: Please add the decoder at the payload decoder of the device configuration.**
362 362  
363 -**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]]
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]]
364 364  
365 -**Due to version update, please use the following decoder for the new version firmware:**
366 -[[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]]
367 -
368 368  [[image:image-20240129172056-7.png||height="457" width="816"]]
369 369  
370 370  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -546,88 +546,11 @@
546 546  [[image:image-20230802112413-43.png||height="407" width="825"]]
547 547  
548 548  
549 -== 3.7 ThingsBoard.Cloud (via COAP) ==
539 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
550 550  
551 -=== 3.7.1 Configure ThingsBoard ===
541 +=== 3.7.1 Create device & Get Credentials ===
552 552  
553 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
554 554  
555 -
556 -(% style="color:blue" %)**Uplink Converter**
557 -
558 -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.
559 -
560 -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.
561 -
562 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
563 -
564 -
565 -(% style="color:blue" %)**Downlink Converter**
566 -
567 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
568 -
569 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
570 -
571 -
572 -==== 3.7.1.2 COAP Integration Setup ====
573 -
574 -
575 -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" %);
576 -
577 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
578 -
579 -
580 -The next steps is to add the recently created uplink converters;
581 -
582 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
583 -
584 -
585 -==== 3.7.1.3 Add COAP Integration ====
586 -
587 -
588 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
589 -
590 -
591 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
592 -
593 -==== 3.7.2.1 Instruction Description ====
594 -
595 -
596 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
597 -* AT+SERVADDR=COAP Server Address,5683
598 -
599 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
600 -
601 -[[image:image-20240729172305-12.png||height="361" width="624"]]
602 -
603 -Note:The port for the COAP protocol has been fixed to 5683
604 -
605 -
606 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
607 -
608 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
609 -
610 -e.g.
611 -
612 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
613 -
614 -[[image:image-20240729172415-13.png||height="401" width="694"]]
615 -
616 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
617 -
618 -e.g.
619 -
620 -* AT+URL1=11, "i";  
621 -* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
622 -
623 -[[image:image-20240729172500-14.png||height="403" width="700"]]
624 -
625 -
626 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
627 -
628 -=== 3.8.1 Create device & Get Credentials ===
629 -
630 -
631 631  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.
632 632  
633 633  [[image:image-20230802112413-44.png]]
... ... @@ -676,7 +676,7 @@
676 676  
677 677  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
678 678  
679 -=== 3.8.2 Simulate with MQTT.fx ===
592 +=== 3.7.2 Simulate with MQTT.fx ===
680 680  
681 681  
682 682  [[image:image-20230802112413-52.png]]
... ... @@ -692,7 +692,7 @@
692 692  [[image:image-20230808105329-3.png]]
693 693  
694 694  
695 -=== 3.8.3 tago data ===
608 +=== 3.7.3 tago data ===
696 696  
697 697  
698 698  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -700,7 +700,7 @@
700 700  [[image:image-20230802112413-51.png||height="184" width="696"]]
701 701  
702 702  
703 -== 3.9 TCP Connection ==
616 +== 3.8 TCP Connection ==
704 704  
705 705  
706 706  (% style="color:blue" %)**AT command:**
... ... @@ -721,62 +721,11 @@
721 721  [[image:image-20230807233631-2.png]]
722 722  
723 723  
724 -== 3.10 AWS Connection ==
637 += 4. FAQ =
725 725  
639 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
726 726  
727 -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]]
728 728  
729 -
730 -= 4. MQTT/UDP/TCP downlink =
731 -
732 -== 4.1 MQTT (via MQTT.fx) ==
733 -
734 -
735 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
736 -
737 -**1.** Configure node MQTT connection (via MQTT.fx):
738 -
739 -(% style="color:blue" %)**AT command:**
740 -
741 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
742 -
743 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
744 -
745 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
746 -
747 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
748 -
749 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
750 -
751 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
752 -
753 -(% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**
754 -
755 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
756 -
757 -
758 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
759 -
760 -[[image:image-20240418144337-1.png||height="709" width="802"]]
761 -
762 -**3. **The downlink command can be successfully sent only when the downlink port is open.
763 -
764 - The downlink port is opened for about 3 seconds after uplink packets are sent.
765 -
766 - Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
767 -
768 -[[image:image-20240418150435-3.png||height="582" width="659"]]
769 -
770 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
771 -
772 -(% 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.**
773 -
774 -
775 -= 5. FAQ =
776 -
777 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
778 -
779 -
780 780  The NB series has the feature for Multi Sampling and one uplink. See one of them
781 781  
782 782  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
... ... @@ -791,7 +791,7 @@
791 791  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
792 792  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.
793 793  
794 -== 5.2 Why the uplink JSON format is not standard? ==
656 +== 4.2 Why the uplink JSON format is not standard? ==
795 795  
796 796  
797 797  The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
... ... @@ -801,9 +801,9 @@
801 801  [[image:image-20240229233154-1.png]]
802 802  
803 803  
804 -= 6. Trouble Shooting: =
666 += 5. Trouble Shooting: =
805 805  
806 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
668 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
807 807  
808 808  
809 809  There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.
... ... @@ -830,7 +830,7 @@
830 830  If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.
831 831  
832 832  
833 -== 6.2 Issue: "NBIOT did not respond" ==
695 +== 5.2 Issue: "NBIOT did not respond" ==
834 834  
835 835  
836 836  (% class="box errormessage" %)
... ... @@ -858,7 +858,7 @@
858 858  [[image:image-20240208001740-1.png]]
859 859  
860 860  
861 -== 6.3 Issue: "Failed to readI MSI number" ==
723 +== 5.3 Issue: "Failed to readI MSI number" ==
862 862  
863 863  
864 864  (% class="box errormessage" %)
... ... @@ -872,180 +872,9 @@
872 872  Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
873 873  
874 874  
875 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
737 +== 5.4 Why sometime the AT Command is slow in reponse? ==
876 876  
877 877  
878 878  When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
879 879  
880 880  [[image:image-20240226111928-1.png]]
881 -
882 -
883 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
884 -
885 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
886 -=== UDP: ===
887 -
888 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
889 -Its downlink command is the same as the AT command, but brackets are required.
890 -Example:
891 -
892 -{AT+TDC=300}
893 -
894 -
895 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
896 -=== MQTT: ===
897 -
898 -Json：
899 -
900 -The Json format in MQTT mode needs to be configured with all commands.
901 -If you have configurations that need to be changed, please change them in the template below.
902 -Template:
903 -
904 -{
905 -"AT+SERVADDR":"119.91.62.30,1882",
906 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
907 -"AT+UNAME":"usenamedragino",
908 -"AT+PWD":"passworddragino",
909 -"AT+PUBTOPIC":"123",
910 -"AT+SUBTOPIC":"321",
911 -"AT+TDC":"7200",
912 -"AT+INTMOD":"0",
913 -"AT+APN":"NULL",
914 -"AT+5VT":"0",
915 -"AT+PRO":"3,5",
916 -"AT+TR":"900",
917 -"AT+NOUD":"0",
918 -"AT+CSQTIME":"5",
919 -"AT+DNSTIMER":"0",
920 -"AT+TLSMOD":"0,0",
921 -"AT+MQOS":"0",
922 -"AT+TEMPALARM1":"0",
923 -"AT+TEMPALARM2":"10",
924 -"AT+TEMPALARM3":"0"
925 -}
926 -
927 -Hex：
928 -
929 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
930 -
931 -The supported commands are consistent with LoRaWAN's hex commands.
932 -Please refer to the following link to obtain the hex format:
933 -
934 -[[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/]]
935 -
936 -
937 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
938 -
939 -
940 -* **AT Command: AT** **+GETLOG**
941 -
942 -This command can be used to query upstream logs of data packets.
943 -
944 -[[image:image-20240701114700-1.png]]
945 -
946 -
947 -== 6.7 How to find the AT Command Password if lost? ==
948 -
949 -
950 -=== Why can't the password access AT command after upgrade(-NB)? ===
951 -
952 -
953 -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.
954 -
955 -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).
956 -
957 -Two different restore factory Settings configurations.
958 -
959 -(% style="color:blue" %)**AT command:**
960 -
961 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
962 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
963 -
964 -=== Version Confirmation ===
965 -
966 -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:
967 -
968 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
969 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
970 -**Firmware version**
971 -
972 -**(without FDR1 function)**
973 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
974 -**Firmware version**
975 -
976 -**(with FDR1 function)**
977 -)))
978 -|(% style="width:210px" %)(((
979 -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;
980 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
981 -|(% style="width:210px" %)(((
982 -WL03A-NB, SDI-12-NB;
983 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
984 -After V1.0.8 (including V1.0.2)
985 -)))
986 -|(% style="width:210px" %)(((
987 -SW3L-NB, PS-NB;
988 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
989 -After V1.0.5 (including V1.0.5)
990 -)))
991 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
992 -
993 -=== UART connection and firmware update methods ===
994 -
995 -
996 -Users can query passwords only using the UART interface via the STM32CubeProgrammer.
997 -
998 -See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
999 -
1000 -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]]**.
1001 -
1002 -
1003 -=== query the password via STM32CubeProgrammer ===
1004 -
1005 -
1006 -Users can use the password address to query the password through STM32CubeProgrammer.
1007 -
1008 -* The password address for old firmware(without FDR1 function) : **0x08019000**
1009 -* The password address for new firmware(with FDR1 function) : **0x08025D00**
1010 -
1011 -(% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1012 -
1013 -
1014 -**Procedure for querying the password(old firmware):**
1015 -
1016 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1017 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1018 -* Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1019 -* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1020 -
1021 -[[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"]]
1022 -
1023 -
1024 -**Procedure for querying the password(new firmware):**
1025 -
1026 -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.
1027 -
1028 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1029 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1030 -* Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1031 -* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1032 -
1033 -[[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"]]
1034 -
1035 -
1036 -
1037 -=== Special case ===
1038 -
1039 -
1040 -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**).
1041 -
1042 -Invalid query screenshot example:
1043 -
1044 -
1045 -[[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"]]
1046 -
1047 -[[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"]]
1048 -
1049 -
1050 -
1051 -
image-20240418144337-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -103.4 KB
Content
image-20240701114700-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -166.8 KB
Content
image-20240729172234-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -57.8 KB
Content
image-20240729172305-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20240729172415-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -54.3 KB
Content
image-20240729172500-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -48.6 KB
Content