Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!pyramid!octopus!pete
From: pete@octopus.UUCP (Pete Holzmann)
Newsgroups: comp.dcom.modems,comp.mail.uucp
Subject: Re: Telebit TrailBlazers and UUCP
Message-ID: <368@octopus.UUCP>
Date: Wed, 18-Nov-87 14:40:23 EST
Article-I.D.: octopus.368
Posted: Wed Nov 18 14:40:23 1987
Date-Received: Sat, 21-Nov-87 11:18:06 EST
References: <222@lamont.LDGO.Columbia.edu>
Reply-To: pete@octopus.UUCP (Pete Holzmann)
Organization: Octopus Enterprises, Cupertino, CA
Lines: 25
Keywords: uucp trailblazers timeouts
Summary: Maybe a trailblazer bug?
Xref: mnetor comp.dcom.modems:1206 comp.mail.uucp:972

In article <222@lamont.LDGO.Columbia.edu> dale@lamont.LDGO.Columbia.edu (dale chayes) writes:
>We are now running between the lab and the ship (at sea) through 
>an INMARSAT satelite link and having intermittent problems.  In general,
>we see "pkcget: alarm n" and eventually the link fails.  We are sucessfully
>transfering files, but the data rate is highly variable, and it is
>not reliable enough to let it run automagicly.

We just received our Trailblazer, running firmware level 3.01. I can also get
the link into a 'pcget: alarm 1' infinite loop. It almost always happens if
I force the serial line between my cpu and the modem to lose a few characters
(either by overrunning the FIFO in the cpu, or by glitching the serial line
with a breakout box.

Since this doesn't happen if I'm not running the Trailblazer's 'g' protocol
spoof, I'm ready to guess that there's a bug in the modem's error recovery
support. I'm working hard on this right now! 

Has anybody else seen this problem?

Pete

-- 
  OOO   __| ___      Peter Holzmann, Octopus Enterprises
 OOOOOOO___/ _______ USPS: 19611 La Mar Court, Cupertino, CA 95014
  OOOOO \___/        UUCP: {hplabs!hpdsd,pyramid}!octopus!pete
___| \_____          Phone: 408/996-7746