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

Summary

Details

Page properties
Content
... ... @@ -586,13 +586,10 @@
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 +* **[[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.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
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  
... ... @@ -963,6 +963,26 @@
963 963  Example: 0x24 01 ~/~/ Same as AT+CHE=1
964 964  
965 965  
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 +
966 966  = 4. Setting for Different Scenarios =
967 967  
968 968  
... ... @@ -1213,15 +1213,19 @@
1213 1213  
1214 1214  == 8.3  Problem after Upgrading Firmware ==
1215 1215  
1216 -=== 8.3.1 Continue Restart after upgrading ===
1233 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1217 1217  
1235 +Error Output
1218 1218  
1237 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1238 +
1219 1219  (((
1220 -If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1240 +Some partition is missed during upgrade, please upgrade below four files as example:
1241 +
1242 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1221 1221  )))
1222 1222  
1223 1223  
1224 -[[image:image-20221118105249-3.png||_mstalt="430664"]]
1225 1225  
1226 1226  
1227 1227  === 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
... ... @@ -1279,12 +1279,6 @@
1279 1279  
1280 1280  
1281 1281  
1282 -=== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===
1283 -
1284 -
1285 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1286 -
1287 -
1288 1288  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1289 1289  
1290 1290