GOOP queues and other stored references

[AKA_TG]

 need to ask this because Im not at the target machine to try it myself until Monday.
Re Endevo by ref Goop Wizard 3.0.5

I am using queues in process objects.
WHen I create the object I create the queue and store the queue reference in the attributes of the object.

Then I use the queue for controlling public status and shutdown functions etc..

Question is the following.

I ran into a glitch today whereby the queue refs and some other refs go invalid while the Goop repository is showing "live" objects.
The values of the refs are intact but they are invalid

Anyone have any Idea what I am describing?

Thank You


PS: I hope this isn't simply Labview not running. How can that be when I am using the object inspector. I don't yet get it.

--------------------

[JeffreyH]

Not sure if I understand your problem correctly..

Could it be that in your create method there is some code generating an error (which you are not catching) preventing SetModifiedAttributes from doing it's work. This would effectively result in a invalid queue ref in your objects' attributes.

Regards, Jeffrey

[AKA_TG]

No I do not think it is an error.

It turns out the queue and DAQ Task references go invalid because of the relationship of the endevo GOOP object to LabVIEW. (or so it seems)  I think it is because the VI that created the object goes idle and so LabVIEW assumes the ref is no longer needed (despite any  options settings. )

I am seeing the objects in the Goop repository however references to queues and Data acquisition tasks are invalidated as

soon as the VI that uses them goes idle.

It does not seem to afffect field point references or VIsa com ports and also all other data in the goop object seems fine. I guess thats because FP and VIsa are only strings

Its a real snag to me because I did not see it coming. Now I have to create the queue and reestablish the Daq tasks to insure it is valid

after the create method even if the object exists. 

 I prefer to use the create or look up existing feature of the method because it gives a lot of flexibility.

Thank You

[Yi Y]

Hi NJG88_TG,
Looks like you are able to figure out the issue with your application. I'm not too familiar with GOOP, however, we do have LVOOP as a NI supported alternative for your OOP needs.

Yi Y.
Applications Engineer
National Instruments
http://www.ni.com/support