Returning Phantom Errors using lvlibp / ppl

[Oli_Wachno]

Hi everybody,

I've been using build libraries for quite some time now, but ran in some troubles lately:

my HAL (LVOOP) project has three hierarchy levels realized as multiple ppls

- Abstract Instrument

- Generic Intruments (Meter, DMM,....) --> inherit from AbstractInstrument.lvlibp:AbstractInstrument.lvclass

- Specific Instruments () --> inherit form Generic_xx.lvlibp:Generic_xx.lvclass

If have used such an architecture successfully before. It works between the AbstractInstrument and the GenericInstruments. The trouble starts when proceeding to the SpecificInstruments:

each time I open the project for building the specific implementations, I get, what I call phantom errors:

The error misteriously disappers as soon as I open the Parent Mehtod of the respective class situated in a lvlibp. Saving the project and closing LabVIEW brings up my old friend, the NI Error Report sending messages to Austin.

When opening the project again, the game re-starts.

I have to admit, that these phantom errors only occur with a certain GenericInstrumentClass. If the lvclass file was somehow corrupt, how could it be fixed?

Cheers

Oli

[Oli_Wachno]

Using LabVIEW 13.0.1f5

[Oli_Wachno]

For the records:

It seems to me that this is an issue with a semi-corrupt lvclass file. After a lot of manual changes to the class, the lvlibp compiles and works.

NI Error Report still brings up warnings (prototyp.cpp or sth alike) but I've chosen to ignore this for the time being and verify the behaviour when switching to 2014