Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

Deploying an RT-vi.

Well, things go the following way.

I have two VIs: one of them is RT vi and
the second controls the first by means of
VI-Server.

Under the project,
if I first deploy the RT VI, everything goes fine - one vi starts another wich reads the data, switches between case structure cases, sends the data to VI Server and so on - these two VI work the way they should.

But then, when the *.rtexe and Win-exe are freshly prepared, *.rtexe FTP-ed to RT,
the part of the functionality crashes.
I mean, the vi starts, reads the data regularly from the very first case but refuses to switch between case conditions (or refuses to read the data?). It looks like the control is lost.
The RT vi returns easily only to the very first conditional case and refuses to send any data to the VIServer from DAQmx in another cases.
It shoul be mentioned, I suppose, that RT vi uses DAQmx within each case condition and only the first started works fine.

I'd like to say once more that all goes right if I deploy the RT vi from project to the RT-machine beforetime.

What's up?

Thanx in adv.
0 Kudos
Message 1 of 3
(4,226 Views)
It might help if you explain from a higher level what you are trying to do in your application.  Have you tried creating very simple VIs/EXEs that can reproduce this behavior to rule out something wrong in your code (ie. the case structure programming)?

Finally, here is an example program that may help you rule out something wrong in your code:
VI Server to Control an Executable on the RT Engine
0 Kudos
Message 2 of 3
(4,214 Views)
I've already found the key to the question.

It was the misuse:) of property nodes of case structure variables that made project-RT-vi to behave the different way compared to the same vi in *.rtexe.

Anyway, thanks, Mark, for the answer!
0 Kudos
Message 3 of 3
(4,185 Views)