wilkes@mips.COM (John Wilkes) (02/26/88)
Well, I didn't really pay too much attention to the articles that flew by
concerning hooking up a Trailblazer to tty000 on the Unix-PC. You see, I
figured that I'd probably invest in a laser printer before I shelled out
the bucks for a trailblazer. I now find myself in the happy situation of
wishing I'd saved some of that info. My benevolent employer has provided
me with a 'blazer to fiddle with since I have a home unix system.
So, would one of you who has already done it give me some pointers? What
do I need to do to get uucp to use the Trailblazer? I've managed to get it
working with the ATE stuff (yuck! I also want to figure out how to get it
working with the mdm program - hi, Emmet!)
Thanks!
John Wilkes
--
-- @home:
-- ucbvax!ucscc--\
-- ames!ucscc.ucsc.edu--->!maow!john OR maow!john@ucscc.ucsc.edu
-- mips--/
--
-- @work:
-- {decwrl,ames,pyramid,prls}!mips!wilkes
-- OR, for those of great faith:
-- wilkes@mips.comwtm@neoucom.UUCP (Bill Mayhew) (02/27/88)
Hi,
Here is what works for me to control a Trailblazer on my 3b1. I
have ver 4.0 firmware now, but the vax I talk to is still using
some level 3.x firmware, so I do not get the benefits of data
compression, etc that level 4.0 gets you. None the less, I
typically get uucp throughputs of 850-950 char/sec on "short" files
under 40 Kbytes. With longer files, I get "only" about 550
char/sec.
Note, you may want to add a couple of new entries to the attached
modemcap file to have an entry that initializes ATs95=0 for 1200
baud connections to computers endowed with non MNP modems (3b1's On
Board Modem, for example). Unfortunately, it is the nature of MNP
to go brain dead when calling a plain-jane modem without MNP. This
is not a bug in the Trailblazer, but rather a bug in MNP. I have
seen the same thing happen with MNP on a US Robotics and on a
MIcrocom 9624.
I have included a couple of DIR entries in the attached L-devices
file so that you can use "cu -ltty000 -snnnn" to directly program
the Trailblazers S regiesters for those special occasions. Since
L-devices is scanned top-down for an available device by uucico and
cu, you should probably stick with the ordering in my example.
Note to get 300 baud out of the On Board Modem, it seems to need a
different name than OBM for that rate- I kind of liked "SOB" for
Slow OBm. I didn't want to insult the Trailblazer by making it
have a 300 baud modemcap.
One thing I haven't implemented in modemcap is to search for return
strings like "BUSY" or "NO DIALTONE", and return with an error from
dialing. That, as they say, is left as an exercise for the reader.
--Bill
----------------------cut for modemcap--------------------------
#sccs "@(#)uucp:modemcap 1.3"
# Modemcap file
# Add the following lines to the bottom of your current modemcap
#
# 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#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----------------pjh@mccc.UUCP (Peter J. Holsberg) (02/28/88)
In article <1683@electron.mips.COM> wilkes@mips.COM (John Wilkes) writes: | |So, would one of you who has already done it give me some pointers? What |do I need to do to get uucp to use the Trailblazer? I've managed to get it |working with the ATE stuff (yuck! I also want to figure out how to get it |working with the mdm program - hi, Emmet!) | (1) WHAT mdm program??? (2) From a previous poster... Configure the pc to believe thatthere's a Hayes 9600 bps modem on tty000. Add "DIR tty000 0 9600" to the end of L-devices. Configure the modem by running "cu -s9600 -ltty000" and sending these: ATQ4 S51=4 S52=1 S53=1 S54=1 S58=2 S66=1 S110=1 S111=30 &W -- Peter Holsberg UUCP: {rutgers!}princeton!mccc!pjh Technology Division CompuServe: 70240,334 Mercer College GEnie: PJHOLSBERG Trenton, NJ 08690 Voice: 1-609-586-4800
wilkes@mips.COM (John Wilkes) (02/29/88)
Thanks to all who have provided help, I configured uucp on my 3B1 to talk
to the Trailblazer. Now, if I could just find someone in the San Jose area
to feed unix-pc to me over a Trailblazer link...
One small problem I have, though. If I configure tty000 to be a modem
port, do I have to tell the Trailblazer to never say anything? It looks
like tty000 and the 'Blazer get into a shouting match, and the 3b1 gets
real s....l....o....w. My solution to this was to configure tty000 as an
"other" and caller-only. Yes, I know, *real* 3b1 owners don't use the ua to
do this sort of thing, but I am not experienced in unix system
administration.... I don't have any dial-in users right now, but might
someday. What will I need to do, tell the 'Blazer to be completely silent,
or something?
John Wilkes
--
-- @work:
-- {decwrl,ames,pyramid,prls}!mips!wilkes
-- OR, for those of great faith:
-- wilkes@mips.comegray@fthood.UUCP (02/29/88)
Reference 'mdm'... Hang in there, I've got a replacement for the 'mdm' program almost ready for release. It will allow external modems of different brands to be used for outgoing calls. Emmet P. Gray US Army, HQ III Corps & Fort Hood ...!ihnp4!uiucuxc!fthood!egray Attn: AFZF-DE-ENV Directorate of Engineering & Housing Environmental Management Office Fort Hood, TX 76544-5057