yellow exclamation mark next to project item

Confuzed · ‎02-02-2015

I inherited a LabVIEW project from someone who's no longer at my company, and the app it generated has been used for years here. Unfortunately, when I open the project in LabVIEW I see no source files, but I do see 2 yellow exclamation marks next to [the only] 2 items in the project. If I select either of these items then right click on them and select explain warning the below message box pops up. By the name of the 1st one it seems highly probable that it's is associated with something generated by the former employee. The 2nd one may be generic. Either way, how can I get more info about what these project items are supposed to be (i.e., path & filename, or something like that) so that I can try to find them? Secondly, is it possible that because of these errors the list of VI's that comprise this project are not shown? Is there any kind of error that causes the list of VI's in the project to become hidden?

Thanks for any help in figuring out what's wrong and fixing it.

Bob_Schor · ‎02-02-2015

When the Project was defined, it was "connected" to multiple hardware devices capable of running LabVIEW code (this is how LabVIEW Real-Time and FPGA code works -- you designate the LabVIEW code to run "on that Instrument over there"). For this to work, you need to either have the actual Instrument connected (usually via TCP/IP) or you need to tell the Project to work with a "simulated instrument".

If you right-click the top line of the Project (the line above "My Computer") and choose "New", you'll see you can designate your code for various devices.

Bob Schor

JÞB · ‎02-02-2015

The readMe.txt and Target-Singlrate documents might shed a lot of light on what components are needed to work with the project. Oh, I hope so... Documentation is a key factor in maintaining code.

There is what appears to be a Compact Field point target you will need the LabVIEW Real Time module. And the Touchpanel module.

"Should be" isn't "Is" -Jay

Confuzed · ‎02-02-2015

Thanks for the quick replies.

So... if I know the IP address of where this test system is on the network, can I somehow enter that in my project and try to do a little remote development, or would I have to connect locally (by connecting to an Ethernet port on this Windows CE box)? I've found some additional info on NI's website that looks troubling. Specifically, it looks like the really old version of Windows CE (Version 5.0, Build 1400) running on an Advantech TPC-1570 Windows CE Device is no longer supported with LabVIEW 2014. So... that means that I can't support this old test system on my LabVIEW 2014 development PC.

That doesn't answer my other question though, which is why no VI's show up as source files for this project. Could it be that because these 2 yellow exclamation marks show up that prevents the rest of the project tree from displaying properly?

The project's readme.txt file has almost no info in it, and none of it looks relevant to this thread.

There's nothing that looks like a Target-Singlrate document in the project.

It is a Compact FieldPoint (cFP-2200) based test system.

Confuzed · ‎02-02-2015

Okay... I found the target-singlerate.html file in the project folder hierarchy (but not listed as a component of the project). Here's what's in it. Does this shed any light on anything?

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Draft//EN">

<HTML>

<HEAD>

<TITLE>Target VI</TITLE>

</HEAD>

<BODY >

<H1>Target VI</H1>

Target VI<P>

</EMBED>

</OBJECT>

</TD></TR></TABLE>

<P>

</BODY>

</HTML>

JÞB · ‎02-02-2015

You can install multiple versions on LabVIEW and work with the older IDE. on older driver sets if you need to.

"Should be" isn't "Is" -Jay

nathand · ‎02-02-2015

The error message explains exactly the problem. The program runs on two remote devices. You don't have the toolkits/plugins needed to talk to those devices, so LabVIEW tells you they're inaccessible and won't show the VIs. With the right toolkits installed, the source files will show up. You don't need access to those devices, nor their IP addresses, to look at the source code, but you do need access in order to run the VIs on those targets.

You can still open the source VIs but you'll have to do it from file->open or from the filesystem, not from the project. If you do this you'll get errors about missing VIs that are part of the missing toolkits, but you can see what the code does.

LabVIEW

yellow exclamation mark next to project item

yellow exclamation mark next to project item

Re: yellow exclamation mark next to project item

Re: yellow exclamation mark next to project item

Re: yellow exclamation mark next to project item

Re: yellow exclamation mark next to project item

Re: yellow exclamation mark next to project item

Re: yellow exclamation mark next to project item