Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!husc6!rice!sun-spots-request
From: frank@ladc.bull.com (Frank Mayhar)
Newsgroups: comp.sys.sun
Subject: Re: Telebit TB+ question
Keywords: Hardware
Message-ID: <411@ladcgw.ladc.bull.com>
Date: 19 May 89 17:40:19 GMT
References: <8905111742.AA06841@macduff.ultra.com>
Sender: usenet@rice.edu
Organization: Bull HN Los Angeles Development Center
Lines: 22
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 7, Issue 303, message 8 of 12

ultra!shj@ames.arc.nasa.gov (Steve Jay) writes:
>Our TB+ is connected to an ALM I port on our 3/280, running OS 4.0.1 + the
>serial patch tape (yapt 5.5).  It works great for tip & uucp.  The
>settings as reported by "at&n" are:
>S50=000 S51=255 S52=002 S53=001 S54=002 S55=000 S56=017 S57=019 S58=003 S59=000

Hmmm.  We just got our TB+, and are using it on a 3/160 running SunOS 3.3.
With S50=0 and S52=2, it refuses to answer the phone.  I've noticed that
when uucico exits, the DTR light on the front of the TB goes out.  So the
Sun isn't supplying DTR, so the modem won't answer incoming calls.  Right
now I have the modem configured to S50=255, S52=0 (PEP mode only, assume
DTR is always on), so it will answer high-speed calls from uunet.  I would
like to be able to use it for 2400 baud calls as well.  How can I either
make the Trailblazer answer calls with DTR low, or force the Sun 3 to
toggle DTR low when uucico exits, then raise it again?

Any help will be very much appreciated.  I ran into this when uunet informed
me that the modem didn't answer for 24 hours after I installed it.  Sigh.

Frank Mayhar  ..!uunet!ladcgw!frank (frank@ladc.bull.com)
              Bull HN Los Angeles Development Center
              5250 W. Century Blvd., LA, CA  90045  Phone:  (213) 216-6241