Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 148.3
edited by Xiaoling
on 2024/03/20 17:58
Change comment: There is no comment for this version
To version 163.1
edited by Bei Jinggeng
on 2024/05/30 18:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
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,7 +48,7 @@
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
... ... @@ -634,11 +634,62 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
637 -= 4. FAQ =
638 638  
639 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
640 640  
639 += 4. MQTT/UDP/TCP downlink =
641 641  
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 +
642 642  The NB series has the feature for Multi Sampling and one uplink. See one of them
643 643  
644 644  [[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]]
... ... @@ -653,11 +653,9 @@
653 653  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
654 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.
655 655  
707 +== 5.2 Why the uplink JSON format is not standard? ==
656 656  
657 657  
658 -== 4.2 Why the uplink JSON format is not standard? ==
659 -
660 -
661 661  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.
662 662  
663 663  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
... ... @@ -665,9 +665,9 @@
665 665  [[image:image-20240229233154-1.png]]
666 666  
667 667  
668 -= 5. Trouble Shooting: =
717 += 6. Trouble Shooting: =
669 669  
670 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
719 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
671 671  
672 672  
673 673  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.
... ... @@ -694,7 +694,7 @@
694 694  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.
695 695  
696 696  
697 -== 5.2 Issue: "NBIOT did not respond" ==
746 +== 6.2 Issue: "NBIOT did not respond" ==
698 698  
699 699  
700 700  (% class="box errormessage" %)
... ... @@ -722,7 +722,7 @@
722 722  [[image:image-20240208001740-1.png]]
723 723  
724 724  
725 -== 5.3 Issue: "Failed to readI MSI number" ==
774 +== 6.3 Issue: "Failed to readI MSI number" ==
726 726  
727 727  
728 728  (% class="box errormessage" %)
... ... @@ -736,9 +736,65 @@
736 736  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"]].
737 737  
738 738  
739 -== 5.4 Why sometime the AT Command is slow in reponse? ==
788 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
740 740  
741 741  
742 742  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.
743 743  
744 744  [[image:image-20240226111928-1.png]]
794 +
795 +
796 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
797 +
798 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
799 +=== UDP: ===
800 +
801 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
802 +Its downlink command is the same as the AT command, but brackets are required.
803 +Example:
804 +
805 +{AT+TDC=300}
806 +
807 +
808 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
809 +=== MQTT: ===
810 +
811 +Json：
812 +
813 +The Json format in MQTT mode needs to be configured with all commands.
814 +If you have configurations that need to be changed, please change them in the template below.
815 +Template:
816 +
817 +{
818 +"AT+SERVADDR":"119.91.62.30,1882",
819 +"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
820 +"AT+UNAME":"usenamedragino",
821 +"AT+PWD":"passworddragino",
822 +"AT+PUBTOPIC":"123",
823 +"AT+SUBTOPIC":"321",
824 +"AT+TDC":"7200",
825 +"AT+INTMOD":"0",
826 +"AT+APN":"NULL",
827 +"AT+5VT":"0",
828 +"AT+PRO":"3,5",
829 +"AT+TR":"900",
830 +"AT+NOUD":"0",
831 +"AT+CSQTIME":"5",
832 +"AT+DNSTIMER":"0",
833 +"AT+TLSMOD":"0,0",
834 +"AT+MQOS":"0",
835 +"AT+TEMPALARM1":"0",
836 +"AT+TEMPALARM2":"10",
837 +"AT+TEMPALARM3":"0"
838 +}
839 +
840 +Hex：
841 +
842 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
843 +
844 +The supported commands are consistent with LoRaWAN's hex commands.
845 +Please refer to the following link to obtain the hex format:
846 +
847 +[[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/]]
848 +
849 +
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