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.

IWR6843AOP + DCA1000EVM "No LVDS Data"

Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: DCA1000EVM, IWR6843AOP, IWR6843, MMWAVEICBOOST

I want collect raw data from DCA1000EVM with IWR6843AOP. when I try CLI command I got No LVDS Data. Can you help me with this please?


Wed Aug 03 13:25:38 2022
FPGA Configuration Command (req)

Wed Aug 03 13:25:38 2022
FPGA Configuration command : Success

Wed Aug 03 13:25:38 2022
Return status : 0

Wed Aug 03 13:25:53 2022
EEPROM Configuration Command (req)

Wed Aug 03 13:25:53 2022
EEPROM Configuration command : Success

Wed Aug 03 13:25:53 2022
Return status : 0

Wed Aug 03 13:26:05 2022
Start Record Command (req)

Wed Aug 03 13:26:05 2022
Start Record Command (req)

Wed Aug 03 13:26:05 2022
Start Record command : Success

Wed Aug 03 13:26:05 2022
Return status : 0

Wed Aug 03 13:26:06 2022
Start Record command : Success

Wed Aug 03 13:26:26 2022
Read Record Process Status (req)

Wed Aug 03 13:26:26 2022
Record is in progress. [status -4029]

Wed Aug 03 13:26:35 2022
No LVDS data

Wed Aug 03 13:26:35 2022
Record stop is done successfully

Wed Aug 03 13:26:45 2022
Read Record Process Status (req)

Wed Aug 03 13:26:45 2022
No record process is running. [error -4002]

Wed Aug 03 13:27:53 2022
Read Record Process Status (req)

Wed Aug 03 13:27:53 2022
No record process is running. [error -4002]

Wed Aug 03 13:27:56 2022
Start Record Command (req)

Wed Aug 03 13:27:56 2022
Start Record Command (req)

Wed Aug 03 13:27:56 2022
Start Record command : Success

Wed Aug 03 13:27:56 2022
Return status : 0

Wed Aug 03 13:27:57 2022
Start Record command : Success

Wed Aug 03 13:28:04 2022
Read Record Process Status (req)

Wed Aug 03 13:28:04 2022
Record is in progress. [status -4029]

Wed Aug 03 13:28:26 2022
No LVDS data

Wed Aug 03 13:28:27 2022
Record stop is done successfully

Wed Aug 03 13:29:53 2022
Read Record Process Status (req)

Wed Aug 03 13:29:53 2022
No record process is running. [error -4002]

Wed Aug 03 13:29:57 2022
Start Record Command (req)

Wed Aug 03 13:29:58 2022
Start Record Command (req)

Wed Aug 03 13:29:58 2022
Start Record command : Success

Wed Aug 03 13:29:58 2022
Return status : 0

Wed Aug 03 13:29:58 2022
Start Record command : Success

  • Hello,

    Please take a look at this E2E thread and the threads linked within it. There you should find your solution. Also make sure everything is correct in the DCA1000 guide linked there as well.

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1012318/iwr6843aopevm-no-lvds-data-with-mmwavestudio

    Best Regards,

    Pedrhom Nafisi

  • Dear Pedrhom,

    Thank you for your response on it. I tried with mmwave studio it's work and I'm able to collect .bin file but I want to use CLI_command which gives me again the same error of " NO LVDS DATA" and I saw a red light on the DCA1000 board, which is on the LVDS_PATH_ERR and HDR_ERR. 

    I hope you understand my question.

    regards, 

    Fahad

  • Hello Fahad,

    I understand, let me look into this further with a specific focus on CLI commands. In the meantime double check the thread below and see if the feedback and document was of any help to you.

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/854734/dca1000evm-no-lvds-data-captured

    Best Regards,

    Pedrhom Nafisi

  • Thank you for looking at it. But I'm confused and don't know what to do. When I start OOB demo visualizer and radar starts capturing and sense the user, so how at the same time I can collect the raw Data from it and save into my pc? By using Mmwave studio or CLI command. but Mmwave studio does not work when radar is in capturing or running phase. So how I can collect raw data.

    Thank you

    Regards,

    Fahad

  • Hello Fahad,

    Have you checked the DCA1000 CLI command user guide? I want to make sure you have fully went through this document in order to see if your problem. 

    4721.TI_DCA1000EVM_CLI_Software_UserGuide.pdf

    Also I want to add, when you are streaming raw data via the DCA1000, you are basically directly transmitting the data which is collected by the ADC's and skipping any processing that would normally be done on the MCU and DSP which are built into the IWR6843. When we talk about a lab/demo (ie Out of Box demo in this case), this is really just a Software image which is ran on the MCU and DSP which captures the data, runs digital signal processing, and outputs some form of processed data (such as a point cloud). Since you are skipping all this processing when doing Raw Data capture, it kind of takes the identity away from the lab, since the raw data will look the same regardless of which demo is on the device.

    Raw data collection requires the DCA1000 + mmWaveStudio setup.

    Best Regards,

    Pedrhom Nafisi

  • Hello Pedrhom,

    Yes, I fully checked with document. But can you explain these things to me please.

    "If there is no LVDS data from RADAR EVM, after configured timeout seconds CLI would display “No LVDS data”. User must ensure the proper DCA1000EVM FPGA configuration and can restart the capture. This occurs if the xWR1xxx EVM is not sending LVDS data to the DCA1000EVM. Check whether the radar EVM is configured and enabled to send data. Check that the cabling assembly is correct between the xWR1xxx EVM and the DCA1000EVM."

    Can you explain this to me please. Yes I'm using mmWave studio as mentioned above that I'm able to get raw data in offline mode through mmwave studio but problem is when I start lab/demo (out of box demo) so in the same time mmwave studio was not working. Because I want to capture raw data in the same time as lab/demo was start. And also problem with CLI as well.

     Best wishes,

    Fahad

  • Hello Fahad,

    You are not able to run the out of box demo at the same time as recording raw data. It does not matter what lab/binary you flash your EVM, the raw data will be the same. That is why it is raw data, it is because it is the data before and post processing that is done to show the results seen across all of our demos. If you want the output of the out of box demo, you can check this document which explains the OOB demo UART output. TIREX also shows how to send CLI commands via UART if that is what you are trying to do.

    https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.12.0&node=AMX8iSNi68MrahObN703AQ__VLyFKFf__4.12.0

    Best Regards,

    Pedrhom Nafisi

  • Dear Pedrhom,

    Thank you for helping me in this case. Actually I want to capture and stored Raw data from any lab/demo which I run with DCA1000. Now can you help me how I can do that with mmwave studio. How I can collect raw data when I run a lab/demo for 10 minutes. Also How I can use CLI command to save the same data without using mmwave studio. whenever I trigger frame after DCA1000 arm I got only 2 sec of data everytime. but my lab/demo ran for 10 mins. 

    I hope you understand this.

    Regards,

    Fahad

  • Hello Fahad,

    To be very clear: the lab that you are running, or any lab that is ran, has no impact on the raw data. It is for this reason that all DCA1000 activities use the same RF evaluation firmware provided with mmWaveStudio.

    It would be extremely difficulty to add LVDS on top of the UART channel, and you would have to remove one of the channels currently implemented in order to manually add LVDS.

    Also, if you were to add LVDS there would be a high chance of there not be enough cycles to maintain the core functionality of outputting data.

    Best Regards,

    Pedrhom Nafisi

  • Dear Pedrhom,

    This all confused me more. Simple question is that how I can capture or stored raw data from any lab/demo by using DCA1000 and saved into my PC a csv file. Also by CLI command as well.

    Thank you very much.

    Regards,

    Fahad

  • Hello Fahad,

    Is there a reason you specifically want RAW data rather than regular UART data output from the sensor? Raw data will look like the picture below

    While UART data will come as strings formatted into a structure known as a TLV (Type, Length, Value). You can easily get information such as location in a point cloud, angle, doppler, and more in a string which requires no post processing and then you can do whatever you'd like with the string outputs. For example the below is the TLV output which is an array of all points in a point cloud.

    Best Regards,

    Pedrhom Nafisi

  • Thank you so much for the clarification. Kindly help me how I can collect Both RAW and UART data, because I will also do some signal processing and machine learning for my own work.

    Kind regards,

    Fahad

  • Everytime I collect data through DCA1000 it gives me same log file with same bin file size.

  • Hello Fahad,

    For UART data, you can learn via the Out of Box demo within TI's mmWave Industrial Toolbox. It will have a developers section and your area of interest will be TLVs. For your DCA1000 issue, have you tried running one of the premade scripts located within this directory: C:\ti\mmwave_studio_02_01_01_00\mmWaveStudio\Scripts

    Best Regards,

    Pedrhom Nafisi

  • Hello Pedrhom,

    Sorry to bother you again but I don't know when I got the solution. But please help me with this why I got all the time only 2 sec of data with different packet Id when I change the parameters in sensor config section. But the duration was always 2 sec while the lab/demo ran for 10 mins. When i stop the lab and then connect DCA1000 for data storing and Trigger frame I got the same 2 sec of data.

     please help me in this regard.

    Fahad

  • Hello Fahad,

    How many frames do you have set in the frame configuration window in mmWaveStudio? The run duration is completely dependent on the number of frames you have set in frame configuration, so changing this will change it to be longer than 2 seconds.

    Best Regards,

    Pedrhom Nafisi

  • Brother I'm too much confused about the whole thing. I want to run vital sign lab/demo for 10 mins and collect raw data for 10 mins as well with mmwave studio or without mmwave studio by using CLI command. But don't know it works in mmwave studio but not in CLI base.

    thank you

  • Increasing the number highlighted in your screenshot will increase your duration. For vital signs you should follow the user guide within the Industrial Toolbox for mmWave sensors and for data you can look through the developer's section on how you can add code to do what ever you want with the incoming data, even if it is as simple as printing it to console and then saving that as a sort of "log". The CLI commands is every line in a .cfg file. You are able to send them one by one in a TeraTerm environment if you'd like, but all these applications such as mmWaveStudio and the Toolbox Visualizer do is send the commands upon giving it the file or setting your options. I hope that helps clear things up at least a little bit.

    Best Regards,

    Pedrhom Nafisi

  • Yes, I understand little bit now. But tell me one thing when I start vital sign demo for 10 mins so how I can relate this 10 mins data with the mmwave studio raw data. if I increase the Frame number. And one other thing is there any documentation in which there is explanation about lab/demo with mmwave studio or CLI detials.

    Kind regards,

    Fahad

  • What you can do is run the Vital Signs demo for however long you want, add code via Code Composer Studio to export the incoming TLV data in whatever format you want, and then run the DCA1000 and decode the bin file to see the raw data of the sensor. This will allow you to see what the data looks like pre and post processing. All and any documentation we have can be found on the Industrial Toolbox for mmWave Sensors.

    Best Regards,

    Pedrhom Nafisi

  • Dear Pedrhom,

    Thank you for your response. Please clarify me these things.

    > "add code via Code Composer Studio to export the incoming TLV data in whatever format you want". What type of code you talked about the same as we do to create .xer47 or .bin file like building the project or the code is something else.

    >"then run the DCA1000 and decode the bin file to see the raw data of the sensor". As you know that both demo and DCA1000 cannot work at the same time then how I run DCA1000? Please tell me as well about the decode process. 

    Kind Regards,

    Fahad

  • Hello Fahad,

    > "add code via Code Composer Studio to export the incoming TLV data in whatever format you want". What type of code you talked about the same as we do to create .xer47 or .bin file like building the project or the code is something else.

    There are multiple ways you can export the data. For example you can add code to mss_main.c which can print whatever sensor data you want like the point cloud to console and then you could save the console as a log. Or you can read the data via UART and a good example will be the python Visualizer we have provided the source code for within Industrial Toolbox for mmWave Sensors version 4.12. within the tools folder. You can go through the python source code, especially gui_main.py, and see how we read and use the incoming data there such as point cloud, number of tracks, vital signs, etc.

    >"then run the DCA1000 and decode the bin file to see the raw data of the sensor". As you know that both demo and DCA1000 cannot work at the same time then how I run DCA1000? Please tell me as well about the decode process. 

    You are correct in which you cannot run both simultaneously. You are asking how you can relate DCA1000 data which has no post processing, with data that comes in from a lab which has post processing. You would do this by recording the data one at a time while not changing the environment that you are recording. Run the lab with whatever setting/environment you want, save that data, change nothing with physically such as object locations, then record the same thing but with the DCA1000 to get raw, unfiltered data. This will allow you to get an idea of what the post processing algorithms do to that data. At the end of the DCA1000 user guide is a section on how to read the raw data's formatting

    Best Regards,

    Pedrhom Nafisi

  • Hello Pedrhom,

    Sorry for being late. Thank you for helping me out. 

    >"There are multiple ways you can export the data. For example you can add code to mss_main.c which can print whatever sensor data you want like the point cloud to console and then you could save the console as a log. Or you can read the data via UART". Can you explain it clearly with example please?

    >"then record the same thing but with the DCA1000 to get raw, unfiltered data" How is it possible to record with DCA1000 if the radar is not working at the same time please explain?

    Thank you

    Kind regards,
    Fahad

  • Hello Fahad,

    >"There are multiple ways you can export the data. For example you can add code to mss_main.c which can print whatever sensor data you want like the point cloud to console and then you could save the console as a log. Or you can read the data via UART". Can you explain it clearly with example please?

    For example, within any lab's main.c, you can find any place that data is being worked with such as the method MmwDemo_handleObjectDetResult within Out of Box demo's main.c, and just put print statements around whatever data you want to collect from what detected object parameters offer.

    >"then record the same thing but with the DCA1000 to get raw, unfiltered data" How is it possible to record with DCA1000 if the radar is not working at the same time please explain?

    I think you are confused on the relation between raw data that comes from the sensor being on and recorded with the DCA1000 which is sent to your computer versus the sensor being on and post-processed data that is sent by the sensor via demos/UART to your computer. The raw data that comes from a DCA1000 returns every possible piece of information it acquires in it's uncompressed form. This is why the DCA1000 requires an Ethernet cable for data transfer because there is so much data coming out of the sensor when recording its raw form that USB data transfer speeds are not good enough. When you look at data from a lab/demo, the sensor does a heavy amount of post-processing and removal of extraneous information to only give the user what they need such as point cloud information, elevation, doppler, SNR, etc. All this data was once in its raw form, which is very large and what the DCA1000 outputs, and then sensor outputs only some of the relevant information, which is much smaller and compressed so that it can be sent via USB and read in comprehendible string integer formats.

    I hope that helps.

    Best Regards,

    Pedrhom Nafisi

  • Hello Pedrhom,

    it's becoming more confusing. 

    Lets make it more easier and clearer. I want to collect data from sensor i.e., raw and processed both. when I run lab/demo of 3D people counting by using IWR6843AOP + MMwaveicboost + DCA1000EVM. So what are the procedures and protocols that I follow to collect. What are the stages and How I can save it in my PC.

    Thank you.

    Fahad

  • Hi Fahad,

    The labs in the mmWave Industrial Toolbox do not support the capture of Raw Data while the demo is running. This is due to processing limitations. I would recommend you capture Raw Data and the Processed data separately in order to accomplish your goals.

    Best Regards,
    Alec

  • Hi Alec,

    Thank you for your response on it. Can you please help me in this that how I can do that to capture Raw Radar Data and the processed data separately and how I can save both data on my PC.

    Thank you

    Fahad

  • Hello Fahad,

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1030539/iwr6843aopevm-how-to-save-the-processed-data-of-iwr6843aop-evm-from-pc-side

    This can tell you how to save processed data. And the DCA1000 User guide tells you how to save raw data to a binary file.

    Best Regards,

    Pedrhom Nafisi

  • Thank you for helping me out. one last question is that can you please share with me MATLAB script for reading and saving the binary bitstream of the UART data into .csv or .mat file. As one I found in pdf file but it is not working properly.

    Regards,

    Fahad

  • Hello Fahad,

    Within mmWaveStudio the directory, we have a Matlab example of turning a .bin output file into a .mat one. You can use the readme.txt in this folder to get started

    C:\ti\mmwave_studio_02_01_01_00\mmWaveStudio\MatlabExamples\singlechip_raw_data_reader_example

    Best Regards,

    Pedrhom Nafisi

  • Dear Pedrhom,

    Thank you for your response. I looked at this but I got some error I don't know how to solve and I didn't get to it.

    "

    Not enough input arguments.

    Error in rawDataReader (line 160)
    dp_exportData(rawDataFileName, radarCubeDataFileName);

    "

    Kind regards,

    Fahad

  • Dear Pedrhom, 

    Is there any script like the one in vital sign/parse folder which gives the data in .csv file with features in column of .csv file as shown below..

    Kind regards,

    Fahad

  • Hello Fahad,

    We do not have a DCA1000 script that formats the output as shown above, you would have to make it yourself.

    Best Regards,

    Pedrhom Nafisi

  • So How I can ellaborate the data if I got different number of rows and columns. Once I capture the 3D people counting lab/demo so, How to identify the actual raw data and to give header names?

    Thank you

    Fahad

  • Hello Fahad,

    Raw data will naturally have different output values because there is no post-processing on it and so you get the nth in-phase sample corresponding to kth RX channel (RxkIn). One chirp of raw data can be related to one frame of post processed data, and the notation of the DCA1000 output is at the bottom of the user guide. What you compare between the two is up to you.

    Best Regards,

    Pedrhom Nafisi