[hylafax-users] Bad 1D/2D pixel counts and invalid code words

To: <hylafax-users@hylafax.org>
Subject: [hylafax-users] Bad 1D/2D pixel counts and invalid code words
From: "Dennis Fellows" <dennis@lamtop.com>
Date: Thu, 12 Apr 2001 15:55:26 -0500
Well, I upgraded to beta3 with no prob and set my session tracing to 0xFFF.
I haven't experienced any Faxgetty hangs (yet)!

I've got some questions as to what the errors are. I waited for at least
three faxes to come in to make sure that the errors were typical (they
were). Now, I know that I may be dealing with line noise (I've given up
fighting with my local telco (Ameritech) and am moving to a local T1 from
another phone company) but I want to make sure these errors are not config
errors. Here is a typical log with my questions interspersed (**)....
Apr 12 14:05:43.55: [ 6035]: SESSION BEGIN 00000004 12626584152
Apr 12 14:05:43.55: [ 6035]: <-- [4:ATA\r]
Apr 12 14:05:50.14: [ 6035]: --> [74:+FHT:FF 03 40 32 35 31 34 49 50 4C 20
20 20
 20 20 20 20 20 20 20 20 20 20 ]
Apr 12 14:05:50.94: [ 6035]: --> [26:+FHT:FF 13 80 00 EE FA 02 ]
Apr 12 14:05:52.00: [ 6035]: --> [5:+FCON]
Apr 12 14:05:52.00: [ 6035]: ANSWER: FAX CONNECTION
Apr 12 14:05:52.00: [ 6035]: STATE CHANGE: ANSWERING -> RECEIVING
Apr 12 14:05:52.00: [ 6035]: MODEM input buffering enabled
Apr 12 14:05:52.00: [ 6035]: RECV FAX: begin
Apr 12 14:05:53.75: [ 6035]: --> [74:+FHR:FF 03 43 32 32 34 34 30 37 32 38
30 36 20 20 20 20 20 20 20 20 20 20 ]
Apr 12 14:05:54.01: [ 6035]: --> [23:+FHR:FF 13 83 00 A2 28 ]
Apr 12 14:05:57.24: [ 6035]: --> [28:+FTSI:"          6082704422"]
Apr 12 14:05:57.24: [ 6035]: REMOTE TSI "6082704422"
Apr 12 14:05:57.24: [ 6035]: --> [21:+FDCS:0,5,0,2,1,0,0,3]
Apr 12 14:05:57.24: [ 6035]: REMOTE wants 14400 bit/s
Apr 12 14:05:57.24: [ 6035]: REMOTE wants page width 1728 pixels in 215 mm
Apr 12 14:05:57.24: [ 6035]: REMOTE wants unlimited page length
Apr 12 14:05:57.24: [ 6035]: REMOTE wants 3.85 line/mm
Apr 12 14:05:57.24: [ 6035]: REMOTE wants 2-D MR
Apr 12 14:05:57.24: [ 6035]: --> [2:OK]
Apr 12 14:05:57.24: [ 6035]: --> [2:OK]
Apr 12 14:05:57.24: [ 6035]: <-- [7:AT+FDR\r]
Apr 12 14:05:58.34: [ 6035]: --> [14:+FHT:FF 13 84 ]
Apr 12 14:05:58.63: [ 6035]: --> [5:+FCFR]
Apr 12 14:05:58.63: [ 6035]: --> [28:+FTSI:"          6082704422"]
Apr 12 14:05:58.63: [ 6035]: REMOTE TSI "6082704422"
Apr 12 14:05:58.63: [ 6035]: --> [21:+FDCS:0,5,0,2,1,0,0,3]
Apr 12 14:05:58.63: [ 6035]: REMOTE wants 14400 bit/s
Apr 12 14:05:58.63: [ 6035]: REMOTE wants page width 1728 pixels in 215 mm
Apr 12 14:05:58.63: [ 6035]: REMOTE wants unlimited page length
Apr 12 14:05:58.63: [ 6035]: REMOTE wants 3.85 line/mm
Apr 12 14:05:58.63: [ 6035]: REMOTE wants 2-D MR
Apr 12 14:06:00.13: [ 6035]: --> [7:CONNECT]
Apr 12 14:06:00.13: [ 6035]: RECV: begin page
Apr 12 14:06:00.13: [ 6035]: RECV: send trigger 022
Apr 12 14:06:00.13: [ 6035]: <-- data [1]
Apr 12 14:06:00.90: [ 6035]: RECV/CQ: Bad 2D pixel count, row 0, got 0,
expected  1728
Apr 12 14:06:01.12: [ 6035]: RECV/CQ: Bad 1D pixel count, row 11, got 1732,
expe
cted 1728
Apr 12 14:06:01.41: [ 6035]: RECV/CQ: Invalid 2D code word, row 27, x 1046

** Why am I getting Bad 2D and 1D pixel counts. What is the invalid 2D code
word? **

Apr 12 14:06:01.41: [ 6035]: RECV/CQ: Bad 2D pixel count, row 27, got 1046,
expe
cted 1728
Apr 12 14:06:05.12: [ 6035]: RECV/CQ: Bad 1D pixel count, row 260, got 1705,
exp
ected 1728
Apr 12 14:06:05.12: [ 6035]: RECV/CQ: Bad 2D pixel count, row 261, got 1803,
exp
ected 1728
Apr 12 14:06:09.22: [ 6035]: RECV/CQ: Bad 1D pixel count, row 500, got 1730,
exp
ected 1728
Apr 12 14:06:14.87: [ 6035]: RECV/CQ: Invalid EOL code word, row 819, x 1364

** Another odd error **

Apr 12 14:06:14.87: [ 6035]: RECV/CQ: Bad 2D pixel count, row 819, got 1364,
exp
ected 1728
Apr 12 14:06:14.87: [ 6035]: RECV/CQ: Bad 2D pixel count, row 820, got 2092,
exp
ected 1728
Apr 12 14:06:14.87: [ 6035]: RECV/CQ: Bad 1D pixel count, row 821, got 2160,
exp
ected 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1050, got 0,
expec
ted 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1051, got 0,
expec
ted 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1052, got 0,
expec
ted 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1053, got 0,
expec
ted 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1054, got 0,
expec
Apr 12 14:06:18.32: [ 6035]: RECV: 31208 bytes of data, 1055 total lines

** This is typical : I get 5 lines in a row at the end of a page that error
then an "adjusting" statement**

Apr 12 14:06:18.32: [ 6035]: RECV/CQ: Adjusting for RTC found at row 1049
Apr 12 14:06:18.32: [ 6035]: --> [15:+FPTS:1,0,0,0,0]
Apr 12 14:06:19.60: [ 6035]: --> [14:+FHR:FF 13 4F ]
Apr 12 14:06:19.60: [ 6035]: --> [6:+FET:0]
Apr 12 14:06:19.60: [ 6035]: RECV recv MPS (more pages, same document)
Apr 12 14:06:19.60: [ 6035]: --> [2:OK]
Apr 12 14:06:19.60: [ 6035]: RECV send MCF (message confirmation)
Apr 12 14:06:19.60: [ 6035]: RECV FAX (00000004): from 6082704422, page 1 in
0:2
2, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
Apr 12 14:06:19.60: [ 6035]: <-- [7:AT+FDR\r]
Apr 12 14:06:20.77: [ 6035]: --> [14:+FHT:FF 13 8C ]
Apr 12 14:06:22.55: [ 6035]: --> [7:CONNECT]
Apr 12 14:06:22.55: [ 6035]: RECV: begin page
Apr 12 14:06:22.55: [ 6035]: RECV: send trigger 022
Apr 12 14:06:22.55: [ 6035]: <-- data [1]
Apr 12 14:06:23.32: [ 6035]: RECV/CQ: Bad 2D pixel count, row 0, got 0,
expected
 1728
Apr 12 14:06:26.01: [ 6035]: RECV/CQ: Bad 2D pixel count, row 116, got 1913,
exp
ected 1728
Apr 12 14:06:26.88: [ 6035]: RECV/CQ: Invalid EOL code word, row 162, x 465
Apr 12 14:06:26.88: [ 6035]: RECV/CQ: Bad 2D pixel count, row 162, got 465,
expe
cted 1728
Apr 12 14:06:26.88: [ 6035]: RECV/CQ: Invalid BlackTable code word, row 163,
x 5
39

** I've received "Invalid WhiteTable code word" on the other faxes **
Apr 12 14:06:26.88: [ 6035]: RECV/CQ: Bad 1D pixel count, row 163, got 539,
expe
cted 1728
Apr 12 14:06:26.96: [ 6035]: RECV/CQ: Bad 2D pixel count, row 164, got 1730,
exp
ected 1728
Apr 12 14:06:27.32: [ 6035]: RECV/CQ: Invalid EOL code word, row 181, x 1618
Apr 12 14:06:27.32: [ 6035]: RECV/CQ: Bad 2D pixel count, row 181, got 1618,
exp
ected 1728
Apr 12 14:06:27.98: [ 6035]: RECV/CQ: Bad 1D pixel count, row 220, got 1773,
exp
ected 1728
Apr 12 14:06:27.98: [ 6035]: RECV/CQ: Bad 2D pixel count, row 221, got 1729,
exp
ected 1728
Apr 12 14:06:41.53: [ 6035]: RECV: 32751 bytes of data, 838 total lines
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1341, got 0,
expec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1342, got 0,
expec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1343, got 0,
expec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1344, got 0,
expec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1345, got 0,
expec
ted 1728
Apr 12 14:06:54.43: [ 6035]: RECV: 23119 bytes of data, 1346 total lines
Apr 12 14:06:54.43: [ 6035]: RECV/CQ: Adjusting for RTC found at row 1340
Apr 12 14:06:54.43: [ 6035]: --> [15:+FPTS:1,0,0,0,0]
Apr 12 14:06:55.72: [ 6035]: --> [14:+FHR:FF 13 2F ]
Apr 12 14:06:55.72: [ 6035]: --> [6:+FET:2]
Apr 12 14:06:55.72: [ 6035]: RECV recv EOP (no more pages or documents)
Apr 12 14:06:55.72: [ 6035]: --> [2:OK]
Apr 12 14:06:55.72: [ 6035]: RECV send MCF (message confirmation)
Apr 12 14:06:55.72: [ 6035]: RECV FAX (00000004): from 6082704422, page 2 in
0:3
6, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
Apr 12 14:06:55.72: [ 6035]: RECV FAX (00000004): recvq/fax00004.tif from
608270
4422, route to <unspecified>, 2 pages in 1:03
Apr 12 14:06:55.72: [ 6035]: <-- [7:AT+FDR\r]
Apr 12 14:06:56.82: [ 6035]: --> [14:+FHT:FF 13 8C ]
Apr 12 14:06:56.82: [ 6035]: RECV FAX: bin/faxrcvd "recvq/fax00004.tif"
"ttyR0"
"00000004" ""

The fax comes across with a few black lines but is perfectly readable.
Here's the config file for that line (Extra stuff snipped)...

[SNIP]
CountryCode:            1
AreaCode:               262
FAXNumber:              1.262.658.4152
LongDistancePrefix:     1
InternationalPrefix:    011
DialStringRules:        etc/dialrules
ServerTracing:          1
SessionTracing:         0xFFF
RecvFileMode:           0600
LogFileMode:            0600
DeviceMode:             0600
RingsBeforeAnswer:      1
SpeakerVolume:          off
GettyArgs:              "-h %l dx_%s"
LocalIdentifier:        LPI4152
TagLineFont:            etc/lutRS18.pcf
TagLineFormat:          "From %%l|%c|Page %%P of %%T"
MaxRecvPages:           250
#
#
TagLineFont:            etc/lutRS18.pcf
TagLineFormat:          "From %%l|%c|Page %%P of %%T"
MaxRecvPages:           250
#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType:              Class2          # use class 2 interface
ModemRate:              57600
ModemFlowControl:       rtscts          # default
#
ModemHardFlowCmd:       AT&E4           # hardware flow control
ModemSoftFlowCmd:       AT&E5           # software flow control
ModemSetupDTRCmd:       AT&D3           # setup so DTR drop resets modem
ModemSetupDCDCmd:       AT&C1           # setup so DCD reflects carrier (or
not)
ModemSetupAACmd:        AT+FAA=1        # enable adaptive-answer in class 2
#
# NB: some models get confused by the @
#
ModemDialCmd:           ATDT%s@         # T for tone dialing, @ for silence
#
Class2RecvDataTrigger:  "\022"          # character sent to modem to start
recv

Best Regards,
Dennis




____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null
Follow-Ups:
- Re: [hylafax-users] Bad 1D/2D pixel counts and invalid code words
  - From: Lee Howard <faxguy@deanox.com>
Prev by Date: Re: [hylafax-users] [Fwd: HylaFAX vulnerability]
Next by Date: Re: [hylafax-users] Bad 1D/2D pixel counts and invalid code words
Prev by thread: Re: [hylafax-users] [Fwd: HylaFAX vulnerability]
Next by thread: Re: [hylafax-users] Bad 1D/2D pixel counts and invalid code words
Index(es):
- Main
- Thread
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services