Last modified by Mengting Qiu on 2025/03/08 11:33
Change comment:
Uploaded new attachment "image-20241126192009-19.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 10 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +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 ... ... @@ -168,7 +168,6 @@ 168 168 169 169 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 170 170 171 - 172 172 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 173 173 174 174 ... ... @@ -210,7 +210,6 @@ 210 210 211 211 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 212 212 213 - 214 214 ==== 3.3.3.2 Uplink Examples ==== 215 215 216 216 ... ... @@ -272,7 +272,6 @@ 272 272 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %) 273 273 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %) 274 274 275 - 276 276 == 3.4 [[Datacake>>https://datacake.co/]] == 277 277 278 278 ... ... @@ -287,7 +287,6 @@ 287 287 288 288 * (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction. 289 289 290 - 291 291 === 3.4.1 For device Already has template === 292 292 293 293 ==== 3.4.1.1 Create Device ==== ... ... @@ -458,7 +458,6 @@ 458 458 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 459 459 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 460 460 461 - 462 462 == 3.6 ThingsBoard.Cloud (via MQTT) == 463 463 464 464 === 3.6.1 Configure ThingsBoard === ... ... @@ -518,6 +518,7 @@ 518 518 519 519 === 3.6.2 Simulate with MQTT.fx === 520 520 516 + 521 521 [[image:image-20230802112413-39.png]] 522 522 523 523 [[image:image-20230802112413-40.png||height="525" width="980"]] ... ... @@ -732,13 +732,16 @@ 732 732 733 733 == 3.11 ThingsEye (via MQTT) == 734 734 731 +(% class="wikigeneratedid" %) 735 735 === 3.11.1 Configure ThingsEye === 736 736 734 + 737 737 ==== 3.11.1.1 Create MQTT integration ==== 738 738 739 739 740 740 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**; 741 741 740 + 742 742 [[image:image-20241126175509-1.png||height="518" width="1081"]] 743 743 744 744 ... ... @@ -775,7 +775,7 @@ 775 775 776 776 (% style="color:blue" %)**Add credential files.** 777 777 778 -Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]]to download the certificates.777 +Click this link to download the certificates. 779 779 780 780 [[image:image-20241126183032-8.png||height="757" width="976"]] 781 781 ... ... @@ -789,7 +789,7 @@ 789 789 ==== 3.11.1.2 Setup uplink and downlink converters ==== 790 790 791 791 792 -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]].791 +First, you need to download the **MQTT uplink/downlink JS** **code**. 793 793 794 794 * (% style="color:blue" %)**Uplink Converter** 795 795 ... ... @@ -815,65 +815,44 @@ 815 815 [[image:image-20241126190737-17.png||height="527" width="1114"]] 816 816 817 817 818 -=== 3. 11.2 Simulate with MQTT.fx ===817 +=== 3.6.2 Simulate with MQTT.fx === 819 819 820 820 821 -[[image:image-202 41126191118-18.png||height="605" width="835"]]820 +[[image:image-20230802112413-39.png]] 822 822 823 -[[image:image-202 41126193252-25.png||height="663" width="803"]]822 +[[image:image-20230802112413-40.png||height="525" width="980"]] 824 824 825 825 826 -=== 3.6.3 Configure -NBnode ===825 +=== 3.6.3 Configure NB-IoT Sensor === 827 827 828 828 829 - Firstou need toconfigure the certificate to the -NB node. Follow the instructionsin 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 +(% style="color:blue" %)**AT Commands** 830 830 831 - Screenshotofsuccessfulcertificatenfiguration:830 +* (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3. 832 832 833 -* ConfiguringtheCArtificate832 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>** 834 834 835 - [[image:image-20241126192009-19.png||height="431"width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]834 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>** 836 836 837 -* Configureclientcertificate836 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined** 838 838 839 - [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402"width="645"]]838 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 840 840 841 -* Configureclientprivatekey840 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined** 842 842 843 - [[image:image-20241126192415-24.png||height="435" width="737"]]842 +Test Uplink by click the button for 1 second 844 844 844 +[[image:image-20230802112413-41.png||height="496" width="828"]] 845 845 846 - When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.846 +[[image:image-20230802112413-42.png]] 847 847 848 - Then configurethe-NBnode to connect to theThingsEyeplatform:848 +[[image:image-20230802112413-43.png||height="407" width="825"]] 849 849 850 -(% style="color:blue" %)**AT Commands** 851 851 852 -* (% style="color:#037691" %)**AT+PRO=3,5 **(%%)** **~/~/ Use MQTT Connection & Json Payload 853 -* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883** 854 -* (% style="color:#037691" %)**AT+SUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye 855 -* (% style="color:#037691" %)**AT+PUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye 856 -* (% style="color:#037691" %)**AT+CLIENT=NULL** 857 -* (% style="color:#037691" %)**AT+UNAME=NULL** 858 -* (% style="color:#037691" %)**AT+PWD=NULL** 859 -* (% style="color:#037691" %)**AT+TLSMOD=1,0** 860 860 861 -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: 862 862 863 -[[image:image-20241126193458-26.png||height="375" width="1012"]] 864 864 865 -[[image:image-20241126193609-27.png||height="424" width="1014"]] 866 866 867 - 868 -Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device. 869 - 870 -[[image:image-20241126194018-28.png||height="318" width="1076"]] 871 - 872 -You can view the data that has just been uplink on the device: 873 - 874 -[[image:image-20241126194123-29.png||height="486" width="1073"]] 875 - 876 - 877 877 = 4. MQTT/UDP/TCP downlink = 878 878 879 879 == 4.1 MQTT (via MQTT.fx) == ... ... @@ -934,11 +934,10 @@ 934 934 1. Give more sampling data points. 935 935 1. Increase reliable in transmission. For example. If user set 936 936 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) 937 -1*. **AT+NOUD=24** 938 -1*. **AT+TDC=7200** 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. 939 939 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. 940 940 941 - 942 942 == 5.2 Why the uplink JSON format is not standard? == 943 943 944 944 ... ... @@ -949,14 +949,6 @@ 949 949 [[image:image-20240229233154-1.png]] 950 950 951 951 952 -== 5.3 What is the data consumption for different transfer mode? == 953 - 954 - 955 -For the data consumption of NB-IoT End node in different transfer mode, reference link: 956 - 957 -[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]] 958 - 959 - 960 960 = 6. Trouble Shooting: = 961 961 962 962 == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == ... ... @@ -1038,11 +1038,9 @@ 1038 1038 1039 1039 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) == 1040 1040 1041 - 1042 1042 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1043 1043 === UDP: === 1044 1044 1045 - 1046 1046 (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %) 1047 1047 Its downlink command is the same as the AT command, but brackets are required. 1048 1048 Example: ... ... @@ -1053,7 +1053,6 @@ 1053 1053 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1054 1054 === MQTT: === 1055 1055 1056 - 1057 1057 Json: 1058 1058 1059 1059 The Json format in MQTT mode needs to be configured with all commands. ... ... @@ -1120,10 +1120,8 @@ 1120 1120 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. 1121 1121 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values except for passwords.(new) 1122 1122 1123 - 1124 1124 === Version Confirmation === 1125 1125 1126 - 1127 1127 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: 1128 1128 1129 1129 (% border="1" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -1151,7 +1151,6 @@ 1151 1151 ))) 1152 1152 |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8) 1153 1153 1154 - 1155 1155 === UART connection and firmware update methods === 1156 1156 1157 1157 ... ... @@ -1195,6 +1195,7 @@ 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-20240827180414-1.png?width=910&height=527&rev=1.1||alt="image-20240827180414-1.png"]] 1196 1196 1197 1197 1161 + 1198 1198 === Special case === 1199 1199 1200 1200 ... ... @@ -1202,6 +1202,7 @@ 1202 1202 1203 1203 Invalid query screenshot example: 1204 1204 1169 + 1205 1205 [[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"]] 1206 1206 1207 1207 [[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-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