Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 6.1 >
edited by Edwin Chen
on 2024/06/02 22:09
To version < 46.2 >
edited by Mengting Qiu
on 2024/08/20 11:02
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.ting
Content
... ... @@ -23,10 +23,12 @@
23 23  1. Power On End Node
24 24  1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net
25 25  
26 -[[image:image-20240208102804-1.png||height="286" width="696"]]
26 +[[image:image-20240602220856-1.png]]
27 27  
28 -[[image:image-20230808205045-1.png||height="293" width="438"]]
29 29  
29 +放一张如何插卡图片。
30 +
31 +
30 30  After doing above, the end nodes should be able to attach to NB-IoT network .
31 31  
32 32  The -CB and -CS models support (% style="color:blue" %)**LTE Cat NB2 and LTE-M (CAT-M1)**(%%), with below frequency band: multiple frequency bands of
... ... @@ -49,11 +49,11 @@
49 49  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:406px" %)China Mainland, HongKong|(% style="width:351px" %) |(% style="width:120px" %)
50 50  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:406px" %)China Mainland|(% style="width:351px" %) |(% style="width:120px" %)
51 51  
52 -
53 53  == 2.2 Speed Up Network Attach time ==
54 54  
55 55  **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**.
56 56  
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.
57 57  
58 58  Attache to 1NCE card for Australia use:
59 59  
... ... @@ -60,7 +60,6 @@
60 60  * AT+COPS=1,2,"50501",8
61 61  * AT+QCFG="band",0,0x8000000,0x8000000,1
62 62  
63 -
64 64  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
65 65  
66 66  AT+QENG="servingcell"
... ... @@ -70,8 +70,116 @@
70 70  
71 71  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/]]**
72 72  
74 +=== **1.Configure Frequency Band** ===
73 73  
76 +AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
74 74  
78 +<GSM_bandval>:
79 +
80 +0 No change 
81 +0x1 EGSM900
82 +0x2 DCS1800
83 +0x4 GSM850 
84 +0x8 PCS1900 
85 +0xF All of the supported bands above
86 +
87 +<eMTC_bandval>:
88 +
89 +0 No change 
90 +0x1  LTE B1
91 +0x2  LTE B2 
92 +0x4  LTE B3 
93 +0x8  LTE B4 
94 +0x10  LTE B5 
95 +0x80  LTE B8 
96 +0x800  LTE B12 
97 +0x1000  LTE B13 
98 +0x20000  LTE B18 
99 +0x40000  LTE B19 
100 +0x80000  LTE B20 
101 +0x1000000  LTE B25 
102 +0x2000000  LTE B26 
103 +0x4000000  LTE B27 
104 +0x8000000  LTE B28 
105 +0x40000000  LTE B31 
106 +0x20000000000000000  LTE B66 
107 +0x800000000000000000  LTE B72 
108 +0x1000000000000000000  LTE B73 
109 +0x1000000000000000000000  LTE B85
110 +
111 +<NB-IoT_bandval>:
112 +
113 +0 No change 
114 +0x1  LTE B1
115 +0x2  LTE B2 
116 +0x4  LTE B3 
117 +0x8  LTE B4 
118 +0x10  LTE B5 
119 +0x80  LTE B8 
120 +0x800  LTE B12 
121 +0x1000  LTE B13 
122 +0x20000  LTE B18 
123 +0x40000  LTE B19 
124 +0x80000  LTE B20 
125 +0x1000000  LTE B25 
126 +0x8000000  LTE B28 
127 +0x40000000  LTE B31 
128 +0x20000000000000000  LTE B66
129 +
130 +0x400000000000000000  LTE B71
131 +0x800000000000000000  LTE B72 
132 +0x1000000000000000000  LTE B73 
133 +0x1000000000000000000000  LTE B85
134 +
135 +For example, setting the LTE-M network frequency band to 3.
136 +
137 +AT+QCFG="band",0xF,0x4,0,1
138 +
139 +When searching for all bands, the value of this command is set to:
140 +
141 +AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
142 +
143 +
144 +=== **2.Configure search network sequence** ===
145 +
146 +AT+QCFG="nwscanseq",<scanseq>,1
147 +
148 +<scanseq>:
149 +
150 +00 Automatic (eMTC → NB-IoT → GSM) 
151 +01 GSM 
152 +02 eMTC 
153 +03 NB-IoT
154 +
155 +AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
156 +
157 +=== **3.Configure Network Category to be Searched for under LTE RAT** ===
158 +
159 +AT+QCFG="iotopmode",mode,1
160 +
161 +0 eMTC 
162 +1 NB-IoT 
163 +2 eMTC and NB-IoT
164 +
165 +=== **4.AT command to set frequency band and network category** ===
166 +
167 +AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
168 +
169 +AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
170 +
171 +**Example :**
172 +
173 +Taking the use of 1nce cards in **the United States** as an example.
174 +
175 +AT+APN=iot.1nce.net  ~/~/set APN
176 +
177 +AT+QBAND=0x100180A,0  ~/~/ eMTC ：Set frequency band B2,B4,B12,B13,B25  NB-IoT：No change
178 +
179 +AT+IOTMOD=0  ~/~/ Set  eMTC Network
180 +
181 +**Setting the above commands in the United States will greatly reduce the network search time of the NB module.**
182 +
183 +
75 75  = 3. Configure to connect to different servers =
76 76  
77 77  == 3.1 General UDP Connection ==
... ... @@ -94,12 +94,34 @@
94 94  
95 95  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
96 96  
97 -[[image:image-20230802112413-2.png]]
206 +[[image:image-20240819102802-1.png]]
98 98  
99 99  ==== 3.1.2.2 Uplink Example ====
100 100  
101 -[[image:image-20230802112413-3.png]]
210 +[[image:image-20240819105418-8.png||height="671" width="1414"]]
102 102  
212 +== 3.2 General COAP Connection ==
213 +
214 +The NB-IoT Sensor can send packet to server use COAP protocol.
215 +
216 +Below are the commands.
217 +
218 +(% style="color:blue" %)**AT Commands:**
219 +
220 +* (% style="color:#037691" %)**AT+PRO=1,0**   (%%) ~/~/ Set to use COAP protocol to uplink, Payload Type select Hex payload.
221 +
222 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
223 +
224 +* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
225 +* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
226 +
227 +[[image:image-20240819103212-2.png]]
228 +
229 +=== 3.2.1 Uplink Example ===
230 +
231 +[[image:image-20240819103909-4.png||height="453" width="955"]]
232 +
233 +
103 103  == 3.2 General MQTT Connection ==
104 104  
105 105  The NB-IoT Sensor can send packet to server use MQTT protocol.
... ... @@ -122,10 +122,11 @@
122 122  
123 123  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/ Set the subscription topic of MQTT
124 124  
125 -[[image:image-20230802112413-4.png]]
256 +[[image:image-20240819105003-7.png||height="613" width="458"]]
126 126  
127 -[[image:image-20230802112413-5.png||height="530" width="987"]]
128 128  
259 +[[image:image-20240819104942-6.png||height="702" width="974"]]
260 +
129 129  (% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.**
130 130  
131 131  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
... ... @@ -134,9 +134,9 @@
134 134  
135 135  [[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.
136 136  
137 -[[image:image-20230802112413-6.png||height="336" width="925"]]
269 +[[image:image-20240819173602-1.png||height="401" width="743"]]
138 138  
139 -[[image:image-20230802112413-7.png]]
271 +[[image:image-20240819173706-3.png||height="595" width="597"]]
140 140  
141 141  === 3.3.2 Simulate with MQTT.fx ===
142 142  
... ... @@ -144,7 +144,7 @@
144 144  
145 145  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
146 146  
147 -[[image:image-20230802112413-8.png]]
279 +[[image:image-20240819173826-4.png||height="534" width="734"]]
148 148  
149 149  * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
150 150  
... ... @@ -158,9 +158,9 @@
158 158  
159 159  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
160 160  
161 -[[image:image-20230802112413-9.png]]
293 +[[image:image-20240819174033-5.png]]
162 162  
163 -[[image:image-20230802112413-10.png]]
295 +[[image:image-20240819174209-6.png]]
164 164  
165 165  (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
166 166  
... ... @@ -172,7 +172,7 @@
172 172  
173 173  (% style="color:blue" %)**Result: **
174 174  
175 -[[image:image-20230802112413-11.png||height="539" width="901"]]
307 +[[image:image-20240819174314-7.png||height="469" width="785"]]
176 176  
177 177  === 3.3.3 Configure NB-IoT Sensor for connection ===
178 178  
... ... @@ -194,7 +194,7 @@
194 194  
195 195  ==== 3.3.3.2 Uplink Examples ====
196 196  
197 -[[image:image-20230816201942-1.png]]
329 +[[image:image-20240819174540-8.png]]
198 198  
199 199  For SE01-NB
200 200  
... ... @@ -222,9 +222,9 @@
222 222  
223 223  When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
224 224  
225 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
357 +[[image:image-20240819174610-9.png]]
226 226  
227 -[[image:image-20230802112413-13.png||height="331" width="978"]]
359 +[[image:image-20240819174618-10.png]]
228 228  
229 229  Below is the NB-IoT Product Table show the mapping.
230 230  
... ... @@ -254,11 +254,11 @@
254 254  Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
255 255  
256 256  (% class="wikigeneratedid" %)
257 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
389 +As example for S31B-CB. there are two versions: **S31B-CB-1D and S31B-CB-GE.**
258 258  
259 -* (% style="color:blue" %)**S31B-NB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
391 +* (% style="color:blue" %)**S31B-CB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
260 260  
261 -* (% style="color:blue" %)**S31B-NB-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.
393 +* (% 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.
262 262  
263 263  === 3.4.1 For device Already has template ===
264 264  
... ... @@ -266,21 +266,21 @@
266 266  
267 267  (% style="color:blue" %)**Add Device**(%%) in DataCake.
268 268  
269 -[[image:image-20230808162301-1.png||height="453" width="952"]]
401 +[[image:image-20240820110003-1.png]]
270 270  
271 -[[image:image-20230808162342-2.png||height="541" width="952"]]
403 +[[image:image-20240820110017-2.png]]
272 272  
273 273  (% style="color:blue" %)**Choose the correct model**(%%) from template.
274 274  
275 -[[image:image-20230808162421-3.png]]
407 +[[image:image-20240820110031-3.png]]
276 276  
277 277  (% style="color:blue" %)**Fill Device ID**(%%). The device ID needs to be filled in with IMEI, and a prefix of(% style="color:blue" %)** 'f' **(%%)needs to be added.
278 278  
279 -[[image:image-20230808163612-7.png||height="549" width="952"]]
411 +[[image:image-20240820110048-4.png]]
280 280  
281 -[[image:image-20230808163035-5.png]]
413 +[[image:image-20240820110103-5.png]]
282 282  
283 -[[image:image-20230808163049-6.png||height="544" width="926"]]
415 +[[image:image-20240820110114-6.png]]
284 284  
285 285  === 3.4.2 For Device already registered in DataCake before shipped ===
286 286  
... ... @@ -288,9 +288,9 @@
288 288  
289 289  Users can use their phones or computers to scan QR codes to obtain device data information.
290 290  
291 -[[image:image-20230808170051-8.png||height="255" width="259"]]
423 +[[image:image-20240820110129-7.png]]
292 292  
293 -[[image:image-20230808170548-9.png]]
425 +[[image:image-20240820110218-9.png]]
294 294  
295 295  ==== 3.4.2.2 Claim Device to User Account ====
296 296  
... ... @@ -300,11 +300,11 @@
300 300  
301 301  **Step1: Add a device**
302 302  
303 -[[image:image-20240129170024-1.png||height="330" width="900"]]
435 +[[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png||height="330" width="900"]]
304 304  
305 305  **Step2: Choose your device type,please select dragino NB-IOT device**
306 306  
307 -[[image:image-20240129170216-2.png||height="534" width="643"]]
439 +[[image:image-20240820110247-11.png]]
308 308  
309 309  **Step3: Choose to create a new device**
310 310  
... ... @@ -566,7 +566,7 @@
566 566  
567 567  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]]
568 568  
569 -= 4. MQTT/UDP/TCP downlink =
701 += 4. COAP/UDP/MQTT/TCP downlink =
570 570  
571 571  == 4.1 MQTT (via MQTT.fx) ==
572 572  
... ... @@ -608,6 +608,24 @@
608 608  
609 609  (% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
610 610  
743 += 5. GPS positioning function =
744 +
745 +=== 1. Turn on GPS function ===
746 +
747 +(% class="wikigeneratedid" %)
748 +AT+GPS=1 or 0  ~/~/GPS function on or off
749 +
750 +
751 +=== 2.Extend the time to turn on GNSS ===
752 +
753 +AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
754 +
755 +
756 +=== 3.Get or set GPS positioning interval in units of hour ===
757 +
758 +AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
759 +
760 +
611 611  = 5. FAQ =
612 612  
613 613  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
image-20240819102802-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +41.5 KB
Content
image-20240819103212-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +49.5 KB
Content
image-20240819103826-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +122.4 KB
Content
image-20240819103909-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +122.2 KB
Content
image-20240819104904-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.1 KB
Content
image-20240819104942-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.1 KB
Content
image-20240819105003-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20240819105418-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +163.8 KB
Content
image-20240819112109-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +12.9 KB
Content
image-20240819173602-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
image-20240819173659-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20240819173706-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20240819173826-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +42.3 KB
Content
image-20240819174033-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +33.1 KB
Content
image-20240819174209-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +18.9 KB
Content
image-20240819174314-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +48.4 KB
Content
image-20240819174540-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content
image-20240819174610-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +127.8 KB
Content
image-20240819174618-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +34.6 KB
Content
image-20240820110003-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +66.5 KB
Content
image-20240820110017-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +78.3 KB
Content
image-20240820110031-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.2 KB
Content
image-20240820110048-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +64.0 KB
Content
image-20240820110103-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.6 KB
Content
image-20240820110114-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.4 KB
Content
image-20240820110129-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +10.7 KB
Content
image-20240820110142-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20240820110218-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +66.7 KB
Content
image-20240820110235-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +21.2 KB
Content
image-20240820110247-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +49.8 KB
Content

Applications

Navigation

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