Other Parts Discussed in Thread: MMWCAS-DSP-EVM, , TDA2, AWR2243, AWR1243
Hello,
We have purchased the MMWCAS-DSP-EVM and the MMWCAS-RF-EVM, and are having issues configuring the device for our purposes. We would like to have the module periodically (say, once every minute) perform a data capture and dump the data to a server connected via ethernet. We then need to be able to parse the dumped data to generate a point cloud for further processing. We would like to have our own application recieve the data and perform the necessary processing, rather than using mmWave Studio or the provided Matlab scripts.
We have been able to successfully run the provided demos in mmWave Studio for the MIMO and BF usecases via modified Lua scripts, and have also been able to capture data by manually selecting a usecase via ssh and running the cascade_MIMO_signalProcessing and radar_cascade_demo Matlab scripts. In both cases, we are able to see the generated .bin and .idx files captured on the ssd. However, these demos do not help us understand how we should design our application to utiize this EVM. So, my questions are:
1) Is there a way to automate the process of configuring the EVM and performing a capture from the server side only? If there are relevant files in the Processor-SDK-Radar package that we would possibly need to integrate into our application to do this, can you point us to them? It seems like there should be some standard controls that we can issue via socket to configure our chirps/frames, start a capture, and dump the data.
2a) From looking at the Matlab scripts provided, it does not look like Matlab is using the .bin and .idx files. Is there any documentation pointing to what data Matlab is receiving, and how it is formatted?
2b) From the mmWave Studio demos, the .bin and .idx files must be transferred to the host machine before post-processing can be done. This must mean that we can generate our desired point cloud without using mmWave Studio if we were to know how to extract the needed data from these files. Is there any documentation detailing the structure of these files?
Thanks,
Clark