Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 184.1 >
edited by Bei Jinggeng
on 2024/09/20 18:03
To version < 177.1 >
edited by kai
on 2024/07/29 17:25
>
Change comment: Uploaded new attachment "image-20240729172500-14.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.kai
Content
... ... @@ -45,11 +45,6 @@
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  
... ... @@ -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]]
357 +**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,6 +546,7 @@
546 546  [[image:image-20230802112413-43.png||height="407" width="825"]]
547 547  
548 548  
540 +
549 549  == 3.7 ThingsBoard.Cloud (via COAP) ==
550 550  
551 551  === 3.7.1 Configure ThingsBoard ===
... ... @@ -572,7 +572,7 @@
572 572  ==== 3.7.1.2 COAP Integration Setup ====
573 573  
574 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" %);
567 +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 576  
577 577  [[image:image-20240729144058-4.png||height="506" width="1021"]]
578 578  
... ... @@ -584,45 +584,23 @@
584 584  
585 585  ==== 3.7.1.3 Add COAP Integration ====
586 586  
579 +==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
587 587  
588 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
589 589  
590 -
591 591  === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
592 592  
593 593  ==== 3.7.2.1 Instruction Description ====
594 594  
595 -
596 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
597 597  * AT+SERVADDR=COAP Server Address,5683
598 598  
599 599  Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
600 600  
601 -[[image:image-20240729172305-12.png||height="361" width="624"]]
602 -
603 603  Note:The port for the COAP protocol has been fixed to 5683
604 604  
592 +AT+URL1=11,character length,""
605 605  
606 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
594 +If the module used is BC660K, only one URL directive needs to be configured, e.g. AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
607 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 626  == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
627 627  
628 628  === 3.8.1 Create device & Get Credentials ===
... ... @@ -727,11 +727,12 @@
727 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 729  
700 +
701 +
730 730  = 4. MQTT/UDP/TCP downlink =
731 731  
732 732  == 4.1 MQTT (via MQTT.fx) ==
733 733  
734 -
735 735  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
736 736  
737 737  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -772,6 +772,11 @@
772 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 773  
774 774  
746 +
747 +
748 +
749 +
750 +
775 775  = 5. FAQ =
776 776  
777 777  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -934,9 +934,8 @@
934 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 935  
936 936  
937 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
913 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
938 938  
939 -
940 940  * **AT Command: AT** **+GETLOG**
941 941  
942 942  This command can be used to query upstream logs of data packets.
... ... @@ -944,108 +944,5 @@
944 944  [[image:image-20240701114700-1.png]]
945 945  
946 946  
947 -== 6.7 How to find the AT Command Password if lost? ==
948 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 1051  

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0