IWR6843ISK: Incorrect target information in Long Range People Detection example

Hello, 

This is not a known issue. I have a few questions to help me better understand the situation.

1. Please help me understand what is meant by "incorrect info". I suppose from your pictures you are saying that there should only be a single target each frame and that the second target is erroneous. Is that correct? 
2. When you notice this behavior, what is the radar "looking at"? Is it an open area with a single person walking around? etc...
3. Is the error in the Industrial Visualizer only seen when running with the modified baud rate?
4. Have you made any modifications to the Industrial Visualizer source code? 

Best Regards,

Josh

Q: Please help me understand what is meant by "incorrect info". I suppose from your pictures you are saying that there should only be a single target each frame and that the second target is erroneous. Is that correct? 

A: Correct. The track ID value of the second target is wrong because the maximum number of tracks passed to trackingCfg is 20.

Q: When you notice this behavior, what is the radar "looking at"? Is it an open area with a single person walking around? etc...

A: It tested indoor, target is a single person. I'm aware that this can cause ghosting by reflections. However, LRPD example ignores static points, so ghosts around DC are not understandable.

Q: Is the error in the Industrial Visualizer only seen when running with the modified baud rate?

A: No, It occurred problem without changing the baudrate

Q: Have you made any modifications to the Industrial Visualizer source code? 

A: Yes, I modified the GUI to display the coordinate information of the target plot. when I ran the prebuilt binary with the modified industiral visualizer it worked fine.

Thanks.

Hi,

Thanks. I'm not quite sure whether the target information issue and visualizer issue are related or completely separate. I would like to spend some time to test this on my end to see if I can replicate the same behavior. Please allow me to test this and get back to you on Monday next week. In the meantime I have a couple more questions.

For the target information issue:

1. Does this seem to occur every time you run the demo? 
2. Is the erroneous target data present when there are no actual targets in the scene? or only if there is another target present?
3. Is the bad data present on every frame or just sporadically?

For the visualizer issue:

1. Does the error occur immediately after launching the visualizer or after some time with the demo running?

Thanks and regards,

Josh

HI,

For the target information issue:

Q: Does this seem to occur every time you run the demo? 

A: Yes it occur everytime I run.

Q: Is the erroneous target data present when there are no actual targets in the scene? or only if there is another target present?

A: Erroneous target data only occurs when another (actual)target present in the scene.

Q: Is the bad data present on every frame or just sporadically?

A: It is sporadically.

For the visualizer issue:

Q: Does the error occur immediately after launching the visualizer or after some time with the demo running?

A: After running the demo I get an error when the target is detected. I expect exception thrown by erroneous target data.

Thanks.

Hi, 

Sorry for the delay here. I have not been able to replicate the issue you are seeing. I apologize for all the questions but I have a few more to see if I can recreate this:

1. Which mmWave SDK version do you have installed?
2. Which version of Long Range People Detection are you running? 6443 or 6843 (mss + dss)?
3. Which configuration file (.cfg) are you using?

Best Regards, 

Josh

Hi,

Q: Which mmWave SDK version do you have installed?

A: I used SDK version 3.5.0.4

Q: Which version of Long Range People Detection are you running? 6443 or 6843 (mss + dss)?

A: IWR6843ISK (mss + dss)

Q: Which configuration file (.cfg) are you using?

A: I used <LRPD example path>/chirp_configs/6843_50m_3D.cfg file and did not change the configurations.

I'll try after reinstalling SDK and Toolbox. I'll update when the results come out.

Thanks.

Hi, 

I'm glad the issue is resolved after updating the SDK and Radar Toolbox. Thank you for posting your solution.

Best Regards,

Josh