Last modified by Mengting Qiu on 2025/07/03 18:55
From version 215.1
edited by Mengting Qiu
on 2024/11/26 19:41
on 2024/11/26 19:41
Change comment:
Uploaded new attachment "image-20241126194123-29.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Xiaoling - Content
-
... ... @@ -46,8 +46,8 @@ 46 46 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %) 47 47 48 48 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %) 49 -|(% style="background-color:#4f81bd; color:white; width:1 17px" %)**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:1 17px" %)**[[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" %)49 +|(% style="background-color:#4f81bd; color:white; width:152px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:169px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:427px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments** 50 +|(% style="width:152px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:169px" %)iot.1nce.net/xxx|(% style="width:427px" %)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 51 52 52 == 2.2 Speed Up Network Attach time == 53 53 ... ... @@ -513,7 +513,6 @@ 513 513 514 514 === 3.6.2 Simulate with MQTT.fx === 515 515 516 - 517 517 [[image:image-20230802112413-39.png]] 518 518 519 519 [[image:image-20230802112413-40.png||height="525" width="980"]] ... ... @@ -584,7 +584,8 @@ 584 584 ==== 3.7.1.3 Add COAP Integration ==== 585 585 586 586 587 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ==== 586 +(% class="wikigeneratedid" id="H" %) 587 +[[image:image-20240729161543-9.png||height="500" width="1009"]] 588 588 589 589 590 590 === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) === ... ... @@ -728,16 +728,13 @@ 728 728 729 729 == 3.11 ThingsEye (via MQTT) == 730 730 731 -(% class="wikigeneratedid" %) 732 732 === 3.11.1 Configure ThingsEye === 733 733 734 - 735 735 ==== 3.11.1.1 Create MQTT integration ==== 736 736 737 737 738 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 739 740 - 741 741 [[image:image-20241126175509-1.png||height="518" width="1081"]] 742 742 743 743 ... ... @@ -774,7 +774,7 @@ 774 774 775 775 (% style="color:blue" %)**Add credential files.** 776 776 777 -Click this link to download the certificates. 774 +Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates. 778 778 779 779 [[image:image-20241126183032-8.png||height="757" width="976"]] 780 780 ... ... @@ -785,10 +785,10 @@ 785 785 [[image:image-20241126184211-11.png||height="161" width="977"]] 786 786 787 787 788 -==== 3.11.1. 2Setup uplink and downlink converters ====785 +==== 3.11.1.3 Setup uplink and downlink converters ==== 789 789 790 790 791 -First, you need to download the **MQTT uplink/downlink JS** **code**. 788 +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]]. 792 792 793 793 * (% style="color:blue" %)**Uplink Converter** 794 794 ... ... @@ -814,44 +814,67 @@ 814 814 [[image:image-20241126190737-17.png||height="527" width="1114"]] 815 815 816 816 817 -=== 3. 6.2 Simulate with MQTT.fx ===814 +=== 3.11.2 Simulate with MQTT.fx === 818 818 819 819 820 -[[image:image-202 30802112413-39.png]]817 +[[image:image-20241126191118-18.png||height="605" width="835"]] 821 821 822 -[[image:image-202 30802112413-40.png||height="525" width="980"]]819 +[[image:image-20241126193252-25.png||height="663" width="803"]] 823 823 824 824 825 -=== 3. 6.3 Configure-IoT Sensor===822 +=== 3.11.3 Configure -NB node === 826 826 827 827 828 - (%style="color:blue"%)**AT Commands**825 +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. 829 829 830 - *(%style="color:#037691"%)**AT+PRO=3,3 **(%%)** **~/~/ UseMQTTtoconnect toThingsBoard. Payload Type setto3.827 +Screenshot of successful certificate configuration: 831 831 832 -* (%style="color:#037691"%)**AT+SUBTOPIC=<device name>**829 +* Configuring the CA Certificate 833 833 834 - * (% style="color:#037691"%)**AT+PUBTOPIC=<device name>**831 +[[image:image-20241126192009-19.png||height="431" width="697"]] 835 835 836 - * (% style="color:#037691" %)**AT+CLIENT=<devicename>or User Defined**833 +[[image:image-20241126192130-21.png||height="426" width="694"]] 837 837 838 -* (% style="color:#037691" %)**AT+UNAME=<deviceame>or UserDefined**835 +* Configure client certificate 839 839 840 - * (% style="color:#037691"%)**AT+PWD=<deviceame>or User Defined**837 +[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]] 841 841 842 - Test Uplink byclick thebuttonfor1 second839 +* Configure client private key 843 843 844 -[[image:image-202 30802112413-41.png||height="496" width="828"]]841 +[[image:image-20241126192415-24.png||height="435" width="737"]] 845 845 846 -[[image:image-20230802112413-42.png]] 847 847 848 - [[image:image-20230802112413-43.png||height="407"width="825"]]844 +When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device. 849 849 846 +Then configure the -NB node to connect to the ThingsEye platform: 850 850 848 +(% style="color:blue" %)**AT Commands** 851 851 850 +* (% style="color:#037691" %)**AT+PRO=3,5 **(%%)** **~/~/ Use MQTT Connection & Json Payload 851 +* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883** 852 +* (% style="color:#037691" %)**AT+SUBTOPIC=8899 **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye 853 +* (% style="color:#037691" %)**AT+PUBTOPIC=8899 **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye 854 +* (% style="color:#037691" %)**AT+CLIENT=NULL** 855 +* (% style="color:#037691" %)**AT+UNAME=NULL** 856 +* (% style="color:#037691" %)**AT+PWD=NULL** 857 +* (% style="color:#037691" %)**AT+TLSMOD=1,0** 852 852 859 +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: 853 853 861 +[[image:image-20241126193458-26.png||height="375" width="1012"]] 854 854 863 +[[image:image-20241126193609-27.png||height="424" width="1014"]] 864 + 865 + 866 +Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device. 867 + 868 +[[image:image-20241126194018-28.png||height="318" width="1076"]] 869 + 870 +You can view the data that has just been uplink on the device: 871 + 872 +[[image:image-20241126194123-29.png||height="486" width="1073"]] 873 + 874 + 855 855 = 4. MQTT/UDP/TCP downlink = 856 856 857 857 == 4.1 MQTT (via MQTT.fx) == ... ... @@ -912,8 +912,8 @@ 912 912 1. Give more sampling data points. 913 913 1. Increase reliable in transmission. For example. If user set 914 914 1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds) 915 -1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 916 -1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 935 +1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 936 +1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 917 917 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. 918 918 919 919 == 5.2 Why the uplink JSON format is not standard? == ... ... @@ -926,6 +926,14 @@ 926 926 [[image:image-20240229233154-1.png]] 927 927 928 928 949 +== 5.3 What is the data consumption for different transfer mode? == 950 + 951 + 952 +For the data consumption of NB-IoT End node in different transfer mode, reference link: 953 + 954 +[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]] 955 + 956 + 929 929 = 6. Trouble Shooting: = 930 930 931 931 == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == ... ... @@ -1007,9 +1007,11 @@ 1007 1007 1008 1008 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) == 1009 1009 1038 + 1010 1010 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1011 1011 === UDP: === 1012 1012 1042 + 1013 1013 (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %) 1014 1014 Its downlink command is the same as the AT command, but brackets are required. 1015 1015 Example: ... ... @@ -1020,6 +1020,7 @@ 1020 1020 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1021 1021 === MQTT: === 1022 1022 1053 + 1023 1023 Json: 1024 1024 1025 1025 The Json format in MQTT mode needs to be configured with all commands. ... ... @@ -1086,8 +1086,10 @@ 1086 1086 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. 1087 1087 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values except for passwords.(new) 1088 1088 1120 + 1089 1089 === Version Confirmation === 1090 1090 1123 + 1091 1091 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: 1092 1092 1093 1093 (% border="1" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -1115,6 +1115,7 @@ 1115 1115 ))) 1116 1116 |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8) 1117 1117 1151 + 1118 1118 === UART connection and firmware update methods === 1119 1119 1120 1120 ... ... @@ -1158,7 +1158,6 @@ 1158 1158 [[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"]] 1159 1159 1160 1160 1161 - 1162 1162 === Special case === 1163 1163 1164 1164 ... ... @@ -1166,7 +1166,6 @@ 1166 1166 1167 1167 Invalid query screenshot example: 1168 1168 1169 - 1170 1170 [[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"]] 1171 1171 1172 1172 [[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"]]