Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 101.1 >
edited by Mengting Qiu
on 2024/08/20 14:33
To version < 117.1 >
edited by Mengting Qiu
on 2024/09/03 09:58
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -201,7 +201,7 @@
201 201  
202 202  * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
203 203  
204 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
204 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1999**  (%%) ~/~/ Set UDP server address and port
205 205  
206 206  [[image:image-20240819102802-1.png]]
207 207  
... ... @@ -698,7 +698,6 @@
698 698  
699 699  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]]
700 700  
701 -(% class="wikigeneratedid" %)
702 702  = =
703 703  
704 704  = 4. COAP/UDP/MQTT/TCP downlink =
... ... @@ -746,9 +746,33 @@
746 746  
747 747  == 4.2 UDP (via Thingseye) ==
748 748  
749 -(% style="color:red" %)**Note:**(%%) The UDP service on the ThingsEye platform needs to be built by the user.
748 +(% style="color:red" %)**Note:**(%%) The UDP service on the ThingsEye platform needs to be built by the user. (Description Link:[[UDP service building instructions>>http://www.ithingsboard.com/docs/user-guide/integrations/udp/]])
750 750  
750 +After the node is successfully connected to the platform, you need to select the corresponding node (you can refer to the node's IMEI to find it)
751 751  
752 +[[image:image-20240820141843-2.png||height="546" width="821"]]
753 +
754 +After clicking Show Node Details Page, (% style="color:blue" %)**Select Properties ~-~-- select Shared Properties ~-~-- click Add Properties**
755 +
756 +[[image:image-20240820143316-3.png||height="555" width="1170"]]
757 +
758 +After clicking Add Shared Attribute, set the key to (% style="color:red" %)**value**(%%), and write the command that needs to be downlinked in the Downlink Command Input box
759 +
760 +(% style="color:red" %)**(Note: Downlinks can only be downlinked in string format, otherwise the node will not recognize the downlink command.)**
761 +
762 +[[image:image-20240820143820-4.png||height="554" width="1168"]]
763 +
764 +After the command is successfully added, the platform will send the command down on the node's next uplink.
765 +
766 +[[image:image-20240820144913-6.png||height="585" width="1232"]]
767 +
768 +[[image:image-20240820145133-7.png||height="582" width="1227"]]
769 +
770 +Upon successful issuance, the platform automatically eliminates the attributes from the queue and waits for the next addition of new attributes
771 +
772 +[[image:image-20240820145309-8.png]]
773 +
774 +
752 752  = 5. GPS positioning function =
753 753  
754 754  === 1. Turn on GPS function ===
... ... @@ -825,7 +825,7 @@
825 825  
826 826  [[image:image-20240820113015-60.png]]
827 827  
828 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the NB device?(%%) ==
851 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
829 829  
830 830  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
831 831  === UDP: ===
... ... @@ -877,5 +877,125 @@
877 877  
878 878  [[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/]]
879 879  
903 +
904 +== 6.4 What if the signal is good but the domain name resolution fails? ==
905 +
906 +
907 +If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
908 +
909 +[[image:image-20240827150705-6.png||height="489" width="687"]]
910 +
911 +If the domain name is correct, but the domain name cannot be resolved, the user can turn off the domain name resolution function(AT+GDNS=1) and use the domain name communication directly.
912 +
913 +* Set the DNS
914 +
915 +(% style="color:blue" %)**AT Command: AT+GDNS**
916 +
917 +**AT+GDNS=0**  ~/~/Default. Automatically resolves the domain name and uses the resolved IP to communicate.
918 +
919 +**AT+GDNS=1    **~/~/Disabling Domain name resolution. Use the domain name directly to communicate.
920 +
921 +(% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
922 +
923 +Example:
924 +
925 +[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
926 +
927 +
928 +== 6.5 GPS debugging ==
929 +
930 +
931 +Indoor GPS signal is very weak, outdoor positioning is generally recommended.
932 +
933 +=== 6.5.1 GPS commands ===
934 +
935 +
936 +The following are three related AT commands that introduce GPS functions.
937 +
938 +* **Turn on/off GPS**
939 +
940 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
941 +
942 +**Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
943 +
944 +**Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
945 +
946 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
947 +
948 +Format: Command Code (0x11) followed by 1 byte.
949 +
950 +Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
951 +
952 +* **Set GNSS open time**
953 +
954 +Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
955 +
956 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
957 +
958 +Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
959 +
960 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
961 +
962 +Format: Command Code (0x10) followed by 2 bytes.
963 +
964 +Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
965 +
966 +* **Set GPS positioning interval**
967 +
968 +Feature: Set GPS positioning interval (unit: hour).
969 +
970 +When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
971 +
972 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
973 +
974 +Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
975 +
976 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
977 +
978 +Format: Command Code (0x12) followed by 3 bytes.
979 +
980 +Example: 24 hours:  24(D)=0x18(H)
981 +
982 + Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
983 +
984 +
985 +=== 6.5.2 GPS workflow ===
986 +
987 +
988 +The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
989 +
990 +~1. When activate the node, the node will turn on the GNSS, if the GPS signal is good, the node will print and upload the position information with the first data packet immediately.
991 +
992 + If the signal is not good, it may take the whole (% style="color:#037691" %)**GNSST**(%%) time but still can not search the latitude and longitude information, at this time the node uploads the latitude and longitude all to 0.
993 +
994 + So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
995 +
996 +2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
997 +
998 + The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
999 +
1000 + Only when the node is activated or every (% style="color:#037691" %)**GTDC**(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool.
1001 +
1002 +
1003 +=== 6.5.3 GPS debugging methods ===
1004 +
1005 +
1006 +In summary, we can deduce the method of debugging GPS:
1007 +
1008 +* **Check whether the GPS antenna is loose**.
1009 +
1010 +If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
1011 +
1012 +[[image:image-20240903094214-1.png||height="340" width="461"]]
1013 +
1014 +* **Use the AT+GNSST command to extend the positioning time.**
1015 +
1016 +The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
1017 +
1018 +If the location fails, users can extend the location time.
1019 +
1020 +
1021 +
1022 +
1023 +
880 880  
881 -​
image-20240820143820-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +161.7 KB
Content
image-20240820144823-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +145.6 KB
Content
image-20240820144913-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +136.4 KB
Content
image-20240820145133-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +164.5 KB
Content
image-20240820145309-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
image-20240827145055-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +74.2 KB
Content
image-20240827150121-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +86.0 KB
Content
image-20240827150705-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +86.7 KB
Content
image-20240903094214-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +4.5 MB
Content
image-20240903094457-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +2.6 MB
Content

Applications

Navigation

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