Re: [hylafax-users] Modem damaged?

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Dave Forrest wrote:

> Dec 15 10:03:46.27: [ 2860]: RECV training at v.17 14400 bit/s
> Dec 15 10:03:46.27: [ 2860]: <-- [11:AT+FRM=145\r]
> Dec 15 10:03:48.01: [ 2860]: --> [7:CONNECT]
> Dec 15 10:03:52.69: [ 2860]: <-- data [1]
> Dec 15 10:03:52.71: [ 2860]: --> [10:NO CARRIER]
> Dec 15 10:03:52.71: [ 2860]: MODEM No carrier
> Dec 15 10:03:52.71: [ 2860]: RECV: TCF 2720 bytes, 0% non-zero, 2698 zero-run
> Dec 15 10:03:52.71: [ 2860]: <-- [9:AT+FRS=7\r]
> Dec 15 10:03:52.79: [ 2860]: --> [2:OK]
> Dec 15 10:03:52.79: [ 2860]: TRAINING succeeded
>  

The little "<-- data [1]" tells us that HylaFAX tried to abort the TCF 
reception attempt because it went a bit long.  However, instead of an OK 
response (as you'd normally see with an abort) the NO CARRIER response 
comes, so it tends to indicate that the sender either just dropped the 
carrier as we went to abort, or the modem was lagged in sending us the 
response and our abort data woke it up.

This could be a modem error, yes.  It's hard to say.  If this happens 
100% of the time then I'd certainly suspect that *something* is wrong, 
but maybe the modem is not the first thing that I'd suspect.  I'd test 
another modem to make sure before you deem this one as damaged.  I'd be 
more inclined to suspect a serial driver or something like that.

HylaFAX+ improves the handling of things in this kind of situation ... 
but I have my doubts that it would salvage the session.

> Dec 15 10:03:59.84: [ 2860]: <-- [9:AT+FRH=3\r]
> Dec 15 10:04:06.84: [ 2860]: --> [0:]
> Dec 15 10:04:06.84: [ 2860]: MODEM <Empty line>
> Dec 15 10:04:06.84: [ 2860]: <-- data [1]
> Dec 15 10:04:06.85: [ 2860]: --> [2:]
> Dec 15 10:04:06.86: [ 2860]: --> [2:OK]
> Dec 15 10:04:06.86: [ 2860]: <-- data [1]
> Dec 15 10:04:07.06: [ 2860]: MODEM <Timeout>

This is another place where HylaFAX+ is fixed.  (Notice that the abort 
comes *after* the OK response and *after* a previous - and successful - 
abort.)  But fixing this won't help rescue the session.

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*