Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 137.1 >
edited by Bei Jinggeng
on 2025/01/13 10:58
To version < 122.1 >
edited by Mengting Qiu
on 2024/09/03 10:25
>
Change comment: Uploaded new attachment "image-20240903102542-6.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.ting
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,23 +194,18 @@
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 -
201 201  === 3.1.1 Simulate UDP Connection by PC tool ===
202 202  
203 -
204 204  We can use PC tool to simulate UDP connection to make sure server works ok.
205 205  
206 -[[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-20230802112413-1.png?width=1024&height=468&rev=1.1||alt="image-20230802112413-1.png"]]
194 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
207 207  
208 -
209 209  === 3.1.2 Configure NB-IoT Sensor ===
210 210  
211 211  ==== 3.1.2.1 AT Commands ====
212 212  
213 -
214 214  (% style="color:blue" %)**AT Commands:**
215 215  
216 216  * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
... ... @@ -219,16 +219,12 @@
219 219  
220 220  [[image:image-20240819102802-1.png]]
221 221  
222 -
223 223  ==== 3.1.2.2 Uplink Example ====
224 224  
210 +[[image:image-20240819105418-8.png||height="671" width="1414"]]
225 225  
226 -[[image:image-20240819105418-8.png||height="611" width="1287"]]
227 -
228 -
229 229  == 3.2 General COAP Connection ==
230 230  
231 -
232 232  The NB-IoT Sensor can send packet to server use COAP protocol.
233 233  
234 234  Below are the commands.
... ... @@ -239,21 +239,18 @@
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
224 +* (% 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]]
246 246  
247 -
248 248  === 3.2.1 Uplink Example ===
249 249  
250 -
251 251  [[image:image-20240819103909-4.png||height="453" width="955"]]
252 252  
253 253  
254 254  == 3.2 General MQTT Connection ==
255 255  
256 -
257 257  The NB-IoT Sensor can send packet to server use MQTT protocol.
258 258  
259 259  Below are the commands.
... ... @@ -281,12 +281,10 @@
281 281  
282 282  (% 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.**
283 283  
284 -
285 285  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
286 286  
287 287  === 3.3.1 Get MQTT Credentials ===
288 288  
289 -
290 290  [[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.
291 291  
292 292  [[image:image-20240819173602-1.png||height="401" width="743"]]
... ... @@ -293,12 +293,10 @@
293 293  
294 294  [[image:image-20240819173706-3.png||height="595" width="597"]]
295 295  
296 -
297 297  === 3.3.2 Simulate with MQTT.fx ===
298 298  
299 299  ==== 3.3.2.1 Establish MQTT Connection ====
300 300  
301 -
302 302  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
303 303  
304 304  [[image:image-20240819173826-4.png||height="534" width="734"]]
... ... @@ -315,7 +315,6 @@
315 315  
316 316  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
317 317  
318 -
319 319  [[image:image-20240819174033-5.png]]
320 320  
321 321  [[image:image-20240819174209-6.png]]
... ... @@ -332,12 +332,10 @@
332 332  
333 333  [[image:image-20240819174314-7.png||height="469" width="785"]]
334 334  
335 -
336 336  === 3.3.3 Configure NB-IoT Sensor for connection ===
337 337  
338 338  ==== 3.3.3.1 AT Commands: ====
339 339  
340 -
341 341  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
342 342  
343 343  * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
... ... @@ -354,7 +354,6 @@
354 354  
355 355  ==== 3.3.3.2 Uplink Examples ====
356 356  
357 -
358 358  [[image:image-20240819174540-8.png]]
359 359  
360 360  For SE01-NB
... ... @@ -379,10 +379,8 @@
379 379  
380 380  For SN50V3-NB
381 381  
382 -
383 383  ==== 3.3.3.3 Map fields to sensor value ====
384 384  
385 -
386 386  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.
387 387  
388 388  [[image:image-20240819174610-9.png]]
... ... @@ -391,25 +391,25 @@
391 391  
392 392  Below is the NB-IoT Product Table show the mapping.
393 393  
394 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1353.82px" %)
395 -|(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:139px" %)Field4|(% style="background-color:#4f81bd; color:white; width:141px" %)Field5|(% style="background-color:#4f81bd; color:white; width:142px" %)Field6|(% style="background-color:#4f81bd; color:white; width:151px" %)Field7|(% style="background-color:#4f81bd; color:white; width:137px" %)Field8|(% style="background-color:#4f81bd; color:white; width:69px" %)Field9|(% style="background-color:#4f81bd; color:white; width:65px" %)Field10
396 -|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
397 -|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:139px" %)dielectric_constant|(% style="width:141px" %)Battery|(% style="width:142px" %)RSSI|(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
398 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
399 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
400 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
401 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
402 -|(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% colspan="1" rowspan="1" style="width:65px" %)
403 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
404 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
405 -|(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:139px" %)calc flag|(% style="width:141px" %)Battery|(% style="width:142px" %)RSSI|(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
406 -|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:139px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:141px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:142px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:137px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:69px" %)Battery|(% colspan="1" rowspan="1" style="width:65px" %)RSSI
407 -|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:142px" %)adc0|(% colspan="1" rowspan="1" style="width:151px" %)Temperature |(% colspan="1" rowspan="1" style="width:137px" %)Humidity|(% colspan="1" rowspan="1" style="width:69px" %) |(% colspan="1" rowspan="1" style="width:65px" %)
408 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" style="width:142px" %)adc0|(% colspan="1" style="width:151px" %)distance|(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
409 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)adc0|(% colspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" style="width:142px" %)adc1|(% colspan="1" style="width:151px" %)Temperature|(% colspan="1" style="width:137px" %)Humidity|(% colspan="1" style="width:69px" %)adc4|(% colspan="1" style="width:65px" %)
410 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:142px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)DS18B20 Temp2|(% colspan="1" style="width:137px" %)DS18B20 Temp3|(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
411 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:142px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)Weight|(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
412 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)count|(% colspan="1" style="width:141px" %) |(% colspan="1" style="width:142px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
363 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
364 +|(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:154px" %)Field4|(% style="background-color:#4f81bd; color:white; width:153px" %)Field5|(% style="background-color:#4f81bd; color:white; width:151px" %)Field6|(% style="background-color:#4f81bd; color:white; width:160px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:67px" %)Field9|(% style="background-color:#4f81bd; color:white; width:69px" %)Field10
365 +|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
366 +|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:154px" %)dielectric_constant|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
367 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
368 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
369 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
370 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
371 +|(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
372 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
373 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
374 +|(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:154px" %)calc flag|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
375 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:67px" %)Battery|(% colspan="1" rowspan="1" style="width:69px" %)RSSI
376 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:151px" %)adc0|(% colspan="1" rowspan="1" style="width:160px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
377 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc0|(% colspan="1" style="width:160px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
378 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)adc0|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc1|(% colspan="1" style="width:160px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:67px" %)adc4|(% colspan="1" style="width:69px" %)
379 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
380 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
381 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
413 413  
414 414  == 3.4 [[Datacake>>https://datacake.co/]] ==
415 415  
... ... @@ -427,7 +427,6 @@
427 427  
428 428  ==== 3.4.1.1 Create Device ====
429 429  
430 -
431 431  (% style="color:blue" %)**Add Device**(%%) in DataCake.
432 432  
433 433  [[image:image-20240820110003-1.png]]
... ... @@ -446,12 +446,10 @@
446 446  
447 447  [[image:image-20240820110114-6.png]]
448 448  
449 -
450 450  === 3.4.2 For Device already registered in DataCake before shipped ===
451 451  
452 452  ==== 3.4.2.1 Scan QR Code to get the device info ====
453 453  
454 -
455 455  Users can use their phones or computers to scan QR codes to obtain device data information.
456 456  
457 457  [[image:image-20240820110129-7.png]]
... ... @@ -458,40 +458,32 @@
458 458  
459 459  [[image:image-20240820110218-9.png]]
460 460  
461 -
462 462  ==== 3.4.2.2 Claim Device to User Account ====
463 463  
464 464  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
465 465  
466 -
467 467  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
468 468  
469 -
470 470  **Step1: Add a device**
471 471  
472 472  [[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png||height="330" width="900"]]
473 473  
474 -
475 475  **Step2: Choose your device type,please select dragino NB-IOT device**
476 476  
477 477  [[image:image-20240820110247-11.png]]
478 478  
479 -
480 480  **Step3: Choose to create a new device**
481 481  
482 482  [[image:image-20240820111016-12.png]]
483 483  
484 -
485 485  **Step4: Fill in the device ID of your NB device**
486 486  
487 487  [[image:image-20240820111101-13.png]]
488 488  
489 -
490 490  **Step5: Please select your device plan according to your needs and complete the creation of the device**
491 491  
492 492  [[image:image-20240820111113-14.png]]
493 493  
494 -
495 495  **Step6: Please add the decoder at the payload decoder of the device configuration.**
496 496  
497 497  **Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
... ... @@ -500,12 +500,10 @@
500 500  
501 501  [[image:image-20240820111248-16.png]]
502 502  
503 -
504 504  **Step7: Add the output of the decoder as a field**
505 505  
506 506  [[image:image-20240820111259-17.png]]
507 507  
508 -
509 509  **Step8: Customize the dashboard and use fields as parameters of the dashboard**
510 510  
511 511  [[image:image-20240820111312-18.png]]
... ... @@ -514,10 +514,8 @@
514 514  
515 515  [[image:image-20240820111333-20.png]]
516 516  
517 -
518 518  === 3.4.4 For device have not configured to connect to DataCake ===
519 519  
520 -
521 521  (% class="lead" %)
522 522  Use AT command for connecting to DataCake
523 523  
... ... @@ -525,12 +525,10 @@
525 525  
526 526  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
527 527  
528 -
529 529  == 3.5 Node-Red (via MQTT) ==
530 530  
531 531  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
532 532  
533 -
534 534  Take S31-NB UDP protocol as an example.
535 535  
536 536  Dragino provides input flow examples for the sensors.
... ... @@ -561,10 +561,8 @@
561 561  
562 562  [[image:image-20240820111448-26.png]]
563 563  
564 -
565 565  === 3.5.2 Simulate Connection ===
566 566  
567 -
568 568  We have completed the configuration of UDP. We can try sending packets to node red.
569 569  
570 570  [[image:image-20240820111504-27.png]]
... ... @@ -571,10 +571,8 @@
571 571  
572 572  [[image:image-20240820111515-28.png]]
573 573  
574 -
575 575  === 3.5.3 Configure NB-IoT Sensors ===
576 576  
577 -
578 578  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
579 579  * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
580 580  * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
... ... @@ -588,15 +588,12 @@
588 588  
589 589  ==== 3.6.1.1 Create Device ====
590 590  
591 -
592 592  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
593 593  
594 594  [[image:image-20240820112210-29.png]]
595 595  
596 -
597 597  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
598 598  
599 -
600 600  (% style="color:blue" %)**Uplink Converter**
601 601  
602 602  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.
... ... @@ -613,10 +613,8 @@
613 613  
614 614  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
615 615  
616 -
617 617  ==== 3.6.1.3 MQTT Integration Setup ====
618 618  
619 -
620 620  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”**(%%), select type (% style="color:blue" %)**MQTT**;
621 621  
622 622  [[image:image-20240820112247-32.png]]
... ... @@ -635,7 +635,6 @@
635 635  
636 636  [[image:image-20240820112330-35.png]]
637 637  
638 -
639 639  === 3.6.2 Simulate with MQTT.fx ===
640 640  
641 641  [[image:image-20240820112340-36.png]]
... ... @@ -642,10 +642,8 @@
642 642  
643 643  [[image:image-20240820112351-37.png]]
644 644  
645 -
646 646  === 3.6.3 Configure NB-IoT Sensor ===
647 647  
648 -
649 649  (% style="color:blue" %)**AT Commands**
650 650  
651 651  * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
... ... @@ -668,83 +668,10 @@
668 668  
669 669  [[image:image-20240820112426-40.png]]
670 670  
611 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
671 671  
613 +=== 3.7.1 Create device & Get Credentials ===
672 672  
673 -== 3.7 ThingsBoard.Cloud (via COAP) ==
674 -
675 -=== 3.7.1 Configure ThingsBoard ===
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,8 @@
791 791  
792 792  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
793 793  
794 -=== 3.8.2 Simulate with MQTT.fx ===
661 +=== 3.7.2 Simulate with MQTT.fx ===
795 795  
796 -
797 797  [[image:image-20240820112552-44.png]]
798 798  
799 799  [[image:image-20240820112604-45.png]]
... ... @@ -804,23 +804,19 @@
804 804  
805 805  [[image:image-20240820112626-47.png]]
806 806  
673 +=== 3.7.3 tago data ===
807 807  
808 -=== 3.8.3 tago data ===
809 -
810 -
811 811  [[image:image-20240820112637-48.png]]
812 812  
813 813  [[image:image-20240820112647-49.png]]
814 814  
679 +== 3.8 TCP Connection ==
815 815  
816 -== 3.9 TCP Connection ==
817 -
818 -
819 819  (% style="color:blue" %)**AT command:**
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)
685 +* (% 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  
... ... @@ -832,18 +832,16 @@
832 832  
833 833  [[image:image-20240820112716-51.png]]
834 834  
697 +== 3.9 AWS Connection ==
835 835  
836 -== 3.10 AWS Connection ==
837 -
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]]
840 840  
701 += =
841 841  
842 842  = 4. COAP/UDP/MQTT/TCP downlink =
843 843  
844 844  == 4.1 MQTT (via MQTT.fx) ==
845 845  
846 -
847 847  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
848 848  
849 849  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -866,12 +866,10 @@
866 866  
867 867  [[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
868 868  
869 -
870 870  **2. **When the node uplink packets, we can observe the data in MQTT.fx.
871 871  
872 872  [[image:image-20240820112813-54.png]]
873 873  
874 -
875 875  **3. **The downlink command can be successfully sent only when the downlink port is open.
876 876  
877 877   The downlink port is opened for about 3 seconds after uplink packets are sent.
... ... @@ -887,7 +887,6 @@
887 887  
888 888  == 4.2 UDP (via Thingseye) ==
889 889  
890 -
891 891  (% style="color:red" %)**Note:**(%%) The UDP service on the ThingsEye platform needs to be built by the user. (Description Link:[[UDP service building instructions>>http://www.ithingsboard.com/docs/user-guide/integrations/udp/]])
892 892  
893 893  After the node is successfully connected to the platform, you need to select the corresponding node (you can refer to the node's IMEI to find it)
... ... @@ -917,30 +917,26 @@
917 917  
918 918  = 5. GPS positioning function =
919 919  
920 -== 1. Turn on GPS function ==
777 +=== 1. Turn on GPS function ===
921 921  
922 -
923 923  (% class="wikigeneratedid" %)
924 -AT+GPS=1 or 0  ~/~/ GPS function on or off
780 +AT+GPS=1 or 0  ~/~/GPS function on or off
925 925  
926 926  
927 -== 2. Extend the time to turn on GNSS ==
783 +=== 2.Extend the time to turn on GNSS ===
928 928  
785 +AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
929 929  
930 -AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
931 931  
788 +=== 3.Get or set GPS positioning interval in units of hour ===
932 932  
933 -== 3. Get or set GPS positioning interval in units of hour ==
790 +AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
934 934  
935 935  
936 -AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
793 += 5. FAQ =
937 937  
795 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
938 938  
939 -= 6. FAQ =
940 -
941 -== 6.1 What is the usage of Multi Sampling and One Uplink? ==
942 -
943 -
944 944  The NB series has the feature for Multi Sampling and one uplink. See one of them
945 945  
946 946  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
... ... @@ -955,9 +955,8 @@
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  
958 -== 6.2 Why the uplink JSON format is not standard? ==
811 +== 5.2 Why the uplink JSON format is not standard? ==
959 959  
960 -
961 961  The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
962 962  
963 963  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
... ... @@ -964,12 +964,10 @@
964 964  
965 965  [[image:image-20240820112848-57.png]]
966 966  
819 += 6. Trouble Shooting: =
967 967  
968 -= 7. Trouble Shooting: =
821 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
969 969  
970 -== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
971 -
972 -
973 973  There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.
974 974  
975 975  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -992,16 +992,14 @@
992 992  If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.
993 993  
994 994  
995 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
845 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.2 Why sometime the AT Command is slow in reponse?(%%) ==
996 996  
997 -
998 998  When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
999 999  
1000 1000  [[image:image-20240820113015-60.png]]
1001 1001  
851 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
1002 1002  
1003 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
1004 -
1005 1005  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1006 1006  === UDP: ===
1007 1007  
... ... @@ -1011,7 +1011,6 @@
1011 1011  
1012 1012  {AT+TDC=300}
1013 1013  
1014 -
1015 1015  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1016 1016  === MQTT: ===
1017 1017  
... ... @@ -1054,7 +1054,7 @@
1054 1054  [[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/]]
1055 1055  
1056 1056  
1057 -== 7.4 What if the signal is good but the domain name resolution fails? ==
904 +== 6.4 What if the signal is good but the domain name resolution fails? ==
1058 1058  
1059 1059  
1060 1060  If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
... ... @@ -1067,31 +1067,28 @@
1067 1067  
1068 1068  (% style="color:blue" %)**AT Command: AT+GDNS**
1069 1069  
1070 -**AT+GDNS=0**  ~/~/ Default. Automatically resolves the domain name and uses the resolved IP to communicate.
917 +**AT+GDNS=0**  ~/~/Default. Automatically resolves the domain name and uses the resolved IP to communicate.
1071 1071  
1072 -**AT+GDNS=1    **~/~/ Disabling Domain name resolution. Use the domain name directly to communicate.
919 +**AT+GDNS=1    **~/~/Disabling Domain name resolution. Use the domain name directly to communicate.
1073 1073  
1074 1074  (% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
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"]]
925 +[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
1079 1079  
1080 1080  
1081 -== 7.5 GPS debugging ==
928 +== 6.5 GPS debugging ==
1082 1082  
1083 1083  
1084 1084  Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
1085 1085  
1086 -[[image:image-20240903104250-9.png||height="275" width="614"]]
933 +[[image:image-20240903100832-4.png||height="268" width="580"]]
1087 1087  
1088 1088  
1089 -[[image:image-20240903104431-10.png||height="291" width="621"]]
936 +=== 6.5.1 GPS commands ===
1090 1090  
1091 1091  
1092 -=== 7.5.1 GPS commands ===
1093 -
1094 -
1095 1095  The following are three related AT commands that introduce GPS functions.
1096 1096  
1097 1097  * **Turn on/off GPS**
... ... @@ -1138,10 +1138,10 @@
1138 1138  
1139 1139  Example: 24 hours:  24(D)=0x18(H)
1140 1140  
1141 -Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
985 + Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1142 1142  
1143 1143  
1144 -=== 7.5.2 GPS workflow ===
988 +=== 6.5.2 GPS workflow ===
1145 1145  
1146 1146  
1147 1147  The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
... ... @@ -1159,15 +1159,11 @@
1159 1159   Only when the node is activated or every (% style="color:#037691" %)**GTDC**(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool.
1160 1160  
1161 1161  
1162 -=== 7.5.3 GPS debugging methods ===
1006 +=== 6.5.3 GPS debugging methods ===
1163 1163  
1164 1164  
1165 -In summary, we can deduce the methods of debugging GPS:
1009 +In summary, we can deduce the method of debugging GPS:
1166 1166  
1167 -* **Check whether the GPS function is enabled.**
1168 -
1169 -[[image:image-20240903102327-5.png||height="271" width="529"]]
1170 -
1171 1171  * **Check whether the GPS antenna is loose**.
1172 1172  
1173 1173  If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
... ... @@ -1180,15 +1180,8 @@
1180 1180  
1181 1181  If the location fails, users can extend the location time.
1182 1182  
1183 -[[image:image-20240903102641-8.png||height="303" width="600"]]
1184 1184  
1185 1185  
1186 -== 7.6 CB device configuration TCP/IP failed ==
1187 1187  
1188 -[[image:image-20250113103816-1.png]]
1189 1189  
1190 -**Use AT+IPTYPE=? to check the IPTYPE configuration.
1191 -AT+IPTYPE can only be configured as 1 or 2.
1192 -If it is configured otherwise, this error will occur**
1193 -
1194 1194  
image-20240903102621-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -21.9 KB
Content
image-20240903102641-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -21.0 KB
Content
image-20240903104250-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -46.9 KB
Content
image-20240903104431-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -49.2 KB
Content
image-20250113103816-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -13.6 KB
Content

Applications

Navigation

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