Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 104.1
edited by Edwin Chen
on 2023/10/02 18:30
Change comment: There is no comment for this version
To version 165.1
edited by Edwin Chen
on 2024/06/08 14:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,12 +18,17 @@
18 18  
19 19  == 2.1 General Configure to attach network ==
20 20  
21 +
21 21  To attache NB-IoT sensors to NB-IoT Network, You need to:
22 22  
23 23  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
24 -1. Insert the SIM card to Sensor
25 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
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
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>), example AT+APN=iot.1nce.net
26 26  
30 +[[image:image-20240208102804-1.png||height="286" width="696"]]
31 +
27 27  [[image:image-20230808205045-1.png||height="293" width="438"]]
28 28  
29 29  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -35,26 +35,33 @@
35 35  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
36 36  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
37 37  
38 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
39 -)))|(% style="width:135px" %)
43 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
44 +)))|(% style="width:135px" %)UK: Band20
40 40  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
41 41  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
42 42  
43 -(% class="wikigeneratedid" %)
44 -== ==
45 -
46 46  == 2.2 Speed Up Network Attach time ==
47 47  
48 -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. User can lock the band to specify band for its operator to make this faster.
49 49  
50 -**AT+QBAND?** ~/~/ Check what is the current used frequency band
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.
51 51  
52 -**AT+QBAND=1,4** ~/~/ Set to use 1 frequency band. Band4
53 +(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 +(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
55 +(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
56 +(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
53 53  
54 -**AT+QBAND=2,8,20** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
58 +(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
59 +(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
60 +(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
61 +(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
55 55  
63 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
56 56  
65 +By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
57 57  
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 +
58 58  = 3. Configure to connect to different servers =
59 59  
60 60  == 3.1 General UDP Connection ==
... ... @@ -68,7 +68,7 @@
68 68  
69 69  We can use PC tool to simulate UDP connection to make sure server works ok.
70 70  
71 -[[image:image-20230802112413-1.png]]
83 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
72 72  
73 73  
74 74  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -82,8 +82,6 @@
82 82  
83 83  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
84 84  
85 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
86 -
87 87  [[image:image-20230802112413-2.png]]
88 88  
89 89  
... ... @@ -197,6 +197,7 @@
197 197  
198 198  ==== 3.3.3.2 Uplink Examples ====
199 199  
210 +
200 200  [[image:image-20230816201942-1.png]]
201 201  
202 202  For SE01-NB
... ... @@ -269,15 +269,16 @@
269 269  
270 270  * (% 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.
271 271  
272 -=== 3.4.1 Create device ===
283 +=== 3.4.1 For device Already has template ===
273 273  
285 +==== 3.4.1.1 Create Device ====
274 274  
275 275  (% style="color:blue" %)**Add Device**(%%) in DataCake.
276 276  
277 -[[image:image-20230808162301-1.png||height="473" width="994"]]
289 +[[image:image-20230808162301-1.png||height="453" width="952"]]
278 278  
279 279  
280 -[[image:image-20230808162342-2.png]]
292 +[[image:image-20230808162342-2.png||height="541" width="952"]]
281 281  
282 282  
283 283  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -287,16 +287,18 @@
287 287  
288 288  (% 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.
289 289  
290 -[[image:image-20230808163612-7.png]]
302 +[[image:image-20230808163612-7.png||height="549" width="952"]]
291 291  
292 292  [[image:image-20230808163035-5.png]]
293 293  
294 -[[image:image-20230808163049-6.png]]
306 +[[image:image-20230808163049-6.png||height="544" width="926"]]
295 295  
296 296  
297 -=== 3.4.2 Scan QR code to obtain data ===
309 +=== 3.4.2 For Device already registered in DataCake before shipped ===
298 298  
311 +==== 3.4.2.1 Scan QR Code to get the device info ====
299 299  
313 +
300 300  Users can use their phones or computers to scan QR codes to obtain device data information.
301 301  
302 302  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -304,9 +304,69 @@
304 304  [[image:image-20230808170548-9.png]]
305 305  
306 306  
307 -=== 3.4.2 AT command for connecting to DataCake ===
321 +==== 3.4.2.2 Claim Device to User Account ====
308 308  
309 309  
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 +
310 310  (% style="color:blue" %)**AT+PRO=2,0**
311 311  
312 312  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -335,7 +335,7 @@
335 335  
336 336  Please select the NB95S31B template.
337 337  
338 -[[image:image-20230809173310-5.png]]
412 +[[image:image-20230809173310-5.png||height="558" width="926"]]
339 339  
340 340  [[image:image-20230809173438-6.png]]
341 341  
... ... @@ -344,7 +344,7 @@
344 344  
345 345  Successfully imported template.
346 346  
347 -[[image:image-20230809173835-8.png]]
421 +[[image:image-20230809173835-8.png||height="515" width="860"]]
348 348  
349 349  
350 350  Users can set UDP port.
... ... @@ -359,15 +359,19 @@
359 359  
360 360  [[image:image-20230810083934-1.png]]
361 361  
362 -[[image:image-20230810084048-2.png]]
436 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
363 363  
438 +
364 364  === 3.5.3 Configure NB-IoT Sensors ===
365 365  
366 366  
367 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
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”**
368 368  
369 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
370 -
371 371  == 3.6 ThingsBoard.Cloud (via MQTT) ==
372 372  
373 373  === 3.6.1 Configure ThingsBoard ===
... ... @@ -377,7 +377,7 @@
377 377  
378 378  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
379 379  
380 -[[image:image-20230802112413-32.png]]
458 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
381 381  
382 382  
383 383  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -389,7 +389,7 @@
389 389  
390 390  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.
391 391  
392 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
470 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
393 393  
394 394  
395 395  (% style="color:blue" %)**Downlink Converter**
... ... @@ -396,7 +396,7 @@
396 396  
397 397  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
398 398  
399 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
477 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
400 400  
401 401  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
402 402  
... ... @@ -406,23 +406,23 @@
406 406  
407 407  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**;
408 408  
409 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
487 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
410 410  
411 411  
412 412  * The next steps is to add the recently created uplink and downlink converters;
413 413  
414 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
492 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
415 415  
416 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
494 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
417 417  
418 418  
419 419  (% style="color:blue" %)**Add a topic filter:**
420 420  
421 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
499 +Consistent with the theme of the node setting.
422 422  
423 423  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
424 424  
425 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
503 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
426 426  
427 427  
428 428  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -430,7 +430,7 @@
430 430  
431 431  [[image:image-20230802112413-39.png]]
432 432  
433 -[[image:image-20230802112413-40.png]]
511 +[[image:image-20230802112413-40.png||height="525" width="980"]]
434 434  
435 435  
436 436  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -452,11 +452,11 @@
452 452  
453 453  Test Uplink by click the button for 1 second
454 454  
455 -[[image:image-20230802112413-41.png]]
533 +[[image:image-20230802112413-41.png||height="496" width="828"]]
456 456  
457 457  [[image:image-20230802112413-42.png]]
458 458  
459 -[[image:image-20230802112413-43.png]]
537 +[[image:image-20230802112413-43.png||height="407" width="825"]]
460 460  
461 461  
462 462  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -518,12 +518,12 @@
518 518  [[image:image-20230802112413-52.png]]
519 519  
520 520  
521 -[[image:image-20230808105300-2.png]]
599 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
522 522  
523 523  
524 524  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
525 525  
526 -[[image:image-20230808105217-1.png]]
604 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
527 527  
528 528  [[image:image-20230808105329-3.png]]
529 529  
... ... @@ -531,7 +531,7 @@
531 531  === 3.7.3 tago data ===
532 532  
533 533  
534 -[[image:image-20230802112413-50.png]]
612 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
535 535  
536 536  [[image:image-20230802112413-51.png||height="184" width="696"]]
537 537  
... ... @@ -555,3 +555,224 @@
555 555  (% style="color:blue" %)**See result in TCP Server:**
556 556  
557 557  [[image:image-20230807233631-2.png]]
636 +
637 +
638 +== 3.9 AWS Connection ==
639 +
640 +
641 +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]]
642 +
643 +
644 +
645 +
646 += 4. MQTT/UDP/TCP downlink =
647 +
648 +== 4.1 MQTT (via MQTT.fx) ==
649 +
650 +Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
651 +
652 +**1.** Configure node MQTT connection (via MQTT.fx):
653 +
654 +(% style="color:blue" %)**AT command:**
655 +
656 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
657 +
658 +* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
659 +
660 +* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
661 +
662 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
663 +
664 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
665 +
666 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
667 +
668 +(% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**
669 +
670 +[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
671 +
672 +
673 +**2. **When the node uplink packets, we can observe the data in MQTT.fx.
674 +
675 +[[image:image-20240418144337-1.png||height="709" width="802"]]
676 +
677 +**3. **The downlink command can be successfully sent only when the downlink port is open.
678 +
679 + The downlink port is opened for about 3 seconds after uplink packets are sent.
680 +
681 + Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
682 +
683 +[[image:image-20240418150435-3.png||height="582" width="659"]]
684 +
685 +[[image:image-20240418150932-4.png||height="492" width="1061"]]
686 +
687 +(% 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.**
688 +
689 +
690 +
691 +
692 +
693 +
694 +
695 += 5. FAQ =
696 +
697 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
698 +
699 +
700 +The NB series has the feature for Multi Sampling and one uplink. See one of them
701 +
702 +[[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]]
703 +
704 +User can use this feature for below purpose:
705 +
706 +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.
707 +1. Give more sampling data points.
708 +1. Increase reliable in transmission. For example. If user set
709 +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)
710 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
711 +1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
712 +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.
713 +
714 +== 5.2 Why the uplink JSON format is not standard? ==
715 +
716 +
717 +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.
718 +
719 +The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
720 +
721 +[[image:image-20240229233154-1.png]]
722 +
723 +
724 += 6. Trouble Shooting: =
725 +
726 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
727 +
728 +
729 +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.
730 +
731 +If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
732 +
733 +[[image:image-20240207002003-1.png]]
734 +
735 +
736 +If fail to attach network, it will shows signal 99. as below:
737 +
738 +[[image:image-20240207002129-2.png]]
739 +
740 +
741 +(% class="lead" %)
742 +When see this issue, below are the checklist:
743 +
744 +* 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.
745 +* 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]].
746 +* 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]].
747 +* Check if the device is attached to Carrier network but reject. (need to check with operator).
748 +* Check if the antenna is connected firmly.
749 +
750 +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.
751 +
752 +
753 +== 6.2 Issue: "NBIOT did not respond" ==
754 +
755 +
756 +(% class="box errormessage" %)
757 +(((
758 +11:24:22.397 [44596]NBIOT did not respond.
759 +11:24:24.315 [46530]NBIOT did not respond.
760 +11:24:26.256 [48464]NBIOT did not respond.
761 +11:24:28.196 [50398]NBIOT did not respond.
762 +11:24:30.115 [52332]NBIOT did not respond.
763 +11:24:32.127 [54266]NBIOT did not respond.
764 +11:24:32.127 [54299]Restart the module...
765 +11:24:39.181 [61332]No response when shutting down
766 +)))
767 +
768 +This issue might due to initiate issue for NB-IoT module. In this case, please try:
769 +
770 +1) Open Enclosure
771 +
772 +2) Power off device by pull out the power on Jumper
773 +
774 +3) Power on device by connect back the power jumper.
775 +
776 +4) push reset button.
777 +
778 +[[image:image-20240208001740-1.png]]
779 +
780 +
781 +== 6.3 Issue: "Failed to readI MSI number" ==
782 +
783 +
784 +(% class="box errormessage" %)
785 +(((
786 +[18170]Failed to read IMSI:1umber.
787 +[20109]Failed to read IMSI numoer.
788 +[22048]Failed to read IMSI number.
789 +[29842lRestart the module...
790 +)))
791 +
792 +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"]].
793 +
794 +
795 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
796 +
797 +
798 +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.
799 +
800 +[[image:image-20240226111928-1.png]]
801 +
802 +
803 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
804 +
805 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
806 +=== UDP: ===
807 +
808 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
809 +Its downlink command is the same as the AT command, but brackets are required.
810 +Example:
811 +
812 +{AT+TDC=300}
813 +
814 +
815 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
816 +=== MQTT: ===
817 +
818 +Json：
819 +
820 +The Json format in MQTT mode needs to be configured with all commands.
821 +If you have configurations that need to be changed, please change them in the template below.
822 +Template:
823 +
824 +{
825 +"AT+SERVADDR":"119.91.62.30,1882",
826 +"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
827 +"AT+UNAME":"usenamedragino",
828 +"AT+PWD":"passworddragino",
829 +"AT+PUBTOPIC":"123",
830 +"AT+SUBTOPIC":"321",
831 +"AT+TDC":"7200",
832 +"AT+INTMOD":"0",
833 +"AT+APN":"NULL",
834 +"AT+5VT":"0",
835 +"AT+PRO":"3,5",
836 +"AT+TR":"900",
837 +"AT+NOUD":"0",
838 +"AT+CSQTIME":"5",
839 +"AT+DNSTIMER":"0",
840 +"AT+TLSMOD":"0,0",
841 +"AT+MQOS":"0",
842 +"AT+TEMPALARM1":"0",
843 +"AT+TEMPALARM2":"10",
844 +"AT+TEMPALARM3":"0"
845 +}
846 +
847 +Hex：
848 +
849 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
850 +
851 +The supported commands are consistent with LoRaWAN's hex commands.
852 +Please refer to the following link to obtain the hex format:
853 +
854 +[[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/]]
855 +
856 +
image-20240129170024-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +39.5 KB
Content
image-20240417173549-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +70.3 KB
Content
image-20240417180145-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.7 KB
Content
image-20240418144337-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +103.4 KB
Content