Skip to Content
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
Change comment: There is no comment for this version
To version 223.1
edited by Edwin Chen
on 2025/01/21 23:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Edwin
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  
... ... @@ -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,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.
774 +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  
... ... @@ -784,10 +784,10 @@
784 784  [[image:image-20241126184211-11.png||height="161" width="977"]]
785 785  
786 786  
787 -==== 3.11.1.2 Setup uplink and downlink converters ====
785 +==== 3.11.1.3 Setup uplink and downlink converters ====
788 788  
789 789  
790 -First, you need to download the **MQTT uplink/downlink JS** **code**.
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]].
791 791  
792 792  * (% style="color:blue" %)**Uplink Converter**
793 793  
... ... @@ -821,7 +821,7 @@
821 821  [[image:image-20241126193252-25.png||height="663" width="803"]]
822 822  
823 823  
824 -=== 3.6.3 Configure -NB node ===
822 +=== 3.11.3 Configure -NB node ===
825 825  
826 826  
827 827  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.
... ... @@ -830,8 +830,10 @@
830 830  
831 831  * Configuring the CA Certificate
832 832  
833 -[[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"]]
834 834  
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,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 -
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
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,8 +938,8 @@
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.
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.
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  
945 945  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -952,6 +952,14 @@
952 952  [[image:image-20240229233154-1.png]]
953 953  
954 954  
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 +
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  
1038 +
1036 1036  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1037 1037  === UDP: ===
1038 1038  
1042 +
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  
1053 +
1049 1049  Json：
1050 1050  
1051 1051  The Json format in MQTT mode needs to be configured with all commands.
... ... @@ -1085,16 +1085,45 @@
1085 1085  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
1086 1086  
1087 1087  
1088 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1093 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1089 1089  
1090 1090  
1091 -* **AT Command: AT** **+GETLOG**
1096 +If user is not able to solve the connection issue, user can use below method and get the device log and send to Dragino (Support@dragino.cc) for further analyze.
1092 1092  
1093 -This command can be used to query upstream logs of data packets.
1094 1094  
1095 -[[image:image-20240701114700-1.png]]
1099 +(% class="lead" %)
1100 +Step1: Use Mobile Phone to connect device
1096 1096  
1102 +See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1097 1097  
1104 +
1105 +(% class="lead" %)
1106 +Step2: Get Log by different commands.
1107 +
1108 +Use below three method to generate logs.
1109 +
1110 +* **AT+CFG       ~-~-> Command to show the current configuration**
1111 +* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1112 +* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1113 +
1114 +
1115 +Above are the output example for about three action:
1116 +
1117 +[[image:image-20250121235119-1.png||height="493" width="455"]]
1118 +
1119 +[[image:image-20240207002129-2.png]]
1120 +
1121 +
1122 +(% class="lead" %)
1123 +Step3: Export Log
1124 +
1125 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155425-16.png?width=330&height=85&rev=1.1||alt="image-20241230155425-16.png" height="85" width="330"]]
1126 +
1127 +select the log you want to export, then click the share icon on the far right to enter the document that comes with your phone and choose to export it.
1128 +
1129 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155528-17.png?width=327&height=324&rev=1.1||alt="image-20241230155528-17.png" height="324" width="327"]]
1130 +
1131 +
1098 1098  == 6.7 How to find the AT Command Password if lost? ==
1099 1099  
1100 1100  
... ... @@ -1114,6 +1114,7 @@
1114 1114  
1115 1115  === Version Confirmation ===
1116 1116  
1151 +
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:
1118 1118  
1119 1119  (% border="1" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -1184,7 +1184,6 @@
1184 1184  [[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"]]
1185 1185  
1186 1186  
1187 -
1188 1188  === Special case ===
1189 1189  
1190 1190  
... ... @@ -1192,7 +1192,6 @@
1192 1192  
1193 1193  Invalid query screenshot example:
1194 1194  
1195 -
1196 1196  [[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"]]
1197 1197  
1198 1198  [[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,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +145.4 KB
Content