deploying vi on rt

[Amit Ahuja]

I have a project in which most of the part is on the rt and only some part of it on the host.

There is vi on the rt which is the main vi which  runs for the first time and susequent vi's are called.The problems are

1. When the main vi is run some of the vi's in the dependency list pop up. I could not understand the problem as no option is

selected in the vi properties of the vi such as run when called.

2. When some of the vi's are made reentrant then the rt gives the message of stop waiting and disconnect even when they are not

called,only deployment is held.

3.Also when we make a vi reentrant when how can we debug the vi as we cannot se the reentrant vi running on RT.

Please help in solving in these problems

I would be really thankful.  

[Vikas_K]

Hi Amit,

1.  Have you made sure the VIs that the main VI uses are configured for the RT target and not for host (see bottom left hand corner of the sub-vi)?

2.  I have seen similar problem on the cRIO system when the rt memory/CPU is overloaded.  There is a tool available to monitor these from the host machine, although I cant remember what precisely it is called. It was in the tools menu the last time I checked.  It is a good idea to keep the CPU usage as low as possible by increasing the loop time.  Also, if possible use the shared/network variables to transfer data to the host vi and do calculations on the host processor.

3.  See 2 above..

Hope it helps.

Vikas

[Amit Ahuja]

I have checked for the configuration of the vi, it shows that the vi has been configured for the pxi only but when i right click on that

three more options are there

1. My computer

2. Main Application Instance

3. Fpga

What really do you mean by configuring it, can u please explain it?

With regards

Amit Ahuja

[Vikas_K]

I am not entirely sure how this works on PXI but in general -

- if the VI pops up on the windows machine, it means the vi is running on your windows engine and not on the rt engine.  If this is the case, your rt VI has to manage not just the various loops, etc. but also has to handle communication between the two engines.  And this may lead to the comms error message you are seeing.

- By VI configuration (see picture) I mean - "My Conputer" means on the windows engine, and so on.  So ensure all your VIs for PXI are deployed to rt engine.

Vikas