Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 165.1
edited by Edwin Chen
on 2024/06/08 14:45
Change comment: There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2024/02/29 23:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -25,7 +25,7 @@
25 25  1. Power Off End Node ( See below for the power off/on position)
26 26  1. Insert the SIM card to Sensor. ( See below for direction)
27 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
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 30  [[image:image-20240208102804-1.png||height="286" width="696"]]
31 31  
... ... @@ -40,8 +40,8 @@
40 40  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
41 41  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
42 42  
43 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
44 -)))|(% style="width:135px" %)UK: Band20
43 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
44 +)))|(% style="width:135px" %)
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,12 +48,13 @@
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.
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 +
54 54  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 +
55 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 58  (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
59 59  (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
... ... @@ -62,7 +62,6 @@
62 62  
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 -By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
66 66  
67 67  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/]]**
68 68  
... ... @@ -310,7 +310,6 @@
310 310  
311 311  ==== 3.4.2.1 Scan QR Code to get the device info ====
312 312  
313 -
314 314  Users can use their phones or computers to scan QR codes to obtain device data information.
315 315  
316 316  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -320,40 +320,34 @@
320 320  
321 321  ==== 3.4.2.2 Claim Device to User Account ====
322 322  
323 -
324 324  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 325  
326 326  
325 +
327 327  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
328 328  
328 +**Step1:Add a device**
329 329  
330 -**Step1: Add a device**
331 -
332 332  [[image:image-20240129170024-1.png||height="330" width="900"]]
333 333  
332 +**Step2:Choose your device type,please select dragino NB-IOT device**
334 334  
335 -**Step2: Choose your device type,please select dragino NB-IOT device**
336 -
337 337  [[image:image-20240129170216-2.png||height="534" width="643"]]
338 338  
336 +**Step3:Choose to create a new device**
339 339  
340 -**Step3: Choose to create a new device**
341 -
342 342  [[image:image-20240129170539-3.png||height="459" width="646"]]
343 343  
340 +**Step4:Fill in the device ID of your NB device**
344 344  
345 -**Step4: Fill in the device ID of your NB device**
346 -
347 347  [[image:image-20240202111546-1.png||height="378" width="651"]]
348 348  
344 +**Step5:Please select your device plan according to your needs and complete the creation of the device**
349 349  
350 -**Step5: Please select your device plan according to your needs and complete the creation of the device**
351 -
352 352  [[image:image-20240129171236-6.png||height="450" width="648"]]
353 353  
348 +**Step6:Please add the decoder at the payload decoder of the device configuration.**
354 354  
355 -**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 -
357 357  **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]]
358 358  
359 359  [[image:image-20240129172056-7.png||height="457" width="816"]]
... ... @@ -360,14 +360,12 @@
360 360  
361 361  [[image:image-20240129173116-9.png||height="499" width="814"]]
362 362  
356 +**Step6:Add the output of the decoder as a field**
363 363  
364 -**Step7: Add the output of the decoder as a field**
365 -
366 366  [[image:image-20240129173541-10.png||height="592" width="968"]]
367 367  
360 +**Step7:Customize the dashboard and use fields as parameters of the dashboard**
368 368  
369 -**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 -
371 371  [[image:image-20240129174518-11.png||height="147" width="1042"]]
372 372  
373 373  [[image:image-20240129174657-12.png||height="538" width="916"]]
... ... @@ -377,7 +377,6 @@
377 377  
378 378  === 3.4.4 For device have not configured to connect to DataCake ===
379 379  
380 -
381 381  (% class="lead" %)
382 382  Use AT command for connecting to DataCake
383 383  
... ... @@ -635,68 +635,10 @@
635 635  [[image:image-20230807233631-2.png]]
636 636  
637 637  
638 -== 3.9 AWS Connection ==
628 += 4. FAQ =
639 639  
630 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
640 640  
641 -Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
642 -
643 -
644 -
645 -
646 -= 4. MQTT/UDP/TCP downlink =
647 -
648 -== 4.1 MQTT (via MQTT.fx) ==
649 -
650 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
651 -
652 -**1.** Configure node MQTT connection (via MQTT.fx):
653 -
654 -(% style="color:blue" %)**AT command:**
655 -
656 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
657 -
658 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
659 -
660 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
661 -
662 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
663 -
664 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
665 -
666 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
667 -
668 -(% 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.**
669 -
670 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
671 -
672 -
673 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
674 -
675 -[[image:image-20240418144337-1.png||height="709" width="802"]]
676 -
677 -**3. **The downlink command can be successfully sent only when the downlink port is open.
678 -
679 - The downlink port is opened for about 3 seconds after uplink packets are sent.
680 -
681 - Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
682 -
683 -[[image:image-20240418150435-3.png||height="582" width="659"]]
684 -
685 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
686 -
687 -(% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
688 -
689 -
690 -
691 -
692 -
693 -
694 -
695 -= 5. FAQ =
696 -
697 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
698 -
699 -
700 700  The NB series has the feature for Multi Sampling and one uplink. See one of them
701 701  
702 702  [[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]]
... ... @@ -709,22 +709,20 @@
709 709  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)
710 710  1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
711 711  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
712 -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.
644 +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.
713 713  
714 -== 5.2 Why the uplink JSON format is not standard? ==
715 715  
647 +== 4.2 Why the uplink JSON format is not standard? ==
716 716  
717 717  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.
718 718  
719 -The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
720 -
721 721  [[image:image-20240229233154-1.png]]
722 722  
723 723  
724 -= 6. Trouble Shooting: =
725 725  
726 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
655 += 5. Trouble Shooting: =
727 727  
657 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
728 728  
729 729  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.
730 730  
... ... @@ -750,9 +750,8 @@
750 750  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.
751 751  
752 752  
753 -== 6.2 Issue: "NBIOT did not respond" ==
683 +== 5.2 Issue: "NBIOT did not respond" ==
754 754  
755 -
756 756  (% class="box errormessage" %)
757 757  (((
758 758  11:24:22.397 [44596]NBIOT did not respond.
... ... @@ -778,9 +778,8 @@
778 778  [[image:image-20240208001740-1.png]]
779 779  
780 780  
781 -== 6.3 Issue: "Failed to readI MSI number" ==
710 +== 5.3 Issue: "Failed to readI MSI number" ==
782 782  
783 -
784 784  (% class="box errormessage" %)
785 785  (((
786 786  [18170]Failed to read IMSI:1umber.
... ... @@ -792,65 +792,11 @@
792 792  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"]].
793 793  
794 794  
795 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
723 +== 5.4 Why sometime the AT Command is slow in reponse? ==
796 796  
797 -
798 798  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.
799 799  
800 800  [[image:image-20240226111928-1.png]]
801 801  
802 802  
803 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
804 -
805 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
806 -=== UDP: ===
807 -
808 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
809 -Its downlink command is the same as the AT command, but brackets are required.
810 -Example:
811 -
812 -{AT+TDC=300}
813 -
814 -
815 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
816 -=== MQTT: ===
817 -
818 -Json：
819 -
820 -The Json format in MQTT mode needs to be configured with all commands.
821 -If you have configurations that need to be changed, please change them in the template below.
822 -Template:
823 -
824 -{
825 -"AT+SERVADDR":"119.91.62.30,1882",
826 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
827 -"AT+UNAME":"usenamedragino",
828 -"AT+PWD":"passworddragino",
829 -"AT+PUBTOPIC":"123",
830 -"AT+SUBTOPIC":"321",
831 -"AT+TDC":"7200",
832 -"AT+INTMOD":"0",
833 -"AT+APN":"NULL",
834 -"AT+5VT":"0",
835 -"AT+PRO":"3,5",
836 -"AT+TR":"900",
837 -"AT+NOUD":"0",
838 -"AT+CSQTIME":"5",
839 -"AT+DNSTIMER":"0",
840 -"AT+TLSMOD":"0,0",
841 -"AT+MQOS":"0",
842 -"AT+TEMPALARM1":"0",
843 -"AT+TEMPALARM2":"10",
844 -"AT+TEMPALARM3":"0"
845 -}
846 -
847 -Hex：
848 -
849 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
850 -
851 -The supported commands are consistent with LoRaWAN's hex commands.
852 -Please refer to the following link to obtain the hex format:
853 -
854 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
855 -
856 856  
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
image-20240418144337-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -103.4 KB
Content