MMWAVEICBOOST: IWR6843

Part Number: MMWAVEICBOOST

Tool/software:

Hello,

we tested the true ground speed demo with the IWR6843-ISK in a simulated test and are so far very statisfied with the results. However we encountered several problems along the way:

* The radar frequently crashes and no longer sends data. This only happens in confined areas (e.g. indoors). Do you know why this might happen? This is our main problem since we want to do a field test and cant restart the radar manually.
* How can we parse the speed data like in the demo without the visualizer? The demo says "The calculated velocity is streamed off the device as a TLV in real time via UART." but it does not say what TLV identifier is used.
* RANSAC (configRANSAC) is enabled by default in the demo. When turning it off or removing this line, the demo program no longer works. Why is that?

Your help would be greatly appreciated!

Regards,

Noel

  • Update: I was able to parse the data by looking at the python code from the demo visualizer, however the two other questions still remain. Thanks for your help!

  • Hello Noel.

    RANSAC (configRANSAC) is enabled by default in the demo. When turning it off or removing this line, the demo program no longer works. Why is that?

    I believe that only with this enabled will the ground speed be calculated, so the TLV that is populated with this information will not be computed and sent out by the device.  Therefore the visualizer as it parses through the data stream will not find the velocity it needs to display on the visualizer.

    * The radar frequently crashes and no longer sends data. This only happens in confined areas (e.g. indoors). Do you know why this might happen? This is our main problem since we want to do a field test and cant restart the radar manually.

    Its possible that you may be getting too many reflections within the confined space and results in a hard fault.  You can reduce the # of points by increasing your CFAR threshold to see if that helps.  If you also run with the debugger you can see where the code might be crashing to get a better understanding of the problem.

    Sincerely,

    Santosh