Query on the configuration of Telebit TrailBlazer+ for HDB UUCP use

[Dennis P. Bednar]

In article <1989Aug4.201049.1391 at jdbbs.uucp>, root at jdbbs.uucp (Jon Diekema) writes:
> Could some kind soul, send me the Dailers entry for the TrailBlazer+ 
> and/or anything else that might help me start taping the power of
> this modem? 

We use a T2500 modem here.  I'm not sure how different it is
from the trailblazer +, though. I have saved two profiles:
	Profile A: enhanced async mode for UUCP communications
	Profile B: enhanced async mode for cu(1) dial-out

Below is the portion of our /usr/lib/uucp/Dialers file for our telebit
modem:

# telebit T2500 for uucp
# &F = enter enhanced async mode, (load factory settings into RAM)
#	(this guarantees the next command can be understood)
# &E1 = load Profile A from EEPROM (Profile A is for UUCP).
#
# Profile A was created as follows:
#	at&f		# load enhanced factory settings into RAM
#	ats50=255	# pg 5-39. Fast Mode (PEP mode).
#	ats7=240	# pg 5-34. Seconds to wait for DCD
#			# ... NOTE: s7=241 stored in profile B,
#			# so easy to tell whats in RAM ("ats7?" to find value)
#	ats52=1		# pg 5-43. Modem hangs up if DTR dropped.
#			# ... Modem will not answer if DTR is off.
#	ats51=4		# pg 5-41. 9600 baud on serial line.
#	ats66=1		# pg 5-50. Lock interface, and use flow control.
#	ats111=30	# select protocol G for uucp
#	at131=1		# pg 5-67. DCD is ON only when carrier from remote modem
#	at&w1		# EEPROM.profileA = RAM (save into Profile A)
# Profile B was created as follows:
#	at&f
#	ats52=4		# DTR drops => drop phone line, etc. DTR off, no answer.
#	ats7=241	# so I can tell which profile is in RAM
#	at&w2
#
telebituucp =,-,	"" \M\dAT&F&E1\r\c OK\r \EATDT\T\r\c CONNECT \m\c
telebitcu   =,-,	"" \M\dAT&F&E2\r\c OK\r \EATDT\T\r\c CONNECT \m\c
-- 
Dennis Bednar	uunet!virtech!dennis		(703) 430-9247
Virtual Technologies Inc, P.O. Box 876, Sterling VA, 22170