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.

IWR1642BOOST: Understanding fHistRT MATLAB data

Part Number: IWR1642BOOST

Hi!

I have been working with the IWR1642BOOST EVM's traffic monitoring lab from the industrial toolbox 3.6.2 and upon running the simulation have attained some fHistRT MATLAB files containing the scenes data. I am unsure if there is a document explaining each of the fields within the MATLAB structure file so am wondering if somebody could please point me to it, or please explain what each fields data represents.

I am mostly looking for:

- Targets range, angle and velocity (not point cloud data only identified targets)

- Potentially estimated size of the vehicle (if possible)

Thank you heaps in advance :)

  • Hi Jake,

    Please refer to the resource pointed in the following thread. 

    Compiler/IWR1642: how to parsing traffic monitring demo uart data

    Once you understand the above, you can also refer to the source of the Matlab visualizer provided in the demo as a reference example on how to parse the output stream.

    Regards

    -Nitin

  • Thank you very much Nitin!

    I am still a little lost as to what the data represents within the targetlist in MATLAB, I understand that it should hold all of the information shown below?

    But I don't quite understand where the posX, posY, velX, velY, accX and accY data is? (below is an example of a target list from one of my fhirst files) does 'S' in the below image represent the position velocity and acceleration?

  • Jake,

    Are you using the Visualizer provided with the demo in the following directory or is the above a snapshot from your own parsing script?

    C:\ti\mmwave_industrial_toolbox_3_6_2\labs\lab0013_traffic_monitoring_16xx\gui\tm_demo.m

    The above script provides a complete parser implementation and you should be able to re-use / derive from it as needed. The parsing logic start at line 326 as shown below.

    while(1)
        while(lostSync == 0)
    
            frameStart = tic;
            fHist(frameNum).timestamp = frameStart;
            bytesAvailable = get(hDataSerialPort,'BytesAvailable');
            if(bytesAvailable > maxBytesAvailable)
                maxBytesAvailable = bytesAvailable;
            end
            fHist(frameNum).bytesAvailable = bytesAvailable;
            if(gotHeader == 0)
                %Read the header first
                [rxHeader, byteCount] = fread(hDataSerialPort, frameHeaderLengthInBytes, 'uint8');
            end
            fHist(frameNum).start = 1000*toc(frameStart);
            
            magicBytes = typecast(uint8(rxHeader(1:8)), 'uint64');
            if(magicBytes ~= syncPatternUINT64)
                reason = 'No SYNC pattern';
                lostSync = 1;
                break;

    Please first check that the demo works with the provided visualizer and use that as a reference for parsing / debugging.

    Note that we are not able to support / debug your own parsing code.

    Thanks

    -Nitin