Sponsored Content
Full Discussion: Serial communication failing
Top Forums Programming Serial communication failing Post 302390024 by Corona688 on Tuesday 26th of January 2010 04:30:18 PM
Old 01-26-2010
Quote:
Originally Posted by DreamWarrior
I am having problems with a piece of code running under Red Hat Linux. Quite simply, I have set up a device to speak to a serial port (9600 Baud, 8 N 1) and can read from this device fine. However, all writes issued to the serial port act like they never made it to the device. It does not respond to them.
What flow control is being used? It might be expecting hardware flow control when there is no flow control at all.
Quote:
Even more odd, if I change the parity to either EVEN or ODD everything stops working, I read garbage.
This at least is to be expected. The settings on both end must match.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Serial port communication

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

Serial Communication in UNIX

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

serial communication

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

ip communication through serial connection

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

problem while having a communication with serial port?????

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)

Serial Communication from shell Mac OS X PHP script

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. Ubuntu

Ubuntu 9.04 Serial application to telnet to serial device

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

8. HP-UX

Serial standard communication (stty)

Hello friends, I am trying to communicate with a programmer memory from Unix (HP-UX) via serial port. Well, I have some code ready stty parameters to achieve communicating the device with the computer, but I have my doubts. I would like to know if you have some code fragment where you use the... (5 Replies)
Discussion started by: Monttanna
5 Replies
termiox(7)						 Miscellaneous Information Manual						termiox(7)

NAME
termiox - extended general terminal interface SYNOPSIS
fildes, request, arg) DESCRIPTION
The extended general terminal interface supplements the termio(7) general terminal interface by adding support for asynchronous hardware flow control and local implementations of additional asynchronous features. Some systems may not support all of these capabilities because of hardware or software limitations. Other systems may not permit certain functions to be disabled. In such cases, the appropriate bits are ignored. If the capabilities can be supported, the interface described here must be used. Hardware Flow Control Modes Hardware flow control supplements the termio and character flow control (see termio(7)). Character flow control occurs when one device controls the data transfer of another device by inserting control characters in the data stream between devices. Hardware flow control occurs when one device controls the data transfer of another device by using electrical control signals on wires (circuits) of the asyn- chronous interface. Character flow control and hardware flow control can be simultaneously set. In asynchronous, full duplex applications, the use of the Electronics Industries Association's EIA-232-D Request To Send (RTS) and Clear To Send (CTS) circuits is the preferred method of hardware flow control. The EIA-232-D standard specified only unidirectional hardware flow control where the Data Circuit-terminating Equipment or Data Communica- tions Equipment (DCE) indicates to the Data Terminal Equipment (DTE) to stop transmitting data. The termiox interface allows both unidi- rectional and bidirectional hardware flow control; when bidirectional flow control is enabled, either the DCE or DTE can indicate to each other to stop transmitting data across the interface. Clock Modes Isochronous flow control and clock mode communication are not supported. Terminal Parameters Parameters that control the behavior of devices providing the termiox interface are specified by the structure, defined in the header file. Several system calls (see ioctl(5)) that fetch or change these parameters use the structure which contains the following members: The field describes hardware flow control modes: Enable RTS hardware flow control on input. Enable CTS hardware flow control on input. The RTS and CTS circuits are involved in establishing CCITT modem connections. Since RTS and CTS circuits are used both by CCITT modem connections and by hardware flow control, CCITT modem and hardware flow control cannot be simultaneously enabled. Variations of different hardware flow control methods can be selected by setting the appropriate bits. For example, bidirectional RTS/CTS flow control is selected by setting both the and bits. Unidirectional CTS hardware flow control is selected by setting only the bit. If is set, the Request to Send (RTS) circuit (line) is raised, and if the asynchronous port needs to have its input stopped, it lowers the Request to Send (RTS) line. If the RTS line is lowered, it is assumed that the connected device will stop its output until RTS is raised. If is set, output occurs only if the Clear To Send (CTS) circuit (line) is raised by the connected device. If the CTS line is lowered by the connected device, output is suspended until CTS is raised. termiox Structure Related IOCTL Command The system calls that reference the structure have the form: Commands using this form are: The argument is a pointer to a structure. The current terminal parameters are fetched and stored into that structure. The argument is a pointer to a structure. The current terminal parameters are set from the values stored in that structure. The change is immedi- ate. Errors that can be returned include: The port does not support hardware flow control. The file descriptor for this port is configured for CCITT mode access. Hardware flow control is not allowed on CCITT mode devices. The argument is a pointer to a structure. The current terminal parameters are set from the values stored in that structure. The change occurs after all characters queued for output have been transmitted. This form should be used when changing parameters that affect output. Errors that can be returned include: The port does not support hardware flow control. The file descriptor for this port is configured for CCITT mode access. Hardware flow control is not allowed on CCITT mode devices. The argument is a pointer to a structure. The current terminal parameters are set from the values stored in that structure. The change occurs after all characters queued for output have been transmitted; all characters queued for input are discarded, then the change occurs. Errors that can be returned include: The port does not support hardware flow control. The file descriptor for this port is configured for CCITT mode access. Hardware flow control is not allowed on CCITT mode devices. AUTHOR
was developed by HP and AT&T. FILES
Files in or under SEE ALSO
ioctl(2), termio(7), modem(7). HP-PB Only termiox(7)
All times are GMT -4. The time now is 01:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy