LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Active-X vs TCP/IP,UDP interconnectivity

Highlighted
Dear LabView Community:

I am a bit of a newbi to LabView. Are the following correct observations:

Active-X is essential an alternate mechanism of interacting and
controlling LabView. Equivalent access to the graphic user interface is
provided. The ability to load, run, and detect error of "vi" programs is
provided.

TCP/IP and UDP interconnectivity is essentially a mechanism to
communicate with a running "vi" program. Not as much, if any, access to the
upper controller "LabView Environment" is supported.


Thanks in advance for an further insight.


Steve Punte
stevep@hamsoft.com
0 Kudos
Message 1 of 2
(939 Views)
> Active-X is essential an alternate mechanism of interacting and
> controlling LabView. Equivalent access to the graphic user interface is
> provided. The ability to load, run, and detect error of "vi" programs is
> provided.
>
> TCP/IP and UDP interconnectivity is essentially a mechanism to
> communicate with a running "vi" program. Not as much, if any, access to the
> upper controller "LabView Environment" is supported.
>

This is pretty close. The VI Server is what exports the
functionality of being able to execute, modify, and generally
operate LV programmatically.

The VI Server is exported through both ActiveX and through
built-in icons which basically use TCP/IP.

So, ActiveX can do what you are getting at, but lots more
as well. Both it a
nd TCP are a mechanism for exporting
data and functionality. They are lower level mechanisms
that the VI Server is exported over as well as being
available for other things.

Greg McKaskle
0 Kudos
Message 2 of 2
(939 Views)