Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!snorkelwacker!bloom-beacon!eru!hagbard!sunic!mcsun!cernvax!chx400!mecazh!paul From: paul@mecazh.uu.ch (Paul Breslaw) Newsgroups: comp.sys.hp Subject: RS232 Hardware Handshaking Keywords: UUCP, hardware handshaking, modems Message-ID: <429@node17.mecazh.uu.ch> Date: 30 Aug 90 09:54:12 GMT Reply-To: paul@mecazh.uu.ch (Paul Breslaw) Organization: Mecasoft SA, CH-8057 Zurich, Switzerland Lines: 65 We have upgraded a working 2400 baud UUCP/CU system with a 9600 baud modem, and a new serial multiplexer card. It is some time since we looked at the way the system was configured, and because the modem is now faster than some of our callers, we need to introduce a few features that were not present on our old system. That is where our problems began. To the details:- Machine: HP9000/330 OS : HP-UX 6.5 MUX : HP 98642 Modem : Multitech V.32 Requirements:- - Bi-directional UUCP on the same serial port. - Call-in and call-out cu(1) on the same port as the UUCP. - Hardware (CTS/RTS) handshaking initiated by the modem. This last requirement is to take advantage of the modem's capability of locking its speed with the computer regardless of the speed of its line connection. The benefit of this is that the gettydef entry is simple, and so are my UUCP callers' chat scripts, since they do not have to send the right number of BREAKs for their individual connection speeds. (In fact they don't have to send BREAK's at all). We need to know the following information. 1. What is the correct cable to use. 2. What is the correct getty to run (ie getty or uugetty). 3. What is the correct gettydef entry. 4. What are the correct minor device numbers for:- /dev/cua13 the auto-dialler line /dev/cul13 the uucp call out line /dev/ttyd13 the dial-in (getty) line /dev/tty13 to set up the modem (ie. cu -s 9600 dir) Our previous configuration works fine except for the hardware-handshaking. With regard to getty, we have used uugetty in the past. But I have noticed recently from modem(7) and various utterances on the Net that bog-standard getty will do. The minor device number seems to be a major stumbling block, because nobody at HP whom I spoke to had had any experience of using the same line as call-in/call-out. Further the HP documentation is contradictory about bit 3. One piece of documentation states that as of HP-UX 5.2 Bit 3 of the minor device number implements CTS/RTS handshaking. The spec for the HP98642 says NA against Bit 3. The documentation for modem(7) says that setting the device to CCITT mode (Bit 2) enables handshaking, as did someone at HP. Can anyone who has actually had this working, provide the information I need. Paul Breslaw -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Paul Breslaw, Mecasoft SA, | telephone : 41 1 362 2040 Guggachstrasse 10, CH-8057 Zurich, | e-mail : paul@mecazh.uu.ch Switzerland. | mcsun!chx400!mecazh!paul