Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 153.1
edited by Edwin Chen
on 2022/11/24 09:16
Change comment: There is no comment for this version
To version 151.1
edited by Edwin Chen
on 2022/11/24 09:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -588,7 +588,7 @@
588 588  
589 589  * **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
590 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.
591 +* **[[PT>>||anchor="H3.2.1SetTransmitInterval"]]** defines the threldhold to detect a motion.
592 592  
593 593  
594 594  == 2.10 LED Status ==
... ... @@ -961,26 +961,6 @@
961 961  Example: 0x24 01 ~/~/ Same as AT+CHE=1
962 962  
963 963  
964 -=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
965 -
966 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
967 -
968 -(% style="color:blue" %)**AT Command:**
969 -
970 -(% style="color:#037691" %)**AT+PT=xx**
971 -
972 - Example:
973 -
974 - AT+PT=14    ~-~->    Set to detect car motion.
975 -
976 - AT+PT=41   ~-~->    set to detect walk motion.
977 -
978 -
979 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
980 -0xB4 14          ~/~/  Same as AT+PT=14
981 -
982 -
983 -
984 984  = 4. Setting for Different Scenarios =
985 985  
986 986