Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 194.1
edited by Mengting Qiu
on 2024/11/26 18:30
Change comment: Uploaded new attachment "image-20241126183032-8.png", version {1}
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) ===
... ... @@ -726,6 +726,152 @@
726 726  Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
727 727  
728 728  
729 +== 3.11 ThingsEye (via MQTT) ==
730 +
731 +=== 3.11.1 Configure ThingsEye ===
732 +
733 +==== 3.11.1.1 Create MQTT integration ====
734 +
735 +
736 +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**;
737 +
738 +[[image:image-20241126175509-1.png||height="518" width="1081"]]
739 +
740 +
741 +Next, directly select to create a new Uplink data converter and downlink data converter.
742 +
743 +[[image:image-20241126180135-2.png||height="535" width="1092"]]
744 +
745 +[[image:image-20241126180223-3.png||height="518" width="1093"]]
746 +
747 +
748 +(% style="color:blue" %)**Add a topic filter:**
749 +
750 +Consistent with the theme of the node setting.
751 +
752 +(% style="color:red" %)**Note: Recommended MQTT broker: lns1.thingseye.io 8883, fixed use. Topic can be changed on their own, but it need to be consistent with the node's publish and subscribe topic.**
753 +
754 +You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
755 +
756 +[[image:image-20241126181024-4.png||height="521" width="1081"]]
757 +
758 +
759 +==== 3.11.1.2 Add credentials to the MQTT integration ====
760 +
761 +
762 +Click on the MQTT integration you just created.
763 +
764 +[[image:image-20241126181837-5.png||height="365" width="1079"]]
765 +
766 +
767 +Click the edit icon in the upper right corner to enter the edit mode.
768 +
769 +[[image:image-20241126184523-13.png||height="330" width="1075"]]
770 +
771 +
772 +(% style="color:blue" %)**Add credential files.**
773 +
774 +Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
775 +
776 +[[image:image-20241126183032-8.png||height="757" width="976"]]
777 +
778 +When the addition is complete, save the Settings.
779 +
780 +[[image:image-20241126184303-12.png||height="284" width="975"]]
781 +
782 +[[image:image-20241126184211-11.png||height="161" width="977"]]
783 +
784 +
785 +==== 3.11.1.3 Setup uplink and downlink converters ====
786 +
787 +
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]].
789 +
790 +* (% style="color:blue" %)**Uplink Converter**
791 +
792 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
793 +
794 +Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT uplink converter that was newly created when the integration was created.
795 +
796 +[[image:image-20241126184906-14.png||height="424" width="1100"]]
797 +
798 +Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
799 +
800 +[[image:image-20241126190131-15.png||height="542" width="1103"]]
801 +
802 +
803 +* (% style="color:blue" %)**Downlink Converter**
804 +
805 +Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT downlink converter that was newly created when the integration was created.
806 +
807 +[[image:image-20241126190251-16.png||height="372" width="1113"]]
808 +
809 +Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
810 +
811 +[[image:image-20241126190737-17.png||height="527" width="1114"]]
812 +
813 +
814 +=== 3.11.2 Simulate with MQTT.fx ===
815 +
816 +
817 +[[image:image-20241126191118-18.png||height="605" width="835"]]
818 +
819 +[[image:image-20241126193252-25.png||height="663" width="803"]]
820 +
821 +
822 +=== 3.11.3 Configure -NB node ===
823 +
824 +
825 +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.
826 +
827 +Screenshot of successful certificate configuration:
828 +
829 +* Configuring the CA Certificate
830 +
831 +[[image:image-20241126192009-19.png||height="431" width="697"]]
832 +
833 +[[image:image-20241126192130-21.png||height="426" width="694"]]
834 +
835 +* Configure client certificate
836 +
837 +[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
838 +
839 +* Configure client private key
840 +
841 +[[image:image-20241126192415-24.png||height="435" width="737"]]
842 +
843 +
844 +When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
845 +
846 +Then configure the -NB node to connect to the ThingsEye platform:
847 +
848 +(% style="color:blue" %)**AT Commands**
849 +
850 +* (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
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
854 +* (% style="color:#037691" %)**AT+CLIENT=NULL**
855 +* (% style="color:#037691" %)**AT+UNAME=NULL**
856 +* (% style="color:#037691" %)**AT+PWD=NULL**
857 +* (% style="color:#037691" %)**AT+TLSMOD=1,0**
858 +
859 +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:
860 +
861 +[[image:image-20241126193458-26.png||height="375" width="1012"]]
862 +
863 +[[image:image-20241126193609-27.png||height="424" width="1014"]]
864 +
865 +
866 +Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
867 +
868 +[[image:image-20241126194018-28.png||height="318" width="1076"]]
869 +
870 +You can view the data that has just been uplink on the device:
871 +
872 +[[image:image-20241126194123-29.png||height="486" width="1073"]]
873 +
874 +
729 729  = 4. MQTT/UDP/TCP downlink =
730 730  
731 731  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -786,8 +786,8 @@
786 786  1. Give more sampling data points.
787 787  1. Increase reliable in transmission. For example. If user set
788 788  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)
789 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
790 -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.
791 791  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.
792 792  
793 793  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -800,6 +800,14 @@
800 800  [[image:image-20240229233154-1.png]]
801 801  
802 802  
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 +
803 803  = 6. Trouble Shooting: =
804 804  
805 805  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -881,9 +881,11 @@
881 881  
882 882  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
883 883  
1038 +
884 884  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
885 885  === UDP: ===
886 886  
1042 +
887 887  (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
888 888  Its downlink command is the same as the AT command, but brackets are required.
889 889  Example:
... ... @@ -894,6 +894,7 @@
894 894  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
895 895  === MQTT: ===
896 896  
1053 +
897 897  Json：
898 898  
899 899  The Json format in MQTT mode needs to be configured with all commands.
... ... @@ -933,16 +933,45 @@
933 933  [[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/]]
934 934  
935 935  
936 -== (% 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?(%%) ==
937 937  
938 938  
939 -* **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.
940 940  
941 -This command can be used to query upstream logs of data packets.
942 942  
943 -[[image:image-20240701114700-1.png]]
1099 +(% class="lead" %)
1100 +Step1: Use Mobile Phone to connect device
944 944  
1102 +See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
945 945  
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 +
946 946  == 6.7 How to find the AT Command Password if lost? ==
947 947  
948 948  
... ... @@ -962,6 +962,7 @@
962 962  
963 963  === Version Confirmation ===
964 964  
1151 +
965 965  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:
966 966  
967 967  (% border="1" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -1032,7 +1032,6 @@
1032 1032  [[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"]]
1033 1033  
1034 1034  
1035 -
1036 1036  === Special case ===
1037 1037  
1038 1038  
... ... @@ -1040,7 +1040,6 @@
1040 1040  
1041 1041  Invalid query screenshot example:
1042 1042  
1043 -
1044 1044  [[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"]]
1045 1045  
1046 1046  [[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-20241126183803-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20241126184136-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +15.7 KB
Content
image-20241126184211-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20241126184303-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +81.7 KB
Content
image-20241126184523-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +88.7 KB
Content
image-20241126184906-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +108.0 KB
Content
image-20241126190131-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +267.9 KB
Content
image-20241126190251-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +94.2 KB
Content
image-20241126190737-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +253.7 KB
Content
image-20241126191118-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +61.4 KB
Content
image-20241126192009-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +113.6 KB
Content
image-20241126192122-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +105.2 KB
Content
image-20241126192130-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +105.2 KB
Content
image-20241126192246-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +87.7 KB
Content
image-20241126192315-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.0 KB
Content
image-20241126192415-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +88.2 KB
Content
image-20241126193252-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +64.2 KB
Content
image-20241126193458-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +144.3 KB
Content
image-20241126193609-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +167.5 KB
Content
image-20241126194018-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +63.5 KB
Content
image-20241126194123-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.7 KB
Content
image-20250121235119-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +145.4 KB
Content