Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 123.1
edited by Bei Jinggeng
on 2024/01/29 17:50
Change comment: There is no comment for this version
To version 132.1
edited by Edwin Chen
on 2024/02/07 00:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Edwin
Content
... ... @@ -44,14 +44,18 @@
44 44  == 2.2 Speed Up Network Attach time ==
45 45  
46 46  
47 -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.
47 +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.
48 48  
49 49  (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
50 50  
51 51  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
52 52  
53 -(% style="color:#037691" %)**AT+QBAND=2,8,20 **(%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
53 +(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
54 54  
55 +(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
56 +(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
57 +(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
58 +(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
55 55  
56 56  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
57 57  
... ... @@ -302,7 +302,7 @@
302 302  
303 303  === 3.4.2 For Device already registered in DataCake before shipped ===
304 304  
305 -**Scan QR Code to get the device info.**
309 +==== 3.4.2.1 Scan QR Code to get the device info ====
306 306  
307 307  Users can use their phones or computers to scan QR codes to obtain device data information.
308 308  
... ... @@ -311,6 +311,12 @@
311 311  [[image:image-20230808170548-9.png]]
312 312  
313 313  
318 +==== 3.4.2.2 Claim Device to User Account ====
319 +
320 +By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
321 +
322 +
323 +
314 314  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
315 315  
316 316  **Step1:Add a device**
... ... @@ -327,7 +327,7 @@
327 327  
328 328  **Step4:Fill in the device ID of your NB device**
329 329  
330 -[[image:image-20240129171029-4.png||height="380" width="648"]]
340 +[[image:image-20240202111546-1.png||height="378" width="651"]]
331 331  
332 332  **Step5:Please select your device plan according to your needs and complete the creation of the device**
333 333  
... ... @@ -335,6 +335,8 @@
335 335  
336 336  **Step6:Please add the decoder at the payload decoder of the device configuration.**
337 337  
348 +**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]]
349 +
338 338  [[image:image-20240129172056-7.png||height="457" width="816"]]
339 339  
340 340  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -609,3 +609,33 @@
609 609  (% style="color:blue" %)**See result in TCP Server:**
610 610  
611 611  [[image:image-20230807233631-2.png]]
624 +
625 +
626 += 4. Trouble Shooting: =
627 +
628 +== 4.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
629 +
630 +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.
631 +
632 +If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
633 +
634 +[[image:image-20240207002003-1.png]]
635 +
636 +
637 +If fail to attach network, it will shows signal 99. as below:
638 +
639 +[[image:image-20240207002129-2.png]]
640 +
641 +
642 +(% class="lead" %)
643 +When see this issue, below are the checklist:
644 +
645 +* 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.
646 +* 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]].
647 +* 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]].
648 +* Check if the device is attached to Carrier network but reject. (need to check with operator).
649 +* Check if the antenna is connected firmly.
650 +
651 +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.
652 +
653 +
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