Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 152.1
edited by Edwin Chen
on 2022/11/24 09:15
Change comment: There is no comment for this version
To version 147.1
edited by Edwin Chen
on 2022/11/22 20:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -586,9 +586,6 @@
586 586  
587 587  In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes.
588 588  
589 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
590 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
591 -* **[[PT>>||anchor="H3.2.1SetTransmitInterval"]]** defines the threldhold to detect a motion.
592 592  
593 593  == 2.10 LED Status ==
594 594  
... ... @@ -858,7 +858,7 @@
858 858  
859 859  
860 860  
861 -=== 3.2.10 Disable/Enable the confirmation mode ===
858 +**Disable/Enable the confirmation mode**
862 862  
863 863  * (% style="color:blue" %)**AT Command:**
864 864  
... ... @@ -877,7 +877,7 @@
877 877  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
878 878  
879 879  
880 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
881 881  
882 882  
883 883  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
... ... @@ -895,10 +895,10 @@
895 895  
896 896  * (% style="color:blue" %)**Downlink Command: 0x34**
897 897  
898 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
899 899  
900 900  
901 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
902 902  
903 903  
904 904  BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
... ... @@ -913,10 +913,10 @@
913 913  
914 914  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
915 915  
916 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
917 917  
918 918  
919 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
916 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
920 920  
921 921  
922 922  WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
... ... @@ -931,10 +931,10 @@
931 931  
932 932  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
933 933  
934 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
935 935  
936 936  
937 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
934 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
938 938  
939 939  
940 940  Users can use this feature to enable/disable Information printing.
... ... @@ -945,7 +945,7 @@
945 945  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
946 946  
947 947  
948 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
949 949  
950 950  
951 951  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -960,26 +960,6 @@
960 960  Example: 0x24 01 ~/~/ Same as AT+CHE=1
961 961  
962 962  
963 -=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
964 -
965 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
966 -
967 -(% style="color:blue" %)**AT Command:**
968 -
969 -(% style="color:#037691" %)**AT+PT=xx**
970 -
971 - Example:
972 -
973 - AT+PT=14    ~-~->    Set to detect car motion.
974 -
975 - AT+PT=41   ~-~->    set to detect walk motion.
976 -
977 -
978 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
979 -0xB4 14          ~/~/  Same as AT+PT=14
980 -
981 -
982 -
983 983  = 4. Setting for Different Scenarios =
984 984  
985 985  
... ... @@ -1276,6 +1276,7 @@
1276 1276  * AT+PDOP=7
1277 1277  * AT+FTIME=180000
1278 1278  
1256 +
1279 1279  Example:
1280 1280  
1281 1281  AT+PDOP=7.00
... ... @@ -1315,11 +1315,11 @@
1315 1315  
1316 1316  2)  Set PDOP to a higher value.
1317 1317  
1318 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1296 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1319 1319  
1320 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1298 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1321 1321  
1322 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1300 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1323 1323  
1324 1324  Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
1325 1325