Xref: utzoo comp.unix.sysv386:6532 comp.unix.xenix.sco:2079 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mjbtn!root From: root@mjbtn.JOBSOFT.COM (Mark J. Bailey) Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco,sco.opendesktop Subject: Help Please with Telebit and SCO RTS/CTS Setup?! (LONG) Summary: RTSFLOW not working as it seems it should. Keywords: RTS/CTS Hardware Flow Telebit RS-232 Unix 386 SCO Message-ID: <5176@mjbtn.JOBSOFT.COM> Date: 1 Apr 91 21:12:26 GMT Followup-To: comp.unix.sysv386 Organization: JobSoft Design & Development Co, Murfreesboro, TN Lines: 116 Hello Netlanders, I am having a problem that I am not sure how to handle. Maybe some of you can help. I am trying to get FULL DUPLEX hardware (RTS/CTS) flow control working on SCO ODT 1.0 (unix version 3.2.1). I am not having much luck. The modem is a Telebit Trailblazer Plus modem. I am locking the baud rate from the serial port to the modem at 19200 baud. I have S66=001 so that the modem serial port baud rate stays locked at that no matter what. I therefore need the hardware flow control for it to work reliably. I setup my /etc/gettydefs for RTSFLOW CTSFLOW as best as I could determine from the OS docs. My 19200 baud entry is as follows: 19200 # EXTA IGNPAR ICANON IXON IXANY OPOST HUPCL ECHO ECHOE ECHOK CS8 CREAD # EXTA IGNPAR ICANON IXON IXANY RTSFLOW CTSFLOW OPOST CS8 HUPCL ECHO ECHOE ECHOK CREAD #Telebit (tty2A)\r\nmjbtn!login: # 19200 Before I began working on this, I had only set CTSFLOW (not RTSFLOW too). That seems to work most of the time, but I wanted to do it more like the book and have the OS (DTE) signal RTS to the modem (DCE). My troubles begin when I include RTSFLOW. I use the dialTBIT.c file for my dialer. The MSETUP strings are: #define MDSETUP1 "AT&FE0F1M0Q4V1X3S0=2S2=043S45=0S48=1S50=0S51=254S52=2\r" #define MDSETUP2 "ATS53=1S54=3S55=0S58=2S60=0S66=1S68=255S92=1S110=255S111=255&W\r" The Telebit settings resulting are: E0 F1 M1 Q4 P V1 X1 Version BA4.00 S00=002 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006 S10=007 S11=070 S12=050 S45=000 S47=004 S48=000 S49=000 S50=000 S51=254 S52=002 S53=002 S54=003 S55=000 S56=017 S57=019 S58=002 S59=000 S60=000 S61=045 S62=003 S63=001 S64=000 S65=000 S66=001 S67=000 S68=255 S90=000 S91=000 S92=000 S95=000 S100=000 S101=000 S102=000 S104=000 S110=255 S111=030 S112=001 S121=000 What is happening is that when the RTSFLOW kicks in (in the "final" phase of getty init - when calling login), the port freezes completely. When it first answers the phone, the prompt comes up just fine. Doing 'stty -a