Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 139.1
edited by Edwin Chen
on 2024/02/08 10:36
Change comment: There is no comment for this version
To version 146.1
edited by Edwin Chen
on 2024/03/03 16:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -51,10 +51,9 @@
51 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 52  
53 53  (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 -
55 55  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 -
57 57  (% 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**
58 58  
59 59  (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
60 60  (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
... ... @@ -94,8 +94,6 @@
94 94  
95 95  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
96 96  
97 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
98 -
99 99  [[image:image-20230802112413-2.png]]
100 100  
101 101  
... ... @@ -312,6 +312,7 @@
312 312  
313 313  ==== 3.4.2.1 Scan QR Code to get the device info ====
314 314  
312 +
315 315  Users can use their phones or computers to scan QR codes to obtain device data information.
316 316  
317 317  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -321,34 +321,40 @@
321 321  
322 322  ==== 3.4.2.2 Claim Device to User Account ====
323 323  
322 +
324 324  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 325  
326 326  
327 -
328 328  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
329 329  
330 -**Step1:Add a device**
331 331  
329 +**Step1: Add a device**
330 +
332 332  [[image:image-20240129170024-1.png||height="330" width="900"]]
333 333  
334 -**Step2:Choose your device type,please select dragino NB-IOT device**
335 335  
334 +**Step2: Choose your device type,please select dragino NB-IOT device**
335 +
336 336  [[image:image-20240129170216-2.png||height="534" width="643"]]
337 337  
338 -**Step3:Choose to create a new device**
339 339  
339 +**Step3: Choose to create a new device**
340 +
340 340  [[image:image-20240129170539-3.png||height="459" width="646"]]
341 341  
342 -**Step4:Fill in the device ID of your NB device**
343 343  
344 +**Step4: Fill in the device ID of your NB device**
345 +
344 344  [[image:image-20240202111546-1.png||height="378" width="651"]]
345 345  
346 -**Step5:Please select your device plan according to your needs and complete the creation of the device**
347 347  
349 +**Step5: Please select your device plan according to your needs and complete the creation of the device**
350 +
348 348  [[image:image-20240129171236-6.png||height="450" width="648"]]
349 349  
350 -**Step6:Please add the decoder at the payload decoder of the device configuration.**
351 351  
354 +**Step6: Please add the decoder at the payload decoder of the device configuration.**
355 +
352 352  **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]]
353 353  
354 354  [[image:image-20240129172056-7.png||height="457" width="816"]]
... ... @@ -355,12 +355,14 @@
355 355  
356 356  [[image:image-20240129173116-9.png||height="499" width="814"]]
357 357  
358 -**Step6:Add the output of the decoder as a field**
359 359  
363 +**Step7: Add the output of the decoder as a field**
364 +
360 360  [[image:image-20240129173541-10.png||height="592" width="968"]]
361 361  
362 -**Step7:Customize the dashboard and use fields as parameters of the dashboard**
363 363  
368 +**Step8: Customize the dashboard and use fields as parameters of the dashboard**
369 +
364 364  [[image:image-20240129174518-11.png||height="147" width="1042"]]
365 365  
366 366  [[image:image-20240129174657-12.png||height="538" width="916"]]
... ... @@ -370,6 +370,7 @@
370 370  
371 371  === 3.4.4 For device have not configured to connect to DataCake ===
372 372  
379 +
373 373  (% class="lead" %)
374 374  Use AT command for connecting to DataCake
375 375  
... ... @@ -631,6 +631,7 @@
631 631  
632 632  == 4.1 What is the usage of Multi Sampling and One Uplink? ==
633 633  
641 +
634 634  The NB series has the feature for Multi Sampling and one uplink. See one of them
635 635  
636 636  [[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,10 +645,20 @@
645 645  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
646 646  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.
647 647  
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 +
648 648  = 5. Trouble Shooting: =
649 649  
650 650  == 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
651 651  
669 +
652 652  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.
653 653  
654 654  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -675,6 +675,7 @@
675 675  
676 676  == 5.2 Issue: "NBIOT did not respond" ==
677 677  
696 +
678 678  (% class="box errormessage" %)
679 679  (((
680 680  11:24:22.397 [44596]NBIOT did not respond.
... ... @@ -702,6 +702,7 @@
702 702  
703 703  == 5.3 Issue: "Failed to readI MSI number" ==
704 704  
724 +
705 705  (% class="box errormessage" %)
706 706  (((
707 707  [18170]Failed to read IMSI:1umber.
... ... @@ -710,4 +710,15 @@
710 710  [29842lRestart the module...
711 711  )))
712 712  
713 -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"]]
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-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