<
From version < 161.1 >
edited by Edwin Chen
on 2024/05/13 22:35
To version < 165.1 >
edited by Edwin Chen
on 2024/06/08 14:45
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -62,6 +62,7 @@
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.
65 65  
66 66  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/]]**
67 67  
... ... @@ -634,8 +634,14 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
638 +== 3.9 AWS Connection ==
637 637  
638 638  
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 +
639 639  = 4. MQTT/UDP/TCP downlink =
640 640  
641 641  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -785,9 +785,65 @@
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 -== 6.4 Why sometime the AT Command is slow in reponse? ==
795 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.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]]
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 +
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0