Teststand-Operatorinterface

[Martin H. Kellner]

I try to use Teststand with the LV-Operatorinterface.

I managed to run the interface on another machine than my developer-machine.
But i get errors when a VI is started as a step. It's the 18001-error.

My LabView is 5.1f. I also compiled the LV-Runtime-Engine coming with
teststand and ported it to the other machine.

My Questions:

1. I can't edit VIs from Teststand when I use the teststand-derived
LV-Runtime-Engine for the VI-adaptor. Why?

2. Should I downgrade my system to 5.1 (without the f !!!) to get it run on
the second machine?

Thanks

Martin Kellner

[Paul Mueller]

Martin,

TestStand uses a particular LV ActiveX server to run the VIs and edit the
VIs.
You configure this under Configure>>Adapters>>LabVIEW Adapter.

If you have the LV development environment installed, you can configure the
LV Adapter to use LabVIEW (development environment) which allows you to edit
the VIs.

Also, if you are running VIs as the code modules that are called from the
steps, these VIs (and all the subVIs) must be compiled with the same version
of the LV Runtime system. You will need the development environment to recompile
the VIs and the runtime system so they all match.

You can use Tools>>Assemble Test VIs to help compile all the VIs used by
a particular sequence file.

Hope this helps,
Paul


"Martin H. Kellner" wrote:
>I t
ry to use Teststand with the LV-Operatorinterface.
>>I managed to run the interface on another machine than my developer-machine.>But
i get errors when a VI is started as a step. It's the 18001-error.>>My LabView
is 5.1f. I also compiled the LV-Runtime-Engine coming with>teststand and
ported it to the other machine.

>>My Questions:>>1. I can't edit VIs from Teststand when I use the teststand-derived>LV-Runtime-Engine
for the VI-adaptor. Why?

>>2. Should I downgrade my system to 5.1 (without the f !!!) to get it run
on>the second machine?>>Thanks>>Martin Kellner>>>

[Martin H. Kellner]

Thanks Paul,

I'm working on this problem with your German dependency now. We bought a
the big "Developer Suite Test Edition" in last october. It came with
TestStand 1.0, not the 1.01. But the German support is very very slow.
It took them 4 days to call back and until now (day number 😎 I didn't
get an answer to my solution. I hope to get a teststand-update-CD for
updating to version 1.0.1.

thanks Martin

Paul Mueller schrieb:
>
> Martin,
>
> TestStand uses a particular LV ActiveX server to run the VIs and edit the
> VIs.
> You configure this under Configure>>Adapters>>LabVIEW Adapter.
>
> If you have the LV development environment installed, you can configure the
> LV Adapter to use LabVIEW (development environment) which allows you to edit
> the VIs.
>

> Also, if you are running VIs as the code modules that are called from the
> steps, these VIs (and all the subVIs) must be compiled with the same version
> of the LV Runtime system. You will need the development environment to recompile
> the VIs and the runtime system so they all match.
>
> You can use Tools>>Assemble Test VIs to help compile all the VIs used by
> a particular sequence file.
>
> Hope this helps,
> Paul
>
> "Martin H. Kellner" wrote:
> >I try to use Teststand with the LV-Operatorinterface.
> >>I managed to run the interface on another machine than my developer-machine.>But
> i get errors when a VI is started as a step. It's the 18001-error.>>My LabView
> is 5.1f. I also compiled the LV-Runtime-Engine coming with>teststand and
> ported it to the other machine.
>
> >>My Questions:>>1. I can't edit VIs from Teststand when I use the teststand-derived>LV-Runtime-Engine
> for the VI-adaptor. Why?
>
> >>2. Should I downgrade my system to 5.1 (
without the f !!!) to get it run
> on>the second machine?>>Thanks>>Martin Kellner>>>