Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 217.1
edited by Mengting Qiu
on 2024/11/26 19:52
Change comment: There is no comment for this version
To version 227.2
edited by Mengting Qiu
on 2025/06/16 08:48
Change comment: There is no comment for this version

Summary

Details

Page properties
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) ===
... ... @@ -602,26 +602,17 @@
602 602  Note:The port for the COAP protocol has been fixed to 5683
603 603  
604 604  
605 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
605 +* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
606 606  
607 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
607 +-NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
608 608  
609 609  e.g.
610 610  
611 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
611 +* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 612  
613 613  [[image:image-20240729172415-13.png||height="401" width="694"]]
614 614  
615 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
616 616  
617 -e.g.
618 -
619 -* AT+URL1=11, "i"
620 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
621 -
622 -[[image:image-20240729172500-14.png||height="403" width="700"]]
623 -
624 -
625 625  == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
626 626  
627 627  === 3.8.1 Create device & Get Credentials ===
... ... @@ -730,7 +730,6 @@
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  
... ... @@ -783,7 +783,7 @@
783 783  [[image:image-20241126184211-11.png||height="161" width="977"]]
784 784  
785 785  
786 -==== 3.11.1.2 Setup uplink and downlink converters ====
776 +==== 3.11.1.3 Setup uplink and downlink converters ====
787 787  
788 788  
789 789  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]].
... ... @@ -820,7 +820,7 @@
820 820  [[image:image-20241126193252-25.png||height="663" width="803"]]
821 821  
822 822  
823 -=== 3.6.3 Configure -NB node ===
813 +=== 3.11.3 Configure -NB node ===
824 824  
825 825  
826 826  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,8 +829,10 @@
829 829  
830 830  * Configuring the CA Certificate
831 831  
832 -[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
822 +[[image:image-20241126192009-19.png||height="431" width="697"]]
833 833  
824 +[[image:image-20241126192130-21.png||height="426" width="694"]]
825 +
834 834  * Configure client certificate
835 835  
836 836  [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
... ... @@ -847,19 +847,14 @@
847 847  (% style="color:blue" %)**AT Commands**
848 848  
849 849  * (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
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 -
842 +* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
843 +* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
844 +* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
855 855  * (% style="color:#037691" %)**AT+CLIENT=NULL**
856 -
857 857  * (% style="color:#037691" %)**AT+UNAME=NULL**
858 -
859 859  * (% style="color:#037691" %)**AT+PWD=NULL**
848 +* (% style="color:#037691" %)**AT+TLSMOD=1,2**
860 860  
861 -* (% style="color:#037691" %)**AT+TLSMOD=1,0**
862 -
863 863  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:
864 864  
865 865  [[image:image-20241126193458-26.png||height="375" width="1012"]]
... ... @@ -876,7 +876,6 @@
876 876  [[image:image-20241126194123-29.png||height="486" width="1073"]]
877 877  
878 878  
879 -
880 880  = 4. MQTT/UDP/TCP downlink =
881 881  
882 882  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -937,8 +937,8 @@
937 937  1. Give more sampling data points.
938 938  1. Increase reliable in transmission. For example. If user set
939 939  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)
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.
926 +1*. **AT+NOUD=24**  ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
927 +1*. **AT+TDC=7200**  ~/~/  Uplink every 2 hours.
942 942  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.
943 943  
944 944  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -951,6 +951,14 @@
951 951  [[image:image-20240229233154-1.png]]
952 952  
953 953  
940 +== 5.3 What is the data consumption for different transfer mode？ ==
941 +
942 +
943 +For the data consumption of NB-IoT End node in different transfer mode, reference link:
944 +
945 +[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
946 +
947 +
954 954  = 6. Trouble Shooting: =
955 955  
956 956  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -1030,21 +1030,21 @@
1030 1030  [[image:image-20240226111928-1.png]]
1031 1031  
1032 1032  
1033 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1027 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1034 1034  
1035 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1036 -=== UDP: ===
1037 1037  
1038 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1039 -Its downlink command is the same as the AT command, but brackets are required.
1040 -Example:
1030 +Firstly, it is recommended that users upgrade the firmware of the -NB node to the latest version, as the processing method for downlink commands varies depending on the firmware version. Below, we will introduce the latest downlink command format.
1031 +(% style="color:red" %)**Note: **
1041 1041  
1042 -{AT+TDC=300}
1033 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1034 +=== **UDP Protocol:** ===
1043 1043  
1036 +Only supports valid **HEX-format downlink commands** corresponding to AT command
1044 1044  
1045 1045  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1046 1046  === MQTT: ===
1047 1047  
1041 +
1048 1048  Json：
1049 1049  
1050 1050  The Json format in MQTT mode needs to be configured with all commands.
... ... @@ -1084,16 +1084,44 @@
1084 1084  [[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/]]
1085 1085  
1086 1086  
1087 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1081 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1088 1088  
1089 1089  
1090 -* **AT Command: AT** **+GETLOG**
1084 +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.
1091 1091  
1092 -This command can be used to query upstream logs of data packets.
1093 1093  
1094 -[[image:image-20240701114700-1.png]]
1087 +(% class="lead" %)
1088 +Step1: Use Mobile Phone to connect device
1095 1095  
1090 +See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1096 1096  
1092 +
1093 +(% class="lead" %)
1094 +Step2: Get Log by different commands.
1095 +
1096 +Use below three method to generate logs.
1097 +
1098 +* **AT+CFG       ~-~-> Command to show the current configuration**
1099 +* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1100 +* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1101 +
1102 +Above are the output example for about three action:
1103 +
1104 +[[image:image-20250121235119-1.png||height="493" width="455"]]
1105 +
1106 +[[image:image-20240207002129-2.png]]
1107 +
1108 +
1109 +(% class="lead" %)
1110 +Step3: Export Log
1111 +
1112 +[[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"]]
1113 +
1114 +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.
1115 +
1116 +[[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"]]
1117 +
1118 +
1097 1097  == 6.7 How to find the AT Command Password if lost? ==
1098 1098  
1099 1099  
... ... @@ -1113,6 +1113,7 @@
1113 1113  
1114 1114  === Version Confirmation ===
1115 1115  
1138 +
1116 1116  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:
1117 1117  
1118 1118  (% border="1" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -1183,7 +1183,6 @@
1183 1183  [[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"]]
1184 1184  
1185 1185  
1186 -
1187 1187  === Special case ===
1188 1188  
1189 1189  
... ... @@ -1191,7 +1191,6 @@
1191 1191  
1192 1192  Invalid query screenshot example:
1193 1193  
1194 -
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-20240827181447-4.png?width=889&height=519&rev=1.1||alt="image-20240827181447-4.png"]]
1196 1196  
1197 1197  [[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