> From: Michael L. Collins <[EMAIL PROTECTED]>
>
> When I use minicom the modem seems
> to work OK. That is, I can send AT commands
> and get OK responses. But when I attempt
> the same commands in the chatscript,
> the script never recieves the "OK" response
> from the modem. pppd exits with (alarm) chatscript
> failed. Any Ideas?
>
----------
> From: Philip Hands <[EMAIL PROTECTED]>
>
> You have to be fairly patient with I-modems, because they take a long
time to
> reset compared with other modems (in some of the versions of the code
this was
> bad enough to make the modem fairly unusable, but the recent code seems
OK)
>
> My mgetty init-chat string (which works with all but the most broken code
> versions) is as follows:
>
> init-chat "" \d\d\d\d\r\d\n\dAT OK ATZ OK ATTS0=0S13.0=1 OK
>
> The delays and carriage return before the first AT gives the modem enough
time
> to recover from the fact that it did an implicit ATZ when DTR dropped on
the
> last connection.
>
Noop,
I added serveral delays, but still do not get a response from modem
when using the chatscript.
By the way, in minicom this modem responses very quickly,
as to returning an "OK". It does seem a bit slower about dialing,
but is reasonable.
I noticed that If I send AT commands from a shell
with echo "AT" > /dev/cua1
I do not get an OK response to the shell.
Would you expect a response to shell here?
Thanks,
Michael
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
