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

Summary

Details

Page properties
Content
... ... @@ -586,7 +586,13 @@
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.
589 589  
591 +~[~[TDC>>||anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
592 +
593 +~[~[PT>>||anchor="H3.2.1SetTransmitInterval"]] defines the threldhold to detect a motion.
594 +
595 +
590 590  == 2.10 LED Status ==
591 591  
592 592  
... ... @@ -855,7 +855,7 @@
855 855  
856 856  
857 857  
858 -**Disable/Enable the confirmation mode**
864 +=== 3.2.10 Disable/Enable the confirmation mode ===
859 859  
860 860  * (% style="color:blue" %)**AT Command:**
861 861  
... ... @@ -874,7 +874,7 @@
874 874  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
875 875  
876 876  
877 -=== 3.2.10  Auto Send None-ACK messages ===
883 +=== 3.2.11  Auto Send None-ACK messages ===
878 878  
879 879  
880 880  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.
... ... @@ -892,10 +892,10 @@
892 892  
893 893  * (% style="color:blue" %)**Downlink Command: 0x34**
894 894  
895 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
901 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
896 896  
897 897  
898 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
904 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
899 899  
900 900  
901 901  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.
... ... @@ -910,10 +910,10 @@
910 910  
911 911  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
912 912  
913 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
919 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
914 914  
915 915  
916 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
922 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
917 917  
918 918  
919 919  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.
... ... @@ -928,10 +928,10 @@
928 928  
929 929  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
930 930  
931 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
937 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
932 932  
933 933  
934 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
940 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
935 935  
936 936  
937 937  Users can use this feature to enable/disable Information printing.
... ... @@ -942,7 +942,7 @@
942 942  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
943 943  
944 944  
945 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
951 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
946 946  
947 947  
948 948  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -1253,7 +1253,6 @@
1253 1253  * AT+PDOP=7
1254 1254  * AT+FTIME=180000
1255 1255  
1256 -
1257 1257  Example:
1258 1258  
1259 1259  AT+PDOP=7.00
... ... @@ -1293,11 +1293,11 @@
1293 1293  
1294 1294  2)  Set PDOP to a higher value.
1295 1295  
1296 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1301 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1297 1297  
1298 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1303 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1299 1299  
1300 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1305 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1301 1301  
1302 1302  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
1303 1303