Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 135.2 >
edited by Xiaoling
on 2024/12/31 15:25
To version < 129.2 >
edited by Xiaoling
on 2024/09/14 10:53
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,15 +1,13 @@
1 -​**Table of Contents:**
1 +​
2 2  
3 -{{toc/}}
4 4  
4 +(% class="wikigeneratedid" id="HTableofContents:" %)
5 +**Table of Contents:**
5 5  
7 +{{toc/}}
6 6  
7 -
8 -
9 -
10 10  = 1. The use of this guideline =
11 11  
12 -
13 13  This configure instruction is for Dragino NB-IoT models with -CB or -CS suffix, for example DDS75-CB. These models use the same NB-IoT Module **[[BG95-M2>>https://www.dropbox.com/sh/3ilyaswz4odgaru/AADR86cAgL9UGlmLuEH-UZgla?st=x1ry6v5j&dl=0]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
14 14  
15 15  
... ... @@ -17,7 +17,6 @@
17 17  
18 18  == 2.1 General Configure to attach network ==
19 19  
20 -
21 21  To attache end nodes to NB-IoT or LTE-M Network, You need to:
22 22  
23 23  1. Get a NB-IoT or LTE-M SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
... ... @@ -29,7 +29,7 @@
29 29  [[image:image-20240602220856-1.png]]
30 30  
31 31  
32 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20230808205045-1.png?width=438&height=293&rev=1.1||alt="image-20230808205045-1.png"]]
29 +放一张如何插卡图片。
33 33  
34 34  
35 35  After doing above, the end nodes should be able to attach to NB-IoT network .
... ... @@ -54,12 +54,8 @@
54 54  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:406px" %)China Mainland, HongKong|(% style="width:351px" %) |(% style="width:120px" %)
55 55  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:406px" %)China Mainland|(% style="width:351px" %) |(% style="width:120px" %)
56 56  
57 -(% class="wikigeneratedid" %)
58 -cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
59 -
60 60  == 2.2 Speed Up Network Attach time ==
61 61  
62 -
63 63  **BG95-M2** supports multi bands (% style="color:blue" %)**in NB-IoT and LTE-M. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**.
64 64  
65 65  **Note:**Before using the NB module command, users need to power on the NB module. Run the AT+QSW command to turn on and off the NB module.Remember to shut down after using the NB module command, otherwise it will consume power.
... ... @@ -66,7 +66,7 @@
66 66  
67 67  Attache to 1NCE card for Australia use:
68 68  
69 -* AT+COPS=1,2,"50501",8 
62 +* AT+COPS=1,2,"50501",8
70 70  * AT+QCFG="band",0,0x8000000,0x8000000,1
71 71  
72 72  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
... ... @@ -78,7 +78,7 @@
78 78  
79 79  See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
80 80  
81 -=== **1. Configure Frequency Band** ===
74 +=== **1.Configure Frequency Band** ===
82 82  
83 83  AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
84 84  
... ... @@ -148,7 +148,7 @@
148 148  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
149 149  
150 150  
151 -=== **2. Configure search network sequence** ===
144 +=== **2.Configure search network sequence** ===
152 152  
153 153  AT+QCFG="nwscanseq",<scanseq>,1
154 154  
... ... @@ -161,9 +161,8 @@
161 161  
162 162  AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
163 163  
157 +=== **3.Configure Network Category to be Searched for under LTE RAT** ===
164 164  
165 -=== **3. Configure Network Category to be Searched for under LTE RAT** ===
166 -
167 167  AT+QCFG="iotopmode",mode,1
168 168  
169 169  0 eMTC 
... ... @@ -170,9 +170,8 @@
170 170  1 NB-IoT 
171 171  2 eMTC and NB-IoT
172 172  
165 +=== **4.AT command to set frequency band and network category** ===
173 173  
174 -=== **4. AT command to set frequency band and network category** ===
175 -
176 176  AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
177 177  
178 178  AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
... ... @@ -194,7 +194,6 @@
194 194  
195 195  == 3.1 General UDP Connection ==
196 196  
197 -
198 198  The NB-IoT Sensor can send packet to server use UDP protocol.
199 199  
200 200  
... ... @@ -239,7 +239,7 @@
239 239  
240 240  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
241 241  
242 -* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
232 +* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
243 243  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
244 244  
245 245  [[image:image-20240819103212-2.png]]
... ... @@ -313,6 +313,7 @@
313 313  
314 314  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
315 315  
306 +
316 316  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
317 317  
318 318  
... ... @@ -352,6 +352,7 @@
352 352  
353 353  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
354 354  
346 +
355 355  ==== 3.3.3.2 Uplink Examples ====
356 356  
357 357  
... ... @@ -423,6 +423,7 @@
423 423  
424 424  * (% style="color:blue" %)**S31B-CB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
425 425  
418 +
426 426  === 3.4.1 For device Already has template ===
427 427  
428 428  ==== 3.4.1.1 Create Device ====
... ... @@ -582,6 +582,7 @@
582 582  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
583 583  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
584 584  
578 +
585 585  == 3.6 ThingsBoard.Cloud (via MQTT) ==
586 586  
587 587  === 3.6.1 Configure ThingsBoard ===
... ... @@ -669,82 +669,11 @@
669 669  [[image:image-20240820112426-40.png]]
670 670  
671 671  
666 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
672 672  
673 -== 3.7 ThingsBoard.Cloud (via COAP) ==
668 +=== 3.7.1 Create device & Get Credentials ===
674 674  
675 -=== 3.7.1 Configure ThingsBoard ===
676 676  
677 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
678 -
679 -
680 -(% style="color:blue" %)**Uplink Converter**
681 -
682 -The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
683 -
684 -To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
685 -
686 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729141300-1.png?width=1115&height=552&rev=1.1||alt="image-20240729141300-1.png" height="579" width="1168"]]
687 -
688 -
689 -(% style="color:blue" %)**Downlink Converter**
690 -
691 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
692 -
693 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729142505-3.png?width=1023&height=507&rev=1.1||alt="image-20240729142505-3.png" height="579" width="1168"]]
694 -
695 -
696 -==== 3.7.1.2 COAP Integration Setup ====
697 -
698 -
699 -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" %)**“CoAP Integration”**(%%), select type **COAP    **(% style="color:blue" %);
700 -
701 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729144058-4.png?width=1021&height=506&rev=1.1||alt="image-20240729144058-4.png" height="583" width="1176"]]
702 -
703 -
704 -The next steps is to add the recently created uplink converters;
705 -
706 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729150142-5.png?width=1023&height=507&rev=1.1||alt="image-20240729150142-5.png" height="591" width="1193"]]
707 -
708 -
709 -==== 3.7.1.3 Add COAP Integration ====
710 -
711 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729161543-9.png?width=1009&height=500&rev=1.1||alt="image-20240729161543-9.png" height="590" width="1191"]]
712 -
713 -
714 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
715 -
716 -==== 3.7.2.1 Instruction Description ====
717 -
718 -
719 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
720 -* AT+SERVADDR=COAP Server Address,5683
721 -
722 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
723 -
724 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172305-12.png?width=624&height=361&rev=1.1||alt="image-20240729172305-12.png" height="417" width="721"]]
725 -
726 -Note:The port for the COAP protocol has been fixed to 5683
727 -
728 -
729 -* AT+URL1=11,"i"
730 -* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
731 -*
732 -
733 --CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
734 -
735 -e.g.
736 -
737 -* AT+URL1=11, "i"
738 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
739 -
740 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172500-14.png?width=700&height=403&rev=1.1||alt="image-20240729172500-14.png" height="413" width="718"]]
741 -
742 -
743 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
744 -
745 -=== 3.8.1 Create device & Get Credentials ===
746 -
747 -
748 748  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
749 749  
750 750  [[image:image-20240820112516-41.png]]
... ... @@ -791,9 +791,10 @@
791 791  
792 792  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
793 793  
794 -=== 3.8.2 Simulate with MQTT.fx ===
795 795  
718 +=== 3.7.2 Simulate with MQTT.fx ===
796 796  
720 +
797 797  [[image:image-20240820112552-44.png]]
798 798  
799 799  [[image:image-20240820112604-45.png]]
... ... @@ -805,7 +805,7 @@
805 805  [[image:image-20240820112626-47.png]]
806 806  
807 807  
808 -=== 3.8.3 tago data ===
732 +=== 3.7.3 tago data ===
809 809  
810 810  
811 811  [[image:image-20240820112637-48.png]]
... ... @@ -813,7 +813,7 @@
813 813  [[image:image-20240820112647-49.png]]
814 814  
815 815  
816 -== 3.9 TCP Connection ==
740 +== 3.8 TCP Connection ==
817 817  
818 818  
819 819  (% style="color:blue" %)**AT command:**
... ... @@ -820,7 +820,7 @@
820 820  
821 821  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
822 822  
823 -* (% style="color:#037691" %)**AT+PRO=4,5   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
747 +* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
824 824  
825 825  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
826 826  
... ... @@ -833,7 +833,7 @@
833 833  [[image:image-20240820112716-51.png]]
834 834  
835 835  
836 -== 3.10 AWS Connection ==
760 +== 3.9 AWS Connection ==
837 837  
838 838  
839 839  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]]
... ... @@ -955,6 +955,7 @@
955 955  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
956 956  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.
957 957  
882 +
958 958  == 6.2 Why the uplink JSON format is not standard? ==
959 959  
960 960  
... ... @@ -1075,7 +1075,7 @@
1075 1075  
1076 1076  Example:
1077 1077  
1078 -[[image:image-20240827150121-5.png||height="473" width="676"]][[image:image-20240827145055-4.png||height="474" width="665"]]
1003 +[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
1079 1079  
1080 1080  
1081 1081  == 7.5 GPS debugging ==

Applications

Navigation

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