LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Telnet

Hi,

does LabVIEW have support for using telnet and ftp on both Windows
and Solaris platforms?

Regards

Jan


Sent via Deja.com http://www.deja.com/
Before you buy.
0 Kudos
Message 1 of 4
(2,073 Views)
In article <8c9mub$djg$1@nnrp1.deja.com>,
jan_klasson@my-deja.com wrote:
> Hi,
>
> does LabVIEW have support for using telnet and ftp on both Windows
> and Solaris platforms?
>
> Regards
>
> Jan
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>
LabVIEW Does in fact support Telnet and FTP, but you have to purchase
the Enterprise Connectivity Toolkit. I use the Telnet VI's regularly,
but I have not tried the FTP Vi's (But they do exist). As far as being
available for Solaris, I can't help there... Sorry
rick


Sent via Deja.com http://www.deja.com/
Before you buy.
0 Kudos
Message 2 of 4
(2,073 Views)
Emailed too. jan_klasson@my-deja.com wrote:

For whoever is interested,...

> does LabVIEW have support for using telnet and ftp
> on both Windows and Solaris platforms?

Hi Jan. I see your message is fairly old, but I just
faced the same thing today (Win98 and telnet) when
trying to communicate w/an instrument that uses 10bT.

From Win98 I can open up Start|Run|Telnet and open
a connection to my instrument and command and query
it, but trying the obvious (TCP/IP functions: Open then
Write then Read then Close sequentially) didn't get me
very far, and left me w/o a clue as to what I was doing
wrong.

Fortunately, in another message Armando García López
wrote:

> lab View has some examples about TCp, you can use
> the one named Talk Passive or Talk Active. It has
all
> necesary to do a simple communication like you want

TalkPassive.vi basically seems to sets up and wait for
another to connect to it. TalkActive.vi on the other
hand provides the same functionality as win98's telnet,
allowing me to interact manually (and successfully 🙂
with the instrument.

I'm all in a tizzy with this news and haven't implemented
it in my real program but it's obvious that it's a cinch.

The only necessary non-obvious tidbit is that Telnet
seems to wanna use port 23 (Win's telnet program
offers port names (like "telnet") but not their numbers,
and I don't know where that bit of information is
available--If I hadn't found it around here by accident
it would have taken a while to figure it out!!).
________________________________Marty
Message 3 of 4
(2,064 Views)
Marty Carts wrote:

> The only necessary non-obvious tidbit is that Telnet
> seems to wanna use port 23 (Win's telnet program
> offers port names (like "telnet") but not their numbers,
> and I don't know where that bit of information is
> available--If I hadn't found it around here by accident
> it would have taken a while to figure it out!!).

This interesting information can be traced to Internet RFC standards
documents (http://www.faqs.org/rfcs/) and found all around the Internet
by searching for the phrase "well-known ports."

Here's a very nice summary of TCP port assignments:
http://www.isi.edu/in-notes/iana/assignments/port-numbers

You'll see that LabVIEW's VI Server has its very own registered port
(3363), along with thousands of others out there, but
low ones such as
23 have long been reserved for Telnet and other fundamental protocols.

Regards,
John Lum
National Instruments
0 Kudos
Message 4 of 4
(2,064 Views)