How can I remotely Start an VI from Teststand on a Realtime

[OneLabviewGuy]

Hey,

I got a huge Problem calling VIs remotely from Teststand on the PXI-8106 RT. If I choose the VI, which I wanna call, as an Teststand "action" and define, that it should run remotely, I get an Error.

The Error says, that the VI is not executable. The VI, which to call, is built and deployed on the Real Time System. And the Realtime is connected on the Labview Project.

HELP ME PLEASE....

[DowNow_]

Hi,

Check the LabVIEW Utility step types. Normally you'll only run remote sequences, not Action steps, using the sequence call step. But that's if the remote machine is Windows and can run TestStand. For RT you have to use  the LabVIEW Utility step types. You might also consider creating a "headless," or embedded VI that runs on the RT target and responds to tcp commands or shared variables.

cc

[OneLabviewGuy]

Thanks for your help. It helped much. Now I got a new Error... When I try to call an VI (which runs in the Labview Project correctly) with FPGA Reference, I get the Error, that the caled VI is broken or not executable.

[DowNow_]

can't help you there. 

cc

[SachaE]

Hi Daoberle,

  one thing to check is that the RT vi you're calling (the cpu based code) that launches the FPGA vi, is the FPGA open in there pointing at the .lvbitx file or is it still pointing at the vi? Also, if you've transferred the .lvbitx file on to the RT target, is it in a findable path (one of the search directories)?

Sacha

[HoussamK]

Hi Daoberle,

could you please post the error message or a screenshot?

[OneLabviewGuy]

It took some time, but finally I've chosen another Design Structure for Testing... Now the FPGA References are on RT and a Statemachine calls the VIs down there.

Support said to me, that I must see the RT as an autonomous system which is communication via shared variables. This works for me.

[Norbert_B]

Just for clarification for everyone:

NI does currently not support dynamic (read: programmatic) deployment and execution of VIs which includes interfaces to FPGA devices on RT targets.

This is not connected to TestStand at all.

The recommended way to control an RT system from TS (or any other host application) ist to define a dedicated interface which the RT application provides and the host application can used. This interface can be "anything" like Shared Variables, "raw" TCP command protocol or any higher level protocol like STM, AMC, ....

This recommendation is also true for VIs without FPGA interfaces, even if daoberle's first approach would work with those.

Norbert

[KLevente]

Hi,

I think the answer lies in a startup executable.

Refer to more details here:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PAhpSAG&l=da-DK

Kind Regards,

Levente