<
From version < 131.1 >
edited by kai
on 2024/10/18 10:00
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kai
1 +XWiki.Xiaoling
Content
... ... @@ -8,7 +8,6 @@
8 8  
9 9  = 1. The use of this guideline =
10 10  
11 -
12 12  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.
13 13  
14 14  
... ... @@ -16,7 +16,6 @@
16 16  
17 17  == 2.1 General Configure to attach network ==
18 18  
19 -
20 20  To attache end nodes to NB-IoT or LTE-M Network, You need to:
21 21  
22 22  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)
... ... @@ -28,7 +28,7 @@
28 28  [[image:image-20240602220856-1.png]]
29 29  
30 30  
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"]]
29 +放一张如何插卡图片。
32 32  
33 33  
34 34  After doing above, the end nodes should be able to attach to NB-IoT network .
... ... @@ -55,7 +55,6 @@
55 55  
56 56  == 2.2 Speed Up Network Attach time ==
57 57  
58 -
59 59  **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**.
60 60  
61 61  **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.
... ... @@ -74,7 +74,7 @@
74 74  
75 75  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/]]**
76 76  
77 -=== **1. Configure Frequency Band** ===
74 +=== **1.Configure Frequency Band** ===
78 78  
79 79  AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
80 80  
... ... @@ -144,7 +144,7 @@
144 144  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
145 145  
146 146  
147 -=== **2. Configure search network sequence** ===
144 +=== **2.Configure search network sequence** ===
148 148  
149 149  AT+QCFG="nwscanseq",<scanseq>,1
150 150  
... ... @@ -157,9 +157,8 @@
157 157  
158 158  AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
159 159  
157 +=== **3.Configure Network Category to be Searched for under LTE RAT** ===
160 160  
161 -=== **3. Configure Network Category to be Searched for under LTE RAT** ===
162 -
163 163  AT+QCFG="iotopmode",mode,1
164 164  
165 165  0 eMTC 
... ... @@ -166,9 +166,8 @@
166 166  1 NB-IoT 
167 167  2 eMTC and NB-IoT
168 168  
165 +=== **4.AT command to set frequency band and network category** ===
169 169  
170 -=== **4. AT command to set frequency band and network category** ===
171 -
172 172  AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
173 173  
174 174  AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
... ... @@ -190,7 +190,6 @@
190 190  
191 191  == 3.1 General UDP Connection ==
192 192  
193 -
194 194  The NB-IoT Sensor can send packet to server use UDP protocol.
195 195  
196 196  
... ... @@ -235,7 +235,7 @@
235 235  
236 236  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
237 237  
238 -* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
232 +* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
239 239  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
240 240  
241 241  [[image:image-20240819103212-2.png]]
... ... @@ -309,6 +309,7 @@
309 309  
310 310  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
311 311  
306 +
312 312  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
313 313  
314 314  
... ... @@ -348,6 +348,7 @@
348 348  
349 349  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
350 350  
346 +
351 351  ==== 3.3.3.2 Uplink Examples ====
352 352  
353 353  
... ... @@ -419,6 +419,7 @@
419 419  
420 420  * (% 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.
421 421  
418 +
422 422  === 3.4.1 For device Already has template ===
423 423  
424 424  ==== 3.4.1.1 Create Device ====
... ... @@ -578,6 +578,7 @@
578 578  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
579 579  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
580 580  
578 +
581 581  == 3.6 ThingsBoard.Cloud (via MQTT) ==
582 582  
583 583  === 3.6.1 Configure ThingsBoard ===
... ... @@ -716,6 +716,7 @@
716 716  
717 717  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
718 718  
717 +
719 719  === 3.7.2 Simulate with MQTT.fx ===
720 720  
721 721  
... ... @@ -880,6 +880,7 @@
880 880  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
881 881  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.
882 882  
882 +
883 883  == 6.2 Why the uplink JSON format is not standard? ==
884 884  
885 885  
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0