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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -8,6 +8,7 @@
8 8  
9 9  = 1. The use of this guideline =
10 10  
11 +
11 11  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.
12 12  
13 13  
... ... @@ -15,6 +15,7 @@
15 15  
16 16  == 2.1 General Configure to attach network ==
17 17  
19 +
18 18  To attache end nodes to NB-IoT or LTE-M Network, You need to:
19 19  
20 20  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)
... ... @@ -26,7 +26,7 @@
26 26  [[image:image-20240602220856-1.png]]
27 27  
28 28  
29 -放一张如何插卡图片。
31 +[[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"]]
30 30  
31 31  
32 32  After doing above, the end nodes should be able to attach to NB-IoT network .
... ... @@ -53,6 +53,7 @@
53 53  
54 54  == 2.2 Speed Up Network Attach time ==
55 55  
58 +
56 56  **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**.
57 57  
58 58  **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.
... ... @@ -71,7 +71,7 @@
71 71  
72 72  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/]]**
73 73  
74 -=== **1.Configure Frequency Band** ===
77 +=== **1. Configure Frequency Band** ===
75 75  
76 76  AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
77 77  
... ... @@ -141,7 +141,7 @@
141 141  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
142 142  
143 143  
144 -=== **2.Configure search network sequence** ===
147 +=== **2. Configure search network sequence** ===
145 145  
146 146  AT+QCFG="nwscanseq",<scanseq>,1
147 147  
... ... @@ -154,8 +154,9 @@
154 154  
155 155  AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
156 156  
157 -=== **3.Configure Network Category to be Searched for under LTE RAT** ===
158 158  
161 +=== **3. Configure Network Category to be Searched for under LTE RAT** ===
162 +
159 159  AT+QCFG="iotopmode",mode,1
160 160  
161 161  0 eMTC 
... ... @@ -162,8 +162,9 @@
162 162  1 NB-IoT 
163 163  2 eMTC and NB-IoT
164 164  
165 -=== **4.AT command to set frequency band and network category** ===
166 166  
170 +=== **4. AT command to set frequency band and network category** ===
171 +
167 167  AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
168 168  
169 169  AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
... ... @@ -185,6 +185,7 @@
185 185  
186 186  == 3.1 General UDP Connection ==
187 187  
193 +
188 188  The NB-IoT Sensor can send packet to server use UDP protocol.
189 189  
190 190  
... ... @@ -229,7 +229,7 @@
229 229  
230 230  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
231 231  
232 -* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
238 +* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
233 233  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
234 234  
235 235  [[image:image-20240819103212-2.png]]
... ... @@ -303,7 +303,6 @@
303 303  
304 304  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
305 305  
306 -
307 307  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
308 308  
309 309  
... ... @@ -343,7 +343,6 @@
343 343  
344 344  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
345 345  
346 -
347 347  ==== 3.3.3.2 Uplink Examples ====
348 348  
349 349  
... ... @@ -415,7 +415,6 @@
415 415  
416 416  * (% 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.
417 417  
418 -
419 419  === 3.4.1 For device Already has template ===
420 420  
421 421  ==== 3.4.1.1 Create Device ====
... ... @@ -575,7 +575,6 @@
575 575  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
576 576  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
577 577  
578 -
579 579  == 3.6 ThingsBoard.Cloud (via MQTT) ==
580 580  
581 581  === 3.6.1 Configure ThingsBoard ===
... ... @@ -663,11 +663,83 @@
663 663  [[image:image-20240820112426-40.png]]
664 664  
665 665  
666 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
667 667  
668 -=== 3.7.1 Create device & Get Credentials ===
669 +== 3.7 ThingsBoard.Cloud (via COAP) ==
669 669  
671 +=== 3.7.1 Configure ThingsBoard ===
670 670  
673 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
674 +
675 +
676 +(% style="color:blue" %)**Uplink Converter**
677 +
678 +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.
679 +
680 +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.
681 +
682 +[[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"]]
683 +
684 +
685 +(% style="color:blue" %)**Downlink Converter**
686 +
687 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
688 +
689 +[[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"]]
690 +
691 +
692 +==== 3.7.1.2 COAP Integration Setup ====
693 +
694 +
695 +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" %);
696 +
697 +[[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"]]
698 +
699 +
700 +The next steps is to add the recently created uplink converters;
701 +
702 +[[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"]]
703 +
704 +
705 +==== 3.7.1.3 Add COAP Integration ====
706 +
707 +[[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"]]
708 +
709 +
710 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
711 +
712 +==== 3.7.2.1 Instruction Description ====
713 +
714 +
715 +* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
716 +* AT+SERVADDR=COAP Server Address,5683
717 +
718 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
719 +
720 +[[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"]]
721 +
722 +Note:The port for the COAP protocol has been fixed to 5683
723 +
724 +
725 +* AT+URL1=11,"i"
726 +* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
727 +*
728 +
729 +-CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
730 +
731 +e.g.
732 +
733 +* AT+URL1=11, "i"
734 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
735 +
736 +
737 +[[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"]]
738 +
739 +
740 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
741 +
742 +=== 3.8.1 Create device & Get Credentials ===
743 +
744 +
671 671  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.
672 672  
673 673  [[image:image-20240820112516-41.png]]
... ... @@ -714,10 +714,9 @@
714 714  
715 715  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
716 716  
791 +=== 3.8.2 Simulate with MQTT.fx ===
717 717  
718 -=== 3.7.2 Simulate with MQTT.fx ===
719 719  
720 -
721 721  [[image:image-20240820112552-44.png]]
722 722  
723 723  [[image:image-20240820112604-45.png]]
... ... @@ -729,7 +729,7 @@
729 729  [[image:image-20240820112626-47.png]]
730 730  
731 731  
732 -=== 3.7.3 tago data ===
805 +=== 3.8.3 tago data ===
733 733  
734 734  
735 735  [[image:image-20240820112637-48.png]]
... ... @@ -737,7 +737,7 @@
737 737  [[image:image-20240820112647-49.png]]
738 738  
739 739  
740 -== 3.8 TCP Connection ==
813 +== 3.9 TCP Connection ==
741 741  
742 742  
743 743  (% style="color:blue" %)**AT command:**
... ... @@ -757,7 +757,7 @@
757 757  [[image:image-20240820112716-51.png]]
758 758  
759 759  
760 -== 3.9 AWS Connection ==
833 +== 3.10 AWS Connection ==
761 761  
762 762  
763 763  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]]
... ... @@ -879,7 +879,6 @@
879 879  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
880 880  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.
881 881  
882 -
883 883  == 6.2 Why the uplink JSON format is not standard? ==
884 884  
885 885  

Applications

Navigation

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