> On Sun, Oct 12, 2008 at 07:32:20PM -0500, Andy Herkey wrote: > >>>> Run the script and post the screen output and the /tmp/modemtest.log >>>> it creates. >>>> > > Thanks for your help on this Andy! > > I've finally gotten around to adding your modemtest.rb script to contrib. > I've added both versions (one from Aug and this one) to the CVS history. > > I've also added the following copyright notice and help text. Please > let me know if my assumption is correct with regard to the license. > > # > # Copyright (C) 2008, Andy Herkey <[EMAIL PROTECTED]> > # > # This program is free software; you can redistribute it and/or modify > # it under the terms of the GNU General Public License as published by > # the Free Software Foundation; either version 2 of the License, or > # (at your option) any later version. > # > # This program is distributed in the hope that it will be useful, > # but WITHOUT ANY WARRANTY; without even the implied warranty of > # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > # > # See the GNU General Public License in the COPYING file at the > # root directory of this project for more details. > # > # > > # > # The purpose of this script is to try a large batch of known AT > # commands, and report which ones work with your Blackberry > # modem / provider. There will be output written to stdout > # as well as a file created in /tmp/modemtest.log which holds > # the raw pppob traffic log. > # > Works for me! Thanks. :) > >> Mike, >> The modem responded as expected to the commands that were sent to it >> which leads me to believe there is a problem with the chat script. Try >> creating a new chat script with just the following: >> >> ABORT ERROR '' >> +++AT '' >> ATZ OK >> AT&F OK >> ATE0V1 OK >> AT OK >> ATS0=0 OK >> ATDT#777 CONNECT >> > > > I'm inclined to update the barry-verizon.chat script to this version. > Could other Verizon users test this and let me know if they run into > problems? > > Chris, this chat script is a little odd since it is backwards from normal chat scrips. I did it that way on purpose to make it clear when you send the command ATZ to expect OK. I never understood the why the expected response for the command on the previous line on the same line as the next command. I guess it was more clear back in the UUCP days when it was all on one line. Any way this is the standard way of doing it:
ABORT ERROR '' +++AT '' ATZ OK AT&F OK ATE0V1 OK AT OK ATS0=0 OK ATDT#777 CONNECT Some people seem confused on how these chat scripts work. You know this stuff, but for those that don't here are some basics. Chat scripts do 3 main things for all modems and service providers. 1. Get the modem's attention. 2. Initialize the modem. (Very important because the rest of the chat script depends on this.) 3. Dial a number. The obvious difference would be the dial number. The not so obvious would be what needs to go between step 2 and step 3. This is were the service provider settings need to go. Things like setting up Access points i.e. (AT+CGDCONT=1,"IP","internet.com"). Hope that helps someone. --Andy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel