Re : Custom services

[thumble]

Hello,

I'm using a VeriStand 2011SP1 real time application running on LabVIEW RT on a PXI device.

I need to run a specialized homemade network service that must run as soon as the target is booted, and until its shutdown. It has no interaction with VeriStand.

It is in LabVIEW code and shall start along with VeriStand at boot time.

What is the way to do this?

Best regards

[thumble]

Hello,

Anybody out there ? This question becomes urgent.

Best regards,

[PeterFoerster]

Hi,

I assume your problem is the Veristand RT Engine blocking the execution of the other VI? Unfortunately I don't know a way around that.

If your Veristand project launches at boot, you could pack your VI into an asynchronous custom device and simply let it run from within VS. I don't know if this satisfies your requierements for startup time and I don't think it's the "best" way to do this you asked for in you original post.

[Jarrod_S. · Accepted solution]

There is no supported way to do this, but you can use a debug entry point that we have for VeriStand to start a top-level VI as soon as the VeriStand Engine starts up. It does not require waiting for deployment, and has no interaction with a deployed system definition file.

To do this, create a top-level VI called NIVS Debug.vi and build an LLB source distribution with it named NIVS Debug.llb. Then place this LLB in the same directory as the VeriStand rtexe file. If this works, you should see "Starting NIVS Debug..." printed on the console when the engine first starts up. If something goes wrong, you should see an error message printed.

This VI is started asynchronously.

Hope this helps.

[thumble]

Thanks Jarrod, We're going to try it. It should be a good way to solve our problem.

Best regards,