Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 181.1 >
edited by Mengting Qiu
on 2024/08/28 14:37
To version < 209.1 >
edited by Mengting Qiu
on 2024/11/26 19:23
>
Change comment: Uploaded new attachment "image-20241126192315-23.png", version {1}

Summary

Details

Page properties
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: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 +
48 48  == 2.2 Speed Up Network Attach time ==
49 49  
50 50  
... ... @@ -612,8 +612,8 @@
612 612  
613 613  e.g.
614 614  
615 -* AT+URL1=11, "i";  
616 -* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
619 +* AT+URL1=11, "i"
620 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
617 617  
618 618  [[image:image-20240729172500-14.png||height="403" width="700"]]
619 619  
... ... @@ -722,6 +722,132 @@
722 722  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]]
723 723  
724 724  
729 +== 3.11 ThingsEye (via MQTT) ==
730 +
731 +(% class="wikigeneratedid" %)
732 +=== 3.11.1 Configure ThingsEye ===
733 +
734 +
735 +==== 3.11.1.1 Create MQTT integration ====
736 +
737 +
738 +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**;
739 +
740 +
741 +[[image:image-20241126175509-1.png||height="518" width="1081"]]
742 +
743 +
744 +Next, directly select to create a new Uplink data converter and downlink data converter.
745 +
746 +[[image:image-20241126180135-2.png||height="535" width="1092"]]
747 +
748 +[[image:image-20241126180223-3.png||height="518" width="1093"]]
749 +
750 +
751 +(% style="color:blue" %)**Add a topic filter:**
752 +
753 +Consistent with the theme of the node setting.
754 +
755 +(% 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.**
756 +
757 +You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
758 +
759 +[[image:image-20241126181024-4.png||height="521" width="1081"]]
760 +
761 +
762 +==== 3.11.1.2 Add credentials to the MQTT integration ====
763 +
764 +
765 +Click on the MQTT integration you just created.
766 +
767 +[[image:image-20241126181837-5.png||height="365" width="1079"]]
768 +
769 +
770 +Click the edit icon in the upper right corner to enter the edit mode.
771 +
772 +[[image:image-20241126184523-13.png||height="330" width="1075"]]
773 +
774 +
775 +(% style="color:blue" %)**Add credential files.**
776 +
777 +Click this link to download the certificates.
778 +
779 +[[image:image-20241126183032-8.png||height="757" width="976"]]
780 +
781 +When the addition is complete, save the Settings.
782 +
783 +[[image:image-20241126184303-12.png||height="284" width="975"]]
784 +
785 +[[image:image-20241126184211-11.png||height="161" width="977"]]
786 +
787 +
788 +==== 3.11.1.2 Setup uplink and downlink converters ====
789 +
790 +
791 +First, you need to download the **MQTT uplink/downlink JS** **code**.
792 +
793 +* (% style="color:blue" %)**Uplink Converter**
794 +
795 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
796 +
797 +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.
798 +
799 +[[image:image-20241126184906-14.png||height="424" width="1100"]]
800 +
801 +Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
802 +
803 +[[image:image-20241126190131-15.png||height="542" width="1103"]]
804 +
805 +
806 +* (% style="color:blue" %)**Downlink Converter**
807 +
808 +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.
809 +
810 +[[image:image-20241126190251-16.png||height="372" width="1113"]]
811 +
812 +Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
813 +
814 +[[image:image-20241126190737-17.png||height="527" width="1114"]]
815 +
816 +
817 +=== 3.6.2 Simulate with MQTT.fx ===
818 +
819 +
820 +[[image:image-20230802112413-39.png]]
821 +
822 +[[image:image-20230802112413-40.png||height="525" width="980"]]
823 +
824 +
825 +=== 3.6.3 Configure NB-IoT Sensor ===
826 +
827 +
828 +(% style="color:blue" %)**AT Commands**
829 +
830 +* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
831 +
832 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
833 +
834 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
835 +
836 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
837 +
838 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
839 +
840 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
841 +
842 +Test Uplink by click the button for 1 second
843 +
844 +[[image:image-20230802112413-41.png||height="496" width="828"]]
845 +
846 +[[image:image-20230802112413-42.png]]
847 +
848 +[[image:image-20230802112413-43.png||height="407" width="825"]]
849 +
850 +
851 +
852 +
853 +
854 +
725 725  = 4. MQTT/UDP/TCP downlink =
726 726  
727 727  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -942,7 +942,7 @@
942 942  == 6.7 How to find the AT Command Password if lost? ==
943 943  
944 944  
945 -== 6.7.1. Why can't the password access AT command after upgrade(-NB)? ==
1075 +=== Why can't the password access AT command after upgrade(-NB)? ===
946 946  
947 947  
948 948  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.
... ... @@ -956,9 +956,8 @@
956 956  * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
957 957  * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
958 958  
959 -== 6.7.2 Version Confirmation ==
1089 +=== Version Confirmation ===
960 960  
961 -
962 962  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:
963 963  
964 964  (% border="1" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -986,10 +986,9 @@
986 986  )))
987 987  |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
988 988  
1118 +=== UART connection and firmware update methods ===
989 989  
990 -== 6.7.3 UART connection and firmware update methods ==
991 991  
992 -
993 993  Users can query passwords only using the UART interface via the STM32CubeProgrammer.
994 994  
995 995  See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
... ... @@ -997,7 +997,7 @@
997 997  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]]**.
998 998  
999 999  
1000 -== 6.7.4 query the password via STM32CubeProgrammer ==
1128 +=== query the password via STM32CubeProgrammer ===
1001 1001  
1002 1002  
1003 1003  Users can use the password address to query the password through STM32CubeProgrammer.
... ... @@ -1020,7 +1020,7 @@
1020 1020  
1021 1021  **Procedure for querying the password(new firmware):**
1022 1022  
1023 -Refer to [[the old and new firmware division>>http://wiki.dragino.com/xwiki/bin/view/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/#H3.A0VersionConfirmation]] above, and run the firmware first after updating the firmware.
1151 +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.
1024 1024  
1025 1025  * After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1026 1026  * Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
... ... @@ -1031,7 +1031,7 @@
1031 1031  
1032 1032  
1033 1033  
1034 -== 6.7.5. Special case ==
1162 +=== Special case ===
1035 1035  
1036 1036  
1037 1037  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**).
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

Applications

Navigation

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