Problem of property node (sequence context) in LabVIEW

[M.Blanchard]

Hi,

I create under LabVIEW 8.2 a property node with like reference a sequence context and any property. I save this vi.

When I open it on another computer, this vi has a start and asks to be to save. However, if this vi was saved without diagram, there is an arrow broken (impossibility of remaking the bonds), therefore it cannot be to run and Step Types under TestStand 3.5 does not function.

I test vi on several computer and the problem is the same one.

Conversely one vi created on another computer will not go on mine.

I recovered a ghost of my computer with only Windows XP. I installed only LabVIEW 8.2, TestStand 3.5 and Device Drivers (NI Developer Suite November 2006). I made a mass compile.

But the problem remains the same one.

An example of the vi is in attached file.

Thanks you for your answers

Best regards,

Marc

[AllenP]

Marc,

Your VI contains a typdef in it.  When you move the VI to another machine, it needs to relink to this typedef (which you didn't copy over).  When you do this, since that typedef is an old version of LabVIEW, it needs to be upgraded to the current version of LabVIEW (TestStand ships all VIs in older versions of LabVIEW to support those versions as well).  When it is relinking, it re-upgrades the typedef, which causes your VI to need to be saved.  When you remove the diagram, LabVIEW is unable to relink the typedef.

In the example you attached, there is no reason to use a typedef.  You could either use a generic ActiveX Reference, and select the class to be the Sequence Context, or you could right-click on the Sequence Context control, and select "Disconnect FromTypedef".  This should solve your problems.

Allen P.
NI

[M.Blanchard]

 Allen,

Sorry, I link the bad example.
Here is the good example with the sequence context disconnected

Best regards
Marc

[AllenP]

Marc,

It appears that this behavior changed in LabVIEW 8.0.  I have made a note to the LabVIEW R&D team to have this resolved in a future version of LabVIEW.  In the mean time, I would recommend using a password protected VI rather than removing the diagram.

Allen P.
NI