<
From version < 132.1 >
edited by Edwin Chen
on 2024/02/07 00:29
To version < 124.1 >
edited by Bei Jinggeng
on 2024/02/02 11:15
>
Change comment: Uploaded new attachment "image-20240202111546-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Bei
Content
... ... @@ -44,18 +44,14 @@
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 and show Signal Strenght:99. 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. 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" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
53 +(% style="color:#037691" %)**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
59 59  
60 60  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
61 61  
... ... @@ -306,7 +306,7 @@
306 306  
307 307  === 3.4.2 For Device already registered in DataCake before shipped ===
308 308  
309 -==== 3.4.2.1 Scan QR Code to get the device info ====
305 +**Scan QR Code to get the device info.**
310 310  
311 311  Users can use their phones or computers to scan QR codes to obtain device data information.
312 312  
... ... @@ -315,12 +315,6 @@
315 315  [[image:image-20230808170548-9.png]]
316 316  
317 317  
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 -
324 324  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
325 325  
326 326  **Step1:Add a device**
... ... @@ -337,7 +337,7 @@
337 337  
338 338  **Step4:Fill in the device ID of your NB device**
339 339  
340 -[[image:image-20240202111546-1.png||height="378" width="651"]]
330 +[[image:image-20240129171029-4.png||height="380" width="648"]]
341 341  
342 342  **Step5:Please select your device plan according to your needs and complete the creation of the device**
343 343  
... ... @@ -345,8 +345,6 @@
345 345  
346 346  **Step6:Please add the decoder at the payload decoder of the device configuration.**
347 347  
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 -
350 350  [[image:image-20240129172056-7.png||height="457" width="816"]]
351 351  
352 352  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -621,33 +621,3 @@
621 621  (% style="color:blue" %)**See result in TCP Server:**
622 622  
623 623  [[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-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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0