Sponsored Content
Special Forums Hardware Serial connection CAT5 instead of RS232 and Null Modem or Straight cable. Post 302548126 by jgt on Wednesday 17th of August 2011 01:09:45 PM
Old 08-17-2011
The Terminal is DTE, the computer end is trickier. If you are connecting to COM1 or COM2 then those ports are also DTE, so you will need a null modem cable.
If you are connecting to a multiport serial card, then you will have to look at the documentation, as some ports can be set either DTE or DCE via software.
All you really need to do is buy an extra RJ45 to RS232 (either 9 or 25 pin) adapter, and wire one for DCE and the other for DTE.
This User Gave Thanks to jgt For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Is anyone using unix with cable modem

Is anyone using a cable modem with unix and if so does your cable co. support unix or did you get that going on your own and how. Thank you for all your help. (5 Replies)
Discussion started by: gparsons70
5 Replies

2. UNIX for Dummies Questions & Answers

cable modem to sparc

hi , i have sparc machine , i want to connect my le0 (ethernet interface) directly to cable modem , i have created a file resolv.conf,hosts, dhcp.le0,defaultrouter,nisswitch,hostname.le0. i dont know my cable companies <domain name> and <name server assigned to me> , also they even dont know how... (5 Replies)
Discussion started by: raju
5 Replies

3. UNIX for Dummies Questions & Answers

Hyperterminal null modem connection to Solaris

I am new to Unix. I just got my SUN box from ebay with Solaris supposedly preloaded. The problem is I am unable to connect via Hyperterminal to Solaris, or more to the point, cannot tell if I have a successful connection and that solaris is the one not properly booted up. I hooked up a null... (3 Replies)
Discussion started by: seethams
3 Replies

4. Solaris

null modem serial cable for server testing

HI all, i still have a problem when using null modem to see the output from my server(sun ultra en 3000). i followed the instruction from the internet, but it is not working. 1. i am using db9(5 4, 2 rows,put in laptop serial port) and db25(13 12, 2 rows,put in (A) server serial port). 2.... (3 Replies)
Discussion started by: waterbear
3 Replies

5. Solaris

Is the cable you are using a null modem cable or a modem cable

Hi all, Is there any difference between a null modem cable or a modem cable ? i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup. please correct if i am wrong, thks (2 Replies)
Discussion started by: waterbear
2 Replies

6. Solaris

cannot telnet/ftp to solaris machine by straight cable makes problem ..

Hi All, 1. modify /etc/default/login file as make commented # console= 2.put my laptops ip at both /etc/inet/ipnodes and /etc/host file still i can login via telnet/ftp through a DB9-serial cable, but when i tried through a lan stratight cable directly connected that machine... (7 Replies)
Discussion started by: mahadib
7 Replies

7. Solaris

Null modem cable in Ultra sparc 10

Hi Gurus, Can I use null modem cable in Ultra sparc 10 workstation Thanks (3 Replies)
Discussion started by: kumarmani
3 Replies

8. AIX

Transferring files via RS232 cable

Current setup: Some old AIX standalone machine (F series) My WinXP laptop Null modem cable from laptop to AIX machine (console port). On Hypterminal on WinXP I can connect to the AIX machine (serial connection), but when I try to transfer file, it will just sit there. I'm guessing the... (3 Replies)
Discussion started by: apra143
3 Replies

9. AIX

serial modem connection

I configured the serial modem in my P6-550 AIX 5.3 box But i dont have telephone line. when I run the command # cu -l /dev/tty1 the output is as follows does it mean that my modem is responding to the command? can i say my serial port is working and communicating fine? Connected ... (3 Replies)
Discussion started by: pchangba
3 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 10:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy