04-28-2006 04:31 AM
05-03-2006 12:04 AM
05-03-2006 01:23 AM
Hello Thomas,
thanks for your reply. So what I see is actually the intended behaviour.
The reason why I used the -target xxx -quithost call to an RT program on the host was that I was not allowed to deploy the RT prograrm on the RT target. So I had to "deploy" it on the target (an embedded PXI system with PharLap) without making it the startup application or writing it to disk. I did so by callling the RT program at the beginning of the host program via an system exec call with -target xxx -quithost. Then I worked with a TCP connection in between the host program and the now running RT program. This worked perfectly well.
How can I do something likewise with LV 8 / RT 8?
Thanks in advance for any hint.
schi
05-03-2006
01:43 AM
- last edited on
11-24-2025
09:24 AM
by
Content Cleaner
Hi Schi,
I do not understand the circumstances why you havn't rights to deploy the executable...
However, with RT 8.0 you have no other opportunity, I think.
There is another gimmick possible since RT 8.0: Startup - VI
To establish a connection with a startup vi or exe with your Host application you can use either TCP/IP, UDP or Shared Variables
If you have problems to create an RT application (TCL/NPL - Host VI) you can use the RT Communication Wizard
Regards,
ThSa