NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/protocol/ppp/752

Internet Message Format | 1992-09-08 | 1.9 KB

Xref: sparky comp.protocols.ppp:752 comp.dcom.modems:13060
Newsgroups: comp.protocols.ppp,comp.dcom.modems
Path: sparky!uunet!mcsun!sunic!psinntp!psinntp!hyphenw!dwight
From: [e-mail] (Dwight Ernest)
Subject: Re: Help with World Blazer
Message-ID: <[e-mail]>
Organization: Hyphen, Inc., Wilmington, MA 01887 USA / [phone]
References: <[e-mail]> <[e-mail]>
Date: Sun, 6 Sep 1992 21:25:05 GMT
Lines: 26

[e-mail] (Dave Platt) writes:

>I have noticed that the WorldBlazer command-parser seems to have trouble
>if you blast dialing commands at it at a high serial-port speed.  Last
>night, I tried using Taylor uucp (1.03) to dial out using our
>WorldBlazer with the serial-port speed set to 38400 (and the WorldBlazer
>configuration set to use that speed, only).  The first few bytes of the
>dial-and-configuration command went out OK, as each one is followed by a
>pause to allow the modem to autobaud (not necessary in this case).
>However, when the remainder of the command was blasted out at 38400 bps,
>the WorldBlazer abruptly deasserted CTS and failed to respond.

>You may need to hack your dialer so that the dialing command is
>"paced"... that is, your dialer must send each individual character, and
>then pause for 10 milliseconds or so before sending the next character.
>This may enable the WorldBlazer to keep up with the command.

I've noticed the same thing on password input.  When S46==3 and a dialin
password is set in the WB, if the dialin password is entered too quickly
by the calling system, it will fail to be properly interpreted.  We've
had to setup our UUCP scripts in such a way that the modem password is
entered slowly, with a slight pause between each character.
--
--Dwight A. Ernest   Special Projects Engineer   I speak only for myself.
  Hyphen, Inc. / 187 Ballardvale St. / Wilmington, MA 01887 / [phone]
  [e-mail]        [e-mail]