Project messed up due to LVOOP

[Eugen_Graf]

It begann in building a Executable with error 3 (Could not load Front Panel), than I did uncheck "remove FP", but got the 2208 error. Now I changed paths of some Controls and VIs in some classes because of name conflicts. And get very much errors "VI is locked by owner". In two days I should make factory acceptance test of my project, and I think I will lost my work, because this big and expencive project will not work.

Sorry, I would say LVOOP has some bigs, so don't use it.

Message Edited by Support on 11-23-2008 06:32 PM

[Pnt]

In general Labview is crashing very easily.

You should constantly keep backups which is quite annoying.

A project, i work, simply was crashing when i changed a type-def. If i did not remember what i had changed, that whould be... very bad.

I hope you will not lose your work.

Message Edited by Support on 12-01-2008 01:28 PM

[Intaris]

Running a mass compile on your project files will help you find out if there are any corrupt elements in your code.

I just had to work my way through this in an 8.20 App.  Lots of fpsane errors when simply working in 8.2.1 (no errors) and then opening it in 8.20 (lots of fpsane errors).  The same thing happened in the other direction too (8.20 to 8.2.1).

Spent quite a while getting it fixed up.

A pain, but it might just help.

Shane.

Message Edited by Support on 12-01-2008 01:28 PM

[smercurio_fc]

---

Sorry, I would say LVOOP has some bigs, so don't use it.

---

That's an interesting conclusion based on a sample size of 1. While I empathize with you, it's clear your comments are borne out of frustration, and a certain amount of leeway can be given since many of us have been in a similar situation. But only a certain amount. 

In the future you may wish to cool off a bit before posting a message like that, and especially with that kind of subject line. 

Message Edited by Support on 12-01-2008 01:28 PM

[Eugen_Graf]

Thank you all for answers (sorry, I'm really frustrated about it). Unfortunately I get still these errors. Can anybody help?

 

Message Edited by Eugen Graf on 11-24-2008 04:08 AM

Message Edited by Support on 12-01-2008 01:29 PM

[Intaris]

An answer in the form of a few Questions....

 1) LabVIEW version?

 2) Mass compile results? 

 3) PCAN_X.vi are LVOOP VIs?  What do they do?

I'd most certainly try performing a Mass Compile to see if any of the links or VIs are damaged.  Even if the MAss compile doesn't fix things, it gives an idea where to start fixing the code.

Shane. 

Message Edited by Intaris on 11-24-2008 04:11 AM

Message Edited by Support on 12-01-2008 01:29 PM

[Eugen_Graf]

1) 8.6

2) 

3) PCAN_X VIs are not members of a class, but they will be called by member VIs of the CAN Class

Message Edited by Eugen Graf on 11-24-2008 04:20 AM

Message Edited by Support on 12-01-2008 01:29 PM

[Intaris]

I generally do NOT load the project when doing a mass compile.  From the load screen of LAbVIEW (No VIs open) you can choose Options - Mass compile.

I find this gives different results sometimes.

 What about the bad VIs and missing VIs? Logger? Non-critical VIs?

Don't know otherwise.. Sorry. 

Shane. 

Message Edited by Support on 12-01-2008 01:30 PM

[Eugen_Graf]

I got the first error in mass compile log avay. The Status.ctl was twice i my project. The logger class is being no more used in my project and doesn't exist. How can I say to LV not to use and not to search for the Logger Class?

Message Edited by Eugen Graf on 11-24-2008 04:35 AM

Message Edited by Support on 12-01-2008 01:30 PM

[Intaris]

Don't you have an item in your project heirarchy corresponding to the no-longer existing Logger Class?  It should have a warning sign next to it.

If you're feeling brave, you could edit the XML of the .proj file.  Back up everything before trying that though.

Maybe you have a corrupt project file.  Try running the mass compile without the project loaded (Status still says the project is loaded into memory). 

Shane. 

Message Edited by Support on 12-01-2008 01:30 PM