Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

The serial ports on Linux are found in the device folder (/dev/). They are normally called /dev/ttySX, were X is the serial port number: for example, /dev/ttyS0 is COM1. Udev is the layer within modern Linux systems that configures the default permissions and device mapping for the serial ports. Of course serial ports first need to be configured correctly before you can transmit and receive data. The Baud rate, Flow Control and Start, Stop and Data bits will need to match on both servers.

Thanks Harry, Now do I need to set ispeed and ospeed? And a recomendation of the best way to tranfer some data from our SCO box to our SUSE linux box?
Thanks Jack Privitt

Quote:

Originally Posted by harry edwards

The serial ports on Linux are found in the device folder (/dev/). They are normally called /dev/ttySX, were X is the serial port number: for example, /dev/ttyS0 is COM1. Udev is the layer within modern Linux systems that configures the default permissions and device mapping for the serial ports. Of course serial ports first need to be configured correctly before you can transmit and receive data. The Baud rate, Flow Control and Start, Stop and Data bits will need to match on both servers.

Thanks Harry, Now do I need to set ispeed and ospeed? And a recomendation of the best way to tranfer some data from our SCO box to our SUSE linux box?
Thanks Jack Privitt

Quote:

Originally Posted by harry edwards

The serial ports on Linux are found in the device folder (/dev/). They are normally called /dev/ttySX, were X is the serial port number: for example, /dev/ttyS0 is COM1. Udev is the layer within modern Linux systems that configures the default permissions and device mapping for the serial ports. Of course serial ports first need to be configured correctly before you can transmit and receive data. The Baud rate, Flow Control and Start, Stop and Data bits will need to match on both servers.

In a previous reply, you suggested 'stty sane 38400 raw -echo crtscts </dev/ttyS0' . The port on the SCO box is already set up for baud 38400, but I am not sure how to check data bit, stop bit and parity. I have set the ttyS0 using the above command. and stty -a </dev/ttyS0 shows baud 38400.

Checking a third computer, that is using Anzio to access the SCO box, is setup to access SCO box at 38400,7,M.

I am at my office and I will go to site this afternoon and test your suggestion.

My goal is to transfer the Key files from SCO filePro to SUSE filepro.

The previous post I made was only an example (sorry), normally when using a serial port you will have the baud rate, data bits and stop bits as a prerequisite, in your case you need to choose the attributes and assigned them so they match on both sides.

To set the data bit, stop bit and parity you can add the following to your stty command:

Larry,
I used your code on the linux box and when I tried on the SCO box, it did not have crtscts option. I used the ixon, which the linux box also shows for flow control.

When I cat (a file) /dev/ttyb02 on the SCO to Linux. Data was displaying on the screen, but nothing on the Linux box.

Thanks,
Jack

;

PHP Code:

[PHP]

[/PHP]

Quote:

Originally Posted by harry edwards

The previous post I made was only an example (sorry), normally when using a serial port you will have the baud rate, data bits and stop bits as a prerequisite, in your case you need to choose the attributes and assigned them so they match on both sides.

To set the data bit, stop bit and parity you can add the following to your stty command:

The port set-up on both sides must match, so if you opt for hardware control cts/rts then both sides need this setting. The opposite is software control xon/xoff. I've not had much experience with software control; hence, I would used hardware control. SCO should has an equivalent setting. The other thing to check is the RS232 cable: is it wired correctly?

Harry,
I have not been able to connect yet. I am seeing some of the differences between SCO and Linux, SUSE.

I have Linux set, parity generator on, parenb, even parity, -parodd, cs8, 8 bit word, hupcl, hangup when last process closes the tty, cread, allow input to be read, crtscts, enable RTS/CTS handshaking. I still have clocal and all of the default output settings that I originally did when I did the 'stty sane.

The SCO box is setup with -parenb, which I can not seem to enable. When I try, the flow control get disabled. Flow control enabled is ortsfl ctsflow rtsflow. When I enable flow control, I get loblk enabled. ?????...

I also have just preformed the connection confirmation procedure. 1st, I set up the receive, cat < /dev/ttySO, and then went across the shop and to do an echo "this is a test" > /dev/ttyb02 and nothing.

I've just checked the SCO manual. It appears that flow control is not support for your specified port. The article I read states there is a difference between ttyb02 and ttyB02 . The capital letter device supports hardware flow control (RTS/CTS). Do you have the ttyB02 device?

Harry,
I will check ttyB02 & see about serial manager tomorrow when I get to site. I hope you know that this is an old SCO 3.x. (1988-1989). I have saved it on two occasions, but it has its noises and problems and is still holding up, I don't know how long it is going to hold up.

Also, we have been using the serial port that I am trying to use on another PC that has Anzio as a port emulator. We did connect to the other WinXP system and access the filePro program. I was hoping that this serial access woulb be easier that it has been.

Also, I am going to try to use Microscope Diagnostics and check to see if the serial port on the Linux system is good. That is one of the verables that I have not checked. Linex see it and configueres it, but I don't know that just because Linux sees the port, that it is ok.

Again I really appreciate you help on this. I am really having to call up some of my old Hardware experance.