This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
The time interval between two consecutive frames is termed as Inter-frame time and it is derived from the chirp parameters you've programmed. Below is the formula to calculate this:
Inter-frame time = Frame time - (Ramp end time + Chirp Idle time) * Total number of chirps
Regards,
Ishita
Hello,
Hi,
Actually 10 seconds is just not attributed to the frame period, time starts as soon as you click the "TSW1400 ARM" button. After that, when you actually click the "trigger frame" button, some time has already passed, which is why you're not able to capture 500/400 frames. The capture threshold of TSW1400 is limited by this time of 10 seconds or 1GB memory (whichever fills out first). In your case, the time goes out first.
To capture maximum frames in this time interval, you can make a script which would reduce the time delay between the ARM button and the triggering of frames, OR I would recommend you to use DCA1000 if you want to capture a large number of frames.
Regards,
Ishita
Hello,Ishita.
Yes, you are right, HSDC Pro takes time in processing the captured data and displaying it on the screen. It includes both the time of capturing and processing the data at once.
I hope I was able to answer your query, if you need any more clarifications, please feel free to ask.
Regards,
Ishita
Hi,
Yes, the entire data is collected first and only then processed. So in this case, 8 seconds worth of frame data would be collected all at once.
May I understand what are you trying to do?
Regards,
Ishita
Hello,Ishita
Hi,
I'm not able to understand the error you encountered. From your output log, I can see the frame configuration was successful. Are you seeing an error after this?
Could you send a screenshot of the error?
Regards,
Ishita
Hello,Ishita.
Hello,
Yes, you are right, once you get an async event in the mmwave studio output window saying that frames have ended, it means that all the chirp data have been captured. The ADC data from AWR1243 is received by TSW1400 over the LVDS interface, so there might be a slight overhead because of that as well. Although, 2 mins is a long time, we haven't seen that as of now. Can you check this on a different machine as well?
Also, I'm not able to see the picture you've attached. Could you add it again?
Regards,
Ishita
Hello,Ishita
I'm sorry to disturb you again. Due to the limitation of data collection by TSW1400, I would like to ask, besides DCA1000, are there other boards that can be used with awr1243 to collect data continuously for a long time? For example, is TDA2x ok?
Hi,
Yes you can use TDA to capture data, but TI doesn't offer that, so you would have to build your own solution
Regards,
Ishita
Okay, you mean building your own solution means that there is no well-designed hardware connection method and no corresponding software matching. These have to be designed by yourself, including some code for connection and data acquisition, etc. Is my understanding correct ? (Together, it is achievable, but it is quite difficult to achieve)
Hello,
Yes, you are right, TI doesn't provide the hardware and software support for capturing single chip data using TDA. Although we do provide TDA support in case of cascade devices but not single chip.
Regards,
Ishita
Thank you very much,Ishita