Last modified by Mengting Qiu on 2025/07/03 18:55

From version 214.1
edited by Mengting Qiu
on 2024/11/26 19:40
Change comment: Uploaded new attachment "image-20241126194018-28.png", version {1}
To version 219.2
edited by Xiaoling
on 2024/12/12 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +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: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" %)
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"]]
... ... @@ -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.
778 +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  
... ... @@ -788,7 +788,7 @@
788 788  ==== 3.11.1.2 Setup uplink and downlink converters ====
789 789  
790 790  
791 -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]].
792 792  
793 793  * (% style="color:blue" %)**Uplink Converter**
794 794  
... ... @@ -814,44 +814,65 @@
814 814  [[image:image-20241126190737-17.png||height="527" width="1114"]]
815 815  
816 816  
817 -=== 3.6.2 Simulate with MQTT.fx ===
818 +=== 3.11.2 Simulate with MQTT.fx ===
818 818  
819 819  
820 -[[image:image-20230802112413-39.png]]
821 +[[image:image-20241126191118-18.png||height="605" width="835"]]
821 821  
822 -[[image:image-20230802112413-40.png||height="525" width="980"]]
823 +[[image:image-20241126193252-25.png||height="663" width="803"]]
823 823  
824 824  
825 -=== 3.6.3 Configure NB-IoT Sensor ===
826 +=== 3.6.3 Configure -NB node ===
826 826  
827 827  
828 -(% style="color:blue" %)**AT Commands**
829 +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  **(%%)** **~/~/ Use MQTT tconnect to ThingsBoard. Payload Type set to 3.
831 +Screenshot of successful certificate configuration:
831 831  
832 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
833 +* Configuring the CA Certificate
833 833  
834 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
835 +[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
835 835  
836 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
837 +* Configure client certificate
837 837  
838 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
839 +[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
839 839  
840 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
841 +* Configure client private key
841 841  
842 -Test Uplink by click the button for 1 second
843 +[[image:image-20241126192415-24.png||height="435" width="737"]]
843 843  
844 -[[image:image-20230802112413-41.png||height="496" width="828"]]
845 845  
846 -[[image:image-20230802112413-42.png]]
846 +When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
847 847  
848 -[[image:image-20230802112413-43.png||height="407" width="825"]]
848 +Then configure the -NB node to connect to the ThingsEye platform:
849 849  
850 +(% style="color:blue" %)**AT Commands**
850 850  
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**
851 851  
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:
852 852  
863 +[[image:image-20241126193458-26.png||height="375" width="1012"]]
853 853  
865 +[[image:image-20241126193609-27.png||height="424" width="1014"]]
854 854  
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 +
855 855  = 4. MQTT/UDP/TCP downlink =
856 856  
857 857  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -912,10 +912,11 @@
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.
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.
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  
941 +
919 919  == 5.2 Why the uplink JSON format is not standard? ==
920 920  
921 921  
... ... @@ -926,6 +926,14 @@
926 926  [[image:image-20240229233154-1.png]]
927 927  
928 928  
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 +
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  
1041 +
1010 1010  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1011 1011  === UDP: ===
1012 1012  
1045 +
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  
1056 +
1023 1023  Json:
1024 1024  
1025 1025  The Json format in MQTT mode needs to be configured with all commands.
... ... @@ -1086,6 +1086,7 @@
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  
1123 +
1089 1089  === Version Confirmation ===
1090 1090  
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:
... ... @@ -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  
1153 +
1118 1118  === UART connection and firmware update methods ===
1119 1119  
1120 1120  
image-20241126194123-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.7 KB
Content