Last modified by Mengting Qiu on 2025/03/08 11:33
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.ting - 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 52px" %)**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:1 52px" %)**[[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" %)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 51 52 52 == 2.2 Speed Up Network Attach time == 53 53 ... ... @@ -513,6 +513,7 @@ 513 513 514 514 === 3.6.2 Simulate with MQTT.fx === 515 515 516 + 516 516 [[image:image-20230802112413-39.png]] 517 517 518 518 [[image:image-20230802112413-40.png||height="525" width="980"]] ... ... @@ -583,8 +583,7 @@ 583 583 ==== 3.7.1.3 Add COAP Integration ==== 584 584 585 585 586 -(% class="wikigeneratedid" id="H" %) 587 -[[image:image-20240729161543-9.png||height="500" width="1009"]] 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,6 +730,7 @@ 730 730 731 731 === 3.11.1 Configure ThingsEye === 732 732 733 + 733 733 ==== 3.11.1.1 Create MQTT integration ==== 734 734 735 735 ... ... @@ -782,7 +782,7 @@ 782 782 [[image:image-20241126184211-11.png||height="161" width="977"]] 783 783 784 784 785 -==== 3.11.1. 3Setup uplink and downlink converters ====786 +==== 3.11.1.2 Setup uplink and downlink converters ==== 786 786 787 787 788 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]]. ... ... @@ -819,7 +819,7 @@ 819 819 [[image:image-20241126193252-25.png||height="663" width="803"]] 820 820 821 821 822 -=== 3. 11.3 Configure -NB node ===823 +=== 3.6.3 Configure -NB node === 823 823 824 824 825 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. ... ... @@ -828,10 +828,8 @@ 828 828 829 829 * Configuring the CA Certificate 830 830 831 -[[image:image-20241126192009-19.png||height="431" width="697"]] 832 +[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]] 832 832 833 -[[image:image-20241126192130-21.png||height="426" width="694"]] 834 - 835 835 * Configure client certificate 836 836 837 837 [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]] ... ... @@ -848,12 +848,17 @@ 848 848 (% style="color:blue" %)**AT Commands** 849 849 850 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 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 + 854 854 * (% style="color:#037691" %)**AT+CLIENT=NULL** 856 + 855 855 * (% style="color:#037691" %)**AT+UNAME=NULL** 858 + 856 856 * (% style="color:#037691" %)**AT+PWD=NULL** 860 + 857 857 * (% style="color:#037691" %)**AT+TLSMOD=1,0** 858 858 859 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: ... ... @@ -872,6 +872,7 @@ 872 872 [[image:image-20241126194123-29.png||height="486" width="1073"]] 873 873 874 874 879 + 875 875 = 4. MQTT/UDP/TCP downlink = 876 876 877 877 == 4.1 MQTT (via MQTT.fx) == ... ... @@ -932,8 +932,8 @@ 932 932 1. Give more sampling data points. 933 933 1. Increase reliable in transmission. For example. If user set 934 934 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) 935 -1*. **AT+NOUD=24** 936 -1*. **AT+TDC=7200** 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. 937 937 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. 938 938 939 939 == 5.2 Why the uplink JSON format is not standard? == ... ... @@ -946,14 +946,6 @@ 946 946 [[image:image-20240229233154-1.png]] 947 947 948 948 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 - 957 957 = 6. Trouble Shooting: = 958 958 959 959 == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == ... ... @@ -1035,11 +1035,9 @@ 1035 1035 1036 1036 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) == 1037 1037 1038 - 1039 1039 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1040 1040 === UDP: === 1041 1041 1042 - 1043 1043 (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %) 1044 1044 Its downlink command is the same as the AT command, but brackets are required. 1045 1045 Example: ... ... @@ -1050,7 +1050,6 @@ 1050 1050 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1051 1051 === MQTT: === 1052 1052 1053 - 1054 1054 Json: 1055 1055 1056 1056 The Json format in MQTT mode needs to be configured with all commands. ... ... @@ -1117,10 +1117,8 @@ 1117 1117 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. 1118 1118 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values except for passwords.(new) 1119 1119 1120 - 1121 1121 === Version Confirmation === 1122 1122 1123 - 1124 1124 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: 1125 1125 1126 1126 (% border="1" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -1148,7 +1148,6 @@ 1148 1148 ))) 1149 1149 |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8) 1150 1150 1151 - 1152 1152 === UART connection and firmware update methods === 1153 1153 1154 1154 ... ... @@ -1192,6 +1192,7 @@ 1192 1192 [[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"]] 1193 1193 1194 1194 1186 + 1195 1195 === Special case === 1196 1196 1197 1197 ... ... @@ -1199,6 +1199,7 @@ 1199 1199 1200 1200 Invalid query screenshot example: 1201 1201 1194 + 1202 1202 [[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"]] 1203 1203 1204 1204 [[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"]]
- image-20250121235119-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -145.4 KB - Content