Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 142.1
edited by Mengting Qiu
on 2024/02/26 11:28
Change comment: There is no comment for this version
To version 161.1
edited by Edwin Chen
on 2024/05/13 22:35
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
... ... @@ -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>)
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
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, US Virgin Islands
44 -)))|(% style="width:135px" %)
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
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,13 +48,12 @@
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 -
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=10,8,20,28,2,4,12,13,66,85,5**
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  
... ... @@ -627,10 +627,62 @@
627 627  [[image:image-20230807233631-2.png]]
628 628  
629 629  
630 -= 4. FAQ =
631 631  
632 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
633 633  
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 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
660 +
661 +(% 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.**
662 +
663 +[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
664 +
665 +
666 +**2. **When the node uplink packets, we can observe the data in MQTT.fx.
667 +
668 +[[image:image-20240418144337-1.png||height="709" width="802"]]
669 +
670 +**3. **The downlink command can be successfully sent only when the downlink port is open.
671 +
672 + The downlink port is opened for about 3 seconds after uplink packets are sent.
673 +
674 + 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.
675 +
676 +[[image:image-20240418150435-3.png||height="582" width="659"]]
677 +
678 +[[image:image-20240418150932-4.png||height="492" width="1061"]]
679 +
680 +(% 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.**
681 +
682 +
683 +
684 +
685 +
686 +
687 +
688 += 5. FAQ =
689 +
690 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
691 +
692 +
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]]
... ... @@ -643,12 +643,23 @@
643 643  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)
644 644  1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
645 645  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
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.
705 +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  
648 -= 5. Trouble Shooting: =
707 +== 5.2 Why the uplink JSON format is not standard? ==
649 649  
650 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
651 651  
710 +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.
711 +
712 +The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
713 +
714 +[[image:image-20240229233154-1.png]]
715 +
716 +
717 += 6. Trouble Shooting: =
718 +
719 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
720 +
721 +
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)
... ... @@ -673,8 +673,9 @@
673 673  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.
674 674  
675 675  
676 -== 5.2 Issue: "NBIOT did not respond" ==
746 +== 6.2 Issue: "NBIOT did not respond" ==
677 677  
748 +
678 678  (% class="box errormessage" %)
679 679  (((
680 680  11:24:22.397 [44596]NBIOT did not respond.
... ... @@ -700,8 +700,9 @@
700 700  [[image:image-20240208001740-1.png]]
701 701  
702 702  
703 -== 5.3 Issue: "Failed to readI MSI number" ==
774 +== 6.3 Issue: "Failed to readI MSI number" ==
704 704  
776 +
705 705  (% class="box errormessage" %)
706 706  (((
707 707  [18170]Failed to read IMSI:1umber.
... ... @@ -713,11 +713,9 @@
713 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"]].
714 714  
715 715  
716 -== 5.4 Why sometime the AT Command is slow in reponse? ==
788 +== 6.4 Why sometime the AT Command is slow in reponse? ==
717 717  
790 +
718 718  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.
719 719  
720 720  [[image:image-20240226111928-1.png]]
721 -
722 -
723 -
image-20240229233154-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +39.5 KB
Content
image-20240417173549-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +70.3 KB
Content
image-20240417180145-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.7 KB
Content
image-20240418144337-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +103.4 KB
Content