Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 149.1
edited by Edwin Chen
on 2022/11/24 09:07
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,13 +586,7 @@
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 590  
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 -
596 596  == 2.10 LED Status ==
597 597  
598 598  
... ... @@ -861,7 +861,7 @@
861 861  
862 862  
863 863  
864 -=== 3.2.10 Disable/Enable the confirmation mode ===
858 +**Disable/Enable the confirmation mode**
865 865  
866 866  * (% style="color:blue" %)**AT Command:**
867 867  
... ... @@ -880,7 +880,7 @@
880 880  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
881 881  
882 882  
883 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
884 884  
885 885  
886 886  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.
... ... @@ -898,10 +898,10 @@
898 898  
899 899  * (% style="color:blue" %)**Downlink Command: 0x34**
900 900  
901 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
902 902  
903 903  
904 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
905 905  
906 906  
907 907  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.
... ... @@ -916,10 +916,10 @@
916 916  
917 917  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
918 918  
919 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
920 920  
921 921  
922 -=== 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） ===
923 923  
924 924  
925 925  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.
... ... @@ -934,10 +934,10 @@
934 934  
935 935  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
936 936  
937 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
938 938  
939 939  
940 -=== 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） ===
941 941  
942 942  
943 943  Users can use this feature to enable/disable Information printing.
... ... @@ -948,7 +948,7 @@
948 948  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
949 949  
950 950  
951 -=== 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） ===
952 952  
953 953  
954 954  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -1259,6 +1259,7 @@
1259 1259  * AT+PDOP=7
1260 1260  * AT+FTIME=180000
1261 1261  
1256 +
1262 1262  Example:
1263 1263  
1264 1264  AT+PDOP=7.00
... ... @@ -1298,11 +1298,11 @@
1298 1298  
1299 1299  2)  Set PDOP to a higher value.
1300 1300  
1301 -* (% _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.）
1302 1302  
1303 -* (% _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）
1304 1304  
1305 -* (% _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）
1306 1306  
1307 1307  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
1308 1308