TestStand Adapter Setiings in LabVIEW Run Time environment gives error

[PalanivelThiruvenkadam]

Hello All,

I have Developed a sequence in TestStand which calls LabVIEW VI as Module, It works properly when the adopter settings is in Development Environment,

I need to Run the LabVIEW in Runtime Environemnt, when the adopter settings is chnaged to Run Time Envienment, TestStand gives Error Stating ""Software Confguration

"The Version of subVI might not match the version of run time engine or a vi dependency might be missing"

Softare Version

TestStand Development System 2014 SP1

LabVIEW (2015) Full Development System

[buton]

i have run into this problem but i dont remember how i solved it...

i think it has something to do with the runtime not knowing on which directory the vi dependencies are...

[.aCe.]

I have seen a similar issue. Found a workaround but did not get much time to investigate it. It was related to typedefs in the VI, seemed as if the VI did not recompile after a change to the typedef. Relinking all typedefs in the VI (use Replace context menu and point to the same file again) seems to force the VI to recompile.

You could also try the following if the above fails:

• Mass compile your code.
• Check dependencies in your LabVIEW project for any conflicts.

[WireWeaver]

This error can happen for a few reasons, including the ones pointed out in the error message. The LabVIEW RTE cannot recompile VIs like the development environment can and it also uses different search directories - as the last paragraph of this document points out.

I agree with the previous suggestion of mass compile and locating VI dependencies. I've also seen a few other corner cases cause this problem. If the mass compile doesn't work, you can use a diagram disable structure to disable the code inside that VI and slowly enable the subVIs until you find the culprit.

A pretty easy catch-all is to build the VI into some kind of distribution (like a PPL) before calling it from TestStand - but I would still recommend finding the cause of the problem so you can avoid it in the future.

Hope this helps!

Trent

[jsiegel]

This error can occur if the VI that TestStand is trying to call has subVIs saved in a different version of LabVIEW from that of the top-level VI.

[PalanivelThiruvenkadam · Accepted solution]

Thank you all for the support!

I had a discussion with NI support team and we found like TesStand (64 bit) will  work good for LabVIEW (64 bit) and like the same for 32 bit in both the cases.

Though it will support cross bit version in Developemnet mode, but it won't be the same in Runtime Mode.