05-08-2015
What do you want to do with it? Are you trying to talk to it on a terminal? Use minicom for that. Or are you trying to script something?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We're running SCO Unix Openserver 5.05 and I'm having trouble with serial communication between the com2 serial port and a handheld device. Downloading data from Unix to the handheld works perfectly, but the other way around creates a major problem. I don't know whether it's a buffer overflow or... (1 Reply)
Discussion started by: Aretha
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I am working on serial communication on Unix. Can anyone guide me through it. The steps required for RS 232 communication and can i do serial communication even if i dont have super user previledges.
Thankx,
Vicky (1 Reply)
Discussion started by: Vicky
1 Replies
3. UNIX for Dummies Questions & Answers
This isn't really a unix question, or even a programming question, but I hope you guys can help. I want to create a program to control the electricity on a model railway.
I have created the program to that it sends characters over the serial cable, but now I need to do the switch that will... (1 Reply)
Discussion started by: KrazyGuyPaul
1 Replies
4. IP Networking
I have serial modem connection between two computers. We have to login the remote computer through ip address. How can I get the ip address in this connection? (1 Reply)
Discussion started by: pcsaji
1 Replies
5. Programming
hello,
I am gettin problem while sending and recieving data through seial port...
when I am sending Data then the reciever end is not able to recieve that data .....
Reciever end is running in infinite loop just polling after some time to check that there is data on the port and then again... (9 Replies)
Discussion started by: arunchaudhary19
9 Replies
6. OS X (Apple)
Hi again,
I spoke with Keyspan and they assured me the USB to Serial device was working if I could use the Screen tool.
I asked why I was unable to redirect stdin/stdout to and from the /dev/tty. device and was told there was no reason I shouldn't be able to do so.
I have tried:
... (1 Reply)
Discussion started by: cpfogarty
1 Replies
7. Shell Programming and Scripting
Hi there
how can i get the result of a command to not give me its error. For example, on certain systems the 'zfs' command below is not available, but this is fine becaues I am testing against $? so i dont want to see the message " command not found" Ive tried outputting to /dev/null 2>&1 to no... (5 Replies)
Discussion started by: hcclnoodles
5 Replies
8. Ubuntu
Hello!
I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
Discussion started by: mvona
5 Replies
9. Programming
edit: never mind; mods please delete. I finally got so frustrated I figured it couldn't be the code and it must be the device on the other end. After pulling it out of its cradle, I realized it was a different model number than the one I was using before, and wasn't accepting my... (1 Reply)
Discussion started by: DreamWarrior
1 Replies
10. UNIX for Dummies Questions & Answers
Hey, I'm completely new at this and I was wondering if there is a way that I would be able to redirect the log files in a directories standard output and standard error into and excel spreadsheet in anyway?
Please remember don't use too advanced of terminology as I just started using shell... (6 Replies)
Discussion started by: killaram
6 Replies
talk(1) General Commands Manual talk(1)
NAME
talk - talk to another user
SYNOPSIS
talk_party [ttyname]
DESCRIPTION
The utility is a two-way, screen-oriented communication program.
The command argument talk_party can take one the following forms:
user
where user is a login name and host is a host name.
The optional command argument, ttyname, can be used to specify the terminal to be used when contacting a user who is logged in more than
once. In absence of this argument, will try to contact the user on the user's most recently used terminal.
When first invoked, sends the following message to the party it tries to connect to (callee):
...
At this point, the recipient of the message can reply by typing:
Once communication is established, the two parties can type simultaneously, with their output displayed in separate regions of the screen.
Characters are processed as follows:
o Typing characters from LC_CTYPE classifications print or space will cause those characters to be sent to the recipient's terminal.
o Typing <control>-L will cause the sender's screen to be refreshed.
o Typing the erase, kill or kill word character will delete the last character, line or word on the sender's terminal, with the action
propagated to the recipient's terminal.
o Typing the interrupt character will terminate the local talk utility. Once the talk session has been terminated on one side, the other
side of the talk session will be notified that the session has been terminated and will be able to do nothing except exit.
o Other non-printable characters typed on the sender's terminal are converted to printable characters before they are sent to the recipi-
ent's terminal.
Permission to be a recipient of a message can be denied or granted by using the utility. However, a user may need other privileges to be
able to access other users' terminals. The utility will fail when the user lacks the appropriate privileges.
SEE ALSO
mesg(1), who(1), write(1).
STANDARDS CONFORMANCE
talk(1)