AWR1642BOOST: How can i modify the object detection range of radar module for "Short Range Radar"

You can use the 2nd tab of the sensing estimator tool to see the range of your profile configuration and modify it

dev.ti.com/.../mmWaveSensingEstimator

Hello Ahmad,

Thanks for a reply.

I have successfully flashed the srrdemo_16xx.bin file onto the AWR1642BOOST and am using a MATLAB GUI (screenshot attached) to provide inputs such as the port number and maximum detection range. The demo begins once the inputs are provided, and the system visualizes the data accordingly. 

However, I would like to modify the functionality in the code so that, upon powering the AWR1642BOOST, it automatically starts detecting objects within a fixed range, without requiring input through the GUI.

Could you please guide me on how to adjust the code to set a predefined object detection range and ensure that the detection process begins automatically upon powering the device?

Note: your suggested thread is not opening.

e2e.ti.com/.../awrl1432-bsd-demo-v2-2-ghost-object-in-even-frame-if-there-is-moving-object 

Thank you 

Mitesh

Regarding AWR1642 Boost, what does TLV stands for? what does type of data TLV contains ? is there any document I can find the details of TLV in? there is no mention  of 'TLV' in "mmW Demo Data Structure 8_16".pdf.

I sent the wrong link, I have corrected it

TLV is the output detected objects. You can read more about the processing and tlv structure for the outofbox demo which is similar to the srr demo here 

file:///C:/ti/mmwave_sdk_03_06_00_00-LTS/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html

https://www.ti.com/tool/MMWAVE-SDK

Please see the following link on how to bypass CLI

e2e.ti.com/.../ccs-iwr1642boost-how-to-run-independently-from-the-host-computer

e2e.ti.com/.../2744589

I flashed the "srrdemo_16xx.bin" and using AWE1642BOOST"EVM

I modify the code in the mss_main.c to send the data through UART for thepacket .

The below code is modify code to capture the raw data of the SRR.

if(message.body.detObj.tlv[itemIdx].type == 0x01)
{
UART_writePolling (gSrrMSSMCB.loggingUartHandle,
(uint8_t*)SOC_translateAddress(message.body.detObj.tlv[itemIdx].address,
SOC_TranslateAddr_Dir_FROM_OTHER_CPU,NULL),
message.body.detObj.tlv[itemIdx].length);

}

Data for the one packet is :

0100000014000000020007000000290DDEFD0406 C5FA 7E0D FFFE 5406 04000000440000000F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F

Packet Analysis:

Through my analysis, I've identified some parts of the packet:

Type (MMWDEMO_OUTPUT_MSG_DETECTED_POINTS) -01000000

length-14000000

object descriptor (02000700) ----> 0200(number of object) and 0700(xyzOutputQformat)

i think below for the first object

0000-(Don't know)

290D-(Don't know)

DEFD-(Don't know)

0406-( Don't know)

i think below for the second object

C5FA 7E0D FFFE 5406 (" Don't know)

Type- (MMWDEMO_OUTPUT_MSG_AZIMUT_STATIC_HEAT_MAP) - 04000000
440000000F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F

Question: Is the data I identified correct, and could you explain the fields marked as "Don't know"?

Hello, 

you can use the DCA1000+mmwavestudio to capture Raw ADC data. The UART interface is too slow to capture at correct bandwidth, ethernet is used in the DCA1000 capture card

https://www.ti.com/tool/DCA1000EVM

https://www.ti.com/tool/MMWAVE-STUDIO

Hello Zorah Ahmad,

I am tasked with sending radar data to an application microcontroller through UART, where further operations will be performed based on these data.

To proceed effectively, I need to accurately identify each type of data within the packet. I've identified certain sections of the data packet. Could you help me with the parts labeled as 'Don't know'?"

For this purpose, I won’t require the use of the DCA100EVM module.

I would appreciate your assistance in understanding and identifying the packet structure and data of SRR.

Thank you for your support.

"I modify the code in the mss_main.c to send the data through UART for thepacket ." We can't help you with modifications, we only support what is provided in the sdk. You can find the structure of the TLV here 

file:///C:/ti/mmwave_sdk_03_06_00_00-LTS/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html

Hello Ahmad,

Previously, I used the following path as a reference:

"file:///C:/ti/mmwave_sdk_03_06_00_00-LTS/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html"

Based on that, I analyzed a packet from the SRR output without making any modifications to the SRR code.

Here is a sample packet data I captured:

0201040306050807000206038000000042160A00E10E000073E580D4030000000200000000000000010000001C0000000300070000000812A9FE9002000043100702A70500006A10F302A605030000001C00000002000700A8FE8E02000000008C008C001B039005FEFF0100810046000F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0

I've identified most of the fields as follows:

Header Information:

Header start
MAGIC WORD- 0201040306050807
VERSION- 00020603
total packet length-80000000
platform- 42160A00
frame number- E10E0000
time-CPU cycles- 73E580D4
no of detected object- 03000000
no of data structures in package(number of TLV) - 02000000
number of subframe- b00000000
Header complete

Detected Object TLV Information:

type -(MMWDEMO_OUTPUT_MSG_DETECTED_POINTS)-01000000
length- 1C000000
Descriptor-- (number of object)-->0300 xyzQformat--> 0700
for object-1 (0000 0812 A9FE 9002) ----> unknown
for object-2 (0000 4310 0702 A705) ----> unknown
for object-3 (0000 6A10 F302 A605) ----> unknown

type-03000000
length 1C000000
02000700A8FE8E02000000008C008C001B039005FEFF010081004600

padding data (to make the packet multiple of 32 byte)-->0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0

Questions:

1. Have I correctly identified the fields above? If there are any discrepancies, could you please help me verify?

2. Could you provide details about the unknown fields I marked for each detected object? This would help clarify what they represent in the SRR data.

3. Is the packet structure of the SRR output (generated by flashing srrdemo_16xx.bin from ti\radar_toolbox_2_20_00_05\source\ti\examples\ADAS\short_range_radar\prebuilt_binaries\) consistent with the documentation provided by you (file:///C:/ti/mmwave_sdk_03_06_00_00-LTS/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html)

Thank you in advance for your guidance.

Hello, 

Please start a new thread for better resolution of the problem

Hello Ahmad,

you didn't give me the answer of the below my question for that i created this thread.

"How can i modify the object detection range of radar module for "Short Range Radar" by changing the code in the CCS."

for the below questions i will create the new thread.

Questions:
1.Have I correctly identified the fields above? If there are any discrepancies, could you please help me verify?

2.Could you provide details about the unknown fields I marked for each detected object? This would help clarify what they represent in the SRR data.

3. Is the packet structure of the SRR output (generated by flashing srrdemo_16xx.bin from ti\radar_toolbox_2_20_00_05\source\ti\examples\ADAS\short_range_radar\prebuilt_binaries\) consistent with the documentation provided by you (file:///C:/ti/mmwave_sdk_03_06_00_00-LTS/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html)

Thanks 

Mitesh Singh