Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 225.1 >
edited by Mengting Qiu
on 2025/03/08 11:26
To version < 215.1 >
edited by Mengting Qiu
on 2024/11/26 19:41
>
Change comment: Uploaded new attachment "image-20241126194123-29.png", version {1}

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: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+URL1=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+URL1=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 ===
... ... @@ -719,13 +719,16 @@
719 719  
720 720  == 3.11 ThingsEye (via MQTT) ==
721 721  
731 +(% class="wikigeneratedid" %)
722 722  === 3.11.1 Configure ThingsEye ===
723 723  
734 +
724 724  ==== 3.11.1.1 Create MQTT integration ====
725 725  
726 726  
727 727  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**;
728 728  
740 +
729 729  [[image:image-20241126175509-1.png||height="518" width="1081"]]
730 730  
731 731  
... ... @@ -762,7 +762,7 @@
762 762  
763 763  (% style="color:blue" %)**Add credential files.**
764 764  
765 -Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
777 +Click this link to download the certificates.
766 766  
767 767  [[image:image-20241126183032-8.png||height="757" width="976"]]
768 768  
... ... @@ -773,10 +773,10 @@
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 ====
788 +==== 3.11.1.2 Setup uplink and downlink converters ====
777 777  
778 778  
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]].
791 +First, you need to download the **MQTT uplink/downlink JS** **code**.
780 780  
781 781  * (% style="color:blue" %)**Uplink Converter**
782 782  
... ... @@ -802,67 +802,44 @@
802 802  [[image:image-20241126190737-17.png||height="527" width="1114"]]
803 803  
804 804  
805 -=== 3.11.2 Simulate with MQTT.fx ===
817 +=== 3.6.2 Simulate with MQTT.fx ===
806 806  
807 807  
808 -[[image:image-20241126191118-18.png||height="605" width="835"]]
820 +[[image:image-20230802112413-39.png]]
809 809  
810 -[[image:image-20241126193252-25.png||height="663" width="803"]]
822 +[[image:image-20230802112413-40.png||height="525" width="980"]]
811 811  
812 812  
813 -=== 3.11.3 Configure -NB node ===
825 +=== 3.6.3 Configure NB-IoT Sensor ===
814 814  
815 815  
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.
828 +(% style="color:blue" %)**AT Commands**
817 817  
818 -Screenshot of successful certificate configuration:
830 +* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
819 819  
820 -* Configuring the CA Certificate
832 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
821 821  
822 -[[image:image-20241126192009-19.png||height="431" width="697"]]
834 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
823 823  
824 -[[image:image-20241126192130-21.png||height="426" width="694"]]
836 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
825 825  
826 -* Configure client certificate
838 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
827 827  
828 -[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
840 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
829 829  
830 -* Configure client private key
842 +Test Uplink by click the button for 1 second
831 831  
832 -[[image:image-20241126192415-24.png||height="435" width="737"]]
844 +[[image:image-20230802112413-41.png||height="496" width="828"]]
833 833  
846 +[[image:image-20230802112413-42.png]]
834 834  
835 -When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
848 +[[image:image-20230802112413-43.png||height="407" width="825"]]
836 836  
837 -Then configure the -NB node to connect to the ThingsEye platform:
838 838  
839 -(% style="color:blue" %)**AT Commands**
840 840  
841 -* (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
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
845 -* (% style="color:#037691" %)**AT+CLIENT=NULL**
846 -* (% style="color:#037691" %)**AT+UNAME=NULL**
847 -* (% style="color:#037691" %)**AT+PWD=NULL**
848 -* (% style="color:#037691" %)**AT+TLSMOD=1,2**
849 849  
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  
852 -[[image:image-20241126193458-26.png||height="375" width="1012"]]
853 853  
854 -[[image:image-20241126193609-27.png||height="424" width="1014"]]
855 -
856 -
857 -Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
858 -
859 -[[image:image-20241126194018-28.png||height="318" width="1076"]]
860 -
861 -You can view the data that has just been uplink on the device:
862 -
863 -[[image:image-20241126194123-29.png||height="486" width="1073"]]
864 -
865 -
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.
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.
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,14 +937,6 @@
937 937  [[image:image-20240229233154-1.png]]
938 938  
939 939  
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 -
948 948  = 6. Trouble Shooting: =
949 949  
950 950  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -1026,11 +1026,9 @@
1026 1026  
1027 1027  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1028 1028  
1029 -
1030 1030  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1031 1031  === UDP: ===
1032 1032  
1033 -
1034 1034  (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1035 1035  Its downlink command is the same as the AT command, but brackets are required.
1036 1036  Example:
... ... @@ -1041,7 +1041,6 @@
1041 1041  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1042 1042  === MQTT: ===
1043 1043  
1044 -
1045 1045  Json：
1046 1046  
1047 1047  The Json format in MQTT mode needs to be configured with all commands.
... ... @@ -1081,44 +1081,16 @@
1081 1081  [[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/]]
1082 1082  
1083 1083  
1084 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1062 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1085 1085  
1086 1086  
1087 -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.
1065 +* **AT Command: AT** **+GETLOG**
1088 1088  
1067 +This command can be used to query upstream logs of data packets.
1089 1089  
1090 -(% class="lead" %)
1091 -Step1: Use Mobile Phone to connect device
1069 +[[image:image-20240701114700-1.png]]
1092 1092  
1093 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1094 1094  
1095 -
1096 -(% class="lead" %)
1097 -Step2: Get Log by different commands.
1098 -
1099 -Use below three method to generate logs.
1100 -
1101 -* **AT+CFG       ~-~-> Command to show the current configuration**
1102 -* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1103 -* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1104 -
1105 -Above are the output example for about three action:
1106 -
1107 -[[image:image-20250121235119-1.png||height="493" width="455"]]
1108 -
1109 -[[image:image-20240207002129-2.png]]
1110 -
1111 -
1112 -(% class="lead" %)
1113 -Step3: Export Log
1114 -
1115 -[[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"]]
1116 -
1117 -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.
1118 -
1119 -[[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"]]
1120 -
1121 -
1122 1122  == 6.7 How to find the AT Command Password if lost? ==
1123 1123  
1124 1124  
... ... @@ -1138,7 +1138,6 @@
1138 1138  
1139 1139  === Version Confirmation ===
1140 1140  
1141 -
1142 1142  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:
1143 1143  
1144 1144  (% border="1" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -1209,6 +1209,7 @@
1209 1209  [[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"]]
1210 1210  
1211 1211  
1161 +
1212 1212  === Special case ===
1213 1213  
1214 1214  
... ... @@ -1216,6 +1216,7 @@
1216 1216  
1217 1217  Invalid query screenshot example:
1218 1218  
1169 +
1219 1219  [[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"]]
1220 1220  
1221 1221  [[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,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -145.4 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0