Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 161.2 >
edited by Bei Jinggeng
on 2024/05/30 17:49
To version < 153.1 >
edited by Mengting Qiu
on 2024/04/17 18:07
>
Change comment: Uploaded new attachment "image-20240417180737-3.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.ting
Content
... ... @@ -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  
... ... @@ -634,62 +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="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 -
693 693  The NB series has the feature for Multi Sampling and one uplink. See one of them
694 694  
695 695  [[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]]
... ... @@ -704,7 +704,7 @@
704 704  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
705 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.
706 706  
707 -== 5.2 Why the uplink JSON format is not standard? ==
656 +== 4.2 Why the uplink JSON format is not standard? ==
708 708  
709 709  
710 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.
... ... @@ -714,9 +714,9 @@
714 714  [[image:image-20240229233154-1.png]]
715 715  
716 716  
717 -= 6. Trouble Shooting: =
666 += 5. Trouble Shooting: =
718 718  
719 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
668 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
720 720  
721 721  
722 722  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.
... ... @@ -743,7 +743,7 @@
743 743  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.
744 744  
745 745  
746 -== 6.2 Issue: "NBIOT did not respond" ==
695 +== 5.2 Issue: "NBIOT did not respond" ==
747 747  
748 748  
749 749  (% class="box errormessage" %)
... ... @@ -771,7 +771,7 @@
771 771  [[image:image-20240208001740-1.png]]
772 772  
773 773  
774 -== 6.3 Issue: "Failed to readI MSI number" ==
723 +== 5.3 Issue: "Failed to readI MSI number" ==
775 775  
776 776  
777 777  (% class="box errormessage" %)
... ... @@ -785,21 +785,9 @@
785 785  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"]].
786 786  
787 787  
788 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
737 +== 5.4 Why sometime the AT Command is slow in reponse? ==
789 789  
790 790  
791 791  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.
792 792  
793 793  [[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 -
799 -NB devices use downlink commands in Json format.
800 -Its downlink command is the same as the AT command, but brackets are required.
801 -Example:
802 -
803 -{AT+TDC=300}
804 -
805 -
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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0