Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 185.1 >
edited by kai
on 2024/10/18 09:56
To version < 173.1 >
edited by kai
on 2024/07/29 16:15
>
Change comment: Uploaded new attachment "image-20240729161543-9.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -45,10 +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 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
49 -|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
50 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net/xxx|(% style="width:474px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
51 -
52 52  == 2.2 Speed Up Network Attach time ==
53 53  
54 54  
... ... @@ -288,7 +288,6 @@
288 288  
289 289  ==== 3.4.1.1 Create Device ====
290 290  
291 -
292 292  (% style="color:blue" %)**Add Device**(%%) in DataCake.
293 293  
294 294  [[image:image-20230808162301-1.png||height="453" width="952"]]
... ... @@ -359,11 +359,8 @@
359 359  
360 360  **Step6: Please add the decoder at the payload decoder of the device configuration.**
361 361  
362 -**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]]
363 363  
364 -**Due to version update, please use the following decoder for the new version firmware:**
365 -[[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]]
366 -
367 367  [[image:image-20240129172056-7.png||height="457" width="816"]]
368 368  
369 369  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -545,88 +545,11 @@
545 545  [[image:image-20230802112413-43.png||height="407" width="825"]]
546 546  
547 547  
548 -== 3.7 ThingsBoard.Cloud (via COAP) ==
540 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
549 549  
550 -=== 3.7.1 Configure ThingsBoard ===
542 +=== 3.7.1 Create device & Get Credentials ===
551 551  
552 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
553 553  
554 -
555 -(% style="color:blue" %)**Uplink Converter**
556 -
557 -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.
558 -
559 -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.
560 -
561 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
562 -
563 -
564 -(% style="color:blue" %)**Downlink Converter**
565 -
566 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
567 -
568 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
569 -
570 -
571 -==== 3.7.1.2 COAP Integration Setup ====
572 -
573 -
574 -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" %);
575 -
576 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
577 -
578 -
579 -The next steps is to add the recently created uplink converters;
580 -
581 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
582 -
583 -
584 -==== 3.7.1.3 Add COAP Integration ====
585 -
586 -
587 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
588 -
589 -
590 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
591 -
592 -==== 3.7.2.1 Instruction Description ====
593 -
594 -
595 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
596 -* AT+SERVADDR=COAP Server Address,5683
597 -
598 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
599 -
600 -[[image:image-20240729172305-12.png||height="361" width="624"]]
601 -
602 -Note:The port for the COAP protocol has been fixed to 5683
603 -
604 -
605 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
606 -
607 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
608 -
609 -e.g.
610 -
611 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 -
613 -[[image:image-20240729172415-13.png||height="401" width="694"]]
614 -
615 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
616 -
617 -e.g.
618 -
619 -* AT+URL1=11, "i";  
620 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
621 -
622 -[[image:image-20240729172500-14.png||height="403" width="700"]]
623 -
624 -
625 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
626 -
627 -=== 3.8.1 Create device & Get Credentials ===
628 -
629 -
630 630  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.
631 631  
632 632  [[image:image-20230802112413-44.png]]
... ... @@ -675,7 +675,7 @@
675 675  
676 676  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
677 677  
678 -=== 3.8.2 Simulate with MQTT.fx ===
593 +=== 3.7.2 Simulate with MQTT.fx ===
679 679  
680 680  
681 681  [[image:image-20230802112413-52.png]]
... ... @@ -691,7 +691,7 @@
691 691  [[image:image-20230808105329-3.png]]
692 692  
693 693  
694 -=== 3.8.3 tago data ===
609 +=== 3.7.3 tago data ===
695 695  
696 696  
697 697  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -699,7 +699,7 @@
699 699  [[image:image-20230802112413-51.png||height="184" width="696"]]
700 700  
701 701  
702 -== 3.9 TCP Connection ==
617 +== 3.8 TCP Connection ==
703 703  
704 704  
705 705  (% style="color:blue" %)**AT command:**
... ... @@ -720,17 +720,18 @@
720 720  [[image:image-20230807233631-2.png]]
721 721  
722 722  
723 -== 3.10 AWS Connection ==
638 +== 3.9 AWS Connection ==
724 724  
725 725  
726 726  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]]
727 727  
728 728  
644 +
645 +
729 729  = 4. MQTT/UDP/TCP downlink =
730 730  
731 731  == 4.1 MQTT (via MQTT.fx) ==
732 732  
733 -
734 734  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
735 735  
736 736  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -771,6 +771,11 @@
771 771  (% 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.**
772 772  
773 773  
690 +
691 +
692 +
693 +
694 +
774 774  = 5. FAQ =
775 775  
776 776  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -933,9 +933,8 @@
933 933  [[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/]]
934 934  
935 935  
936 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
857 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
937 937  
938 -
939 939  * **AT Command: AT** **+GETLOG**
940 940  
941 941  This command can be used to query upstream logs of data packets.
... ... @@ -943,108 +943,5 @@
943 943  [[image:image-20240701114700-1.png]]
944 944  
945 945  
946 -== 6.7 How to find the AT Command Password if lost? ==
947 947  
948 -
949 -=== Why can't the password access AT command after upgrade(-NB)? ===
950 -
951 -
952 -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.
953 -
954 -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).
955 -
956 -Two different restore factory Settings configurations.
957 -
958 -(% style="color:blue" %)**AT command:**
959 -
960 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
961 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
962 -
963 -=== Version Confirmation ===
964 -
965 -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:
966 -
967 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
968 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
969 -**Firmware version**
970 -
971 -**(without FDR1 function)**
972 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
973 -**Firmware version**
974 -
975 -**(with FDR1 function)**
976 -)))
977 -|(% style="width:210px" %)(((
978 -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;
979 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
980 -|(% style="width:210px" %)(((
981 -WL03A-NB, SDI-12-NB;
982 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
983 -After V1.0.8 (including V1.0.2)
984 -)))
985 -|(% style="width:210px" %)(((
986 -SW3L-NB, PS-NB;
987 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
988 -After V1.0.5 (including V1.0.5)
989 -)))
990 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
991 -
992 -=== UART connection and firmware update methods ===
993 -
994 -
995 -Users can query passwords only using the UART interface via the STM32CubeProgrammer.
996 -
997 -See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
998 -
999 -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]]**.
1000 -
1001 -
1002 -=== query the password via STM32CubeProgrammer ===
1003 -
1004 -
1005 -Users can use the password address to query the password through STM32CubeProgrammer.
1006 -
1007 -* The password address for old firmware(without FDR1 function) : **0x08019000**
1008 -* The password address for new firmware(with FDR1 function) : **0x08025D00**
1009 -
1010 -(% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1011 -
1012 -
1013 -**Procedure for querying the password(old firmware):**
1014 -
1015 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1016 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1017 -* Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1018 -* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1019 -
1020 -[[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"]]
1021 -
1022 -
1023 -**Procedure for querying the password(new firmware):**
1024 -
1025 -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.
1026 -
1027 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1028 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1029 -* Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1030 -* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1031 -
1032 -[[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"]]
1033 -
1034 -
1035 -
1036 -=== Special case ===
1037 -
1038 -
1039 -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**).
1040 -
1041 -Invalid query screenshot example:
1042 -
1043 -
1044 -[[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"]]
1045 -
1046 -[[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"]]
1047 -
1048 -
1049 -
1050 1050  
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

Applications

Navigation

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