Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 145.2 >
edited by Xiaoling
on 2024/03/01 10:15
To version < 99.1 >
edited by Edwin Chen
on 2023/08/10 12:36
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -4,10 +4,6 @@
4 4  {{toc/}}
5 5  
6 6  
7 -
8 -
9 -
10 -
11 11  = 1. The use of this guideline =
12 12  
13 13  
... ... @@ -16,19 +16,13 @@
16 16  
17 17  = 2. Attach Network =
18 18  
19 -== 2.1 General Configure to attach network ==
20 20  
21 -
22 22  To attache NB-IoT sensors to NB-IoT Network, You need to:
23 23  
24 24  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
25 -1. Power Off End Node ( See below for the power off/on position)
26 -1. Insert the SIM card to Sensor. ( See below for direction)
27 -1. Power On End Node
19 +1. Insert the SIM card to Sensor
28 28  1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
29 29  
30 -[[image:image-20240208102804-1.png||height="286" width="696"]]
31 -
32 32  [[image:image-20230808205045-1.png||height="293" width="438"]]
33 33  
34 34  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -45,28 +45,6 @@
45 45  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
46 46  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 47  
48 -== 2.2 Speed Up Network Attach time ==
49 -
50 -
51 -BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) 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. User can lock the band to specify band for its operator to make this faster.
52 -
53 -(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 -
55 -(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 -
57 -(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
58 -
59 -(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
60 -(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
61 -(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
62 -(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
63 -
64 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
65 -
66 -
67 -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/]]**
68 -
69 -
70 70  = 3. Configure to connect to different servers =
71 71  
72 72  == 3.1 General UDP Connection ==
... ... @@ -80,7 +80,7 @@
80 80  
81 81  We can use PC tool to simulate UDP connection to make sure server works ok.
82 82  
83 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
51 +[[image:image-20230802112413-1.png]]
84 84  
85 85  
86 86  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -94,6 +94,8 @@
94 94  
95 95  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
96 96  
65 +* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
66 +
97 97  [[image:image-20230802112413-2.png]]
98 98  
99 99  
... ... @@ -128,7 +128,7 @@
128 128  
129 129  [[image:image-20230802112413-4.png]]
130 130  
131 -[[image:image-20230802112413-5.png||height="530" width="987"]]
101 +[[image:image-20230802112413-5.png]]
132 132  
133 133  (% 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.**
134 134  
... ... @@ -140,7 +140,7 @@
140 140  
141 141  [[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.
142 142  
143 -[[image:image-20230802112413-6.png||height="336" width="925"]]
113 +[[image:image-20230802112413-6.png]]
144 144  
145 145  [[image:image-20230802112413-7.png]]
146 146  
... ... @@ -183,7 +183,7 @@
183 183  
184 184  (% style="color:blue" %)**Result: **
185 185  
186 -[[image:image-20230802112413-11.png||height="539" width="901"]]
156 +[[image:image-20230802112413-11.png]]
187 187  
188 188  
189 189  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -193,7 +193,7 @@
193 193  
194 194  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
195 195  
196 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
166 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) **~/~/ Set to use ThingSpeak Server and Related Payload**
197 197  
198 198  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
199 199  
... ... @@ -208,7 +208,7 @@
208 208  ==== 3.3.3.2 Uplink Examples ====
209 209  
210 210  
211 -[[image:image-20230816201942-1.png]]
181 +For S31-NB
212 212  
213 213  For SE01-NB
214 214  
... ... @@ -239,9 +239,9 @@
239 239  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.
240 240  
241 241  
242 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
212 +[[image:image-20230802112413-12.png]]
243 243  
244 -[[image:image-20230802112413-13.png||height="331" width="978"]]
214 +[[image:image-20230802112413-13.png]]
245 245  
246 246  
247 247  Below is the NB-IoT Product Table show the mapping.
... ... @@ -266,121 +266,42 @@
266 266  |(% 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" %)
267 267  |(% 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" %)
268 268  
269 -== 3.4 [[Datacake>>https://datacake.co/]] ==
239 +== 3.4 Datacake ==
270 270  
241 +=== 3.4.1 Create device ===
271 271  
272 -(% class="wikigeneratedid" %)
273 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
274 274  
244 +[[image:image-20230808162301-1.png]]
275 275  
276 -(% class="wikigeneratedid" %)
277 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
278 278  
279 -* (% 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.
247 +[[image:image-20230808162342-2.png]]
280 280  
281 -* (% 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.
282 282  
283 -=== 3.4.1 For device Already has template ===
284 -
285 -==== 3.4.1.1 Create Device ====
286 -
287 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
288 -
289 -[[image:image-20230808162301-1.png||height="453" width="952"]]
290 -
291 -
292 -[[image:image-20230808162342-2.png||height="541" width="952"]]
293 -
294 -
295 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
296 -
297 297  [[image:image-20230808162421-3.png]]
298 298  
299 299  
300 -(% 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.
253 +The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
301 301  
302 -[[image:image-20230808163612-7.png||height="549" width="952"]]
255 +[[image:image-20230808163612-7.png]]
303 303  
304 304  [[image:image-20230808163035-5.png]]
305 305  
306 -[[image:image-20230808163049-6.png||height="544" width="926"]]
259 +[[image:image-20230808163049-6.png]]
307 307  
308 308  
309 -=== 3.4.2 For Device already registered in DataCake before shipped ===
262 +=== 3.4.2 Scan QR code to obtain data ===
310 310  
311 -==== 3.4.2.1 Scan QR Code to get the device info ====
312 312  
313 -
314 314  Users can use their phones or computers to scan QR codes to obtain device data information.
315 315  
316 -[[image:image-20230808170051-8.png||height="255" width="259"]]
267 +[[image:image-20230808170051-8.png]]
317 317  
318 318  [[image:image-20230808170548-9.png]]
319 319  
320 320  
321 -==== 3.4.2.2 Claim Device to User Account ====
272 +=== 3.4.2 AT command for connecting to DataCake ===
322 322  
323 323  
324 -By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 -
326 -
327 -=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
328 -
329 -
330 -**Step1: Add a device**
331 -
332 -[[image:image-20240129170024-1.png||height="330" width="900"]]
333 -
334 -
335 -**Step2: Choose your device type,please select dragino NB-IOT device**
336 -
337 -[[image:image-20240129170216-2.png||height="534" width="643"]]
338 -
339 -
340 -**Step3: Choose to create a new device**
341 -
342 -[[image:image-20240129170539-3.png||height="459" width="646"]]
343 -
344 -
345 -**Step4: Fill in the device ID of your NB device**
346 -
347 -[[image:image-20240202111546-1.png||height="378" width="651"]]
348 -
349 -
350 -**Step5: Please select your device plan according to your needs and complete the creation of the device**
351 -
352 -[[image:image-20240129171236-6.png||height="450" width="648"]]
353 -
354 -
355 -**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 -
357 -**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]]
358 -
359 -[[image:image-20240129172056-7.png||height="457" width="816"]]
360 -
361 -[[image:image-20240129173116-9.png||height="499" width="814"]]
362 -
363 -
364 -**Step7: Add the output of the decoder as a field**
365 -
366 -[[image:image-20240129173541-10.png||height="592" width="968"]]
367 -
368 -
369 -**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 -
371 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
372 -
373 -[[image:image-20240129174657-12.png||height="538" width="916"]]
374 -
375 -[[image:image-20240129174840-13.png||height="536" width="750"]]
376 -
377 -
378 -=== 3.4.4 For device have not configured to connect to DataCake ===
379 -
380 -
381 -(% class="lead" %)
382 -Use AT command for connecting to DataCake
383 -
384 384  (% style="color:blue" %)**AT+PRO=2,0**
385 385  
386 386  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -406,19 +406,17 @@
406 406  
407 407  [[image:image-20230809173127-4.png]]
408 408  
409 -
410 410  Please select the NB95S31B template.
411 411  
412 -[[image:image-20230809173310-5.png||height="558" width="926"]]
302 +[[image:image-20230809173310-5.png]]
413 413  
414 414  [[image:image-20230809173438-6.png]]
415 415  
416 416  [[image:image-20230809173800-7.png]]
417 417  
418 -
419 419  Successfully imported template.
420 420  
421 -[[image:image-20230809173835-8.png||height="515" width="860"]]
310 +[[image:image-20230809173835-8.png]]
422 422  
423 423  
424 424  Users can set UDP port.
... ... @@ -425,27 +425,21 @@
425 425  
426 426  [[image:image-20230809174053-9.png]]
427 427  
428 -
429 429  === 3.5.2 Simulate Connection ===
430 430  
431 -
432 432  We have completed the configuration of UDP. We can try sending packets to node red.
433 433  
434 434  [[image:image-20230810083934-1.png]]
435 435  
436 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
323 +[[image:image-20230810084048-2.png]]
437 437  
438 -
439 439  === 3.5.3 Configure NB-IoT Sensors ===
440 440  
441 441  
442 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
443 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
444 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
445 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
446 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
447 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
328 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)**(%%)    **~/~/  Set to UDP Server and  Payload**
448 448  
330 +* **AT+SERVADDR=xx.xx.xx.xx,port   ** **~/~/  Set Server IP and  port**
331 +
449 449  == 3.6 ThingsBoard.Cloud (via MQTT) ==
450 450  
451 451  === 3.6.1 Configure ThingsBoard ===
... ... @@ -455,7 +455,7 @@
455 455  
456 456  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
457 457  
458 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
341 +[[image:image-20230802112413-32.png]]
459 459  
460 460  
461 461  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -467,7 +467,7 @@
467 467  
468 468  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" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
469 469  
470 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
353 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
471 471  
472 472  
473 473  (% style="color:blue" %)**Downlink Converter**
... ... @@ -474,7 +474,7 @@
474 474  
475 475  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
476 476  
477 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
360 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
478 478  
479 479  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
480 480  
... ... @@ -484,23 +484,23 @@
484 484  
485 485  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**;
486 486  
487 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
370 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
488 488  
489 489  
490 490  * The next steps is to add the recently created uplink and downlink converters;
491 491  
492 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
375 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
493 493  
494 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
377 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
495 495  
496 496  
497 497  (% style="color:blue" %)**Add a topic filter:**
498 498  
499 -Consistent with the theme of the node setting.
382 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
500 500  
501 501  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
502 502  
503 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
386 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
504 504  
505 505  
506 506  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -508,7 +508,7 @@
508 508  
509 509  [[image:image-20230802112413-39.png]]
510 510  
511 -[[image:image-20230802112413-40.png||height="525" width="980"]]
394 +[[image:image-20230802112413-40.png]]
512 512  
513 513  
514 514  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -530,11 +530,11 @@
530 530  
531 531  Test Uplink by click the button for 1 second
532 532  
533 -[[image:image-20230802112413-41.png||height="496" width="828"]]
416 +[[image:image-20230802112413-41.png]]
534 534  
535 535  [[image:image-20230802112413-42.png]]
536 536  
537 -[[image:image-20230802112413-43.png||height="407" width="825"]]
420 +[[image:image-20230802112413-43.png]]
538 538  
539 539  
540 540  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -592,16 +592,14 @@
592 592  
593 593  === 3.7.2 Simulate with MQTT.fx ===
594 594  
595 -
596 596  [[image:image-20230802112413-52.png]]
597 597  
598 598  
599 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
481 +[[image:image-20230808105300-2.png]]
600 600  
601 -
602 602  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
603 603  
604 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
485 +[[image:image-20230808105217-1.png]]
605 605  
606 606  [[image:image-20230808105329-3.png]]
607 607  
... ... @@ -609,11 +609,12 @@
609 609  === 3.7.3 tago data ===
610 610  
611 611  
612 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
493 +[[image:image-20230802112413-50.png]]
613 613  
614 614  [[image:image-20230802112413-51.png||height="184" width="696"]]
615 615  
616 616  
498 +
617 617  == 3.8 TCP Connection ==
618 618  
619 619  
... ... @@ -633,114 +633,3 @@
633 633  (% style="color:blue" %)**See result in TCP Server:**
634 634  
635 635  [[image:image-20230807233631-2.png]]
636 -
637 -
638 -= 4. FAQ =
639 -
640 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
641 -
642 -
643 -The NB series has the feature for Multi Sampling and one uplink. See one of them
644 -
645 -[[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]]
646 -
647 -User can use this feature for below purpose:
648 -
649 -1. **Reduce power consumption**. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.
650 -1. Give more sampling data points.
651 -1. Increase reliable in transmission. For example. If user set
652 -1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
653 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
654 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
655 -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.
656 -
657 -
658 -
659 -== 4.2 Why the uplink JSON format is not standard? ==
660 -
661 -
662 -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.
663 -
664 -[[image:image-20240229233154-1.png]]
665 -
666 -
667 -= 5. Trouble Shooting: =
668 -
669 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
670 -
671 -
672 -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.
673 -
674 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
675 -
676 -[[image:image-20240207002003-1.png]]
677 -
678 -
679 -If fail to attach network, it will shows signal 99. as below:
680 -
681 -[[image:image-20240207002129-2.png]]
682 -
683 -
684 -(% class="lead" %)
685 -When see this issue, below are the checklist:
686 -
687 -* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
688 -* Do you configure the correct APN? [[Check here for APN settings>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
689 -* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
690 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
691 -* Check if the antenna is connected firmly.
692 -
693 -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.
694 -
695 -
696 -== 5.2 Issue: "NBIOT did not respond" ==
697 -
698 -
699 -(% class="box errormessage" %)
700 -(((
701 -11:24:22.397 [44596]NBIOT did not respond.
702 -11:24:24.315 [46530]NBIOT did not respond.
703 -11:24:26.256 [48464]NBIOT did not respond.
704 -11:24:28.196 [50398]NBIOT did not respond.
705 -11:24:30.115 [52332]NBIOT did not respond.
706 -11:24:32.127 [54266]NBIOT did not respond.
707 -11:24:32.127 [54299]Restart the module...
708 -11:24:39.181 [61332]No response when shutting down
709 -)))
710 -
711 -This issue might due to initiate issue for NB-IoT module. In this case, please try:
712 -
713 -1) Open Enclosure
714 -
715 -2) Power off device by pull out the power on Jumper
716 -
717 -3) Power on device by connect back the power jumper.
718 -
719 -4) push reset button.
720 -
721 -[[image:image-20240208001740-1.png]]
722 -
723 -
724 -== 5.3 Issue: "Failed to readI MSI number" ==
725 -
726 -
727 -(% class="box errormessage" %)
728 -(((
729 -[18170]Failed to read IMSI:1umber.
730 -[20109]Failed to read IMSI numoer.
731 -[22048]Failed to read IMSI number.
732 -[29842lRestart the module...
733 -)))
734 -
735 -Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
736 -
737 -
738 -== 5.4 Why sometime the AT Command is slow in reponse? ==
739 -
740 -
741 -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.
742 -
743 -[[image:image-20240226111928-1.png]]
744 -
745 -
746 -
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content
image-20240129170024-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -39.5 KB
Content

Applications

Navigation

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