Trailblazer and non-BNU uucp

Bill Mayhew wtm at neoucom.UUCP
Sat Dec 9 16:50:05 AEST 1989


The Trailblazer can work with non-BNU uucp.  If you get a device
not present error, make sure that the cable to the tty port carries
1, 2, 3, 4, 5, 6, 8 and 20 signal leads.  You may have to do an
initial set-up on an IBM PC before attaching the Trailblazer to the
Unix PC if the register settings are strange.  My recollection is
that pins 4 and 6 have to be high before getty and/or cu will
believe the device is really there.  You can aso do an "stty tty000
CLOCAL -HUPCL" on the line or set the termio(7) flags in
/etc/gettydefs to bring up the line without modem control to affect
the tests and adjustments to the modem.  You'll need to kill any
gettys and telinit Q if you edit gettydefs.  Editing gettydefs is
potentially dangerous, as you might ruin your ability to log in to
the machine if you bolux-up the file big time.  Also make a back-up
of gettydefs to restore the original conditions once the modem is
configured.

It is pretty easy to edit modemcap to support a TB modem.  You can
use the Hayes entry as a basis.  The key for success with the TB
modem is to allow enough time for PEP tone negotiation.  My tests
showed that calling anohter autobaud TB modem usually requires
about 45 seconds.  It is best to put the puause tokens in the chat
string in modemcap, rather than in the L.sys file, as it gets to
look pretty grody if you have umpteen /p tokens in L.sys.  You need
to add a line to L-devices and L.devices for the tty port where the
Trailblazer is attached.

I'll attach the modemcap lines I had for my Trailblazer for version
3.51.  It's been several years since I used them; as far as I know
the cpio archive I have of my old uucp was working.  There were
also bugs in the uucico distributed with 3.51.  Various people have
reported various degrees of bugs with it.  Most of the common
wisdom says that you never saw bugs if you used only tty00x or phx
for uucp, but not both the On Board Modem and external modem
intermixed.  I received updated uucicos from the AT&T hotline, but
none of them ever really cured the glitches which acted like the
vanishing clist buffers bug, but to a massive degree.  The BNU kit
does not seem to suffer from the problem.

One last note, make sure that you have S7 set to at least 60
seconds when calling into autobauding Trailblazers.

Note that if you use the User Agent to configure your set-up for
uucp, it will truncate any line in L.sys to a max of 80
characters!!!  Beware!

modemcap lines:
=====================================================================
# Telebit trailblazer modem
# same as hayes, but send a couple of "A"s first to get autobaud right
# Name=telebit9600
t9|telebit96|telebit 9600:tr=\r:wp=\r:wk=K:wt=T:\
                         :ta=AT\r:ph=ATDT:\
                         :eh=\r:\
                         :d1#1:d5#5:ti=A:wi=A:\
                         :d2#30:cy=^JBUSY:ay=Remote\ Busy\ :\
                         :pl=tid1tid1tiwid1tad1wpwpwkwpphd2wpwpwpcyaytr:
#
# Name=telebit2400
t2|telebit24|telebit 2400:tr=\r:wp=\r:wk=K:wt=T:\
                         :ta=AT\r:ph=ATDT:\
                         :tp=ATS50=3\r:\
                         :eh=\r:\
                         :d1#1:d5#5:ti=A:wi=A:\
                         :d2#15:\
                         :pl=tid1tid1tid1tiwid1tad1wpwpwkwptpwkphd2wpwpwttr:
#
# Name=telebit1200
t1|telebit12|telebit 1200:tr=\r:wp=\r:wk=K:wt=T:\
                         :ta=AT\r:ph=ATDT:\
                         :tp=ATS50=2\r:\
                         :eh=\r:\
                         :d1#1:d5#5:ti=A:wi=A:\
                         :d2#5:\
                         :pl=tid1tid1tiwid1tad1wpwpwkwptpwkphd2wpwpwttr:

 ---------------------L-devices--------------------------------

#       "@(#)L-devices  5.0"
#     /usr/lib/uucp/L-devices 
#     This file is manipulated by the ADMIN-KIT commands used to
#     configure outgoing data ports.  The shell program is /usr/bin/Outgo.sh
#
#     There are four fields in each entry:
#       1. ACU/DIR : ACU if this is an autodial device, DIR if not
#       2. device  : the /dev special file the physical device is connected to
#       3. 0/MODEMNAME : = zero for DIR lines, otherwise the keyword MODEMNAME
#       4. SPEED   : speed of device (e.g. 300, 1200, 9600)
#
#  There are no devices initially configured, they must be added with ADMIN-KIT
#
ACU tty000 t9 9600
ACU tty000 t2 2400
ACU tty000 t1 1200
OBM ph1 UNIXPC 1200
SOB ph1 UNIXPC 300
DIR tty000 0 9600
DIR tty000 0 2400
DIR tty000 0 1200

----------recommended trailblazer register settings--------------
AT&n

E1 F1 M1 Q6 T V1 X1     Version AA3.00-AB3.00
S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 S08=002 S09=006
S10=007 S11=070 S12=050 
S45=255 S47=004 S48=000 S49=000
S50=255 S51=255 S52=002 S53=001 S54=000 S55=000 S56=017 S57=019 S58=003 S59=000
S60=000 S61=010 S62=003 S63=001 S64=000 S65=000 S66=001 S67=000 S68=255 
S90=000 S91=000 S92=001 S95=001 
S100=000 S101=000 S102=000 S104=000 
S110=255 S111=030 S112=001 
S121=000 
N0:
N1:
N2:
N3:
N4:
N5:
N6:
N7:
N8:
N9:
OK
-----------------------end of transmission----------------

======================
Bill  (wtm at neoucom.edu, wtm at impulse.UUCP)



More information about the Comp.sys.att mailing list