Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 217.2 >
edited by Mengting Qiu
on 2024/11/27 15:40
To version < 181.1 >
edited by Mengting Qiu
on 2024/08/28 14:37
>
Change comment: There is no comment for this version

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  
... ... @@ -616,8 +616,8 @@
616 616  
617 617  e.g.
618 618  
619 -* AT+URL1=11, "i"
620 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
615 +* AT+URL1=11, "i";  
616 +* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
621 621  
622 622  [[image:image-20240729172500-14.png||height="403" width="700"]]
623 623  
... ... @@ -726,152 +726,6 @@
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  
729 -== 3.11 ThingsEye (via MQTT) ==
730 -
731 -=== 3.11.1 Configure ThingsEye ===
732 -
733 -
734 -==== 3.11.1.1 Create MQTT integration ====
735 -
736 -
737 -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**;
738 -
739 -[[image:image-20241126175509-1.png||height="518" width="1081"]]
740 -
741 -
742 -Next, directly select to create a new Uplink data converter and downlink data converter.
743 -
744 -[[image:image-20241126180135-2.png||height="535" width="1092"]]
745 -
746 -[[image:image-20241126180223-3.png||height="518" width="1093"]]
747 -
748 -
749 -(% style="color:blue" %)**Add a topic filter:**
750 -
751 -Consistent with the theme of the node setting.
752 -
753 -(% 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.**
754 -
755 -You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
756 -
757 -[[image:image-20241126181024-4.png||height="521" width="1081"]]
758 -
759 -
760 -==== 3.11.1.2 Add credentials to the MQTT integration ====
761 -
762 -
763 -Click on the MQTT integration you just created.
764 -
765 -[[image:image-20241126181837-5.png||height="365" width="1079"]]
766 -
767 -
768 -Click the edit icon in the upper right corner to enter the edit mode.
769 -
770 -[[image:image-20241126184523-13.png||height="330" width="1075"]]
771 -
772 -
773 -(% style="color:blue" %)**Add credential files.**
774 -
775 -Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
776 -
777 -[[image:image-20241126183032-8.png||height="757" width="976"]]
778 -
779 -When the addition is complete, save the Settings.
780 -
781 -[[image:image-20241126184303-12.png||height="284" width="975"]]
782 -
783 -[[image:image-20241126184211-11.png||height="161" width="977"]]
784 -
785 -
786 -==== 3.11.1.2 Setup uplink and downlink converters ====
787 -
788 -
789 -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]].
790 -
791 -* (% style="color:blue" %)**Uplink Converter**
792 -
793 -The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
794 -
795 -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.
796 -
797 -[[image:image-20241126184906-14.png||height="424" width="1100"]]
798 -
799 -Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
800 -
801 -[[image:image-20241126190131-15.png||height="542" width="1103"]]
802 -
803 -
804 -* (% style="color:blue" %)**Downlink Converter**
805 -
806 -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.
807 -
808 -[[image:image-20241126190251-16.png||height="372" width="1113"]]
809 -
810 -Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
811 -
812 -[[image:image-20241126190737-17.png||height="527" width="1114"]]
813 -
814 -
815 -=== 3.11.2 Simulate with MQTT.fx ===
816 -
817 -
818 -[[image:image-20241126191118-18.png||height="605" width="835"]]
819 -
820 -[[image:image-20241126193252-25.png||height="663" width="803"]]
821 -
822 -
823 -=== 3.6.3 Configure -NB node ===
824 -
825 -
826 -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.
827 -
828 -Screenshot of successful certificate configuration:
829 -
830 -* Configuring the CA Certificate
831 -
832 -[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
833 -
834 -* Configure client certificate
835 -
836 -[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
837 -
838 -* Configure client private key
839 -
840 -[[image:image-20241126192415-24.png||height="435" width="737"]]
841 -
842 -
843 -When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
844 -
845 -Then configure the -NB node to connect to the ThingsEye platform:
846 -
847 -(% style="color:blue" %)**AT Commands**
848 -
849 -* (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
850 -* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
851 -* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
852 -* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
853 -* (% style="color:#037691" %)**AT+CLIENT=NULL**
854 -* (% style="color:#037691" %)**AT+UNAME=NULL**
855 -* (% style="color:#037691" %)**AT+PWD=NULL**
856 -* (% style="color:#037691" %)**AT+TLSMOD=1,0**
857 -
858 -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:
859 -
860 -[[image:image-20241126193458-26.png||height="375" width="1012"]]
861 -
862 -[[image:image-20241126193609-27.png||height="424" width="1014"]]
863 -
864 -
865 -Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
866 -
867 -[[image:image-20241126194018-28.png||height="318" width="1076"]]
868 -
869 -You can view the data that has just been uplink on the device:
870 -
871 -[[image:image-20241126194123-29.png||height="486" width="1073"]]
872 -
873 -
874 -
875 875  = 4. MQTT/UDP/TCP downlink =
876 876  
877 877  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -1092,7 +1092,7 @@
1092 1092  == 6.7 How to find the AT Command Password if lost? ==
1093 1093  
1094 1094  
1095 -=== Why can't the password access AT command after upgrade(-NB)? ===
945 +== 6.7.1. Why can't the password access AT command after upgrade(-NB)? ==
1096 1096  
1097 1097  
1098 1098  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.
... ... @@ -1106,8 +1106,9 @@
1106 1106  * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1107 1107  * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1108 1108  
1109 -=== Version Confirmation ===
959 +== 6.7.2 Version Confirmation ==
1110 1110  
961 +
1111 1111  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:
1112 1112  
1113 1113  (% border="1" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -1135,9 +1135,10 @@
1135 1135  )))
1136 1136  |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1137 1137  
1138 -=== UART connection and firmware update methods ===
1139 1139  
990 +== 6.7.3 UART connection and firmware update methods ==
1140 1140  
992 +
1141 1141  Users can query passwords only using the UART interface via the STM32CubeProgrammer.
1142 1142  
1143 1143  See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
... ... @@ -1145,7 +1145,7 @@
1145 1145  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]]**.
1146 1146  
1147 1147  
1148 -=== query the password via STM32CubeProgrammer ===
1000 +== 6.7.4 query the password via STM32CubeProgrammer ==
1149 1149  
1150 1150  
1151 1151  Users can use the password address to query the password through STM32CubeProgrammer.
... ... @@ -1168,7 +1168,7 @@
1168 1168  
1169 1169  **Procedure for querying the password(new firmware):**
1170 1170  
1171 -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.
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.
1172 1172  
1173 1173  * After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1174 1174  * Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
... ... @@ -1179,7 +1179,7 @@
1179 1179  
1180 1180  
1181 1181  
1182 -=== Special case ===
1034 +== 6.7.5. Special case ==
1183 1183  
1184 1184  
1185 1185  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,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -241.0 KB
Content
image-20241126180135-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -192.8 KB
Content
image-20241126180223-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -213.1 KB
Content
image-20241126181024-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -238.8 KB
Content
image-20241126181837-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
image-20241126182007-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -136.3 KB
Content
image-20241126182135-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20241126183032-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -111.4 KB
Content
image-20241126183803-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20241126184136-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -15.7 KB
Content
image-20241126184211-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20241126184303-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -81.7 KB
Content
image-20241126184523-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -88.7 KB
Content
image-20241126184906-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -108.0 KB
Content
image-20241126190131-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -267.9 KB
Content
image-20241126190251-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -94.2 KB
Content
image-20241126190737-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -253.7 KB
Content
image-20241126191118-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -61.4 KB
Content
image-20241126192009-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -113.6 KB
Content
image-20241126192122-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -105.2 KB
Content
image-20241126192130-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -105.2 KB
Content
image-20241126192246-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -87.7 KB
Content
image-20241126192315-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -99.0 KB
Content
image-20241126192415-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -88.2 KB
Content
image-20241126193252-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -64.2 KB
Content
image-20241126193458-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -144.3 KB
Content
image-20241126193609-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -167.5 KB
Content
image-20241126194018-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -63.5 KB
Content
image-20241126194123-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -126.7 KB
Content

Applications

Navigation

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