Asynchronous Call By Reference on Real-Time target (cRIO)

[Sam Dexter]

Curious if anybody can suggest a solution to my problem. I want to programatically call a few VIs and be able to stop them and restart on cRIO.

A simple test project works fine on the PC but fails to restart the VIs on the real-time target. They do stop and I can manually restart them

clicking the arrow but not programatically. I wonder if anybody can point out what I am doing wrong here (maybe overlooking something)?

Thanks in advance.

Async Call.zip

[Mads]

If you start the VIs manually y clicking on the run-button you are really just launching VIs in memory from the host machine, not sourcing them from the file path.

Have you deployed these VIs to the correct folders on the cRIO target so that the code will actually find them there (what error code doe sthe asyncronous call give?)? The atached project was not a real-time project so what the real-time application build pushed to the target is unclear...Once the files are where they are supposed to the launch will not be shown as they will run on the target with no user interface (unlike a VI that is manually started from the host) so you should add code to verify that they are indeed launching (make them write a log f.eks)...

[Sam Dexter]

Thank you Mads.

There was a couple of issues with that project. First, the paths were Windows style and not understood by cRIO.

Second, yes, you were right - the referenced VIs had to be in the folder on the cRIO. However, they still had to be

compiled along with the launcher to be executable. Otherwise it didn't work.

[Sam Dexter]

Still, it looks rather cumbersome. I was hoping to get something configurable at the run time.

Maybe need to look at the classes instead of simple super-loop VIs to get to a truly run-time

configurable system.

[Mads]

They have to be compiled for the target yes, but you just include them in the application build and configure that to save them where they should be...I often just deploy the executable, then continue to work on the other VIs. If they are run from the development environment they still find the compiled dynamic VIs. It is not ideal, but not that big of a hassle.

[Mads]

Maybe this should be suggested in the idea exchange at ni:  When working on RT we should be able to specify where VIs/LLBs/LVLIBs/Config files etc belong on the target in its properties or somewhere else, and whenever you run anyhting in the project in the development environment the system would automatically check and ensure that those sources were compiled and deployed to that location automatically (if not already there in their current form). This would replace the need to manually build and deploy an application to get the support items in place...(reminds me of this idea by the way; build and deploy in one go...)