Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 165.1 >
edited by Edwin Chen
on 2024/06/08 14:45
To version < 156.1 >
edited by Mengting Qiu
on 2024/04/18 14:43
>
Change comment: Uploaded new attachment "image-20240418144337-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
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  
... ... @@ -62,7 +62,6 @@
62 62  
63 63  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64 64  
65 -By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
66 66  
67 67  See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
68 68  
... ... @@ -635,14 +635,8 @@
635 635  [[image:image-20230807233631-2.png]]
636 636  
637 637  
638 -== 3.9 AWS Connection ==
639 639  
640 640  
641 -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]]
642 -
643 -
644 -
645 -
646 646  = 4. MQTT/UDP/TCP downlink =
647 647  
648 648  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -649,11 +649,11 @@
649 649  
650 650  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
651 651  
652 -**1.** Configure node MQTT connection (via MQTT.fx):
645 +**1.** **Configure node MQTT connection (via MQTT.fx):**
653 653  
654 654  (% style="color:blue" %)**AT command:**
655 655  
656 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
649 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
657 657  
658 658  * (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
659 659  
... ... @@ -663,35 +663,19 @@
663 663  
664 664  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
665 665  
666 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
659 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) **~/~/ to set MQTT server address and port**
667 667  
668 668  (% 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.**
669 669  
670 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
663 +[[image:image-20240417180145-2.png||height="545" width="737"]]
671 671  
665 +[[image:image-20240417180737-3.png||height="544" width="738"]]
672 672  
673 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
674 674  
675 -[[image:image-20240418144337-1.png||height="709" width="802"]]
676 676  
677 -**3. **The downlink command can be successfully sent only when the downlink port is open.
678 678  
679 - The downlink port is opened for about 3 seconds after uplink packets are sent.
680 680  
681 - 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.
682 682  
683 -[[image:image-20240418150435-3.png||height="582" width="659"]]
684 -
685 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
686 -
687 -(% 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.**
688 -
689 -
690 -
691 -
692 -
693 -
694 -
695 695  = 5. FAQ =
696 696  
697 697  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -792,65 +792,9 @@
792 792  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"]].
793 793  
794 794  
795 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
772 +== 6.4 Why sometime the AT Command is slow in reponse? ==
796 796  
797 797  
798 798  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 799  
800 800  [[image:image-20240226111928-1.png]]
801 -
802 -
803 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
804 -
805 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
806 -=== UDP: ===
807 -
808 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
809 -Its downlink command is the same as the AT command, but brackets are required.
810 -Example:
811 -
812 -{AT+TDC=300}
813 -
814 -
815 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
816 -=== MQTT: ===
817 -
818 -Json：
819 -
820 -The Json format in MQTT mode needs to be configured with all commands.
821 -If you have configurations that need to be changed, please change them in the template below.
822 -Template:
823 -
824 -{
825 -"AT+SERVADDR":"119.91.62.30,1882",
826 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
827 -"AT+UNAME":"usenamedragino",
828 -"AT+PWD":"passworddragino",
829 -"AT+PUBTOPIC":"123",
830 -"AT+SUBTOPIC":"321",
831 -"AT+TDC":"7200",
832 -"AT+INTMOD":"0",
833 -"AT+APN":"NULL",
834 -"AT+5VT":"0",
835 -"AT+PRO":"3,5",
836 -"AT+TR":"900",
837 -"AT+NOUD":"0",
838 -"AT+CSQTIME":"5",
839 -"AT+DNSTIMER":"0",
840 -"AT+TLSMOD":"0,0",
841 -"AT+MQOS":"0",
842 -"AT+TEMPALARM1":"0",
843 -"AT+TEMPALARM2":"10",
844 -"AT+TEMPALARM3":"0"
845 -}
846 -
847 -Hex：
848 -
849 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
850 -
851 -The supported commands are consistent with LoRaWAN's hex commands.
852 -Please refer to the following link to obtain the hex format:
853 -
854 -[[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/]]
855 -
856 -
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