🚀 go-pugleaf

In article <1992Sep1.172122.8640@colorado.edu> laura@boulder.colorado.edu (Laura Compagnoni) writes:
   Is anybody using this modem with better luck than me?

We like ours fine.  We set it up first with

at&f9 s0=1 s7=120 s48=1 s51=6 s58=2 s59=15 s61=0 s63=1 s92=1 tq2x12&c1&d3&s1&w

which results in

WorldBlazer - SA - Version LA5.01 - Active Configuration
 B1  E1  L1  M1  Q2  T   V1  X12  Y0
&C1 &D3 &G0 &J0 &L0 &Q0 &R3 &S1 &T4 &X0
S000:1   S001=0   S002=43  S003=13  S004=10  S005=8   S006=2   S007:120
S008=2   S009=6   S010=14  S011=70  S012=50  S018=0   S025=5   S026=1
S038=0   S041=0   S045=0   S046=0   S047=4   S048:1   S050=0   S051:6
S056=17  S057=19  S058:2   S059:15  S060=0   S061:0   S062=15  S063:1
S064=0   S068=255 S069=0   S090=0   S092:1   S093=8   S094=1   S100=0
S104=0   S105=1   S111=255 S112=1   S151=4   S155=0   S180=2   S181=1
S183=25  S190=1   S191=7   S253=10  S254=255 S255=255
OK

which differs from your registers in some perhaps-significant ways.

>I have two WorldBlazer's wich I want to use to run PPP.
>I was successfull in setting the modems up in such a way that the one I use
>for dial in works fine when I call using a T2500.
>But if I use the other WB to dial out the chat program can not communicate
>well with the modem and the call aborts before the modem goes on hook.
>I tried to dial out with tip, the version that comes with slip, and the
>dialer get confused as well.
>Is anybody using this modem with better luck than me?

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.

-- 
Dave Platt                                                VOICE: (415) 813-8917
              Domain: dplatt@ntg.com      UUCP: ...netcomsv!ntg!dplatt
 USNAIL: New Technologies Group Inc. 2468 Embarcardero Way, Palo Alto CA 94303

In article <1992Sep2.172450.10844@ntg.com> dplatt@ntg.com (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).

Don't take this as a flame, but
why are you using autobaud?  Just lock the DTE speed and be done with it.
That might solve your problem.  You could also break the dialing command into
pieces.    I use about a 60-80 char string for some dialing and don't
have a problem.  This is at 19200 though.  But, I would assume the input
buffer is the same size.
-- 
Alan Edmonds                                     Texas Instruments, Inc.
I don't speak for TI; TI doesn't speak for me    M/S 8513
Work phone: (214)575-6427                        6620 Chase Oaks Blvd.
Email: alan@ernest.dseg.ti.com                   Plano, Texas  75023

dplatt@ntg.com (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 / +1 508 988 0880
  dae@world.std.com		dwight@hyphen.com