Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 145.2
edited by Xiaoling
on 2024/03/01 10:15
Change comment: There is no comment for this version
To version 157.1
edited by Mengting Qiu
on 2024/04/18 14:47
Change comment: Uploaded new attachment "image-20240418144714-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
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  
... ... @@ -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
... ... @@ -635,11 +635,46 @@
635 635  [[image:image-20230807233631-2.png]]
636 636  
637 637  
638 -= 4. FAQ =
639 639  
640 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
641 641  
639 += 4. MQTT/UDP/TCP downlink =
642 642  
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="545" width="737"]]
664 +
665 +[[image:image-20240417180737-3.png||height="544" width="738"]]
666 +
667 +
668 +
669 +
670 +
671 +
672 += 5. FAQ =
673 +
674 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
675 +
676 +
643 643  The NB series has the feature for Multi Sampling and one uplink. See one of them
644 644  
645 645  [[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]]
... ... @@ -652,21 +652,21 @@
652 652  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)
653 653  1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
654 654  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
655 -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.
689 +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.
656 656  
691 +== 5.2 Why the uplink JSON format is not standard? ==
657 657  
658 658  
659 -== 4.2 Why the uplink JSON format is not standard? ==
660 -
661 -
662 662  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.
663 663  
696 +The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
697 +
664 664  [[image:image-20240229233154-1.png]]
665 665  
666 666  
667 -= 5. Trouble Shooting: =
701 += 6. Trouble Shooting: =
668 668  
669 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
703 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
670 670  
671 671  
672 672  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.
... ... @@ -693,7 +693,7 @@
693 693  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.
694 694  
695 695  
696 -== 5.2 Issue: "NBIOT did not respond" ==
730 +== 6.2 Issue: "NBIOT did not respond" ==
697 697  
698 698  
699 699  (% class="box errormessage" %)
... ... @@ -721,7 +721,7 @@
721 721  [[image:image-20240208001740-1.png]]
722 722  
723 723  
724 -== 5.3 Issue: "Failed to readI MSI number" ==
758 +== 6.3 Issue: "Failed to readI MSI number" ==
725 725  
726 726  
727 727  (% class="box errormessage" %)
... ... @@ -735,12 +735,9 @@
735 735  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"]].
736 736  
737 737  
738 -== 5.4 Why sometime the AT Command is slow in reponse? ==
772 +== 6.4 Why sometime the AT Command is slow in reponse? ==
739 739  
740 740  
741 741  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.
742 742  
743 743  [[image:image-20240226111928-1.png]]
744 -
745 -
746 -
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