Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 164.1
edited by Mengting Qiu
on 2024/05/31 09:19
Change comment: There is no comment for this version
To version 145.2
edited by Xiaoling
on 2024/03/01 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
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
... ... @@ -634,68 +634,11 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
637 -== 3.9 AWS Connection ==
638 += 4. FAQ =
638 638  
640 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
639 639  
640 -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]]
641 641  
642 -
643 -
644 -
645 -= 4. MQTT/UDP/TCP downlink =
646 -
647 -== 4.1 MQTT (via MQTT.fx) ==
648 -
649 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
650 -
651 -**1.** Configure node MQTT connection (via MQTT.fx):
652 -
653 -(% style="color:blue" %)**AT command:**
654 -
655 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
656 -
657 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
658 -
659 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
660 -
661 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
662 -
663 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
664 -
665 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
666 -
667 -(% 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.**
668 -
669 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
670 -
671 -
672 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
673 -
674 -[[image:image-20240418144337-1.png||height="709" width="802"]]
675 -
676 -**3. **The downlink command can be successfully sent only when the downlink port is open.
677 -
678 - The downlink port is opened for about 3 seconds after uplink packets are sent.
679 -
680 - 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.
681 -
682 -[[image:image-20240418150435-3.png||height="582" width="659"]]
683 -
684 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
685 -
686 -(% 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.**
687 -
688 -
689 -
690 -
691 -
692 -
693 -
694 -= 5. FAQ =
695 -
696 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
697 -
698 -
699 699  The NB series has the feature for Multi Sampling and one uplink. See one of them
700 700  
701 701  [[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]]
... ... @@ -708,21 +708,21 @@
708 708  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)
709 709  1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
710 710  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
711 -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.
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.
712 712  
713 -== 5.2 Why the uplink JSON format is not standard? ==
714 714  
715 715  
716 -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.
659 +== 4.2 Why the uplink JSON format is not standard? ==
717 717  
718 -The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
719 719  
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 +
720 720  [[image:image-20240229233154-1.png]]
721 721  
722 722  
723 -= 6. Trouble Shooting: =
667 += 5. Trouble Shooting: =
724 724  
725 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
669 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
726 726  
727 727  
728 728  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.
... ... @@ -749,7 +749,7 @@
749 749  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.
750 750  
751 751  
752 -== 6.2 Issue: "NBIOT did not respond" ==
696 +== 5.2 Issue: "NBIOT did not respond" ==
753 753  
754 754  
755 755  (% class="box errormessage" %)
... ... @@ -777,7 +777,7 @@
777 777  [[image:image-20240208001740-1.png]]
778 778  
779 779  
780 -== 6.3 Issue: "Failed to readI MSI number" ==
724 +== 5.3 Issue: "Failed to readI MSI number" ==
781 781  
782 782  
783 783  (% class="box errormessage" %)
... ... @@ -791,7 +791,7 @@
791 791  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"]].
792 792  
793 793  
794 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
738 +== 5.4 Why sometime the AT Command is slow in reponse? ==
795 795  
796 796  
797 797  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,57 +799,4 @@
799 799  [[image:image-20240226111928-1.png]]
800 800  
801 801  
802 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
803 -
804 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
805 -=== UDP: ===
806 -
807 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
808 -Its downlink command is the same as the AT command, but brackets are required.
809 -Example:
810 -
811 -{AT+TDC=300}
812 -
813 -
814 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
815 -=== MQTT: ===
816 -
817 -Json：
818 -
819 -The Json format in MQTT mode needs to be configured with all commands.
820 -If you have configurations that need to be changed, please change them in the template below.
821 -Template:
822 -
823 -{
824 -"AT+SERVADDR":"119.91.62.30,1882",
825 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
826 -"AT+UNAME":"usenamedragino",
827 -"AT+PWD":"passworddragino",
828 -"AT+PUBTOPIC":"123",
829 -"AT+SUBTOPIC":"321",
830 -"AT+TDC":"7200",
831 -"AT+INTMOD":"0",
832 -"AT+APN":"NULL",
833 -"AT+5VT":"0",
834 -"AT+PRO":"3,5",
835 -"AT+TR":"900",
836 -"AT+NOUD":"0",
837 -"AT+CSQTIME":"5",
838 -"AT+DNSTIMER":"0",
839 -"AT+TLSMOD":"0,0",
840 -"AT+MQOS":"0",
841 -"AT+TEMPALARM1":"0",
842 -"AT+TEMPALARM2":"10",
843 -"AT+TEMPALARM3":"0"
844 -}
845 -
846 -Hex：
847 -
848 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
849 -
850 -The supported commands are consistent with LoRaWAN's hex commands.
851 -Please refer to the following link to obtain the hex format:
852 -
853 -[[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/]]
854 -
855 855  
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