Last modified by Mengting Qiu on 2025/07/03 18:55
From version 216.1
edited by Mengting Qiu
on 2024/11/26 19:42
on 2024/11/26 19:42
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 ... ... @@ -168,6 +168,7 @@ 168 168 169 169 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 170 170 171 + 171 171 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 172 172 173 173 ... ... @@ -209,6 +209,7 @@ 209 209 210 210 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 211 211 213 + 212 212 ==== 3.3.3.2 Uplink Examples ==== 213 213 214 214 ... ... @@ -270,6 +270,7 @@ 270 270 |(% 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" %) 271 271 |(% 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" %) 272 272 275 + 273 273 == 3.4 [[Datacake>>https://datacake.co/]] == 274 274 275 275 ... ... @@ -284,6 +284,7 @@ 284 284 285 285 * (% 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. 286 286 290 + 287 287 === 3.4.1 For device Already has template === 288 288 289 289 ==== 3.4.1.1 Create Device ==== ... ... @@ -454,6 +454,7 @@ 454 454 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 455 455 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 456 456 461 + 457 457 == 3.6 ThingsBoard.Cloud (via MQTT) == 458 458 459 459 === 3.6.1 Configure ThingsBoard === ... ... @@ -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"]] ... ... @@ -730,13 +730,11 @@ 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 737 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 738 739 - 740 740 [[image:image-20241126175509-1.png||height="518" width="1081"]] 741 741 742 742 ... ... @@ -773,7 +773,7 @@ 773 773 774 774 (% style="color:blue" %)**Add credential files.** 775 775 776 -Click this link to download the certificates. 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 777 778 778 [[image:image-20241126183032-8.png||height="757" width="976"]] 779 779 ... ... @@ -787,7 +787,7 @@ 787 787 ==== 3.11.1.2 Setup uplink and downlink converters ==== 788 788 789 789 790 -First, you need to download the **MQTT uplink/downlink JS** **code**. 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 791 792 792 * (% style="color:blue" %)**Uplink Converter** 793 793 ... ... @@ -848,17 +848,12 @@ 848 848 (% style="color:blue" %)**AT Commands** 849 849 850 850 * (% style="color:#037691" %)**AT+PRO=3,5 **(%%)** **~/~/ Use MQTT Connection & Json Payload 851 - 852 -* (% style="color:#037691" %)**AT+SUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye 853 - 854 -* (% style="color:#037691" %)**AT+PUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye 855 - 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 856 * (% style="color:#037691" %)**AT+CLIENT=NULL** 857 - 858 858 * (% style="color:#037691" %)**AT+UNAME=NULL** 859 - 860 860 * (% style="color:#037691" %)**AT+PWD=NULL** 861 - 862 862 * (% style="color:#037691" %)**AT+TLSMOD=1,0** 863 863 864 864 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: ... ... @@ -877,7 +877,6 @@ 877 877 [[image:image-20241126194123-29.png||height="486" width="1073"]] 878 878 879 879 880 - 881 881 = 4. MQTT/UDP/TCP downlink = 882 882 883 883 == 4.1 MQTT (via MQTT.fx) == ... ... @@ -938,10 +938,11 @@ 938 938 1. Give more sampling data points. 939 939 1. Increase reliable in transmission. For example. If user set 940 940 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) 941 -1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 942 -1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 937 +1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 938 +1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 943 943 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. 944 944 941 + 945 945 == 5.2 Why the uplink JSON format is not standard? == 946 946 947 947 ... ... @@ -952,6 +952,14 @@ 952 952 [[image:image-20240229233154-1.png]] 953 953 954 954 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 + 955 955 = 6. Trouble Shooting: = 956 956 957 957 == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == ... ... @@ -1033,9 +1033,11 @@ 1033 1033 1034 1034 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) == 1035 1035 1041 + 1036 1036 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1037 1037 === UDP: === 1038 1038 1045 + 1039 1039 (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %) 1040 1040 Its downlink command is the same as the AT command, but brackets are required. 1041 1041 Example: ... ... @@ -1046,6 +1046,7 @@ 1046 1046 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1047 1047 === MQTT: === 1048 1048 1056 + 1049 1049 Json: 1050 1050 1051 1051 The Json format in MQTT mode needs to be configured with all commands. ... ... @@ -1112,6 +1112,7 @@ 1112 1112 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. 1113 1113 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values except for passwords.(new) 1114 1114 1123 + 1115 1115 === Version Confirmation === 1116 1116 1117 1117 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: ... ... @@ -1141,6 +1141,7 @@ 1141 1141 ))) 1142 1142 |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8) 1143 1143 1153 + 1144 1144 === UART connection and firmware update methods === 1145 1145 1146 1146