Last modified by Mengting Qiu on 2025/07/03 18:55
From version 217.1
edited by Mengting Qiu
on 2024/11/26 19:52
on 2024/11/26 19:52
Change comment:
There is no comment for this version
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) === ... ... @@ -730,7 +730,6 @@ 730 730 731 731 === 3.11.1 Configure ThingsEye === 732 732 733 - 734 734 ==== 3.11.1.1 Create MQTT integration ==== 735 735 736 736 ... ... @@ -783,7 +783,7 @@ 783 783 [[image:image-20241126184211-11.png||height="161" width="977"]] 784 784 785 785 786 -==== 3.11.1. 2Setup uplink and downlink converters ====785 +==== 3.11.1.3 Setup uplink and downlink converters ==== 787 787 788 788 789 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]]. ... ... @@ -820,7 +820,7 @@ 820 820 [[image:image-20241126193252-25.png||height="663" width="803"]] 821 821 822 822 823 -=== 3. 6.3 Configure -NB node ===822 +=== 3.11.3 Configure -NB node === 824 824 825 825 826 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. ... ... @@ -829,8 +829,10 @@ 829 829 830 830 * Configuring the CA Certificate 831 831 832 -[[image:image-20241126192009-19.png||height="431" width="697"]] [[image:image-20241126192130-21.png||height="426" width="694"]]831 +[[image:image-20241126192009-19.png||height="431" width="697"]] 833 833 833 +[[image:image-20241126192130-21.png||height="426" width="694"]] 834 + 834 834 * Configure client certificate 835 835 836 836 [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]] ... ... @@ -847,17 +847,12 @@ 847 847 (% style="color:blue" %)**AT Commands** 848 848 849 849 * (% style="color:#037691" %)**AT+PRO=3,5 **(%%)** **~/~/ Use MQTT Connection & Json Payload 850 - 851 -* (% style="color:#037691" %)**AT+SUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye 852 - 853 -* (% style="color:#037691" %)**AT+PUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye 854 - 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 855 855 * (% style="color:#037691" %)**AT+CLIENT=NULL** 856 - 857 857 * (% style="color:#037691" %)**AT+UNAME=NULL** 858 - 859 859 * (% style="color:#037691" %)**AT+PWD=NULL** 860 - 861 861 * (% style="color:#037691" %)**AT+TLSMOD=1,0** 862 862 863 863 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: ... ... @@ -876,7 +876,6 @@ 876 876 [[image:image-20241126194123-29.png||height="486" width="1073"]] 877 877 878 878 879 - 880 880 = 4. MQTT/UDP/TCP downlink = 881 881 882 882 == 4.1 MQTT (via MQTT.fx) == ... ... @@ -937,8 +937,8 @@ 937 937 1. Give more sampling data points. 938 938 1. Increase reliable in transmission. For example. If user set 939 939 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) 940 -1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 941 -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. 942 942 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. 943 943 944 944 == 5.2 Why the uplink JSON format is not standard? == ... ... @@ -951,6 +951,14 @@ 951 951 [[image:image-20240229233154-1.png]] 952 952 953 953 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 + 954 954 = 6. Trouble Shooting: = 955 955 956 956 == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == ... ... @@ -1032,9 +1032,11 @@ 1032 1032 1033 1033 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) == 1034 1034 1038 + 1035 1035 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1036 1036 === UDP: === 1037 1037 1042 + 1038 1038 (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %) 1039 1039 Its downlink command is the same as the AT command, but brackets are required. 1040 1040 Example: ... ... @@ -1045,6 +1045,7 @@ 1045 1045 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1046 1046 === MQTT: === 1047 1047 1053 + 1048 1048 Json: 1049 1049 1050 1050 The Json format in MQTT mode needs to be configured with all commands. ... ... @@ -1111,8 +1111,10 @@ 1111 1111 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. 1112 1112 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values except for passwords.(new) 1113 1113 1120 + 1114 1114 === Version Confirmation === 1115 1115 1123 + 1116 1116 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: 1117 1117 1118 1118 (% border="1" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -1140,6 +1140,7 @@ 1140 1140 ))) 1141 1141 |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8) 1142 1142 1151 + 1143 1143 === UART connection and firmware update methods === 1144 1144 1145 1145 ... ... @@ -1183,7 +1183,6 @@ 1183 1183 [[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"]] 1184 1184 1185 1185 1186 - 1187 1187 === Special case === 1188 1188 1189 1189 ... ... @@ -1191,7 +1191,6 @@ 1191 1191 1192 1192 Invalid query screenshot example: 1193 1193 1194 - 1195 1195 [[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"]] 1196 1196 1197 1197 [[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"]]