home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.ppp:745 comp.dcom.modems:12881
- Path: sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!m2.dseg.ti.com!ernest!alan
- From: alan@ernest.dseg.ti.com (Alan Edmonds)
- Newsgroups: comp.protocols.ppp,comp.dcom.modems
- Subject: Re: Help with World Blazer
- Message-ID: <BtywCA.41v@ernest.dseg.ti.com>
- Date: 2 Sep 92 20:16:56 GMT
- References: <1992Sep1.172122.8640@colorado.edu> <1992Sep2.172450.10844@ntg.com>
- Organization: Texas Instruments, Inc. - Plano, Tx
- Lines: 20
-
- 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
-