Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 154.1 >
edited by Mengting Qiu
on 2024/04/17 18:08
To version < 107.1 >
edited by Edwin Chen
on 2023/12/30 17:09
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Edwin
Content
... ... @@ -22,13 +22,9 @@
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
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
25 +1. Insert the SIM card to Sensor
26 +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 .
... ... @@ -48,18 +48,15 @@
48 48  == 2.2 Speed Up Network Attach time ==
49 49  
50 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.
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.
52 52  
53 53  (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
50 +
54 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**
57 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
53 +(% style="color:#037691" %)**AT+QBAND=2,8,20 **(%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
62 62  
55 +
63 63  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64 64  
65 65  
... ... @@ -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  
89 +* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
90 +
96 96  [[image:image-20230802112413-2.png]]
97 97  
98 98  
... ... @@ -279,9 +279,8 @@
279 279  
280 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 ===
277 +=== 3.4.1 Create device ===
283 283  
284 -==== 3.4.1.1 Create Device ====
285 285  
286 286  (% style="color:blue" %)**Add Device**(%%) in DataCake.
287 287  
... ... @@ -305,11 +305,9 @@
305 305  [[image:image-20230808163049-6.png||height="544" width="926"]]
306 306  
307 307  
308 -=== 3.4.2 For Device already registered in DataCake before shipped ===
302 +=== 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 ====
312 +=== 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**
... ... @@ -495,7 +495,7 @@
495 495  
496 496  (% style="color:blue" %)**Add a topic filter:**
497 497  
498 -Consistent with the theme of the node setting.
430 +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  
... ... @@ -632,147 +632,3 @@
632 632  (% style="color:blue" %)**See result in TCP Server:**
633 633  
634 634  [[image:image-20230807233631-2.png]]
635 -
636 -
637 -
638 -
639 -= 4. MQTT/UDP/TCP downlink =
640 -
641 -== 4.1 MQTT (via MQTT.fx) ==
642 -
643 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
644 -
645 -**1.** **Configure node MQTT connection (via MQTT.fx):**
646 -
647 -(% style="color:blue" %)**AT command:**
648 -
649 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
650 -
651 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
652 -
653 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
654 -
655 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
656 -
657 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
658 -
659 -
660 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
661 -
662 -(% 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.**
663 -
664 -[[image:image-20240417180145-2.png||height="545" width="737"]]
665 -
666 -[[image:image-20240417180737-3.png||height="544" width="738"]]
667 -
668 -
669 -
670 -
671 -
672 -
673 -= 5. FAQ =
674 -
675 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
676 -
677 -
678 -The NB series has the feature for Multi Sampling and one uplink. See one of them
679 -
680 -[[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]]
681 -
682 -User can use this feature for below purpose:
683 -
684 -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.
685 -1. Give more sampling data points.
686 -1. Increase reliable in transmission. For example. If user set
687 -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)
688 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
689 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
690 -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.
691 -
692 -== 5.2 Why the uplink JSON format is not standard? ==
693 -
694 -
695 -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.
696 -
697 -The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
698 -
699 -[[image:image-20240229233154-1.png]]
700 -
701 -
702 -= 6. Trouble Shooting: =
703 -
704 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
705 -
706 -
707 -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.
708 -
709 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
710 -
711 -[[image:image-20240207002003-1.png]]
712 -
713 -
714 -If fail to attach network, it will shows signal 99. as below:
715 -
716 -[[image:image-20240207002129-2.png]]
717 -
718 -
719 -(% class="lead" %)
720 -When see this issue, below are the checklist:
721 -
722 -* 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.
723 -* 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]].
724 -* 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]].
725 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
726 -* Check if the antenna is connected firmly.
727 -
728 -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.
729 -
730 -
731 -== 6.2 Issue: "NBIOT did not respond" ==
732 -
733 -
734 -(% class="box errormessage" %)
735 -(((
736 -11:24:22.397 [44596]NBIOT did not respond.
737 -11:24:24.315 [46530]NBIOT did not respond.
738 -11:24:26.256 [48464]NBIOT did not respond.
739 -11:24:28.196 [50398]NBIOT did not respond.
740 -11:24:30.115 [52332]NBIOT did not respond.
741 -11:24:32.127 [54266]NBIOT did not respond.
742 -11:24:32.127 [54299]Restart the module...
743 -11:24:39.181 [61332]No response when shutting down
744 -)))
745 -
746 -This issue might due to initiate issue for NB-IoT module. In this case, please try:
747 -
748 -1) Open Enclosure
749 -
750 -2) Power off device by pull out the power on Jumper
751 -
752 -3) Power on device by connect back the power jumper.
753 -
754 -4) push reset button.
755 -
756 -[[image:image-20240208001740-1.png]]
757 -
758 -
759 -== 6.3 Issue: "Failed to readI MSI number" ==
760 -
761 -
762 -(% class="box errormessage" %)
763 -(((
764 -[18170]Failed to read IMSI:1umber.
765 -[20109]Failed to read IMSI numoer.
766 -[22048]Failed to read IMSI number.
767 -[29842lRestart the module...
768 -)))
769 -
770 -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"]].
771 -
772 -
773 -== 6.4 Why sometime the AT Command is slow in reponse? ==
774 -
775 -
776 -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.
777 -
778 -[[image:image-20240226111928-1.png]]
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
image-20240417173549-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -70.3 KB
Content
image-20240417180145-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -59.7 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0