09-06-2006 02:15 PM
09-06-2006
03:04 PM
- last edited on
11-25-2025
11:01 AM
by
Content Cleaner
Take a look here , here , and here [broken links removed]
Maybe those can shed some light on the topic.. I know they helped me.
EDIT: Just relized you said "control remotely"... well... i hope those links can still help. Although Im sure youve run across them already.
Message Edited by MJBrehm on 09-06-2006 03:06 PM
09-07-2006
12:55 AM
- last edited on
11-25-2025
11:02 AM
by
Content Cleaner
Hi uits,
Here's [broken link removed] a link that demonstrates a LabVIEW program as an ActiveX server - called from a VB client. I think with a little work you can move the VB client to a different "remote" machine.
I don't know if LabVIEW's dot-NET tools provide a similar interface. Of course you could always brute-force remote-control from VB through a TCP/IP connection to a LabVIEW program (setting up your own messaging.)
Cheers!
09-07-2006 03:51 PM
09-08-2006 01:16 PM
Hello uits,
It may be possible to do this using the SetControlValue method. You can change the values of the controls while the VI is executing. This may not address the other issue of the error. What gets this error and is it the vi or the visual basic program that gets the error? A screen shot may be very helpful to figuring out what is happening.
I hope this helps.
Steven T.