Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 146.1 >
edited by Edwin Chen
on 2024/03/03 16:50
To version < 100.1 >
edited by Edwin Chen
on 2023/08/12 22:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
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,27 +45,7 @@
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 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 -(% 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=11,8,20,28,2,4,12,13,66,85,5,4**
57 -
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
62 -
63 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64 -
65 -
66 -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/]]**
67 -
68 -
69 69  = 3. Configure to connect to different servers =
70 70  
71 71  == 3.1 General UDP Connection ==
... ... @@ -79,7 +79,7 @@
79 79  
80 80  We can use PC tool to simulate UDP connection to make sure server works ok.
81 81  
82 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
52 +[[image:image-20230802112413-1.png]]
83 83  
84 84  
85 85  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -93,6 +93,8 @@
93 93  
94 94  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
95 95  
66 +* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
67 +
96 96  [[image:image-20230802112413-2.png]]
97 97  
98 98  
... ... @@ -127,7 +127,7 @@
127 127  
128 128  [[image:image-20230802112413-4.png]]
129 129  
130 -[[image:image-20230802112413-5.png||height="530" width="987"]]
102 +[[image:image-20230802112413-5.png]]
131 131  
132 132  (% 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.**
133 133  
... ... @@ -139,7 +139,7 @@
139 139  
140 140  [[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.
141 141  
142 -[[image:image-20230802112413-6.png||height="336" width="925"]]
114 +[[image:image-20230802112413-6.png]]
143 143  
144 144  [[image:image-20230802112413-7.png]]
145 145  
... ... @@ -163,6 +163,7 @@
163 163  
164 164  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
165 165  
138 +
166 166  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
167 167  
168 168  
... ... @@ -182,7 +182,7 @@
182 182  
183 183  (% style="color:blue" %)**Result: **
184 184  
185 -[[image:image-20230802112413-11.png||height="539" width="901"]]
158 +[[image:image-20230802112413-11.png]]
186 186  
187 187  
188 188  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -204,10 +204,11 @@
204 204  
205 205  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
206 206  
180 +
207 207  ==== 3.3.3.2 Uplink Examples ====
208 208  
209 209  
210 -[[image:image-20230816201942-1.png]]
184 +For S31-NB
211 211  
212 212  For SE01-NB
213 213  
... ... @@ -238,9 +238,9 @@
238 238  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.
239 239  
240 240  
241 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
215 +[[image:image-20230802112413-12.png]]
242 242  
243 -[[image:image-20230802112413-13.png||height="331" width="978"]]
217 +[[image:image-20230802112413-13.png]]
244 244  
245 245  
246 246  Below is the NB-IoT Product Table show the mapping.
... ... @@ -265,6 +265,7 @@
265 265  |(% 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" %)
266 266  |(% 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" %)
267 267  
242 +
268 268  == 3.4 [[Datacake>>https://datacake.co/]] ==
269 269  
270 270  
... ... @@ -273,43 +273,40 @@
273 273  
274 274  
275 275  (% class="wikigeneratedid" %)
276 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
251 +As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
277 277  
278 -* (% 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.
253 +* **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.
254 +* **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.
279 279  
280 -* (% 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.
281 281  
282 -=== 3.4.1 For device Already has template ===
257 +=== 3.4.1 Create device ===
283 283  
284 -==== 3.4.1.1 Create Device ====
285 285  
286 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
260 +**Add Device** in DataCake.
287 287  
288 -[[image:image-20230808162301-1.png||height="453" width="952"]]
262 +[[image:image-20230808162301-1.png]]
289 289  
290 290  
291 -[[image:image-20230808162342-2.png||height="541" width="952"]]
265 +[[image:image-20230808162342-2.png]]
292 292  
293 293  
294 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
268 +**Choose the correct model** from template.
295 295  
296 296  [[image:image-20230808162421-3.png]]
297 297  
298 298  
299 -(% 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.
273 +**Fill Device ID**. The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
300 300  
301 -[[image:image-20230808163612-7.png||height="549" width="952"]]
275 +[[image:image-20230808163612-7.png]]
302 302  
303 303  [[image:image-20230808163035-5.png]]
304 304  
305 -[[image:image-20230808163049-6.png||height="544" width="926"]]
279 +[[image:image-20230808163049-6.png]]
306 306  
307 307  
308 -=== 3.4.2 For Device already registered in DataCake before shipped ===
282 +=== 3.4.2 Scan QR code to obtain data ===
309 309  
310 -==== 3.4.2.1 Scan QR Code to get the device info ====
311 311  
312 -
313 313  Users can use their phones or computers to scan QR codes to obtain device data information.
314 314  
315 315  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -317,69 +317,9 @@
317 317  [[image:image-20230808170548-9.png]]
318 318  
319 319  
320 -==== 3.4.2.2 Claim Device to User Account ====
292 +=== 3.4.2 AT command for connecting to DataCake ===
321 321  
322 322  
323 -By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
324 -
325 -
326 -=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
327 -
328 -
329 -**Step1: Add a device**
330 -
331 -[[image:image-20240129170024-1.png||height="330" width="900"]]
332 -
333 -
334 -**Step2: Choose your device type,please select dragino NB-IOT device**
335 -
336 -[[image:image-20240129170216-2.png||height="534" width="643"]]
337 -
338 -
339 -**Step3: Choose to create a new device**
340 -
341 -[[image:image-20240129170539-3.png||height="459" width="646"]]
342 -
343 -
344 -**Step4: Fill in the device ID of your NB device**
345 -
346 -[[image:image-20240202111546-1.png||height="378" width="651"]]
347 -
348 -
349 -**Step5: Please select your device plan according to your needs and complete the creation of the device**
350 -
351 -[[image:image-20240129171236-6.png||height="450" width="648"]]
352 -
353 -
354 -**Step6: Please add the decoder at the payload decoder of the device configuration.**
355 -
356 -**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]]
357 -
358 -[[image:image-20240129172056-7.png||height="457" width="816"]]
359 -
360 -[[image:image-20240129173116-9.png||height="499" width="814"]]
361 -
362 -
363 -**Step7: Add the output of the decoder as a field**
364 -
365 -[[image:image-20240129173541-10.png||height="592" width="968"]]
366 -
367 -
368 -**Step8: Customize the dashboard and use fields as parameters of the dashboard**
369 -
370 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
371 -
372 -[[image:image-20240129174657-12.png||height="538" width="916"]]
373 -
374 -[[image:image-20240129174840-13.png||height="536" width="750"]]
375 -
376 -
377 -=== 3.4.4 For device have not configured to connect to DataCake ===
378 -
379 -
380 -(% class="lead" %)
381 -Use AT command for connecting to DataCake
382 -
383 383  (% style="color:blue" %)**AT+PRO=2,0**
384 384  
385 385  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -408,7 +408,7 @@
408 408  
409 409  Please select the NB95S31B template.
410 410  
411 -[[image:image-20230809173310-5.png||height="558" width="926"]]
323 +[[image:image-20230809173310-5.png]]
412 412  
413 413  [[image:image-20230809173438-6.png]]
414 414  
... ... @@ -417,7 +417,7 @@
417 417  
418 418  Successfully imported template.
419 419  
420 -[[image:image-20230809173835-8.png||height="515" width="860"]]
332 +[[image:image-20230809173835-8.png]]
421 421  
422 422  
423 423  Users can set UDP port.
... ... @@ -432,19 +432,16 @@
432 432  
433 433  [[image:image-20230810083934-1.png]]
434 434  
435 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
347 +[[image:image-20230810084048-2.png]]
436 436  
437 -
438 438  === 3.5.3 Configure NB-IoT Sensors ===
439 439  
440 440  
441 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
442 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
443 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
444 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
445 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
446 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
352 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
447 447  
354 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
355 +
356 +
448 448  == 3.6 ThingsBoard.Cloud (via MQTT) ==
449 449  
450 450  === 3.6.1 Configure ThingsBoard ===
... ... @@ -454,7 +454,7 @@
454 454  
455 455  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
456 456  
457 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
366 +[[image:image-20230802112413-32.png]]
458 458  
459 459  
460 460  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -466,7 +466,7 @@
466 466  
467 467  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.
468 468  
469 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
378 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
470 470  
471 471  
472 472  (% style="color:blue" %)**Downlink Converter**
... ... @@ -473,7 +473,7 @@
473 473  
474 474  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
475 475  
476 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
385 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
477 477  
478 478  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
479 479  
... ... @@ -483,23 +483,23 @@
483 483  
484 484  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**;
485 485  
486 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
395 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
487 487  
488 488  
489 489  * The next steps is to add the recently created uplink and downlink converters;
490 490  
491 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
400 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
492 492  
493 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
402 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
494 494  
495 495  
496 496  (% style="color:blue" %)**Add a topic filter:**
497 497  
498 -Consistent with the theme of the node setting.
407 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
499 499  
500 500  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
501 501  
502 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
411 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
503 503  
504 504  
505 505  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -507,7 +507,7 @@
507 507  
508 508  [[image:image-20230802112413-39.png]]
509 509  
510 -[[image:image-20230802112413-40.png||height="525" width="980"]]
419 +[[image:image-20230802112413-40.png]]
511 511  
512 512  
513 513  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -529,11 +529,11 @@
529 529  
530 530  Test Uplink by click the button for 1 second
531 531  
532 -[[image:image-20230802112413-41.png||height="496" width="828"]]
441 +[[image:image-20230802112413-41.png]]
533 533  
534 534  [[image:image-20230802112413-42.png]]
535 535  
536 -[[image:image-20230802112413-43.png||height="407" width="825"]]
445 +[[image:image-20230802112413-43.png]]
537 537  
538 538  
539 539  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -589,6 +589,7 @@
589 589  
590 590  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
591 591  
501 +
592 592  === 3.7.2 Simulate with MQTT.fx ===
593 593  
594 594  
... ... @@ -595,12 +595,12 @@
595 595  [[image:image-20230802112413-52.png]]
596 596  
597 597  
598 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
508 +[[image:image-20230808105300-2.png]]
599 599  
600 600  
601 601  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
602 602  
603 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
513 +[[image:image-20230808105217-1.png]]
604 604  
605 605  [[image:image-20230808105329-3.png]]
606 606  
... ... @@ -608,7 +608,7 @@
608 608  === 3.7.3 tago data ===
609 609  
610 610  
611 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
521 +[[image:image-20230802112413-50.png]]
612 612  
613 613  [[image:image-20230802112413-51.png||height="184" width="696"]]
614 614  
... ... @@ -632,113 +632,3 @@
632 632  (% style="color:blue" %)**See result in TCP Server:**
633 633  
634 634  [[image:image-20230807233631-2.png]]
635 -
636 -
637 -= 4. FAQ =
638 -
639 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
640 -
641 -
642 -The NB series has the feature for Multi Sampling and one uplink. See one of them
643 -
644 -[[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]]
645 -
646 -User can use this feature for below purpose:
647 -
648 -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.
649 -1. Give more sampling data points.
650 -1. Increase reliable in transmission. For example. If user set
651 -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)
652 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
653 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
654 -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.
655 -
656 -
657 -== 4.2 Why the uplink JSON format is not standard? ==
658 -
659 -
660 -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.
661 -
662 -[[image:image-20240229233154-1.png]]
663 -
664 -
665 -= 5. Trouble Shooting: =
666 -
667 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
668 -
669 -
670 -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.
671 -
672 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
673 -
674 -[[image:image-20240207002003-1.png]]
675 -
676 -
677 -If fail to attach network, it will shows signal 99. as below:
678 -
679 -[[image:image-20240207002129-2.png]]
680 -
681 -
682 -(% class="lead" %)
683 -When see this issue, below are the checklist:
684 -
685 -* 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.
686 -* 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]].
687 -* 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]].
688 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
689 -* Check if the antenna is connected firmly.
690 -
691 -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.
692 -
693 -
694 -== 5.2 Issue: "NBIOT did not respond" ==
695 -
696 -
697 -(% class="box errormessage" %)
698 -(((
699 -11:24:22.397 [44596]NBIOT did not respond.
700 -11:24:24.315 [46530]NBIOT did not respond.
701 -11:24:26.256 [48464]NBIOT did not respond.
702 -11:24:28.196 [50398]NBIOT did not respond.
703 -11:24:30.115 [52332]NBIOT did not respond.
704 -11:24:32.127 [54266]NBIOT did not respond.
705 -11:24:32.127 [54299]Restart the module...
706 -11:24:39.181 [61332]No response when shutting down
707 -)))
708 -
709 -This issue might due to initiate issue for NB-IoT module. In this case, please try:
710 -
711 -1) Open Enclosure
712 -
713 -2) Power off device by pull out the power on Jumper
714 -
715 -3) Power on device by connect back the power jumper.
716 -
717 -4) push reset button.
718 -
719 -[[image:image-20240208001740-1.png]]
720 -
721 -
722 -== 5.3 Issue: "Failed to readI MSI number" ==
723 -
724 -
725 -(% class="box errormessage" %)
726 -(((
727 -[18170]Failed to read IMSI:1umber.
728 -[20109]Failed to read IMSI numoer.
729 -[22048]Failed to read IMSI number.
730 -[29842lRestart the module...
731 -)))
732 -
733 -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"]].
734 -
735 -
736 -== 5.4 Why sometime the AT Command is slow in reponse? ==
737 -
738 -
739 -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.
740 -
741 -[[image:image-20240226111928-1.png]]
742 -
743 -
744 -
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