Sponsored Content
Operating Systems HP-UX Serial standard communication (stty) Post 302943368 by jgt on Thursday 7th of May 2015 08:47:33 PM
Old 05-07-2015
You have xon-xoff flow control turned off and rts-cts control also turned off.
You should lower the baud rate to no more than 9600, and you may get it to work.
How many wires are in the circuit? What is the pin-out?
What does the manufacturer of the device you are connecting to suggest, and what are the defaults? Is the device even RS232, or maybe RS485?
 

10 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. Shell Programming and Scripting

standard error to standard out question

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

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

9. Programming

Serial communication failing

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

Redirect Standard output and standard error into spreadsheet

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
syncinit(1M)						  System Administration Commands					      syncinit(1M)

NAME
syncinit - set serial line interface operating parameters SYNOPSIS
/usr/sbin/syncinit device [ [baud_rate] | [keyword=value,...] | [single-word option]] DESCRIPTION
The syncinit utility allows the user to modify some of the hardware operating modes common to synchronous serial lines. This can be useful in troubleshooting a link, or necessary to the operation of a communications package. If run without options, syncinit reports the options as presently set on the port. If options are specified, the new settings are reported after they have been made. OPTIONS
Options to syncinit normally take the form of a keyword, followed by an equal sign and a value. The exception is that a baud rate may be specified as a decimal integer by itself. Keywords must begin with the value shown in the options table, but may contain additional letters up to the equal sign. For example, loop= and loopback= are equivalent. The following options are supported: Keyword Value Effect loop yes Set the port to operate in internal loopback mode. The receiver is elec- trically disconnected from the DCE receive data input and tied to the outgoing transmit data line. Transmit data is available to the DCE. The Dig- ital Phase-Locked Loop (DPLL) may not be used as a clock source in this mode. If no other clocking options have been specified, perform the equivalent of txc=baud and rxc=baud. no Disable internal loopback mode. If no other clocking options have been spec- ified, perform the equivalent of txc=txc and rxc=rxc. echo yes Set the port to operate in auto-echo mode. The transmit data output is electrically disconnected from the transmitter and tied to the receive data input. Incoming receive data is still visible. Use of this mode in combination with local loopback mode has no value, and should be rejected by the device driver. The auto-echo mode is useful to make a system become the endpoint of a remote loopback test. no Disable auto-echo mode. nrzi yes Set the port to operate with NRZI data encoding. no Set the port to operate with NRZ data encoding. txc txc Transmit clock source will be the TxC signal (pin 15). rxc Transmit clock source will be the RxC signal (pin 17). baud Transmit clock source will be the internal baud rate generator. pll Transmit clock source will be the out- put of the DPLL circuit. rxc rxc Receive clock source will be the RxC signal (pin 17). txc Receive clock source will be the TxC signal (pin 15). baud Receive clock source will be the internal baud rate generator. pll Receive clock source will be the out- put of the DPLL circuit. speed integer Set the baud rate to integer bits per second. There are also several single-word options that set one or more paramaters at a time: Keyword Equivalent to Options: external txc=txc rxc=rxc loop=no sender txc=baud rxc=rxc loop=no internal txc=pll rxc=pll loop=no stop speed=0 EXAMPLES
Example 1: Using syncinit The following command sets the first CPU port to loop internally, using internal clocking and operating at 38400 baud: example# syncinit zsh0 38400 loop=yes device: /dev/zsh ppa: 0 speed=38400, loopback=yes, echo=no, nrzi=no, txc=baud, rxc=baud The following command sets the same port's clocking, local loopback and baud rate settings to their default values: example# syncinit zsh0 stop loop=no device: /dev/zsh ppa: 0 speed=0, loopback=no, echo=no, nrzi=no, txc=txc, rxc=rxc ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
syncloop(1M), syncstat(1M), intro(2), ioctl(2), attributes(5), zsh(7D) DIAGNOSTICS
device missing minor device number The name device does not end in a decimal number that can be used as a minor device number. bad speed: arg The string arg that accompanied the speed= option could not be interpreted as a decimal integer. Bad arg: arg The string arg did not make sense as an option. ioctl failure code = errno An ioctl(2) system called failed. The meaning of the value of errno may be found in intro(2). WARNINGS
Do not use syncinit on an active serial link, unless needed to resolve an error condition. Do not use this command casually or without being aware of the consequences. SunOS 5.10 9 Mar 1993 syncinit(1M)
All times are GMT -4. The time now is 02:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy