Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] (cvs) RTN with 2-D, ok (MCF) with 1-D
Giulio Orsero <giulioo@pobox.com> writes:
> >Could you try to connect both modems to the Hylafax server and send the
> >same fax from modem #2 to modem #1? The log on receiving side is very
> >interesting. Also save intermediate TIFF -- it would help to catch the bug
> >if it really exists.
>
> I tried
> FROM modem #2 (topic) attached to a server with the latest cvs
> TO modem #1 (rockwell) attached to a server with april cvs (beta2).
>
> "Unfortunately" the fax trasmission went well, no errors.
> However the log at the receiving side show some "anomalies" (bad pixel count),
> so I'm sending it; note that the same anomalies show with 1D,
> though. I don't remember seeing the same anomalies when
> the sending fax was the rockwell chipset one; tomorrow I'll be able to
> test this.
Yes, that's very interesting.
> If necessary, tomorrow I can attach the receiving modem to
> a current cvs version.
>
> What do you mean by "intermediate" tiff? The tiff on the receiving side?
The TIFF on the *sending* side generated by Ghostscript, temporarily
created in docq directory; something like doc2107.ps;70 (you can recognize
it by "II*" in the beginning).
> The tiff received by HylaFAX was ok, no barcode.
>
> Thanks
>
> Oct 29 21:24:13.80: [17391]: SESSION BEGIN 00003330 39111111111
> Oct 29 21:24:13.80: [17391]: MODEM set XON/XOFF/FLUSH: input ignored, output disabled
> Oct 29 21:24:13.80: [17391]: <-- [4:ATA\r]
> Oct 29 21:24:19.90: [17391]: --> [7:CONNECT]
> Oct 29 21:24:19.90: [17391]: ANSWER: FAX CONNECTION
> Oct 29 21:24:19.90: [17391]: STATE CHANGE: ANSWERING -> RECEIVING
> Oct 29 21:24:19.90: [17391]: MODEM input buffering enabled
> Oct 29 21:24:19.90: [17391]: RECV FAX: begin
> Oct 29 21:24:19.92: [17391]: MODEM input buffering disabled
> Oct 29 21:24:19.92: [17391]: <-- HDLC<23:FF C0 02 0C EC 6C EC 4C 6C 04 9C 8C 0C 04 9C CC D4 04 04 04 04 04 04>
> Oct 29 21:24:19.92: [17391]: <-- data [23]
> Oct 29 21:24:19.92: [17391]: <-- data [2]
> Oct 29 21:24:21.59: [17391]: --> [7:CONNECT]
> Oct 29 21:24:21.59: [17391]: <-- HDLC<10:FF C8 01 00 77 5F 01 79 03 C0>
> Oct 29 21:24:21.59: [17391]: <-- data [10]
> Oct 29 21:24:21.59: [17391]: <-- data [2]
> Oct 29 21:24:22.14: [17391]: --> [2:OK]
> Oct 29 21:24:22.14: [17391]: <-- [9:AT+FRH=3\r]
> Oct 29 21:24:22.54: [17391]: --> [7:CONNECT]
> Oct 29 21:24:24.03: [17391]: --> HDLC<25:FF C0 C2 0C 0C 0C 0C 0C 0C 04 0C 0C 0C 04 9C CC D4 04 04 04 04 04 04 C7 7B>
> Oct 29 21:24:24.03: [17391]: --> [2:OK]
> Oct 29 21:24:24.03: [17391]: REMOTE TSI "+39 000 000000"
> Oct 29 21:24:24.03: [17391]: <-- [9:AT+FRH=3\r]
> Oct 29 21:24:24.05: [17391]: --> [7:CONNECT]
> Oct 29 21:24:24.38: [17391]: --> HDLC<8:FF C8 C1 00 47 1E 36 71>
> Oct 29 21:24:24.39: [17391]: --> [2:OK]
> Oct 29 21:24:24.39: [17391]: REMOTE wants 14400 bit/s
> Oct 29 21:24:24.39: [17391]: REMOTE wants page width 1728 pixels in 215 mm
> Oct 29 21:24:24.39: [17391]: REMOTE wants unlimited page length
> Oct 29 21:24:24.39: [17391]: REMOTE wants 7.7 line/mm
> Oct 29 21:24:24.39: [17391]: REMOTE wants 2-D MR
> Oct 29 21:24:24.39: [17391]: RECV training at v.17 14400 bit/s
> Oct 29 21:24:24.39: [17391]: MODEM set XON/XOFF/DRAIN: input ignored, output generated
> Oct 29 21:24:24.39: [17391]: <-- [11:AT+FRM=145\r]
> Oct 29 21:24:26.18: [17391]: --> [7:CONNECT]
> Oct 29 21:24:27.76: [17391]: MODEM set XON/XOFF/DRAIN: input ignored, output disabled
> Oct 29 21:24:27.76: [17391]: RECV: TCF 2808 bytes, 0% non-zero, 2774 zero-run
> Oct 29 21:24:27.77: [17391]: --> [10:NO CARRIER]
> Oct 29 21:24:27.77: [17391]: DELAY 75 ms
> Oct 29 21:24:27.85: [17391]: <-- [9:AT+FTH=3\r]
> Oct 29 21:24:27.90: [17391]: --> [7:CONNECT]
> Oct 29 21:24:27.90: [17391]: <-- HDLC<3:FF C8 21>
> Oct 29 21:24:27.90: [17391]: <-- data [3]
> Oct 29 21:24:27.90: [17391]: <-- data [2]
> Oct 29 21:24:29.22: [17391]: --> [2:OK]
> Oct 29 21:24:29.22: [17391]: TRAINING succeeded
> Oct 29 21:24:29.22: [17391]: MODEM input buffering enabled
> Oct 29 21:24:29.22: [17391]: MODEM set XON/XOFF/FLUSH: input ignored, output generated
> Oct 29 21:24:29.22: [17391]: <-- [11:AT+FRM=146\r]
> Oct 29 21:24:29.79: [17391]: --> [7:CONNECT]
> Oct 29 21:24:29.79: [17391]: RECV: begin page
> Oct 29 21:24:43.29: [17391]: RECV/CQ: Bad 2D pixel count, row 1366, got 79, expected 1728
The error happens just before RTC, which is send separately. Maybe the
problem is caused by too slow logging on the sending side (together with
the flow control problems in the modem)? Disable the session logging there
and try again.
> Oct 29 21:24:43.29: [17391]: RECV/CQ: Bad 1D pixel count, row 1367, got 0, expected 1728
> Oct 29 21:24:43.29: [17391]: RECV/CQ: Bad 1D pixel count, row 1368, got 0, expected 1728
> Oct 29 21:24:43.29: [17391]: RECV/CQ: Bad 1D pixel count, row 1369, got 0, expected 1728
> Oct 29 21:24:43.29: [17391]: RECV/CQ: Bad 1D pixel count, row 1370, got 0, expected 1728
> Oct 29 21:24:43.29: [17391]: RECV/CQ: Bad 1D pixel count, row 1371, got 0, expected 1728
That's quite normal (RTC code)
> Oct 29 21:24:43.69: [17391]: RECV/CQ: Adjusting for RTC found at row 1366
[...]
Hope to hear from you soon,
Dmitry
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null