The first one is easy - the sensor detected an object at some close distance and then applied the offset correction. Unfortunately, after the correction, the distance is below zero. And we were forbidden to return negative numbers, so we generated an error instead.
double check the offset correction. I fear it's too large in the negative direction.
The FF error is a bit more difficult. Something went wrong with the range and the sensor could not tell what. But the numbers the sensor was getting made no sense, and so it returned an "unspecified error".
One would have to know what was going on in order to figure it out. Massive motion might have caused it, but more likely it is two factors mixed. Something like massive motion in addition to close distances.
The FF doesn't show up very often unless something is going on with the target. Perhaps you have a small one in front of a large far one, and maybe some motion is causing the A range to not align with the B range.
(Under the covers, the A range and B range use different pulse repetition intervals to detect radar aliasing. But the ranges should align.)
- john
If this or any post solves your issue, please mark them as 'Accept as Solution' It really helps. And if you notice anything wrong do not hesitate to 'Report Inappropriate Content'. Someone will review it.
