TrailBlazer Plus (and PC Pursuit) configuration with HDB
Karl Swartz
kls at ditka.UUCP
Fri Nov 4 19:19:35 AEST 1988
This article describes the configuration I have been successfully using
on ditka with HoneyDanBer (HDB) uucp, a Telebit TrailBlazer Plus, and PC
Pursuit. While most of the TB stuff is specific to the AT&T UNIX PC,
there may be some neat tricks for other systems; the PC Pursuit scripts
should be useful to anybody running the HDB (aka BNU) breed of uucp.
In setting up the TrailBlazer, I had several seemingly contradictory re-
quirements. First, I wanted to list the desired speed in the Systems
entries, precluding a locked outgoing interface. This was motivated by
these considerations:
-- The 1200 baud on-board modem (OBM) on ditka has a phone line, and I
didn't want to have separate Systems entries for each modem at 1200
baud. The software *should* be able to select whatever modem match-
es the speed criterion.
-- Some TrailBlazers that I call answer with PEP tones last, and there-
fore need a special chat script to connect. This rightfully belongs
in the Dialers script, and that's where I wanted it to be.
On the other hand, I did not want callers to have to send BREAKs to
change the baud rate when calling the TrailBlazer. For one thing, this
seems ugly and unnecessary since the modem and the computer can both use
hardware flow control (HFC) and just leave the connection at 19200 baud.
More importantly, when my modem arrived I was running the 3.51 release
kernel, which wouldn't pass BREAKs correctly, and while the 3.51a kernel
fixed this it broke things if you dialed in with a vt100, which I need
to do.
So, what I wanted was a locked interface speed while still having an un-
locked interface on dialout. After puzzling over Telebit's manual, it
seemed that nothing said you couldn't do it; I tried a few experiments
and discovered that it worked. A call to Telebit the next day confirmed
that this was indeed legal; they hadn't documented it because it seemed
pretty bizarre, and more likely to confuse people than anything else.
Here are the settings that are different from the factory defaults:
Q6 Return result codes only on outgoing calls.
X1 Return extended result codes.
S51=254 Autobaud outgoing calls, assume 19200 on incoming.
S52=2 Reset to EEPROM values on DTR drop.
S54=3 Pass BREAKs transparently.
S58=2 Use hardware (RTS/CTS) flow control.
S66=1 Lock interface speed.
S110=0 Disable data compression.
S111=30 Enable UUCP "g" protocol support.
The weird looking part is S66=1 and S51=254, but it works.
Here's the full procedure for getting a brand-new TrailBlazer working
with your UNIX PC. I assume it's connected to the built-in serial port
(tty000) but it should work on expansion ports as well.
1. Append the following line to /usr/lib/uucp/Devices:
Direct tty000 - Any direct
2. From Install's "Main Menu", select "Administration", within that
select "Hardware Setup", then select "RS232 Setup". Select the
"MODEM/SWITCH" device, 9600 baud rate, and enable hardware flow
control. (Yes, you can do this without resorting to the stupid
User Agent, but this was the simplest for me to figure out.)
3. Connect to the modem using cu:
cu -l tty000 -s 9600
and configure the modem:
AT &F Q6 X1 S51=254 S52=002 S54=003 S58=002 S66=001
S110=000 S111=030 &W
That's all on one line; I wrapped it for readability. Note that
you may need to hit 'A' several times at the beginning of the
line.
Now that your modem is configured, there are a bunch of files that need
to be modified:
/etc/gettydefs
If you don't have an entry beginning with "19200#" you need to
add one--just copy the "9600#" line and change all occurences
of 9600 in the copy to 19200. (If your gettydefs was stock
there should be four changes required in the line.)
/etc/inittab
Change the line beginning with " 000:" to read as follows:
000:2:respawn:/usr/lib/uucp/uugetty -r -t60 tty000 19200
Note that there must be exactly *one* space at the beginning of
this line. You'll need to say "telinit q" for this to take
effect.
/usr/lib/uucp/modemcap
Add the following entries (for dial() and maybe other stuff):
# 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:\
:pl=tid1tid1tiwid1tad1wpwpwkwpphd2wpwpwttr:
#
# 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#20:\
:pl=tid1tid1tid1tiwid1tad1wpwpwkwptpwkphd2wpwpwttr:
#
# Name=telebit1200
t1|telebit12|telebit 1200:tr=\r:wp=\r:wk=OK:wt=ECT:\
:ta=AT\r:ph=DT:\
:tp=ATS50=2:\
:eh=\r:\
:d1#1:d5#5:ti=A:wi=A:\
:d2#20:\
:pl=titid1titid1titiwitad1wktpphd2wt:
(These are slightly hacked from some I saw posted on the net; I
regret not being able to find the information to properly credit
their original source.)
/usr/lib/uucp/Devices
Make sure something like the following lines are present:
#
# UNIX PC's on-board modem
#
ACU ph1 ph1 1200 PC7300 \T
ACU ph1 ph1 obm.1200 PC7300 \T
Add entries for the TrailBlazer:
#
# TrailBlazer
#
Direct tty000 - Any direct
Direct tty000 - 9600 direct
ACU tty000 - 19200 tbfast \D
ACU tty000 - 9600 tbfast \D
ACU tty000 - 2400 tb2400 \D
ACU tty000 - 1200 tb1200 \D
ACU tty000 - mnp.2400 tbmnp24 \D
ACU tty000 - mnp.1200 tbmnp12 \D
ACU tty000 - tb.19200 tbfast \D
ACU tty000 - tb.9600 tbfast \D
ACU tty000 - tb.2400 tb2400 \D
ACU tty000 - tb.1200 tb1200 \D
Assuming you want 1200 baud dialouts to use the TrailBlazer only
if the OBM is busy, make sure the TrailBlazer entries are after
the PC7300 entries.
In addition, if you use PC Pursuit via the OBM, add these lines
(suitably tailored with your local Telenet access number and the
names of the outdial ports you are interested in):
#
# PC Pursuit via OBM
#
ACU ph1 ph1 CASFA.1200 PC7300 5551212 pcp1200 CASFA pcpdial \D
ACU ph1 ph1 ILCHI.1200 PC7300 5551212 pcp1200 ILCHI pcpdial \D
ACU ph1 ph1 NYNYO.1200 PC7300 5551212 pcp1200 NYNYO pcpdial \D
Or if you really want to use your TrailBlazer for PC Pursuit:
#
# PC Pursuit via TrailBlazer
#
ACU tty000 - CASFA.1200 tb1200 5551212 pcp1200 CASFA pcpdial \D
ACU tty000 - ILCHI.1200 tb1200 5551212 pcp1200 ILCHI pcpdial \D
ACU tty000 - NYNYO.1200 tb1200 5551212 pcp1200 NYNYO pcpdial \D
ACU tty000 - ILCHI.2400 tb2400 5551212 pcp2400 ILCHI pcpdial \D
ACU tty000 - NYNYO.2400 tb2400 5551212 pcp2400 NYNYO pcpdial \D
/usr/lib/uucp/Dialers
Add the following lines for the TrailBlazer:
# Telebit TrailBlazer
tbfast =W-/ "" A\pA\pA\pAT OK ATS64=1S92=0S50=255S7=60DWT\T FAST-\c-FAST
tb2400 =W-/ "" A\pA\pA\pAT OK ATS64=1S92=0S50=3S95=0DWT\T CONNECT\s2400
tb1200 =W-/ "" A\pA\pA\pAT OK ATS64=1S92=0S50=2S95=0DWT\T CONNECT\s1200
tbmnp24 =W-/ "" A\pA\pA\pAT OK ATS64=1S92=0S50=3S95=1DWT\T CONNECT\s2400
tbmnp12 =W-/ "" A\pA\pA\pAT OK ATS64=1S92=0S50=2S95=1DWT\T CONNECT\s1200
In the "tbfast" entry "S7=60" and "FAST-\c-FAST" are to handle
the long connect times that may be necessary if you are making a
long-distance call to TrailBlazer configured to answer with PEP
tones last (i.e. S92=1).
The "S64=1 S92=0" stuff seems to be necessary to work with the
"locked but not really" operating mode. Telebit's support staff
helped a great deal to make this all work; it appears there is a
slight bug in the ROM here. (Note that the S92=0 isn't needed
unless you normally have S92=1. I used to have it that way and
was too lazy to change the scripts when I changed the modem.)
If you're using PC Pursuit, add these lines too (again, after
suitable customization):
# PC Pursuit
pcp2400 =W-/ "" \d\r at D\r\c INAL= D1\r\c @ C\sD/\D/24,USERID,PASSWD\r\c ECTED-\rC\sD/\D/24,USERID,PASSWD\r\c-ECTED
pcp1200 =W-/ "" \d\rD\r\c INAL= D1\r\c @ C\sD/\D/12,USERID,PASSWD\r\c ECTED-\rC\sD/\D/12,USERID,PASSWD\r\c-ECTED
pcpdial =W-/ "" \r@\r\c @ SET\s1:0,7:0,4:2\r\c @ CONT\r\pI\r\dATZ\r\c OK-I\r\dATZ\r\c-OK ATDT\T ECT-ATDT\T-ECT
/usr/lib/uucp/Systems
These are just a few examples; tailor to your requirements:
# PC Pursuit when available, TrailBlazer at other times
chicago Wk1805-0630,SaSu;5 ACU ILCHI.2400 5551212 ogin: nuucp
chicago Wk1805-0630,SaSu;5 ACU ILCHI.1200 5551212 ogin: nuucp
chicago Wk0630-1800 ACU tb.19200 13125551212 ogin: nuucp
# PC Pursuit only
sanfran Wk1805-0630,SaSu;5 ACU CASFA.1200 5551212 ogin: nuucp
# Local 1200, try OBM then TB
local12 Any ACU 1200 5551212 ogin: nuucp
# UNIX PC, sometimes gets confused by TB so only use OBM
unix-pc Any ACU obm.1200 5551212 ogin: nuucp
/usr/lib/uucp/uucico
If you receive much data via PC Pursuit (whether you place the
call or the remote calls you), you'll want to patch your uucico
to run with WINDOWS=7 instead of 3. Change the 31188'th byte
of uucico from a 3 to a 7; a "cmp -l" of the old and new files
should give this result:
31188 3 7
How do you do this? That, as they say, is left as an exercise
for the reader. (In other words, somebody sent me a patched
copy and I'm too lazy to figure out how to patch it myself.)
Well, that's pretty long-winded, but it took even longer to get it all
working. (All the pieces have been working reliably on ditka for months
now.) Many, many thanks to a variety of people around the net and in
Customer Support at Telebit for help with various bits and pieces--all
I did was put them together.
--
Karl Swartz |UUCP {ames!hc!rt1,uunet!dasys1}!ditka!kls
1-505/667-7777 (work) |ARPA rt1!ditka!kls at hc.dspo.gov
1-505/672-3113 (home) |BIX kswartz
"I never let my schooling get in the way of my education." (Twain)
More information about the Unix-pc.uucp
mailing list