LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Non-*NIX Forums > Programming
User Name
Password
Programming This forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.

Notices


Reply
  Search this Thread
Old 12-14-2007, 09:58 AM   #1
stevebennett
LQ Newbie
 
Registered: Dec 2007
Posts: 1

Rep: Reputation: 0
RS232 Comms failure between 2 machines


Forgive me if this is a simple problem, however I am not very experienced in this area.

I have two machines (server A and server B) connected using a serial cable. Server A writes to its serial port, which is then read by server A. The messages are very simple, and usually consist of a single word, or a couple of words separated by '|'.

This was all working fine, until a couple of days ago, when it suddenly stopped working. I've tried running this command on Server A:

Code:
watch "echo fish > /dev/ttyS0
And tried to watch the serial port on server B using:

Code:
tail -f /dev/ttyS0
However, nothing is coming from server A and arriving on server B.

Where can I start in order to fix this problem?

Thanks in advance
 
Old 12-14-2007, 10:47 AM   #2
theNbomr
LQ 5k Club
 
Registered: Aug 2005
Distribution: OpenSuse, Fedora, Redhat, Debian
Posts: 5,399
Blog Entries: 2

Rep: Reputation: 908Reputation: 908Reputation: 908Reputation: 908Reputation: 908Reputation: 908Reputation: 908Reputation: 908
When trying to resolve serial communications problems, I always turn to C-Kermit first. It is a tool built for performing serial communications, and allows access to the serial ports in any possible configuration. It has decent reporting of status and error conditions. It allows you to interactively configure the ports, and see responses. A simple test is to loopback the Tx pin onto the Rx pin (pins 2 & 3 normally), and test for keystrokes echoing back. This can be done on each host independently to test the hardware and cabling. Further diagnostics can proceed from there. Another useful tool for this kind of job is an RS-232 breakout box. These used to be avaialable from Black Box, but I haven't bought one for a long time.

--- rod.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
byte collisions through rs232 comms knobby67 Programming 1 07-19-2006 10:30 PM
USB>RS232 versus PCMCIA>RS232 jayhel Linux - Laptop and Netbook 2 08-04-2005 06:09 PM
User/Kernel Space Comms under Redhat 9.0 snigglyfox Programming 3 09-07-2004 05:24 AM
3Com Etherlink III - No Comms on RH9 Pikie-Me Linux - Networking 13 10-05-2003 08:40 PM
symbols for networking and comms equipment antken General 1 10-29-2002 07:45 AM

LinuxQuestions.org > Forums > Non-*NIX Forums > Programming

All times are GMT -5. The time now is 12:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration