Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 228.8
edited by Mengting Qiu
on 2025/06/16 09:06
Change comment: There is no comment for this version
To version 219.1
edited by Kilight Cao
on 2024/12/11 17:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Kilight
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: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" %)
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  
... ... @@ -513,6 +513,7 @@
513 513  
514 514  === 3.6.2 Simulate with MQTT.fx ===
515 515  
516 +
516 516  [[image:image-20230802112413-39.png]]
517 517  
518 518  [[image:image-20230802112413-40.png||height="525" width="980"]]
... ... @@ -583,8 +583,7 @@
583 583  ==== 3.7.1.3 Add COAP Integration ====
584 584  
585 585  
586 -(% class="wikigeneratedid" id="H" %)
587 -[[image:image-20240729161543-9.png||height="500" width="1009"]]
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,17 +602,26 @@
602 602  Note:The port for the COAP protocol has been fixed to 5683
603 603  
604 604  
605 -* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
605 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
606 606  
607 --NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
607 +If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
608 608  
609 609  e.g.
610 610  
611 -* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
611 +* AT+URL1=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,
615 615  
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 +
616 616  == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
617 617  
618 618  === 3.8.1 Create device & Get Credentials ===
... ... @@ -721,6 +721,7 @@
721 721  
722 722  === 3.11.1 Configure ThingsEye ===
723 723  
733 +
724 724  ==== 3.11.1.1 Create MQTT integration ====
725 725  
726 726  
... ... @@ -773,7 +773,7 @@
773 773  [[image:image-20241126184211-11.png||height="161" width="977"]]
774 774  
775 775  
776 -==== 3.11.1.3 Setup uplink and downlink converters ====
786 +==== 3.11.1.2 Setup uplink and downlink converters ====
777 777  
778 778  
779 779  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]].
... ... @@ -810,7 +810,7 @@
810 810  [[image:image-20241126193252-25.png||height="663" width="803"]]
811 811  
812 812  
813 -=== 3.11.3 Configure -NB node ===
823 +=== 3.6.3 Configure -NB node ===
814 814  
815 815  
816 816  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.
... ... @@ -819,10 +819,8 @@
819 819  
820 820  * Configuring the CA Certificate
821 821  
822 -[[image:image-20241126192009-19.png||height="431" width="697"]]
832 +[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
823 823  
824 -[[image:image-20241126192130-21.png||height="426" width="694"]]
825 -
826 826  * Configure client certificate
827 827  
828 828  [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
... ... @@ -840,12 +840,12 @@
840 840  
841 841  * (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
842 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
851 +* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
852 +* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
845 845  * (% style="color:#037691" %)**AT+CLIENT=NULL**
846 846  * (% style="color:#037691" %)**AT+UNAME=NULL**
847 847  * (% style="color:#037691" %)**AT+PWD=NULL**
848 -* (% style="color:#037691" %)**AT+TLSMOD=1,2**
856 +* (% style="color:#037691" %)**AT+TLSMOD=1,0**
849 849  
850 850  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:
851 851  
... ... @@ -863,6 +863,7 @@
863 863  [[image:image-20241126194123-29.png||height="486" width="1073"]]
864 864  
865 865  
874 +
866 866  = 4. MQTT/UDP/TCP downlink =
867 867  
868 868  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -923,8 +923,8 @@
923 923  1. Give more sampling data points.
924 924  1. Increase reliable in transmission. For example. If user set
925 925  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)
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.
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.
928 928  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.
929 929  
930 930  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -937,7 +937,7 @@
937 937  [[image:image-20240229233154-1.png]]
938 938  
939 939  
940 -== 5.3 What is the data consumption for different transfer mode？ ==
949 +== 5.3 What is the data consumption for different transfer mode？ ==
941 941  
942 942  
943 943  For the data consumption of NB-IoT End node in different transfer mode, reference link:
... ... @@ -944,7 +944,6 @@
944 944  
945 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 946  
947 -
948 948  = 6. Trouble Shooting: =
949 949  
950 950  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -1024,22 +1024,21 @@
1024 1024  [[image:image-20240226111928-1.png]]
1025 1025  
1026 1026  
1027 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1035 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1028 1028  
1029 -
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 -
1032 1032  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1033 -=== **UDP Protocol:** ===
1038 +=== UDP: ===
1034 1034  
1035 -Only supports valid **HEX-format downlink commands** corresponding to AT command.
1040 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1041 +Its downlink command is the same as the AT command, but brackets are required.
1042 +Example:
1036 1036  
1044 +{AT+TDC=300}
1037 1037  
1038 1038  
1039 1039  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1040 1040  === MQTT: ===
1041 1041  
1042 -
1043 1043  Json：
1044 1044  
1045 1045  The Json format in MQTT mode needs to be configured with all commands.
... ... @@ -1079,55 +1079,16 @@
1079 1079  [[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/]]
1080 1080  
1081 1081  
1082 -(% style="color:red" %)**Note:**
1089 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1083 1083  
1084 -(% style="color:red" %)**1. Only when the correct and valid download command is used and the format is correct can the device be configured through the download command. Invalid download content cannot be processed by the device and will be automatically restarted.**
1085 1085  
1086 -(% style="color:red" %)**2. Devices designed with downlink commands can utilize different downlink formats (e.g., JSON or HEX) for configuration. However, regardless of the format, the functionality is strictly limited to the downlink command specifications described in the user manual's AT command explanation.**
1092 +* **AT Command: AT** **+GETLOG**
1087 1087  
1088 -(% style="color:red" %)**For example, the HEX-format downlink command corresponding to AT+TDC can only be used to configure TDC and cannot be used for queries. There is no HEX-format downlink command equivalent to AT+TDC=? , so querying TDC via downlink is not supported.**
1094 +This command can be used to query upstream logs of data packets.
1089 1089  
1090 -[[image:1750035004731-376.png||height="276" width="557"]]
1096 +[[image:image-20240701114700-1.png]]
1091 1091  
1092 1092  
1093 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1094 -
1095 -
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.
1097 -
1098 -
1099 -(% class="lead" %)
1100 -Step1: Use Mobile Phone to connect device
1101 -
1102 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1103 -
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 -Above are the output example for about three action:
1115 -
1116 -[[image:image-20250121235119-1.png||height="493" width="455"]]
1117 -
1118 -[[image:image-20240207002129-2.png]]
1119 -
1120 -
1121 -(% class="lead" %)
1122 -Step3: Export Log
1123 -
1124 -[[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"]]
1125 -
1126 -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.
1127 -
1128 -[[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"]]
1129 -
1130 -
1131 1131  == 6.7 How to find the AT Command Password if lost? ==
1132 1132  
1133 1133  
... ... @@ -1147,7 +1147,6 @@
1147 1147  
1148 1148  === Version Confirmation ===
1149 1149  
1150 -
1151 1151  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:
1152 1152  
1153 1153  (% border="1" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -1218,6 +1218,7 @@
1218 1218  [[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"]]
1219 1219  
1220 1220  
1188 +
1221 1221  === Special case ===
1222 1222  
1223 1223  
... ... @@ -1225,6 +1225,7 @@
1225 1225  
1226 1226  Invalid query screenshot example:
1227 1227  
1196 +
1228 1228  [[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"]]
1229 1229  
1230 1230  [[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"]]
1750035004731-376.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -55.1 KB
Content
image-20250121235119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -145.4 KB
Content