Know Issue
[Fixed]Why does the firmware default to all three regions being detected?
When we initially designed it, we set the value of each zone to the maximum range, but apparently this caused a misunderstanding, and we will fix it in the next version of the firmware by changing the zone target default to 0.
It’s Fix now.
[Fixed]I set the zone's area coordinates to 0, 0, 0, 0, but why does it still show someone?
- Explanation: this is another known bug, we just found it from you read here. Yes, it doesn't make sense and we will fix it in the next firmware.
- Deeper explanation: The principle that causes it is that when we process the region, we just judge the x range of the region to include x and the y range to include y, and we don't deal with the special case of 0.
- Temporary solution: Setting the region to 1 can avoid the special case of 0.
- Firmware fix: We will fix it in the firmware starting from V230802.
It’s Fix now.
Zone Functionality Intro
What do you mean by XY in coordinates?
The X in it stands for the horizontal axis, which is the left/right offset of the target distance sensor.
How can I exclude an area?
(Question By harob1969)
In the current firmware, a zone can be excluded using the zout1 region, which leads to the logic: if the target exists in zout1, it is excluded from any zone region.
23年9月3日_18时41分26秒_M1_SYSREC.mov
HilinkRadarTool App