LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Dependency is broken

I had a working project in LabView FPGA. Including, the firmware from VI FPGA was compiled. However, at one point when I went into FPGA VI, it was broken (screenshot with an error). I am more than sure that nothing The cause of the errors is the fractional interpolation block provided by the LabView developers. How can I fix this error?

0 Kudos
Message 1 of 11
(582 Views)

I had a working project in LabVIEW FPGA. Including, the firmware was compiled from VI FPGA. However, at one point when I went into FPGA VI, it was broken (screenshot with an error). The cause of the errors is the fractional interpolation block provided by the LabView developers, since without it the errors disappear. I am more than sure that I did not change anything in this block, especially since it is protected from changes with a password. How can I fix this error?

0 Kudos
Message 2 of 11
(605 Views)

You're not giving us a lot to go on...

 

Are you opening the VI from the project? I'd expect these errors if you open the VI in LabVIEW without a project, or if you have a project but the VI isn't in the FPGA context.

 

For instance, if you open LabVIEW and open the VI from recent VIs, it will open the VI in 'normal' LabVIEW and a lot of the FPGA stuff will be broken.

0 Kudos
Message 3 of 11
(577 Views)

@BEZENCHUK wrote:

 The cause of the errors is the fractional interpolation block provided by the LabView developers, since without it the errors disappear


I merged your posts.

 

The bold part wasn't in the 1st post.

0 Kudos
Message 4 of 11
(566 Views)

I certainly open FPGA VI in ​​the project. FPGA VI refers to FPGA. Everything worked and I have a working firmware compiled from this VI and I am convinced that I did not change anything and everything broke. But I need to modify this VI further, and I can not do anything because of the error.
At the same time, the interpolator block is password protected from changes.
I believe that for some reason the scope of the labview changed, due to which the dependencies are no longer perceived correctly.

0 Kudos
Message 5 of 11
(499 Views)

Haven't used that... I don't think I can help much with it.

 

I wander what that node is... FPGA (used to) use a lot of xnodes and other magic.

 

The node could break depending on input values (like the value of the clock).

 

There could be a caching problem. As the code is already broken it won't hurt much to clear caches (Tools>Advanced>Clear Compiled Object Caches). AFAIK, This has little to do with FGPA Compilation...

 

Starting with a cleared cache can probably also be achieved by simply copying the project to another location, as (AFAIK) the cache is kept per project path.

Message 6 of 11
(481 Views)

Clearing caches is a good idea. In addition to the VIObjCache, here's another to try deleting:

c:\ProgramData\National Instruments\InstCache

I am also curious what software you have installed and what versions. A while back there was some incompatibility between some different RIO products that were both trying to install this dsp idl and were pulling in different dependency versions. This installation order did the trick in that case: 

"Then I needed to install LV2019 vanilla and ensure that only LV2019 without any libraries was installed. Then I can install all of the libraries except for flexrio, compact rio, and the reconfigurable oscope. Next I need to install the libraries in that order, this is the critical step, they need to be done in that order."

Message 7 of 11
(470 Views)

Unfortunately, it didn't help.

0 Kudos
Message 8 of 11
(429 Views)

after clearing the cache using your method and the method suggested in the previous answer, the error did not disappear. Copying the project to another location did not help either.
I have LabView 2021 installed, as well as libraries NI USRP and Modulation Toolkit.

Everything worked before this error.

0 Kudos
Message 9 of 11
(427 Views)

What version of usrp and the modulation toolkit?

Any other RIO drivers installed such as FlexRIO?

At what point did the error start occurring - as in what changed?

Check for the presence of this registry entry:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer

NIPUBDOCSDIR

Expected string value: C:\Users\Public\Documents\National Instruments\
regentryMightBeMissing.png

If it is not present, try adding it and restarting labview.

Message 10 of 11
(421 Views)