Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Failed to properly detect high-speed data carrier
The error message "Failed to properly detect high-speed data carrier"
is merely an indicator of some other problem that occurred earlier in
the session that now is preventing the modem from being able to detect
the image data carrier.
On 2004.12.13 02:03 Sing wrote:
Dec 13 17:41:22.18: [ 3306]: RECV training at v.17 14400 bit/s
Dec 13 17:41:22.18: [ 3306]: <-- [11:AT+FRM=145\r]
Dec 13 17:41:24.20: [ 3306]: --> [7:CONNECT]
Dec 13 17:41:25.70: [ 3306]: RECV: TCF 2718 bytes, 79% non-zero, 393
zero-run
Dec 13 17:41:25.70: [ 3306]: RECV: reject TCF (too many non-zero, max
10%)
Dec 13 17:41:25.70: [ 3306]: RECV: reject TCF (zero run too short, min
1800)
Firstly, it looks like there is some kind of interference. Note how
both V.17 14400 and V.17 12000 fail training...
Dec 13 17:41:30.39: [ 3306]: RECV training at v.17 12000 bit/s
Dec 13 17:41:30.39: [ 3306]: <-- [11:AT+FRM=121\r]
Dec 13 17:41:32.41: [ 3306]: --> [7:CONNECT]
Dec 13 17:41:33.92: [ 3306]: RECV: TCF 2266 bytes, 96% non-zero, 38
zero-run
Dec 13 17:41:33.92: [ 3306]: RECV: reject TCF (too many non-zero, max
10%)
Dec 13 17:41:33.92: [ 3306]: RECV: reject TCF (zero run too short, min
1500)
It's almost as if the sender and receiver V.17 modulators are
incompatible.
Dec 13 17:41:38.61: [ 3306]: RECV training at v.17 9600 bit/s
Dec 13 17:41:38.61: [ 3306]: <-- [10:AT+FRM=97\r]
Dec 13 17:41:40.63: [ 3306]: --> [7:CONNECT]
Dec 13 17:41:42.14: [ 3306]: RECV: TCF 1814 bytes, 1% non-zero, 1778
zero-run
And... the sender makes the unfortunate decision to use V.17 9600
rather than V.29 9600, so we won't really know if the problem is with
the modulators or with the line.
Dec 13 17:41:42.15: [ 3306]: --> [10:NO CARRIER]
Dec 13 17:41:42.15: [ 3306]: DELAY 75 ms
Dec 13 17:41:42.23: [ 3306]: TRAINING succeeded
Dec 13 17:41:42.23: [ 3306]: <-- [9:AT+FTH=3\r]
Dec 13 17:41:42.25: [ 3306]: --> [7:CONNECT]
Dec 13 17:41:42.25: [ 3306]: <-- data [3]
Dec 13 17:41:42.25: [ 3306]: <-- data [2]
Dec 13 17:41:43.92: [ 3306]: --> [2:OK]
Dec 13 17:41:43.92: [ 3306]: <-- [10:AT+FRM=98\r]
Dec 13 17:41:50.92: [ 3306]: <-- data [1]
Dec 13 17:41:51.03: [ 3306]: --> [2:^P^C]
Dec 13 17:41:51.03: [ 3306]: --> [2:OK]
But, when the modem went to listen for the high-speed data carrier
(AT+FRM=98) it couldn't hear it. So HylaFAX cancelled the command (<--
data [1]) and terminated the session.
I would recommend that you try a different modem (not USR). That
should give you some indication if it is a modulator incompatibility.
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*