cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
tasker.j
Contributor
Contributor
975 Views
Registered: ‎10-23-2018

ZCU111 RFSoc TRD - LVM File Version Error

Jump to solution

Hi,

I'm trying to load a LVM file that I created using lab view to the DAC for playback, but I'm getting a "File Version not compatible:" error when I load the file.  Screen shot of error is below and the lvm file I am loading is attached.  Thanks in advance.

rfdc_gui_lvm_error.jpg

Tags (4)
0 Kudos
Reply
1 Solution

Accepted Solutions
travisc
Moderator
Moderator
918 Views
Registered: ‎10-19-2011

Are you using a converter, or just a direct export for the LVM file? Below is a guide on the LVM format and working with our TRD tool.

 

http://www.xilinx.com/support/answers/71687.htm

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

3 Replies
travisc
Moderator
Moderator
919 Views
Registered: ‎10-19-2011

Are you using a converter, or just a direct export for the LVM file? Below is a guide on the LVM format and working with our TRD tool.

 

http://www.xilinx.com/support/answers/71687.htm

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

tasker.j
Contributor
Contributor
910 Views
Registered: ‎10-23-2018

Hi @travisc,

Thanks for the reply but unfortunately I've already spent some time reviewing the provided link and have verified that the attached lvm file matches the settings in the provided document ("RF Data Converter Evaluation GUI file support".

I'm exporting the information directly from LabView in the LVM format. Any other ideas? What versioning is the GUI checking to get this error? Or is this just a general error with the file format?  

Thanks again as I am still searching for a solution.

-Jim

0 Kudos
Reply
tasker.j
Contributor
Contributor
895 Views
Registered: ‎10-23-2018

HI again @travisc,

I re-read the link that you sent and the documents and found that the file had to have a Version of 1.2.0 in the special header section.  It now works as expected.  Thank you for your time.

0 Kudos
Reply