TestStand 3.5 unable to deploy overridden LabVIEW methods

[davidpcl]

Just found a slight in-compatibility between TestStand and LabVIEW.

I've created and deployed many LabVIEW classes using TestStand 3.5 without any problems including using inheritance.

But I've just discovered that if you inherit a class and then override one of its methods then TestStand is unable to deploy this.

As TestStand 3.5 was around before LabVIEW 8.2 I'm not overly suprised it doesn't work in this case, although it does seem to work with most of the other class functionality, but thought I'd just flag it up in case anyone else is thinking of using LabVIEW inheritance and overriding with TestStand 3.5.

Maybe it works in 4.0?

[JonBowers]

Hi David,

I will test this out in TS 3.5 and 4 and let you know what I find.

Regards

Jon B
Applications Engineer
NI UK & Ireland

[JonBowers]

Hi David,

I have created a small test sequence that calls a VI with a parent and child class that uses an overide VI. In the sequence editor it works fine but in deployment you get a naming conflict because of the overide VI. I am going to try and raise this with R&D and see if there is any work around.

Regards

Jon Bowers
Applications Engineer
NI UK

[davidpcl]

Hi Jon,

That would be great if there is a workaround for it - it's a real shame that TestStand isn't totally compatible with LabVIEW classes - it has really impacted on my ability to make best use of them as every bit of LabVIEW we do is called via TestStand, but hopefully R&D will come up with something, or this problem will be fixed in a future release.

Thanks for your reply to my post,

[JonBowers]

Hi David,

I have come up with a work around for this though it is not very elegant. If you explicitly inlcude the overide VI's in you workspace file then you can exclude these files from the distribition by unchecking them in the deployment utility. Then you can manually copy them over. Defeats the idea of a deployment I know. I will let you know if I hear anything back from R&D.

Regards

Jon

[davidpcl]

Hi Jon,

That's a fairly sneeky way round it, but unfortunately due to the way we deploy our test software it just wouldn't be workable, and would in fact completely destroy the whole point of our system architecture so it's a no-go unfortunately.

Many thanks for looking into it anyway, hopefully R&D will come up with a fix for a future TestStand release - as I've said it is a real shame as i'm using the LabVIEW classes by default now, and have just been starting to realise the full potential of using the classes in a number of software modules I've been working on, but if the override functionality is not compatible with TestStand then I'm going to have to regress slightly from where I was.

Damn shame,