TestStand called by labview MMI, cannot load a vi already opened

[seica1]

Hello, I have a Main VI' that executes a a modified version of the 'TestStand 2017 (32-bit) LabVIEW Simple UI'.

When I run the Main  VI by labview all is OK, the MMI executes and a Teststand sequence is called without errors and then terminates correctly.

Inside the TS sequence I have a step that call a VI already loaded and run by the Main VI, this was ok if run by labview.

I created the executable for Main VI, when I run it TS reports the error attached, TS is unable to load the same vi I loaded and executed in the Main VI.

I need to execute this VI on both sides, first from the Main VI and then inside TS sequence called by MMI.

Thank you

Massimo Ponte

[Oli_Wachno]

Seems you have a crosslinking issue here. 

The error message is quite clear here: you are trying to load the same VI (or two VIs with the identical name) from two different locations.

You might want to check your exe build script

[seica1]

Hello, the vi is present in one location only, first it is loaded by labview TS MMI and then it's loaded inside TS sequence (called by MMI), the error says that TS is not able to load the same vi previously loaded by LV MMI.

Regards.

[Oli_Wachno]

The error message posted earlier on says the contrary

[seica1]

Hello the error has something strange because there is a path that not exist:

D:\HANON Test Motore\MMI\Test Motore.exe\Leggi file configurazione.vi

the folder D:\HANON Test Motore\MMI contains only the Test motore.exe file, I checked several times and the VI is present only in one position and both loadings (LV and TS) refers to the same VI and same location.

regards.

[Oli_Wachno]

Does the SubVI in question happen to be loaded dynamically? And the path get's assembled somehow?

[seica1]

Hello, I tried both Load dynamically and Preload with no success. The path is directly inserted no any expression is used.

Thank you.

Regads.

[Oli_Wachno]

What I was thinking of: does your LabVIEW code call this particular VI using a base path like application directory or something similar?

There are some VIs which will behave differently when called using the Runtime engine / compiled as EXE