From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-20-2009 08:27 AM - edited 05-20-2009 08:29 AM
I've inherited an AWFUL program that I need to modify. I was successful upgrading it last year (in LV 8.5), but when I open it now I see a bunch of Shared Variables that look like this:
Have you seen this before? What do I need to do?
05-20-2009 08:31 AM
05-20-2009 08:35 AM
Yes. It's the same LV Project that I used last year.
Another piece of information - the Error list says "Shared Variable '?': Not linked "
05-20-2009 08:38 AM - edited 05-20-2009 08:47 AM
Any chance SV was bound to hardware I/O?
Weird part is that symbol displayed of SV is exactly what is on the block diagram pallettes.
05-20-2009 08:52 AM
Will it let you 'right click' and then Select Variable from lib in project?
05-20-2009 09:01 AM
Yes, and I can do that for the few of them that are wired to type-defs. The problem is that many of them, like the one pictured, are connected to boolean constants with no hint of which variable was used.
Wayne.C wrote:Any chance SV was bound to hardware I/O?
The only reason this application uses SVs is because the author didn't know any better. I could forgive him if he was sorry for what he did, but he was proud of it.
05-20-2009 09:12 AM
Ouch! Maybe he was so proud that he framed images of block diagrams?
I made up a simple project and tried to come up with a sequence of events that could cause this. Have been unable to do so. I just can't figure out how the link between SV on block diagram and svlib could get blown away.
05-20-2009 10:40 AM - edited 05-20-2009 10:41 AM