Path: utzoo!mnetor!uunet!oddjob!hao!gatech!mcnc!rutgers!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.dcom.modems
Subject: Re: Trailblazer Madness
Message-ID: <3390@cbmvax.UUCP>
Date: 29 Feb 88 18:56:38 GMT
References: <3362@cbmvax.UUCP> <1024@neoucom.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Distribution: comp
Organization: Commodore Technology, West Chester, PA
Lines: 23
Keywords: telebit trailblazer s50 carrier

In article <1024@neoucom.UUCP> wtm@neoucom.UUCP (Bill Mayhew) writes:
> 
> The telebit manual does suggest changing the time limit to for
> detecting the carrier to 60 seconds, if you set the modem to try
> 1200 and 2400 before trying out FAST.  I had the same problems that
> George did, but found I got consistent connections after changing
> to 60 sec timeout.  I discovered the problem since our dial-in has
> to support calls coming in from non Trailblazers too.

Yes, but that's in reference to a modem calling into a trailblazer
with S92=1, where it's fairly obvious that you might need to allow
a longer time to sniff the PEP answer sequence.

In my case, I was calling a "dumb" modem and saying, use 2400 baud
and don't search.  It is counter-intuitive for this condition to
require a longer carrier detect delay than one that has to wait
through the entire 2400 baud answer sequence and then perhaps
listen for PEP stuff.

-- 
George Robbins - now working for,	uucp: {uunet|ihnp4|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)