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.

awr1243+tsw1400

Other Parts Discussed in Thread: AWR1243
Hello everyone! When using awr1243 + devpack + tsw1400 to collect data, if 5 frames are set, is there a continuous interval or a time interval between each two frames? If there is a time interval, how can this time interval be measured?
  • 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,

    I used awr1243 + devpack + tsw1400 to successfully collect the data, but I have the following questions, can you help me?
    I learned from the manual that the time limit for TSW1400 to collect data is 10s, but when I set the frame number to 500 and the frame period to 20ms (the data collection time is 10s), the collection error is reported, and when I change the frame number to 400, The frame period remains unchanged, and the acquisition still reports errors. I changed the number of frames to 200, and the frame period is unchanged. At this time, the data can be collected smoothly, and the theoretical time at this time is 200 * 20ms = 4s, which is far less than 10s. What is going on? When I successfully collected data, I recorded the running time of HSDC pro, which is roughly 90s, which is much larger than the theoretical 10s. I am very confused and need your help, thank you very much!

  • 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.

    Thank you very much for your answers, I understand. In addition, I would like to ask when the theoretical collection time of 200 frames * 20ms = 4s, the actual HSDC pro or the entire awr1243 + devpack + tsw1400 collection system has been running for a long time, about 2 minutes( The real situation of my experiment), what is the matter ? Is it because it contains other time like data processing?If yes, may I ask whether to collect the data once or collect the data at once, and the remaining time is used for processing? Or what other way?
  • 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

  • Hello,Ishita
    Suppose I set 400frames * 20ms = 8s data collection. When actually collecting the data, is the 8s data collected at one time and then processed? Still collect 2s (assuming) first and then process 2s and then process again, and so on.
  • 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

  • of course.
    Thank you very much for your questions and answers. I have benefited a lot from communicating with you and wish you a happy life!
  • Hello,Ishita

    Unfortunately, I encountered another problem, this is the case. When I click the set button in the Frame column after setting the mmWave Studio--SensorConfig--frame, the following error will be reported occasionally, causing subsequent data collection to fail. Please help me to check. (The other previous operations are displayed without problems)
    [09:59:41]  Test Source Already Disabled...!!!
    [09:59:41]  [RadarAPI]: ar1.DisableTestSource(0)
    [09:59:41]  [RadarAPI]: Status: Passed
    [09:59:41]  [RadarAPI]: ar1.FrameConfig(0, 0, 20, 128, 40, 0, 0, 1)
    [09:59:41]  [RadarAPI]: Status: Passed
  • 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.

    Sorry, I found that the last problem is normal, because I did another experiment and showed the same problem, but the data can be collected smoothly.
    I took a screenshot of the output display of a successful data collection and marked the point where I want to ask a question. When everything is ready, I click the Trigger Frame button, and after a few seconds (8s), the Frame Ended pops up in the output window. I would like to ask, does this mean that my data collection is completed? That is to say, all my pulses have been transmitted, and then no more signals will be transmitted, but only data processing. Then after a long time (2min), the output window pops up Tsw1400 capture complete, which means that the data processing is completed, is my understanding correct?
  • 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

  • Thank you very much,Ishita.
    Your reply answers many of my questions. I am grateful. The picture may not be put because of the wrong format, but this is not important. Even if there is no picture, you still gave me the answer I want. Thank you again and wish you a happy life!
  • 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

    I plan to start with a DCA1000 EVM. If I encounter any problems in the future, I will ask you again and wish you a happy life!