Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 156.1
edited by Mengting Qiu
on 2024/04/18 14:43
Change comment: Uploaded new attachment "image-20240418144337-1.png", version {1}
To version 146.1
edited by Edwin Chen
on 2024/03/03 16:50
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>), 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  
... ... @@ -48,12 +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 54  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
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**
56 +(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=11,8,20,28,2,4,12,13,66,85,5,4**
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
... ... @@ -634,46 +634,11 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
637 += 4. FAQ =
637 637  
639 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
638 638  
639 -= 4. MQTT/UDP/TCP downlink =
640 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="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 -
677 677  The NB series has the feature for Multi Sampling and one uplink. See one of them
678 678  
679 679  [[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]]
... ... @@ -686,21 +686,20 @@
686 686  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)
687 687  1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
688 688  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
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.
654 +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.
690 690  
691 -== 5.2 Why the uplink JSON format is not standard? ==
692 692  
657 +== 4.2 Why the uplink JSON format is not standard? ==
693 693  
659 +
694 694  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.
695 695  
696 -The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
697 -
698 698  [[image:image-20240229233154-1.png]]
699 699  
700 700  
701 -= 6. Trouble Shooting: =
665 += 5. Trouble Shooting: =
702 702  
703 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
667 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
704 704  
705 705  
706 706  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.
... ... @@ -727,7 +727,7 @@
727 727  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.
728 728  
729 729  
730 -== 6.2 Issue: "NBIOT did not respond" ==
694 +== 5.2 Issue: "NBIOT did not respond" ==
731 731  
732 732  
733 733  (% class="box errormessage" %)
... ... @@ -755,7 +755,7 @@
755 755  [[image:image-20240208001740-1.png]]
756 756  
757 757  
758 -== 6.3 Issue: "Failed to readI MSI number" ==
722 +== 5.3 Issue: "Failed to readI MSI number" ==
759 759  
760 760  
761 761  (% class="box errormessage" %)
... ... @@ -769,9 +769,12 @@
769 769  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"]].
770 770  
771 771  
772 -== 6.4 Why sometime the AT Command is slow in reponse? ==
736 +== 5.4 Why sometime the AT Command is slow in reponse? ==
773 773  
774 774  
775 775  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.
776 776  
777 777  [[image:image-20240226111928-1.png]]
742 +
743 +
744 +
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