AWR1843BOOST: Data Interpretation Issues

Hi,

As mentioned in the ODS demo documentation, the ODS demo was designed to work with AWR1642BOOST-ODS EVM.

If you run the demo with AWR1843BOOST, the angle information is not correct.

Regarding the format of the output data, please see the User Guide.Once you detect the magic number, you should be able to understand the content of the data.

The (x,y,z) is provided in Q9 format. So you will have to scale the integer data by 2^9=512

Please also see attached snapshot that may help

Here is the matlab code that performs this operation in the gui

function [detObj, idx] = getDetObj(bytevec, idx, tlvLen, rangeIdxToMeters, dopplerResolutionMps, numDopplerBins)

    global OBJ_STRUCT_SIZE_BYTES;

    detObj =[];

    detObj.numObj = 0;

    if tlvLen > 0

        %Get detected object descriptor

        word = [1 256]';

        detObj.numObj = sum(bytevec(idx+(1:2)) .* word);

        idx = idx + 2;

        xyzQFormat = 2^sum(bytevec(idx+(1:2)) .* word);

        idx = idx + 2;

        %Get detected array of detected objects

        bytes = bytevec(idx+(1:detObj.numObj*OBJ_STRUCT_SIZE_BYTES));

        idx = idx + detObj.numObj*OBJ_STRUCT_SIZE_BYTES;

        bytes = reshape(bytes, OBJ_STRUCT_SIZE_BYTES, detObj.numObj);

        detObj.speedIdx = (bytes(1,:)+bytes(2,:)*256);

        detObj.x = bytes(3,:)+bytes(4,:)*256;

        detObj.y = bytes(5,:)+bytes(6,:)*256;

        detObj.z = bytes(7,:)+bytes(8,:)*256;

        detObj.x( detObj.x > 32767) =  detObj.x( detObj.x > 32767) - 65536;

        detObj.y( detObj.y > 32767) =  detObj.y( detObj.y > 32767) - 65536;

        detObj.z( detObj.z > 32767) =  detObj.z( detObj.z > 32767) - 65536;

        detObj.x =  detObj.x / xyzQFormat;

        detObj.y =  detObj.y / xyzQFormat;

        detObj.z =  detObj.z / xyzQFormat;

Hey Cesar,

Thanks for the quick reply.

Is there anyway I could correct this angle information or Do I have to use another demo, which is designed for AWR1843BOOST?

I tried to work with automated_parking demo, but the object detection with ods_demo is far better than automated_parking demo (my observation). I just need to detect objects  with in 2 or 3 meters range.

What configurational changes do I need to implement on automated_parking example, in order to make it work like ods_demo?

As far as I understood chirp_configuration for automated_parking example are hardcoded. Can you please point me, where I can change these parameters?

Thanks in advance.

BR

Venkatesh

Hi Cesar,

Thank you I will try that demo and get back to you if i have any doubts.

I think there is a typing mistake in Data packet format of the ODS_DEMO (Just for Info) . Thats why I was bit lost. Here I am adding the text from frame header packet of  ODS_DEMO . 

frameHeaderStructType = struct(... 'sync',

{'uint16', 8}, ... % syncPattern in hex is: '02 01 04 03 06 05 08 07'

'version', {'uint32', 4}, ... % 0xA1642 or 0xA1443

'totalPacketLen', {'uint32', 4}, ... % In bytes, including the header

'platform', {'uint32', 4}, ... % See description below

'frameNumber', {'uint32', 4}, ... % Starting from 1

'timeCpuCycles', {'uint32', 4}, ... % Time in DSP cycles when the message was created

'numDetectedObj', {'uint32', 4}, ... % number of detected objects

'numTLVs' , {'uint32', 4}, ... % Number of TLVs in this message '

subFrameIndex', {'uint32', 4}); % always zero 

Platform Value should be % 0xA1642 or 0xA1443, but not the version. 

Thank you.

BR

Venkatesh.

Hello Cesar,

I tried to work in debug mode. I loaded DSS and MSS programs using code composer studio and ran the group as specified in the user guide. I opened the GUI and I can see the data. But when I tried to put some brakpoints inside the code (send TLVs part in  MSS_MAIN.c file), it is not stopping there.  But I do know that the send TLVs part, where a put breakpoint is executing in a every cycle.Is there any reason behind that? 

I would like to send only x,y and z coordinate via UART from the radar. I do not want to send all other information like magicword, platform. How can send only x,y and z coordinates? 

Thanks in advance.

BR

venkatesh.

Hallo Cesar,

Before I used to work with ODS_DEMO example on AWR1843BOOST board and the output data format is as shown below.

But currently I am using xxr1843Demo on the same board and the data output format seems different(Detected object infomation) from ODS_Demo output data. The current output data is

The message format (Object information) is not same as the ODS_Demo example. I looked into index file in Doxygen folder, but there is no information about how to get x,y and z co-ordinates of the detected objects in that file. Where can I find the documentation related to the specific data formats ?

How can I get x,y and z coordinates of the detected objects? Where Can I find Parser or GUI for the xxr1843Demo ?

Thank you.

BR

Venkatesh.