This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR6843AOP: Processing on MATLAB vs. On-chip for Demo

Part Number: AWR6843AOP

Hey Team,

I had a question on the Vehicle Occupancy Detection demo/lab located here.

My customer runs a MATLAB script when using this lab. We are wondering where the line is drawn regarding processing of data. Could you help us to understand how much processing of data is done within MATLAB versus on the chip itself?

Is the MATLAB script getting raw data, processing, and generating visuals? Is MATLAB only getting info on what seat is occupied then translating this to a graphic? etc...

Thank you!

Best,
Dajon McGill

  • Hello

    The main intent of the marlab gui is to show the visualization and provide GUIto control the demo.

    As such all of the processing and results shown on the demo can be completely executed on the mmWave device in real time.

    Having said that for ease of configuration limited few final steps are carried out on the GUI. We can help you identify based on specific implemenations.

    Can you please help us know the exact demo and version you are using for this?

    Thank you

    Vaibhav

  • Hey Vaibhav,

    The demo is Vehicle Occupant Detection and they are using mmWave Automotive Toolbox 3.4.0.

    Do we have more questions before we can provide an answer?

    Best,
    Dajon McGill

  • HI, Dajon:

    There are several labs for in-cabin sensing.  Only the lab below, the device outputs point clouds, and the zone mapping and decision is done in Visualizer.  

    C:\ti\mmwave_automotive_toolbox_3_4_0\labs\incabinsensing\overhead_mount_occupancy

    All other lab under \incabinsensing directory, the decision is made inside the device, and visualizer is only for display purpose.  

    Each lab has users guide, you can find more details in each users guide.

    Best,

    Zigang