LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Oh Boy, my VI always asks to SAVE

I've seen others complain about this, but this is the first time I've personally had the problem:

One particular VI in my project always thinks objects on the block diagram were modified and so recompiles the VI. This of course means that everytime I close it, it wants to SAVE the changes.

This VI simply opens a reference to an FPGA and then closes it (just testing).
This VI also happens to take a long time to load which I attribute to the number of FPGA references I have in my project. N.I. is aware of this issue, but I'm wondering if it has a side-effect which I'm now seeing.

LabVIEW 8.5


Message Edited by Bill@NGC on 09-06-2007 10:13 PM

Message Edited by Bill@NGC on 09-06-2007 10:14 PM

0 Kudos
Message 1 of 5
(5,484 Views)
And by the way, if I remove the open/close FPGA references....voila! no more thinking something changed.
0 Kudos
Message 2 of 5
(5,473 Views)

Sorry, I have no experience with FPGA, so here are just a few stabs in the dark... 🙂

  • Does it tell more specifically what it thinks has changed?
  • Could it be something was not masscompiled last time you upgraded (e.g. 8.20 to 8.2.1)?
  • Have you tried saving the once? (Sorrry, you did not mention this detail) 😉
  • Do you have write permission to the location where these things are located?
Message 3 of 5
(5,461 Views)
  • Does it tell more specifically what it thinks has changed?
  • Could it be something was not masscompiled last time you upgraded (e.g. 8.20 to 8.2.1)?
  • Have you tried saving the once? (Sorrry, you did not mention this detail)
  • Do you have write permission to the location where these things are located?
The  message only says that "objects have been modified on the block diagram...VI  recompiled".  No more details are shown. I've been running fine under 8.5 for a few weeks, this suddenly started  so I can't see a permission problem or mass compile issue.

Thanks for your response.


Message Edited by Bill@NGC on 09-07-2007 08:56 AM

0 Kudos
Message 4 of 5
(5,370 Views)
Chalk it up to a "corrupted" VI. Created a new one and no problem. Hmmm........
0 Kudos
Message 5 of 5
(5,340 Views)