Sponsored Content
Operating Systems SCO Modifying serial printers device Post 302613757 by herot on Tuesday 27th of March 2012 06:48:29 PM
Old 03-27-2012
Actually they are RIO remote serial boxes. Its a card in the server that they plug into and they are little boxes with 8 serial ports on them. I already used the config.rio utility to map the port I want to the ttyr014. I just can't figure out how to tell SCO that check3 should point to ttyr014 instead of ttyr002.

No "mpi" here

Last edited by herot; 03-27-2012 at 07:55 PM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

serial port device path

hi. Im trying to install a switch. And the manual says i should type a command including a SerialPortDevicePath. which is the filepath to serial port used for connection. However.. nothing about how to find this info. Could anyone help me where to find this path? thx mr.T (6 Replies)
Discussion started by: tyskertøs
6 Replies

2. Programming

Accessing device with Prolific USB-serial controller.

I am trying to access DG-100 gps logger on Mac OS X with POSIX API. The device uses a Prolific usb-serial controller, and connect to the usb port on my mac. After I install the Prolific driver, it shows up as /dev/tty.usbserial and /dev/cu.usbserial. The vendor has published the data format. So... (1 Reply)
Discussion started by: monkeybiz
1 Replies

3. Linux

Device serial number

Hey! I'm trying to figure out a sollution for a problem I have at my company with an Iomega MiniMax 500 GB USB disk. If i run cat /proc/bus/usb/devices I get this information: T: Bus=01 Lev=02 Prnt=04 Port=00 Cnt=01 Dev#= 5 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00... (2 Replies)
Discussion started by: noratx
2 Replies

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

5. Programming

Problem with read data from serial device

I have problem with C programming. I want to send & receive data through serial communication. I send data(command) to device to get data from device but when receive data, it can't get altogether of data. It get only some data. What should I do to get altogether of data? If all of... (7 Replies)
Discussion started by: noppon_s
7 Replies

6. Solaris

"Device busy" When Reopening Serial Port

Any help much appreciated. I am a Java developer, not a Solaris adept. I'm having an issue reopening serial port with the Java app I am developing. I develop in Windows and deploy the app on Solaris 10 (Sunfire X4170 with Xeon.) On the target machine my app uses the two serial ports... (11 Replies)
Discussion started by: Jim Ryan
11 Replies

7. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

8. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

9. Shell Programming and Scripting

Read line from serial device with BASH

I'm new to Linux (Ubuntu 16.04), and very new to BASH scripting. I have a Numato 8-channel USB GPIO device, which is a DAQ that appears in the system as a serial port. In Linux it appears as ttyACM0. I can easily manipulate a GPO with, for example: echo "gpio set 7" > /dev/ttyACM0 ...followed... (12 Replies)
Discussion started by: Chalk-X
12 Replies
CZ(4)							   BSD Kernel Interfaces Manual 						     CZ(4)

NAME
cz -- Cyclades-Z series multi-port serial adapter device driver SYNOPSIS
cz* at pci? dev ? function ? DESCRIPTION
The cz device driver supports the Cyclades-Z series of multi-port serial adapters. The Cyclades-Z is an intelligent serial controller com- prising: o PLX9060ES PCI bus interface o Xilinx XC5204 FPGA o IDT R3052 MIPS CPU The MIPS CPU runs firmware provided by the device driver. Communication with the MIPS is performed by modifying data structures located in board local RAM or host RAM. The Cyclades-Z comes in three basic flavors: o Cyclades-8Zo rev. 1 -- This is an older 8-port board with no FPGA. The serial ports are provided by an octopus cable. o Cyclades-8Zo rev. 2 -- This is the newer 8-port board. The serial ports are provided by an octopus cable. o Cyclades-Ze -- This is the expandable version of the Cyclades-Z. It uses an HD-50 SCSI cable to connect the board to a 1U rack mountable serial expansion box. Each box has 16 RJ45 serial ports, and up to 4 boxes may be chained together, for a total of 64 ports. Boxes 3 and 4 require their own external power supply, otherwise the firmware will refuse to start (as it cannot communi- cate with the UARTs in those boxes). The Cyclades-Z has several features to improve performance under high serial I/O load: o The board may operate in interrupt-driven mode or polled mode to reduce interrupt load. o Each channel has a large input and output buffer. o Each channel may be programmed to generate an interrupt based on reception of a specific character, e.g. a PPP End-Of-Frame charac- ter. o The MIPS CPU on the board performs all flow-control handling. FILES
/dev/ttyCZnnnn -- dial-in (normal) TTY device /dev/dtyCZnnnn -- dial-out TTY device SEE ALSO
pci(4), termios(4), tty(4) HISTORY
The cz driver first appeared in NetBSD 1.5. AUTHORS
The cz driver was written by Jason R. Thorpe <thorpej@zembu.com> and Bill Studenmund <wrstuden@zembu.com> of Zembu Labs, Inc. BUGS
The cz driver does not currently implement communication via host RAM. While this may improve performance by reducing the number of PCI mem- ory space read/write cycles, it is not straightforward to implement with the current bus_dma(9) API. Interrupt mode has not been tested. There is no support for reading or writing the EEPROM connected to the PLX PCI bus controller. BSD
May 17, 2000 BSD
All times are GMT -4. The time now is 03:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy