HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] RECV/CQ: Bad 1D pixel count ...



Diego Chaparro wrote:

Mar 02 14:13:50.91: [ 2382]: <-- [9:AT+FRH=3\r]
Mar 02 14:13:50.93: [ 2382]: --> [7:CONNECT]
Mar 02 14:13:51.25: [ 2382]: --> HDLC<8:FF C8 C1 00 44 1E 63 22>
Mar 02 14:13:51.28: [ 2382]: --> [2:OK]
Mar 02 14:13:51.28: [ 2382]: REMOTE wants 14400 bit/s
Mar 02 14:13:51.28: [ 2382]: REMOTE wants A4 page width (215 mm)
Mar 02 14:13:51.28: [ 2382]: REMOTE wants unlimited page length
Mar 02 14:13:51.28: [ 2382]: REMOTE wants 3.85 line/mm
Mar 02 14:13:51.28: [ 2382]: REMOTE wants 1-D MH
Mar 02 14:13:51.28: [ 2382]: RECV training at v.17 14400 bit/s
Mar 02 14:13:51.28: [ 2382]: MODEM set XON/XOFF/DRAIN: input ignored,
output generated
Mar 02 14:13:51.28: [ 2382]: <-- [11:AT+FRM=145\r]
Mar 02 14:13:53.07: [ 2382]: --> [7:CONNECT]
Mar 02 14:13:54.84: [ 2382]: MODEM set XON/XOFF/DRAIN: input ignored,
output disabled
Mar 02 14:13:54.84: [ 2382]: RECV: TCF 2520 bytes, 0% non-zero, 2520
zero-run
Mar 02 14:13:54.84: [ 2382]: --> [10:NO CARRIER]
Mar 02 14:13:54.84: [ 2382]: DELAY 75 ms
Mar 02 14:13:54.92: [ 2382]: TRAINING succeeded
Mar 02 14:13:54.92: [ 2382]: <-- [9:AT+FTH=3\r]
Mar 02 14:13:54.97: [ 2382]: --> [7:CONNECT]
Mar 02 14:13:54.97: [ 2382]: <-- HDLC<3:FF C8 21>
Mar 02 14:13:54.97: [ 2382]: <-- data [3]
Mar 02 14:13:54.97: [ 2382]: <-- data [2]
Mar 02 14:13:56.29: [ 2382]: --> [2:OK]
Mar 02 14:13:56.29: [ 2382]: MODEM input buffering enabled
Mar 02 14:13:56.29: [ 2382]: MODEM set XON/XOFF/FLUSH: input ignored,
output generated
Mar 02 14:13:56.29: [ 2382]: <-- [11:AT+FRM=146\r]
Mar 02 14:13:57.31: [ 2382]: --> [7:CONNECT]
Mar 02 14:13:57.31: [ 2382]: RECV: begin page
Mar 02 14:14:01.48: [ 2382]: RECV/CQ: Bad 1D pixel count, row 440, got
1607, expected 1728
Mar 02 14:14:05.82: [ 2382]: RECV/CQ: Bad 1D pixel count, row 574, got
2188, expected 1728
Mar 02 14:14:05.90: [ 2382]: RECV/CQ: Bad 1D pixel count, row 575, got
657, expected 1728
Mar 02 14:14:05.90: [ 2382]: RECV/CQ: Bad 1D pixel count, row 576, got
723, expected 1728
Mar 02 14:14:05.90: [ 2382]: RECV/CQ: Bad 1D pixel count, row 577, got
1744, expected 1728
Mar 02 14:14:06.45: [ 2382]: RECV/CQ: Bad 1D pixel count, row 593, got
1580, expected 1728
Mar 02 14:14:11.46: [ 2382]: RECV/CQ: Bad 1D pixel count, row 793, got
2160, expected 1728
Mar 02 14:14:11.46: [ 2382]: RECV/CQ: Bad 1D pixel count, row 794, got
1734, expected 1728
Mar 02 14:14:14.44: [ 2382]: RECV/CQ: Bad 1D pixel count, row 873, got
1649, expected 1728
Mar 02 14:14:14.44: [ 2382]: RECV/CQ: Bad 1D pixel count, row 874, got
3302, expected 1728
Mar 02 14:14:16.49: [ 2382]: RECV/CQ: Bad 1D pixel count, row 955, got
1616, expected 1728
Mar 02 14:14:17.74: [ 2382]: RECV/CQ: Bad 1D pixel count, row 1049, got
0, expected 1728
Mar 02 14:14:17.74: [ 2382]: RECV/CQ: Bad 1D pixel count, row 1050, got
0, expected 1728
Mar 02 14:14:17.74: [ 2382]: RECV/CQ: Bad 1D pixel count, row 1051, got
0, expected 1728
Mar 02 14:14:17.74: [ 2382]: RECV/CQ: Bad 1D pixel count, row 1052, got
0, expected 1728
Mar 02 14:14:18.24: [ 2382]: RECV/CQ: Adjusting for RTC found at row
1049
Mar 02 14:14:18.24: [ 2382]: RECV: 1049 total lines, 11 bad lines, 4
consecutive bad lines
Mar 02 14:14:18.24: [ 2382]: RECV: end page
Mar 02 14:14:18.24: [ 2382]: --> [10:NO CARRIER]
Mar 02 14:14:18.24: [ 2382]: <-- [9:AT+FRH=3\r]
Mar 02 14:14:19.50: [ 2382]: --> [7:CONNECT]
Mar 02 14:14:20.66: [ 2382]: --> HDLC<5:FF C8 F2 AC A0>
Mar 02 14:14:20.66: [ 2382]: --> [2:OK]
Mar 02 14:14:20.66: [ 2382]: RECV recv MPS (more pages, same document)
Mar 02 14:14:20.66: [ 2382]: DELAY 70 ms
Mar 02 14:14:20.73: [ 2382]: <-- [9:AT+FTH=3\r]
Mar 02 14:14:20.89: [ 2382]: --> [7:CONNECT]
Mar 02 14:14:20.89: [ 2382]: RECV send MCF (message confirmation)



The sender chose to not use ECM. Unfortunately, then, you're at risk of getting this kind of thing happening.


You could increase your sensitivity to bad scanlines with PercentGoodLines and MaxConsecutiveBadLines, but the end result of that is "just" RTN... and many senders do not retransmit the page with RTN, they just retrain and then send the next page, and perhaps indicate to the user that there was an error in sending.

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*




Project hosted by iFAX Solutions