Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 158.1 >
edited by Mengting Qiu
on 2024/04/18 15:04
To version < 164.1 >
edited by Mengting Qiu
on 2024/05/31 09:19
>
Change comment: There is no comment for this version

Summary

Details

Page properties
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, 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  
... ... @@ -634,8 +634,14 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
637 +== 3.9 AWS Connection ==
637 637  
638 638  
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 +
642 +
643 +
644 +
639 639  = 4. MQTT/UDP/TCP downlink =
640 640  
641 641  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -642,11 +642,11 @@
642 642  
643 643  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
644 644  
645 -**1.** **Configure node MQTT connection (via MQTT.fx):**
651 +**1.** Configure node MQTT connection (via MQTT.fx):
646 646  
647 647  (% style="color:blue" %)**AT command:**
648 648  
649 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
655 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
650 650  
651 651  * (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
652 652  
... ... @@ -656,19 +656,35 @@
656 656  
657 657  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
658 658  
659 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) **~/~/ to set MQTT server address and port**
665 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
660 660  
661 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 662  
663 -[[image:image-20240417180145-2.png||height="545" width="737"]]
669 +[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
664 664  
665 -[[image:image-20240417180737-3.png||height="544" width="738"]]
666 666  
672 +**2. **When the node uplink packets, we can observe the data in MQTT.fx.
667 667  
674 +[[image:image-20240418144337-1.png||height="709" width="802"]]
668 668  
676 +**3. **The downlink command can be successfully sent only when the downlink port is open.
669 669  
678 + The downlink port is opened for about 3 seconds after uplink packets are sent.
670 670  
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.
671 671  
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 +
672 672  = 5. FAQ =
673 673  
674 674  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -769,9 +769,65 @@
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? ==
794 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.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]]
800 +
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 +
image-20240418150932-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +103.4 KB
Content

Applications

Navigation

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