topic Re: Opening VI problem in LabVIEW

Opining VI problem

Mustafasei — Tue, 08 Nov 2016 16:41:07 GMT

When I download any VI from internet and i want to open it from my PC whith labview 2013 i 'm always got these screen as attacvhed which repeated for many times and finally when the VI opend it has no compelte diagram inside

any advice please

Re: Opining VI problem

altenbach — Tue, 08 Nov 2016 16:50:16 GMT

Maybe you need to install some toolkits, e.g. LINX

Re: Opening VI problem

RavensFan — Tue, 08 Nov 2016 16:52:24 GMT

What does you mean by "no complete diagram"? Half of it is missing? Or that there are subVI's it can't find and are replaced by ? marks.

It is looking for the file listed in the dialog box and can't find it. Do youi have the \LabVIEW Hacker\LINX directory installed on your PC? It is probably downloaded from the web.

Re: Opening VI problem

Mustafasei — Tue, 08 Nov 2016 18:15:12 GMT

I mean by diagaram is some logic gates not wired or unknown function blocks

i already install the LINX firmware and its directory because i dont have any problem when I open labview linx examples.

any idea

Re: Opening VI problem

RavensFan — Tue, 08 Nov 2016 18:32:37 GMT

"LabVIEW Hacker" is a very odd sounding install directory. So you may have installed them in a normal directory, but the original creator had their subVI's installed in the odd "LabVIEW Hacker" directory which doesn't exist on your machine, and your machine may not have the library in its search path.

Do you have the Digital Read.VI some within the path your LINX was installed to? If so, when it gets done searching and can't find it, browse that file dialog box to the directory with the LVH-LINX.lvlib file in it. Once it finds it and connects to it, everything should be fine. Be sure to save that VI before closing so it remembers the location of the subVI in your new correct location.

Re: Opening VI problem

Ascona1988 — Tue, 08 Nov 2016 19:06:18 GMT

This happens only when I download vi from internet and save it into my pc on desktop or any place.

So please what shall i have to do to prevent this happned

Re: Opening VI problem

RavensFan — Tue, 08 Nov 2016 19:43:02 GMT

There's nothing you can do. Issue was caused by the person who created the original VI you downloaded. They installed their libraries to a different place than you did.

Just make sure you installed the toolkit libraries to their standard install directory.

Once you fix the downloaded VI's, then be sure to save the updated version.

Re: Opening VI problem

crossrulz — Tue, 08 Nov 2016 20:11:14 GMT

Mustafasei wrote: i already install the LINX firmware and its directory because i dont have any problem when I open labview linx examples.

How did you install LINX? Did you use VIPM to install the package? Or did you just copy the library to some arbitrary directory?

My guess is that you did the later, which means you are the odd one. Install LINX properly with VIPM.

Re: Opening VI problem

Ascona1988 — Tue, 08 Nov 2016 20:40:10 GMT

I install the linx by VIPM

Re: Opening VI problem

RavensFan — Tue, 08 Nov 2016 20:52:35 GMT

My guess is that whoever made the original VI being downloaded is the one who installed in the odd directory and did not use VIPM because the VI is looking for those VI's in "C:\LabVIEW Hacker" which is a very oddly named directory, plus the fact it is in the root drive, to have be the intended install directory.

Re: Opening VI problem

crossrulz — Tue, 08 Nov 2016 21:14:52 GMT

@RavensFan wrote:
because the VI is looking for those VI's in "C:\LabVIEW Hacker" which is a very oddly named directory, plus the fact it is in the root drive, to have be the intended install directory.

The screenshot in the original post is looking for a VI in <vi.lib>\LabVIEW Hacker, which I am fairly certain is where it is supposed to be.

Re: Opining VI problem

altenbach — Tue, 08 Nov 2016 21:55:41 GMT

I assume you are using LabVIEW 2013 32bit. Are you?

Have you looked at this FAQ entry? Certain features require at least LabVIEW 2014.

Re: Opining VI problem

Mustafasei — Wed, 09 Nov 2016 16:30:15 GMT

Yes I'm using 2013.

so what I suppose to do now?

Re: Opining VI problem

altenbach — Wed, 09 Nov 2016 17:10:01 GMT

You already said that you are using 2013. The question is if you are trying to do something with

Arduino/chipkit (supported on 2013) or...
beaglebone/raspberry (not supported in 2013, requires 2014).

What hardware are you trying to use and what hardware is the target for your example programs?

Re: Opening VI problem

RavensFan — Wed, 09 Nov 2016 18:36:49 GMT

@crossrulz wrote:
@RavensFan wrote:
because the VI is looking for those VI's in "C:\LabVIEW Hacker" which is a very oddly named directory, plus the fact it is in the root drive, to have be the intended install directory.
The screenshot in the original post is looking for a VI in <vi.lib>\LabVIEW Hacker, which I am fairly certain is where it is supposed to be.

Your right about VI.lib. I saw the colon at the beginning and to me that always signals the root of the drive. I still think "LabVIEW Hacker" is a very odd name for a professional toolkit.

The OP claims to have installed it in the correct default location. Apparently that location is not the same one that the VI is looking for. So the all the other commentary still applies in that the VI can't find the code where it is looking for it.

Perhaps the version and the LV 13 vs. LV 14 that Altenbach is talking about is the reason. But if so, I think he'd be having issues trying to open an LV 14 VI within LV 13, before it even gets to the point that it can't find the VI.lib library.

Re: Opening VI problem

altenbach — Wed, 09 Nov 2016 18:55:31 GMT

Obviously, we don't have enough information. Maybe the project got down converted for him.

In any case, there is a dedicated forum on that other site, so this discussion should continue over there.

Re: Opening VI problem

Mustafasei — Thu, 10 Nov 2016 16:19:27 GMT

By the way this message repated many times and open the directory in my computer and when its open I always I select the same VI which I have downloaded it from iternet till it finshed but rarely I can find the VI is fully compelte inside mostlly i found it as shown

please see this screen video record which i uploaded it on drop box and advise me

https://www.dropbox.com/s/1as07olpqh6pzm6/ScreenCapture_11-10-2016%206.45.42%20PM.wmv?dl=0

Thank you for all your support

Re: Opening VI problem

RavensFan — Thu, 10 Nov 2016 16:28:46 GMT

The problem is LabVIEW is searching for those subVI's that make up the driver and searching in that LabVIEW Hacker path. When it can't find it, you wind up pointing it to your Fire Alarm.VI and doing that a bunch of times. So all of those subVI instances are being replaced with fire alarm.VI and you wind up with a whole bunch of broken wires because Fire Alarm.vi is not a replacement for those missing driver VI's.

You should be going to find the actual driver subVI's. They are in some other directory, so that means you have to go browsing for them, which is what I was telling you to do back in message #5.

Re: Opening VI problem

Mustafasei — Thu, 10 Nov 2016 16:33:27 GMT

i didnt understan what shall i have to do in replay #5

Re: Opening VI problem

altenbach — Thu, 10 Nov 2016 16:41:24 GMT

I still think all this should be discussed over here instead.

You still have not said if you use LabVIEW 32bit or 64bit. From the vi.lib path seen in the video, you are either using 32bit LabVIEW on a 32bit OS or 64bit LabVIEW on a 64bit OS. More typical is 32bit LabVIEW on a 64bit OS.