Spaces:
Sleeping
Sleeping
| Ticket Name: TDA2SX: Angle Finding radar VSDK use case? | |
| Query Text: | |
| Part Number: TDA2SX Other Parts Discussed in Thread: TDA2, AWR1243 How to customize use case with our angle finding technique for cascade TDA2 EVM? Is modifying the beam forming use case the right place to start? Is there a better choice use case for angle finding or maybe we should look at creating a new custom use case? | |
| Responses: | |
| Hi Zach, Are you using MIMO or beamforming for getting the angle of arrival? You can create your own usecase using the TI out of box usecases as a reference. Thanks and Regards, Piyali | |
| Hi Piyali, We are using MIMO. Thanks and Regards, -Zach | |
| Zach We have a MIMO usecase which is part of the SDK. You can use this as a reference. Thanks and Regards Piyali | |
| We have cascade needed as well. We are expanding the 4 AWR1243 cascade to 8 AWR1243. How do I go about identify and quantify the changes need to get to 8 AWR1243 on TDA2s with one AWR1243 master? Which it the "MIMO" use case? | |
| ***correction*** 8 AWR1243, 2 TDAs, one master AWR1243 | |
| cascade_radar_object_detect is the MIMO usecase. If each AWR1243 would have its own TDA software, you would not need to change the number of AWR1243 for each TDA. Chirp configs would only need to be in sync. | |
| Where is the chirp config that gets used by FxObAoA? Looks like a it read from a file handle. I don't see where this file name string and directory get set. So we can review the chirp setting in the use case. | |
| Where can I see and modify the chirp ramp scenario please? | |
| Hi Zach, There is a default chirp config built into the code in PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\apps\src\rtos\radar\src\common\chains_common_cascade_ar12xx_config_mimo.c The one you see with the file read is searching for a folder with the below name: #define RADAR_CONFIG_PARAM_DIR_NAME "radar_test_vector/" Kindly go through the section: 3.9.1.6.3 File-based Use Case Configuration Support in the file : PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\docs\Radar\ProcessorSDKRadar_UserGuide.pdf You can change the chirp configurations from the files in radar_test_vector under PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\apps\src\rtos\radar\src\usecases\cascade_radar_object_detect and put this folder in an SD card to be plugged into the board. Thanks and Regards, Piyali | |
| For "Control Calibration" file in 3.9.1.6.1 4 AWR1243 Capture + Radar Object Detect (DSP) (MIMO) + Null from PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\docs\Radar\ProcessorSDKRadar_UserGuide.pdf : "For Control Calibration, the Calibration is sent out over Ethernet to the Matlab tool. This is saved as a CC.mat file. Once this file is generated you need to run vision_sdk\apps\src\rtos\radar\src\usecases\cascade_radar_object_detect\create_calib_coefs.m to finally create the SD card based coefficients and then copy this over to the SD card for the next run." Where do I find more information about generating this CC.mat file and it's format? | |
| Zach You can refer to the end of the section 4.2 Data Flow of the vision_sdk\docs\Radar\ProcessorSDKRadar_DataSheet.pdf. You can look at the MATLAB scripts for more details for the format. Thanks and Regards, Piyali | |