View Single Post
  #4   Spotlight this post!  
Unread 06-05-2012, 17:39
plnyyanks's Avatar
plnyyanks plnyyanks is offline
Data wins arguments.
AKA: Phil Lopreiato
FRC #1124 (The ÜberBots), FRC #2900 (The Mighty Penguins)
Team Role: College Student
 
Join Date: Apr 2010
Rookie Year: 2010
Location: NYC/Washington, DC
Posts: 1,113
plnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond repute
Re: remote port or service name

I'm not sure what you want demonstrated with example code, but I'll try and explain in different terms.

The input "Remote Port or Service Name" can take two inputs, an integer, or a string. When given a number, this is the TCP/IP Port on which to operate. So if you want to send/receive data on port 21 (commonly used for FTP), you would wire a numeric constant with the value of 21 to that input.

If you provide a string input, LabVIEW will query the Service Locator and try and resolve your input to an existing service (which will correspond in turn to a port number). In reality, you can avoid using the Service Locator portion of this input, providing you already know which port you need to use.

I'm pretty sure NI has some examples provided in the TCP/UDP sections of their examples (go to Help->Find Examples, you can search for "TCP"), and they're usually pretty helpful.
__________________
Phil Lopreiato - "It's a hardware problem"
Team 1124 (2010 - 2013), Team 1418 (2014), Team 2900 (2016)
FRC Notebook The Blue Alliance for Android
Reply With Quote