Path: utzoo!utgpu!water!watmath!clyde!rutgers!cbmvax!grr From: grr@cbmvax.UUCP (George Robbins) Newsgroups: comp.dcom.modems Subject: Re: Trailblazer, flow control, DMF32 Keywords: telebit trailblazer emulex 19200 Message-ID: <3313@cbmvax.UUCP> Date: 12 Feb 88 08:00:02 GMT References: <272@coherent.uucp> <3249@cbmvax.UUCP> <10433@mimsy.UUCP> <14856@oliveb.olivetti.com> Reply-To: grr@cbmvax.UUCP (George Robbins) Distribution: comp Organization: Commodore Technology, West Chester, PA Lines: 28 In article <14856@oliveb.olivetti.com> jerry@oliveb.UUCP (Jerry Aguirre) writes: > > However the Telebit modem doesn't seem to handle 19200 very well either. > First is the already mentioned problem of getting it to auto-baud > reliably at 19200. Then it will refuse to dial if I send it the ATDT > sequence at full speed. It just sits there. Even when I "tip" to the > modem and type the ATDT sequence slowly it will suddenly type "RNG" or > CNNT in the middle of my typing. Very strange. > Jerry Aguirre Sounds like you're accessing the modem at the same time uucp or some other agency is. Seeing missing characters is often a sign of this. Especially if you start getting result codes when you aren't doing anything to deserve them. Or perhaps it's an incomming call? I've seen the "ignored" ATDT sequences, but I think this is just a sign of failure to auto-baud. One person represented that once the modem started to echo you knew it had auto-bauded, unfortunatly I run mine with echo disabled. Dropping DTR (or perhaps sending a break) then sending some A's or AT's with delays between them seems to work, however it doesn't seem to work every time with only one extra AT... -- George Robbins - now working for, uucp: {uunet|ihnp4|rutgers}!cbmvax!grr but no way officially representing arpa: cbmvax!grr@uunet.uu.net Commodore, Engineering Department fone: 215-431-9255 (only by moonlite)