home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.modems
- Path: sparky!uunet!spool.mu.edu!umn.edu!csus.edu!netcom.com!wolfgang
- From: wolfgang@netcom.com (Wolfgang Henke)
- Subject: Re: Digicom Scout+ problems
- Message-ID: <1993Jan7.074704.18893@netcom.com>
- Organization: Netcom
- X-Newsreader: Tin 1.1 PL5
- References: <9301070210.AA05696@poincare.phys.cmu.edu>
- Date: Thu, 7 Jan 1993 07:47:04 GMT
- Lines: 31
-
- Bradley D. Keister (keister@poincare.phys.cmu.edu) wrote:
- : 2. There are also times (which keep recurring, though I can't
- : forcibly reproduce them) where the modem becomes completely silent,
- : that is, it gives no response whatsoever to any AT commands, including
- : AT*O, and various AT&F commands (even repeated); by "silent" I mean
- : not just no echo, but no OK, either. The only way I can remedy this
- : is to reboot, and, in a few instances, use the reset button. Is this
- : something I should expect, and/or is there a way around it?
-
- The Scout has a command line timeout of about 8 to 10 seconds with the
- intention to minimize the chance of accidental escapes into command
- mode. When you type a command like AT and then wait several seconds,
- maybe to look something up in the manual or quick reference card and
- then continue the command with maybe *O<RETURN> there will be no
- response, because the timeout was triggered. In this case one has to
- start again with AT, AT*O in this case.
-
- Since you write 'even repeated' this may not be your problem, however.
- You may check your ROM version with ATI1. I posted a while ago that
- there is a problem with the 2915/2930 ROM, which can lead to occasional
- lockups. This situation was resolved about two or three months ago
- already. Personnally I use this particular combination in an external
- Scout+ and have been waiting for weeks now for my first lockup.
-
-
-
-
- --
- _________________________________________________________________________
- Wolfgang Henke Data lanes not car pool lanes wolfgang@netcom.com
-
-