From: kak@hico2.westmark.com (Kris A. Kugel)
Newsgroups: comp.sys.3b1
Subject: Re: WorldBlazer on 3b1?
Summary: (long!) Hico2's current TB setup -- includes DETAILED setup info.
Date: 11 Aug 92 17:12:09 GMT
Reply-To: kak@hico2.westmark.com
Organization: High Country Software

A followup to articles by:
	sandy47@cats.ucsc.edu (Sandra Mc Elhiney? Larry McElhiney?)
	gst@gnosys.svle.ma.us (Gary S. Trujillo)

I may be able to help both Gary and (Sandy|Larry) out.
I suspect Gary's problem connecting to Telebits may be the S50=6 setting.
I'm not having the problem he describes.

sandy47@cats.ucsc.edu (Sandra Mc Elhiney? Larry McElhiney?) writes:
: 
: I have a new WorldBlazer which I'd like to use on one of my 3b1s in place
: of a Hayes 2400 currently installed.  HDB is running fine with the Hayes
: at this time and I have a spare machine which I can use to experiment with
: the WorldBlazer.
: 
: I'd like to get an update to the Telebit suggestions from the archives
: which deal directly with the WorldBlazer so that I can essentially "drop
: it in place".  Connections run about 1/3 Telebit PEP, 1/3 High Speed nonTB,
: and 1/3 1200-2400.
: 
: Concerns are:
: 	
: 		-Interface speed 19,200 or "higher"
: 
: 		-TurboPEP activity with HDB uucp
: 
: 		-cu usage
: 
: 		-software switch to other configurations
: 
: Thanks in advance for ANY help you can give me with this.  I'd love to see
: some actual entries which work.
: 
: 
: 				Larry McElhiney

gst@gnosys.svle.ma.us (Gary S. Trujillo) writes:
: 
: I can't answer Larry's questions, since I've only recently installed a WB
: on my 3B1, and haven't really begun using it, due to problems in talking
: to each and every one of the Trailblazers I had formerly communicated with
: using a T2500, due to what Telebit identifies as bugs in their ROM code.
: Even the latest ROMs (BC7.01) don't solve the problems with the TB+ modems.
: Sigh.  (Well, I can get a connection to a TB+ once it's been upgraded, but
: those ROMs introduce a new bug which breaks BREAK handling.  Another sigh.)
: 

I'll start off by assuming (McElhiney) has a 3B1.

First, you probably want to get the HDB uucp.  This will break some
of the phone software, but I understand you can fix this if you hack
around in L.sys (NOT Systems) afterwards.
(async.main only knows about L.sys).

Now, after fussing around with this system for a while, and having some
problems with it, I've gotten the following configuration.

I'm using a semi-locked 19200 interface.  It seems to work OK.

Note the Q1 and E0 settings -- I don't like these settings, but otherwise
the modem doesn't seem to work right.  I describe some of the problems below.

DON'T INSTALL THE REGISTER SETTINGS WITHOUT USING THE BELOW DIALER SCRIPT.
The below register settings are NOT independent of that script.

I'm writing the section on symptoms from memory.  All the below
solutions are incorporated into the below settings.
Previous Problems:
	- the modem babbling to itself
		(symptom: machine locks up, RTS light blinking)
		(symptom: machine does not answer calls)
	  solution: set e0 and q1, and set q2 when making a call
		    increase the DTR down interval: S047:15
	- v.32 modems have problems connecting
		( they connect but get bad characters )
	  solution: put PEP tones LAST in the sequence (s92=1)
	- other pep modems hang up before connecting
	  solution: send out message to connecting administrators
		    to put ATS50=255S7=60 in their PEP dialing sequence.
		    (your connecting admins must be responsive!)

		    Also: let telebit know you'd like to be able
		    to configure which standards get in the answer
		    sequence in later PROM releases.  The VERY long
		    answer sequence contains modem tones I'm NEVER
		    likely to need.  I've suggested this to telebit;
		    if there's enough demand expressed, they might
		    get it into early new prom releases.

There's still occasional times that my modem ignores incoming calls
when there's been plenty of time for the 3b1 software to reset,
and DTR is on.  I'm still seeing if I can determine what causes this.


Modem Registers:
----------------
WorldBlazer - SA - Version LA5.00W- Active Configuration
 B1  E0  L1  M1  Q1  T   V1  X2  Y0 
&C2 &D3 &G0 &J0 &L0 &Q0 &R3 &S0 &T4 &X0 
S000:1   S001=0   S002=43  S003=13  S004=10  S005=8   S006=2   S007=40 
S008=2   S009=6   S010=14  S011=70  S012=50  S018=0   S025=5   S026=1  
S038=0   S041:6   S045=0   S046=0   S047:15  S048=0   S050=0   S051:254
S056=17  S057=19  S058:2   S059:15  S060=0   S061:0   S062=15  S063=0  
S064=0   S068=255 S069=0   S090=0   S092:1   S093=8   S094=1   S100=0  
S104=0   S105=1   S111:30  S112=1   S151=4   S155=0   S180=2   S181=1  
S183=25  S190=1   S191:6   S253=10  S254=255 S255=255 

Telebit also suggests setting S64 to 1 (ignores characters while dialing
or answering a call).  I decided I'd rather be able to interrupt a dial
sequence.

My register settings differ from Gary S. Trujillo's in the following ways:
( == means we both have the same, but different from the default)
	P   == T    Use touch tone dialing by default
	E1  -> E0   See bug description
	L2  -> L1   modem speaker quieter
	Q0  -> Q1   See bug description
	X2  == X2   use extended result codes
	&C2 == &C2  DCD on except when pulsed off during disconnect
	&D0 -> &D3  allows computer to hang up the modem through dropping DTR
	&S1 -> &S0  ? DSR always on.  Maybe I should check this out.

	S000=0   -> S000:1   Answer on one ring
	S011:50  -> S011=70  (Gary uses faster touch-tone timing)
	S041=0   -> S041:6   Time out after 36 idle minutes.
	S047=4   -> S047:15  See bug description
	S050:6   -> S050=0   I set this to 255 in the dial sequence
	                     when dialing PEP modems. 
	S051=255 -> S051:254 autobaud(between 3b1 and modem), default is 19200
	S058:2   == S058:2   Use full-duplex RTS/CTS flow control.
	S059=0   -> S059:15  extended "connect" info
	S061:0   == S061:0   break processing as in register 63 (We use both
	                     use the S63 default: send BREAK in sequence
			     with the data)
        S092:1   == S092:1   Answer sequence selection: PEP tones last.
	S094:0   -> S094=1   allow speed negotiation
	S111:12  -> S111:30  UUCP -g protocol support (Gary's is kermit)
	S180:0   -> S180=2   Enable error control on V.42 and MNP connections
	S183:40  -> S183=25  ? How long to wait for LAP-M or MNP start pattern.
	S190:0   -> S190=1   Enable Data compression
        S191:6   == S191:6   Disable TB LZ data compression

S190/S191: According to Telebit, V.42 compression won't hurt you,
but LZ is a big lose if a lot of your traffic is already compressed.


From Dialers:
-------------
tbfast	=W-,	"" A\pA\p\rATQ2 OK ATS50=255S7=60DTW\T\r CONNECT
tb	=W-,	"" A\pA\p\rATQ2 OK ATS50=0DTW\T\r CONNECT


From Devices:
-------------
Direct tty000 - Any direct

ACU tty000 - Any tb \T

ACUTB tty000 - Any tbfast \T
ACUPEP tty000 - Any tbfast \T
ACUpep tty000 - Any tbfast \T

ACUV32 tty000 - Any tb \T
ACUv32 tty000 - Any tb \T

 - - - - - - - - - - - - - - - - - - - -
 Hope this helps some people out,

Kris A. Kugel	908-842-2707
hico2!kak	kak@hico2.westmark.com
Newsgroups: comp.sys.3b1