TS4.2: VI too early to convert

[mtimti]

Hi,

I'm getting the error -18002 VI too early to convert when I execute a TestStand 4.2 sequence file with the TestStand Base Deployment Engine. I created the Deployment installer with the deployment tool in TS4.2 and installed it on a second system. I added all needed LV runtimes and drivers incl. TestStand Deployment Engine. All installed softwares shown in the MAX are equal to the Developing system. But on the target system I always get the mentioned error. So I searched the NI Forum and found a similar Problem, but no real solution for that. I think, that the TestStand Base Deployment Engine on the target system chooses the wrong LV runtime engine, something higher then 8.2.1 (this is the version of the VI's). When I change the Labview adapter the the developing system to 8.6.1, I get the same error. But with 8.2.1, everything works fine.

How can I change the default LabView Runtime Version for the TestStand Base Deployment Engine?

Thnaks in Advanced

M. Tiedje

[Norbert_B]

This error occurs if the LV developement system cannot update the VI to the version you are currently working with.

If you are taking a look into this table, you can see that opening LV 4.x and 5.x VIs is possible directly with LV 8.2; newer versions are not capable of opening LV 5.x VIs directly.

So i asume that you have rather old VIs, but using in your LV adapter a LV developement system 8.5 or newer..... 

hope this helps,

Norbert 

[mtimti]

thanks for your reply

I don't have any problem with my development system. I'm working with LV 8.2, all VI's can be executed by TS via Active X. My Problem only occurs when I deploy my system. I guess the TestStand Base Deployment system chooses the wrong LV Runtime Enginee, something newer then 8.2. I need a something like the LabView Adapter (like in TestStand developing system) in the TestStand Base Deployment System. All my settings and software version are identical on both systems.

The whole problem started when we decided to change the TS version form 3.5 to 4.2. everything was fine with 3.5 and I thought I only need to deploy everything again and that's it, bau then came the VI version error.


M. Tiedje

SW-Developer 

[Norbert_B]

---

mtimti wrote:

 [...]I need a something like the LabView Adapter (like in TestStand developing system) in the TestStand Base Deployment System.[...]

---

The TestStand deployment has also settings for Adapters. It is possible, that your UI does not supply you with the option to change those settings. You can always install the predefined UIs delievered with TestStand and run it on the deployment system. You can then change the settings for the LV Adapter as needed.

---

mtimti wrote:
[...]All my settings and software version are identical on both systems.[...]

---

If this is true, then the LV Adapter settings should already be correct. Therefore, there has to be another reason for this behavior. But please check the settings as described before.

---

mtimti wrote:
[...]The whole problem started when we decided to change the TS version form 3.5 to 4.2. everything was fine with 3.5 and I thought I only need to deploy everything again and that's it, bau then came the VI version error.[...]

---

Never heared something like this. I asume that not only TestStand was updated in the process. Is it possible, that you have been working with something older than LV 8.2 when using TS 3.5? If so, please masscompile all VIs using 8.2 before deploying them.

hope this helps,

Norbert 

[mtimti]

Thanks norbert,

@Norbert B wrote:

"The TestStand deployment has also settings for Adapters. It is possible, that your UI does not supply you with the option to change those settings. You can always install the predefined UIs delievered with TestStand and run it on the deployment system. You can then change the settings for the LV Adapter as needed."

that's what i need, how can I install an other predefined UIs? I just deployed the system using the deployment tool.
I there an other way to change the Runtime version, like change a ini file or reg-key?

Thanks again

M. Tiedje
 

[Norbert_B · Accepted solution]

You can copy the exe-file of the UI to the target system (or deploy it with your application). You can find the compiled version of the "full featured UI" in the directory C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.2\UserInterfaces\Full-Featured if you installed them in the default directory.

hope this helps,

Norbert 

[mtimti]

Thanks, that helped.

I'm a little bite confused why I have to do this, because I deployed everything with TestStand. A little bit strange... I guess there must a ini or regkey where you can switch the runtime version as well

Best Regards

M. Tiedje

[Dennis_Knutson]

The menu item Configure>Adapters>LabVIEW allows you to select the run-time engine.

[mtimti]

I know, but I think this cannot be the standard way to do this, because the deployed system does not need a TS UI. So I copy just the UI do make that configuration. There must be an easier way to switch the Runtime environment.
By the may this solution works, but can be only a workaround, hence i have to modify is be hand and cannot do it by an installer ...

[Norbert_B]

No, there is not really an easier way:

The setting should be part of one of the config files. Those are by default binary in TS 4.2, so not really easy to work with. So i suggest you to deploy the cfg-files with your application. Otherwise, you can include the possiblity to alterate the adapter settings to your UI as Dennis suggests. Or you have to do the step i guided you for every system you want to deploy....

hope this helps,

Norbert