--- On Fri, 7 Mar 1997 17:15:35 +0100 Juan Carlos Martin <jcmar@mdr.indra-espacio.es> wrote: > from: Juan Carlos Martin / INDRA ESPACIO > jcmar@mdr.indra-espacio.es / 34-1-3963995 / FAX 34-1-3963912 > INDRA ESPACIO > to: VEE Reflector > date: Friday, 7th March 1997 > > > I am sorry, it is about sockets again. > > I am working and trying to communicate to other application which run in > Labview (yes, the enemy). > > I have running labview 3.0.1 on a PC 486/66 with 8 MB of run memory. I am > using this PC to make test to be used in other more powerful although not > installed yet. > > I want to communicate to other process that is running in a workstation > (HP-UX 10.20) in which I am using VEE V3.21. > > My communications is using TCP/IP vi objects from Labview. Making test I use > several concatenated vi elements: TCP Create Listener (port=5001) connected > to a TCP Wait on Listener (timeout=-1) and this connected to a TCP Read > (without bytes to be read and with a specified timeout). I am using VEE to > socket as a client and sending a simple "HELLO" which work with other VEE in > the workstation. In fact, the Labview program runs and it does not pass of > TCP wait vi object, but an error in VEE is always generated: Error 920. I > could sure you that this error is not complicated to be obtained by VEE when > intercommunication between process are performed. > > The question of one million of dollars is: can VEE works using to/from > socket with other processes on Labview?. Is it the socket affair a X-file? > Somebody has really found the "connectivity" of which all SW tools sellers > talk? Well, in fact there are 3 questions instead of one. > > Thanks for reading until here. > ______________________________________________________ > > Juan Carlos Martin > E-mail : jcmar@mdr.indra-espacio.es > Phone : 34-1-3963995 > Fax : 34-1-3963912 > Earth Stations Department > INDRA ESPACIO / MADRID /SPAIN >
---------------End of Original Message-----------------
I can't help with your Labview problem, but I have used VEE communicating via sockets to Visual Basic and C++ programs running on a PC platform without any problems.
from: Juan Carlos Martin / INDRA ESPACIO jcmar@mdr.indra-espacio.es / 34-1-3963995 / FAX 34-1-3963912 INDRA ESPACIO to: VEE Reflector date: Friday, 7th March 1997
I am sorry, it is about sockets again.
I am working and trying to communicate to other application which run in Labview (yes, the enemy).
I have running labview 3.0.1 on a PC 486/66 with 8 MB of run memory. I am using this PC to make test to be used in other more powerful although not installed yet.
I want to communicate to other process that is running in a workstation (HP-UX 10.20) in which I am using VEE V3.21.
My communications is using TCP/IP vi objects from Labview. Making test I use several concatenated vi elements: TCP Create Listener (port=5001) connected to a TCP Wait on Listener (timeout=-1) and this connected to a TCP Read (without bytes to be read and with a specified timeout). I am using VEE to socket as a client and sending a simple "HELLO" which work with other VEE in the workstation. In fact, the Labview program runs and it does not pass of TCP wait vi object, but an error in VEE is always generated: Error 920. I could sure you that this error is not complicated to be obtained by VEE when intercommunication between process are performed.
The question of one million of dollars is: can VEE works using to/from socket with other processes on Labview?. Is it the socket affair a X-file? Somebody has really found the "connectivity" of which all SW tools sellers talk? Well, in fact there are 3 questions instead of one.
Thanks for reading until here. ______________________________________________________
Juan Carlos Martin E-mail : jcmar@mdr.indra-espacio.es Phone : 34-1-3963995 Fax : 34-1-3963912 Earth Stations Department INDRA ESPACIO / MADRID /SPAIN
To: VRf - Vee Reflector From: Andy Fuller acfa@eci-esyst.com Date: 7 March 1997
VEE's handling of sockets is very straightforward and low-level. It doesn't do anything special, just makes it easy to connect to sockets. So, if you follow the interface specifications with your other applications, they should work.
I use VEE sockets on an HP-UX workstation seamlessly with C software on that workstation, other workstations (HP and Sun), and on a PC.
Just for fun, I even wrote an SMTP e-mail program in VEE, to see if it could be done. It worked seamlessly with Sun sendmail.
There is nothing magic, just that TCP/IP follows pretty good rules (better rules than most instruments using IEEE-488 or RS-232 interfaces).
-- Andy
-- Andrew C. Fuller | mailto:acfa@eci-esyst.com Raytheon E-Systems, Inc. | Box 12248 | St. Petersburg, FL 33733 (813)381-2000 x3194 | Fax:(813)381-3329
--- On Fri, 7 Mar 1997 17:15:35 +0100 Juan Carlos Martin <jcmar@mdr.indra-espacio.es> wrote:
> from: Juan Carlos Martin / INDRA ESPACIO
> jcmar@mdr.indra-espacio.es / 34-1-3963995 / FAX 34-1-3963912
> INDRA ESPACIO
> to: VEE Reflector
> date: Friday, 7th March 1997
>
>
> I am sorry, it is about sockets again.
>
> I am working and trying to communicate to other application which run in
> Labview (yes, the enemy).
>
> I have running labview 3.0.1 on a PC 486/66 with 8 MB of run memory. I am
> using this PC to make test to be used in other more powerful although not
> installed yet.
>
> I want to communicate to other process that is running in a workstation
> (HP-UX 10.20) in which I am using VEE V3.21.
>
> My communications is using TCP/IP vi objects from Labview. Making test I use
> several concatenated vi elements: TCP Create Listener (port=5001) connected
> to a TCP Wait on Listener (timeout=-1) and this connected to a TCP Read
> (without bytes to be read and with a specified timeout). I am using VEE to
> socket as a client and sending a simple "HELLO" which work with other VEE in
> the workstation. In fact, the Labview program runs and it does not pass of
> TCP wait vi object, but an error in VEE is always generated: Error 920. I
> could sure you that this error is not complicated to be obtained by VEE when
> intercommunication between process are performed.
>
> The question of one million of dollars is: can VEE works using to/from
> socket with other processes on Labview?. Is it the socket affair a X-file?
> Somebody has really found the "connectivity" of which all SW tools sellers
> talk? Well, in fact there are 3 questions instead of one.
>
> Thanks for reading until here.
> ______________________________________________________
>
> Juan Carlos Martin
> E-mail : jcmar@mdr.indra-espacio.es
> Phone : 34-1-3963995
> Fax : 34-1-3963912
> Earth Stations Department
> INDRA ESPACIO / MADRID /SPAIN
>
---------------End of Original Message-----------------
I can't help with your Labview problem, but I have used VEE communicating via sockets to Visual Basic and
C++ programs running on a PC platform without any problems.
--------------------------------------------------------
Name: Tom Sanders
E-mail: toms@symca.com (Tom Sanders)
Date: 03/07/97
Time: 08:54:49
--------------------------------------------------------