Unwired Front Panel Terminal Warnings?

[PTI@PCI]

I was happily going along today adding some minor updates to one of my programs in Labview 8 when I suddenly noticed the RUN icon had changed to a broken arrow. When I click on it, the Error List panel opens and shows 0 errors and warnings. When I click on the Show Warnings option, a list of 68 warnings (with zero errors) appear all with the following text: Front Panel Terminal '[name]': unwired front panel terminal. Details say: The terminal for this Front Panel control or indicator is unwired.

This is strange because everything was fine one minute, and the next I got this. Now I can't run my program unless I go through it and wire up every front panel terminal (all 68 of them). I really shouldn't have to do this since I can create a new VI and leave the front panel objects unwired in exactly the same way and I don't get the warnings at all.  To further add to the confusion, the NI website states "Warnings do not prevent you from running a VI".

I intensively searched the NI website and internet in general for this problem and I got nothing. Looks like I'm the first person in the world to experience it. Anybody have an idea as to what could be the problem and/or how to correct it?

[Ben]

What version of LV are you running?

Can you recreate this situation from your backup copies?

I have never read of anyone else reporting this behaviour!

Can you post "before and after" version of the offending VI?

Ben

[PTI@PCI]

Using Labview 8

I tried to recreate the problem today using one of my earlier backup copies, but was unsuccessful.  I don't know where or how it started. I swear I wasn't doing any outlandish or wierd programming. Also, I really don't want to go back starting from my old copy again, mainly because I will lose about a week re-doing all my work (and might I run into the problem again?)

I see that I had these warnings in my earlier programs (and ignored them), and they may not be the cause of my current situation.  All I know is I have a program with seemingly zero errors and a broken arrow. 

The VIs are too large and numerous to post here and I'd prefer not (due to customer agreement). But I've sent my program(s) to NI Support to see what they can find out. I'm currently waiting for an answer.

I was just wondering if anyone had any ideas here had an idea for a fix.

[Ben]

" I've sent my program(s) to NI Support..."

Good!

Please keep us posted on the results.

Ben

[tst]

Ben, I have seen (I think it was recently) a report about a bug which breaks your VI but doesn't allow you to see the error (I think it was by leaving a tunnel which should have been deleted). It may have been on the LAVA buglist.

[Ben]

Thanks tst,

I'll have dig through that list.

Ben

[TheYowsaman]

I am having exactly the same issue.  I updated my LabVIEW to 8.0 from 7.0.  Everything recompiled fine, but all of a sudden all of my front panel objects are unwired.  I went through the program completely and found nothing out of place.  I ended up sending the program to the NI engineers to look at because I was at the end of my knowledge rope.  Hopefully they will find something.  When I do find out what it was, I will post it here.

Regards

[PTI@PCI]

Hi Guys,

Just a follow-up from my end here. This issue I had was resolved by NI support, but they really didn't do anything other than save/upgrade my VI on their computers. Here was the last response I got from NI Support:

"That's great news.  Honestly all I did was open the back up file you sent
me in LabVIEW 8 to do the upgrade again.  The upgrade conversion process is
sometimes a litttle tricky due to the large architectural changes in
LabVIEW 8, so there's some wiggle room for things to go wrong.  My advice
would be to keep frequent backups of your important programs; it sounds
like you are already doing that, which is miles ahead of many people.
Hopefully this won't happen in the future, but if it does, try opening the
VI on another system."

Hopefully your issue gets resolved as well.

[Yowsaman]

Hi All,

NI Support found my issue.  They opened the subVIs and found that the representation on the error out code controls was I8 instead of I32, so the case structure was getting messed up, expecting the default error cluster.  That fixed my issue and now my program runs great. Kudo's to NI Support.  Hope this helps someone.