• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 30 subscribers
  • Views 277 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DCA1000EVM: Raw data capture

S M Yahea Mahbub
Prodigy 80 points
Part Number: DCA1000EVM
Other Parts Discussed in Thread: IWR6843AOPEVM

Hello

I am using IWR6843AOPEVM with DCA1000 to capture raw data. My setup is for SAR imaging and it takes around 65-70 minutes to finish 300-350 steps to capture and produce bin files. I make sure that the DCA1000 gets sufficient time (5-7 seconds) to capture and save the bin files at each step. However, there are a lot of occasions I got empty bin files. What seems to be the issue?

Thank you.

Yahea

  • 0
    TI__Genius 16857 points

    Hello Yahea,

    Can you send me the log of your Output tab within mmWaveStudio when you try to capture so that I can see what exactly the error or issue could be?

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 80 points

    Hello Pedrhom

    I have looked at the outputs at the mmWavestudio. When there is a blank bin file produced, it says "No LVDS data" at the output tab of the mmWavestudio. I was looping for 200 data collecting steps, it worked for the first 24 steps, problems start at the 25th, and afterward, it's all blank.

    Previously I have taken raw data at 350 data points in the same setup successfully. All of a sudden it starts having issues. I have attached a picture of the output tab for your convenience.

    Thank you.

    Yahea

  • 0 in reply to S M Yahea Mahbub
    TI__Genius 16857 points

    Hello Yahea,

    No LVDS data is unfortunately a common error in mmWaveStudio and can be caused by a few different things. What power supply are you using for the DCA1000? We recommend 5V 3A, especially for capturing 6843 raw data as it is a higher power and processing requirement device. Are you also saying that the first few steps do NOT say No LVDS data and then after the 25th it starts printing this?

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 80 points

    I am using a 5V 3A adaptor. Yes, last time the issue popped up at the 25th step, however, it's random when the problem will start. I had problems pop up at different stages like 37th, 45th, etc. Previously I have successfully completed up to 350 steps with my very setup without any issues. There are no issues with the connections and DCA1000 setup, they are working perfectly, I have re-checked everything. I have a cooling fan for the 6843 EVM as well.

    I already have replaced the 6843 EVM, but no luck. I do not have a spare DCA1000 that I can try with. You said there are a few different things that can cause the issue, could you please be a little more specific so that I can address and solve the issue?

    Thank you.

  • 0 in reply to S M Yahea Mahbub
    TI__Genius 16857 points

    Hello,

    A few things you can try that have been confirmed to fix No LVDS data error in people's setup.

    • Change USB cables
    • Change Ethernet cable (I have personally ran into this one)
    • Directly connect cables to the computer, no usage of docks or USB expansion hubs.
    • Reflashing of the FPGA firmeware to the DCA1000. Instructions can be found in the DCA1000 PDF User Guide starting on page 22
    • Turning off Windows Firewall

    Usually the behavior I see is that it will say No LVDS data right from the beginning, your case is very unique where it is stopping early on. It could potentially be your chirp configuration being too demanding which causes the mmWave Sensor to crash.

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 80 points

    I am using the simplest chirp config.

  • 0 in reply to S M Yahea Mahbub
    TI__Genius 16857 points

    No LVDS Data error is not usually related to chirp config, but core hardware or firmware issues

    Best Regards,

    Pedrhom