At this link:
http://zone.ni.com/devzone/cda/tut/p/id/2833
NI proposes using a front panel communications link or a network communcation link between a host and an RT target.
Technically at the moment I'm using both ( I have a start/stop button on my RT VI's front panel) but then I'm passing a lot of data around using TCP IP Read/Write VIs.
Something I observe is that as I increase the load on my RT system it starves the front panel communications link of any processor time and my HOST machine gets "frozen" in the sense that "Waiting for RT Target" appears while these communication is starved.
I would like to disable the "waiting" for PXI behavior because I can put keep-alive messages in my own communcations channel.
Since NI proposes using "either-or" in the above document I was hoping this would happen when I close the front panel of the VI running on the RT system. However when I close the front panel the RT execution stops. I would like it to continue if possible and if the RT window needs to be open how can I insure that it is using none (or as little as possible) of the avalible network bandwidth?
Edit: I have been running with the Periodically check responsiveness of RT protocol DISABLED for several weeks and I still exhibit this problem.
Message Edited by AlexDubya on
12-13-2007 01:17 PM
