• Resolved

AWR1642BOOST-ODS: Output data format of AWR1642BOOST-ODS mmWave radar

Prodigy 230 points

Replies: 6

Views: 163

Part Number: AWR1642BOOST-ODS

Hii,

I am working of mmWave AWR1642BOOST-ODS radar. I want to know AWR1642BOOST-ODS mmWave Radar output data & header format details. 

How can I get these details?

Also If I am using another CCS project like Short-range radar project then, will it differ in the data format of xwr16xx demo project and data format for Short-range radar project from automotive tools?

If yes, how can I get the data format details of the short-range radar project for data transmission?

I want to use output data of AWR1642BOOST-ODS in my project, that's why I needed to know the output data format. 

Thanks & Regards,

Harish

  • Hi,

    All the data formats are provided in the respective lab documentation except for SRR. Unfortunately for, this lab the data format is not documented.

    You would need to look at the following:

    In the file:

    mmwave_automotive_toolbox\labs\lab0002_short_range_radar\src\dss\dss_main.c

    SRR_DSS_SendProcessOutputToMSS()

    This function implements the buffers sent to the host.

    For VOD, the data format is documented in the demo UG:

    mmwave_automotive_toolbox\labs\lab0003_occupancy_detection\docs\ODdemo_usersguide.pdf

    See "Data Packet Format" Section

    thank you

    Cesar

  • In reply to Cesar:

    Hi Cesar,

    I saved UART output data of AWR1642BOOST-ODS in hex file using the Record button on mmWave demo visualizer.

    Somehow, we manage to extract information from the output data of AWR1642BOST-ODS with short-range radar package. And this output is as follows:

    0201 0403 0605 0807		sync
    
    0400 0002 				SDK version
    
    c002 0000 				packet length
    
    4216 0a00				Platform type
    
    0100 0000				Frame number 1
    
    eb86 5d6a				time in CPU cycle
    
    0600 0000				Number of detected obj
    
    0300 0000				No. of TLVs
    
    0000 0000				Sub frame number
    
    0100 0000				TLV type 1 - list of detected obj
    
    4c00 0000				TLV length
    
    0600 0900				Extra 4 byte
    
    0900					Number of detected object
    
    0000					Q-point shift value to convert to meters
    
    4c03 					Doppler index
    
    b000 					X-cordinate in meters
    
    6100 					Y-cordinate in meters
    
    0000 					Z-cordinate in meters
    
    3900 					Range index
    
    0000 					Peak Value
    
    eb03 d8ff 
    
    f904 
    
    0000 
    
    f700 
    
    0000 
    
    1e00 
    78ec 
    1c09 
    0000 
    fb00 0000 0e00 d7f9 0415 0000 
    ff00 0000 3e00 24eb be07 0000 
    fb00 0000 0a00 a1f1 8710 0000 
    
    
    0200 0000
    
    0002 0000 be78 a87d 807b d776 dd73 2375
    e26b 6d70 4381 f584 0a7e 6f6e d36a e967
    3063 1f64 5061 f761 a667 6f65 cc61 a359
    db59 4d5a 2e62 286a f266 1a5c 1e5a df5a
    cb63 4966 d268 6668 3d61 dc54 e352 7758
    f453 eb56 a85c 0256 1253 d35f 6161 165b
    6658 ee5a 9655 6d4e ac62 486b 9868 fd5f
    5264 b875 2586 4689 6b7f e56f 5670 126c
    176c 6668 f362 0e63 c46e cb75 ab72 fd65
    af60 d262 6662 7069 3070 6b6f 2e67 9d60
    0760 fe5f ad5e bf5f 9c5a 6b5f f661 ff68
    a26b e86a 0962 9b5f 9c5f 3866 086a 2f65
    8562 6d5c a957 9a5b 6f5c ba5a f95b b85c
    9a5e 605d 4c5d fb61 1767 4863 cb54 b956
    8e5a ef55 5252 b056 915e ff66 d26d 706b
    d35f b158 4a56 cc55 d358 3d59 1b5a d760
    4661 9c58 f656 a261 3667 b65f 2d5d 195f
    af5f 865d 3355 1b55 0a54 1f57 a756 1253
    3d50 3552 d957 ec5a 915b 3e5a 9057 e854
    4d52 e752 2c4f c84e 534e 094d e84c 0f4e
    464c fe4f 3b50 d64b 0749 7749 994e 974c
    214b 1f4a a24d 254e bb4a e845 4245 d246
    f649 8949 8242 8443 dc45 054f a753 b75a
    2f58 c34d 374c c048 2e4a 224a 6052 764f
    4949 5850 0f50 6e49 9945 6747 204e cc50
    1a4c ab50 5f4e 0245 de44 f944 5143 bd46
    7148 ae47 9547 4f4c a049 bc44 af47 cd49
    9b46 b640 d843 9945 9a40 b940 1a45 da46
    4e43 693f 4c45 fd47 7c47 4343 3b42 2a3f
    273a b940 3e3c 1b43 fd43 663f 863d 873c
    5d39 1e3d d93b e739 1639 3f3d bd3e 5247
    2657 f05e dd5b e44c a94e c758 b058 6c57
    685f cb67 0600 0000 1800 0000 bc0e 0000
    0000 0000 ff24 2d00 b90e 0000 0300 0000
    0000 0000 0f0f 0f0f 0f0f 0f0f 0f0f 0f0f
    0f0f 0f0f 0f0f 0f0f 0f0f 0f0f 0f0f 0f0f


    We found the above data meaning from obstacle detection project's user guide and Data over CAN project's guide.


    from highlighted text(in red color) in above data, we didn't able to understand meaning of next data bytes.
    Kindly help to understand the data format?

    Thanks & Regards,

    Harish

  • In reply to Harish More:

    Sorry for the above-messed reply.

     

    We found the above data meaning from obstacle detection project's user guide and Data over CAN project's guide.

    From highlighted text(in red color) in above data, we didn't able to understand meaning of next data bytes.

    Kindly help to understand the data format?

    Thanks and regards,

    Harish. 

  • In reply to Harish More:

    The data for a frame starts with the magic number.

    After that the data packets are as implemented in the code.

    Thank you

    Cesar

  • In reply to Cesar:

    Hi Cesar,

    I have seen dss_main.c file for output data format. And also gone through the C:\ti\mmwave_sdk_02_00_00_04\packages\ti\demo\xwr16xx\mmw\docs\doxygen\html\index.html for output data format.

    But still, it's not getting clarity in exactly what is next hex data format mean? Please provide some hint or exactly how I can find next byte meaning.

    Until now I found output data format as below. 

    0201 0403 0605 0807		sync
    
    0400 0002 				SDK version
    
    c002 0000 				packet length
    
    4216 0a00				Platform type
    
    0100 0000				Frame number 1
    
    eb86 5d6a				time in CPU cycle
    
    0600 0000				Number of detected obj
    
    0300 0000				No. of TLVs
    
    0000 0000				Sub frame number
    
    0100 0000				TLV type 1 - list of detected obj
    
    4c00 0000				TLV length
    
    0600 0900				Extra 4 byte
    
    0900					Number of detected object
    
    0000					Q-point shift value to convert to meters
    
    4c03 					Doppler index
    
    b000 					X-cordinate in meters
    
    6100 					Y-cordinate in meters
    
    0000 					Z-cordinate in meters
    
    3900 					Range index
    
    0000 					Peak Value
    
     di        x      y       z      Ri     pv
    eb03 d8ff f904 0000 f700 0000 
    1e00 78ec 1c09 0000 fb00 0000 
    0e00 d7f9 0415 0000 ff00 0000 
    3e00 24eb be07 0000 fb00 0000 
    0a00 a1f1 8710 0000 0200 0000
    
    0002 0000	?????	Please help to find meaning of next data bytes
    be78 a87d 		??????		
    807b d776 				
    dd73 2375
    e26b 6d70 4381 f584 0a7e 6f6e d36a e967
    3063 1f64 5061 f761 a667 6f65 cc61 a359
    db59 4d5a 2e62 286a f266 1a5c 1e5a df5a
    cb63 4966 d268 6668 3d61 dc54 e352 7758
    f453 eb56 a85c 0256 1253 d35f 6161 165b
    6658 ee5a 9655 6d4e ac62 486b 9868 fd5f
    5264 b875 2586 4689 6b7f e56f 5670 126c
    176c 6668 f362 0e63 c46e cb75 ab72 fd65
    af60 d262 6662 7069 3070 6b6f 2e67 9d60
    0760 fe5f ad5e bf5f 9c5a 6b5f f661 ff68
    a26b e86a 0962 9b5f 9c5f 3866 086a 2f65
    8562 6d5c a957 9a5b 6f5c ba5a f95b b85c
    9a5e 605d 4c5d fb61 1767 4863 cb54 b956
    8e5a ef55 5252 b056 915e ff66 d26d 706b
    d35f b158 4a56 cc55 d358 3d59 1b5a d760
    4661 9c58 f656 a261 3667 b65f 2d5d 195f
    af5f 865d 3355 1b55 0a54 1f57 a756 1253
    3d50 3552 d957 ec5a 915b 3e5a 9057 e854
    4d52 e752 2c4f c84e 534e 094d e84c 0f4e
    464c fe4f 3b50 d64b 0749 7749 994e 974c
    214b 1f4a a24d 254e bb4a e845 4245 d246
    f649 8949 8242 8443 dc45 054f a753 b75a
    2f58 c34d 374c c048 2e4a 224a 6052 764f
    4949 5850 0f50 6e49 9945 6747 204e cc50
    1a4c ab50 5f4e 0245 de44 f944 5143 bd46
    7148 ae47 9547 4f4c a049 bc44 af47 cd49
    9b46 b640 d843 9945 9a40 b940 1a45 da46
    4e43 693f 4c45 fd47 7c47 4343 3b42 2a3f
    273a b940 3e3c 1b43 fd43 663f 863d 873c
    5d39 1e3d d93b e739 1639 3f3d bd3e 5247
    2657 f05e dd5b e44c a94e c758 b058 6c57
    685f cb67 0600 0000 1800 0000 bc0e 0000
    0000 0000 ff24 2d00 b90e 0000 0300 0000
    0000 0000 0f0f 0f0f 0f0f 0f0f 0f0f 0f0f
    0f0f 0f0f 0f0f 0f0f 0f0f 0f0f 0f0f 0f0f

    Thanks and Regards,,

    Harish

  • In reply to Harish More:

    > But still, it's not getting clarity in exactly what is next hex data format mean? Please provide some hint or exactly how I can find next byte meaning.

    I don't understand this question.  Assuming you understand hex data, I guess there is something about the packet format that you don't understand.

    All mmWave demos use the TLV (type-length-value) packet format, but some demos vary a little bit in structure definitions from what the "mmw" (out-of-box) demo uses. And some demos have special output types not contained in any other demo.  So an output parser for one demo may not work for another demo. But every demo should document its packet format fully (it seems SRR is the exception).  For the mmw demo structures, search the .html document for "Output information sent to the host".  All the details you will need are there - the packet structures, sizes and contents.  Otherwise, as Cesar mentioned, you will need to look at the output data structures defined in the target code. This will always be the most exact description of the packet header, TLV header and payload types.

     -dave