Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 121.1 >
edited by Mengting Qiu
on 2024/09/03 10:23
To version < 95.1 >
edited by Mengting Qiu
on 2024/08/20 11:30
>
Change comment: Uploaded new attachment "image-20240820113015-60.png", version {1}

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=8.217.91.207,1999**  (%%) ~/~/ Set UDP server address and port
204 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
205 205  
206 206  [[image:image-20240819102802-1.png]]
207 207  
... ... @@ -614,13 +614,13 @@
614 614  
615 615  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
616 616  
617 -[[image:image-20240820112516-41.png]]
617 +[[image:image-20230802112413-44.png]]
618 618  
619 -[[image:image-20240820112526-42.png]]
619 +[[image:image-20230802112413-45.png]]
620 620  
621 621  Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
622 622  
623 -[[image:image-20240820112539-43.png]]
623 +[[image:image-20230802112413-46.png]]
624 624  
625 625  The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
626 626  
... ... @@ -660,21 +660,21 @@
660 660  
661 661  === 3.7.2 Simulate with MQTT.fx ===
662 662  
663 -[[image:image-20240820112552-44.png]]
663 +[[image:image-20230802112413-52.png]]
664 664  
665 -[[image:image-20240820112604-45.png]]
665 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
666 666  
667 667  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
668 668  
669 -[[image:image-20240820112615-46.png]]
669 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
670 670  
671 -[[image:image-20240820112626-47.png]]
671 +[[image:image-20230808105329-3.png]]
672 672  
673 673  === 3.7.3 tago data ===
674 674  
675 -[[image:image-20240820112637-48.png]]
675 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
676 676  
677 -[[image:image-20240820112647-49.png]]
677 +[[image:image-20230802112413-51.png||height="184" width="696"]]
678 678  
679 679  == 3.8 TCP Connection ==
680 680  
... ... @@ -688,18 +688,16 @@
688 688  
689 689  (% style="color:blue" %)**Sensor Console Output when Uplink:**
690 690  
691 -[[image:image-20240820112704-50.png]]
691 +[[image:image-20230807233631-1.png]]
692 692  
693 693  (% style="color:blue" %)**See result in TCP Server:**
694 694  
695 -[[image:image-20240820112716-51.png]]
695 +[[image:image-20230807233631-2.png]]
696 696  
697 697  == 3.9 AWS Connection ==
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 -= =
702 -
703 703  = 4. COAP/UDP/MQTT/TCP downlink =
704 704  
705 705  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -724,11 +724,11 @@
724 724  
725 725  (% 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.**
726 726  
727 -[[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
725 +[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584">> width="584"]]
728 728  
729 729  **2. **When the node uplink packets, we can observe the data in MQTT.fx.
730 730  
731 -[[image:image-20240820112813-54.png]]
729 +[[image:image-20240418144337-1.png||height="709" width="802"]]
732 732  
733 733  **3. **The downlink command can be successfully sent only when the downlink port is open.
734 734  
... ... @@ -736,42 +736,12 @@
736 736  
737 737   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.
738 738  
739 -[[image:image-20240820112824-55.png]]
737 +[[image:image-20240418150435-3.png||height="582" width="659"]]
740 740  
741 -[[image:image-20240820112835-56.png]]
739 +[[image:image-20240418150932-4.png||height="492" width="1061"]]
742 742  
743 743  (% 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.**
744 744  
745 -
746 -== 4.2 UDP (via Thingseye) ==
747 -
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/]])
749 -
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 -
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 -
775 775  = 5. GPS positioning function =
776 776  
777 777  === 1. Turn on GPS function ===
... ... @@ -814,7 +814,7 @@
814 814  
815 815  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
816 816  
817 -[[image:image-20240820112848-57.png]]
785 +[[image:image-20240229233154-1.png]]
818 818  
819 819  = 6. Trouble Shooting: =
820 820  
... ... @@ -824,11 +824,11 @@
824 824  
825 825  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
826 826  
827 -[[image:image-20240820112859-58.png]]
795 +[[image:image-20240207002003-1.png]]
828 828  
829 829  If fail to attach network, it will shows signal 99. as below:
830 830  
831 -[[image:image-20240820112908-59.png]]
799 +[[image:image-20240207002129-2.png]]
832 832  
833 833  (% class="lead" %)
834 834  When see this issue, below are the checklist:
... ... @@ -842,13 +842,13 @@
842 842  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.
843 843  
844 844  
845 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.2 Why sometime the AT Command is slow in reponse?(%%) ==
813 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
846 846  
847 847  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.
848 848  
849 -[[image:image-20240820113015-60.png]]
817 +[[image:image-20240226111928-1.png]]
850 850  
851 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
819 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
852 852  
853 853  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
854 854  === UDP: ===
... ... @@ -900,128 +900,5 @@
900 900  
901 901  [[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/]]
902 902  
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 -[[image:image-20240903100832-4.png||height="268" width="580"]]
934 -
935 -
936 -=== 6.5.1 GPS commands ===
937 -
938 -
939 -The following are three related AT commands that introduce GPS functions.
940 -
941 -* **Turn on/off GPS**
942 -
943 -(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
944 -
945 -**Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
946 -
947 -**Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
948 -
949 -(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
950 -
951 -Format: Command Code (0x11) followed by 1 byte.
952 -
953 -Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
954 -
955 -* **Set GNSS open time**
956 -
957 -Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
958 -
959 -(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
960 -
961 -Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
962 -
963 -(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
964 -
965 -Format: Command Code (0x10) followed by 2 bytes.
966 -
967 -Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
968 -
969 -* **Set GPS positioning interval**
970 -
971 -Feature: Set GPS positioning interval (unit: hour).
972 -
973 -When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
974 -
975 -(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
976 -
977 -Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
978 -
979 -(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
980 -
981 -Format: Command Code (0x12) followed by 3 bytes.
982 -
983 -Example: 24 hours:  24(D)=0x18(H)
984 -
985 - Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
986 -
987 -
988 -=== 6.5.2 GPS workflow ===
989 -
990 -
991 -The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
992 -
993 -~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.
994 -
995 - 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.
996 -
997 - So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
998 -
999 -2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
1000 -
1001 - The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
1002 -
1003 - 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.
1004 -
1005 -
1006 -=== 6.5.3 GPS debugging methods ===
1007 -
1008 -
1009 -In summary, we can deduce the method of debugging GPS:
1010 -
1011 -* **Check whether the GPS antenna is loose**.
1012 -
1013 -If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
1014 -
1015 -[[image:image-20240903094214-1.png||height="340" width="461"]]
1016 -
1017 -* **Use the AT+GNSST command to extend the positioning time.**
1018 -
1019 -The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
1020 -
1021 -If the location fails, users can extend the location time.
1022 -
1023 -
1024 -
1025 -
1026 -
1027 1027  
872 +​
image-20240820140935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -159.2 KB
Content
image-20240820141136-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -107.6 KB
Content
image-20240820141746-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -122.2 KB
Content
image-20240820141843-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -123.2 KB
Content
image-20240820143316-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20240820143820-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -161.7 KB
Content
image-20240820144823-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -145.6 KB
Content
image-20240820144913-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -136.4 KB
Content
image-20240820145133-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -164.5 KB
Content
image-20240820145309-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -32.6 KB
Content
image-20240827145055-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -74.2 KB
Content
image-20240827150121-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -86.0 KB
Content
image-20240827150705-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -86.7 KB
Content
image-20240903094214-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -4.5 MB
Content
image-20240903094457-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 MB
Content
image-20240903100736-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -250.8 KB
Content
image-20240903100832-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -181.5 KB
Content
image-20240903102327-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -26.2 KB
Content

Applications

Navigation

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