|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[hylafax-users] Re: Bad code word at scanline with Zylex U1496E
___cliff rayman___ <cliff@genwax.com> writes:
> i am getting this Bad code word at scanline problem on about 10% of my
> received faxes..
> we are using: MODEM ZYXEL U1496E/V 6.19 P
>
> has anyone else gotten this modem to work with consistent results?
Yes, works great for me.
> if not, is there any consensus on a modem that does work well for both
> sending and receiving?
>
> below is my current config. i have toggled the ECM line (last line).
ECM is *not* implemented in this modem (despite +FCC responce), so better
disable it again ASAP.
> tried 38400 and 19200. and also tried the class2.0 interface. i still
> get the bad code word error message on about 10% of my faxes.:
> CountryCode: 1
> AreaCode: 818
> FAXNumber: 1.818.764.3878
> LongDistancePrefix: 1
> InternationalPrefix: 011
> DialStringRules: etc/dialrules
> ServerTracing: 1
> SessionTracing: 11
> RecvFileMode: 0644
> LogFileMode: 0644
> DeviceMode: 0600
> RingsBeforeAnswer: 1
> #SpeakerVolume: medium
> SpeakerVolume: low
> GettyArgs: "-h %l %s"
> LocalIdentifier: GENWAX
> TagLineFont: etc/lutRS18.pcf
> TagLineFormat: "From %%l|%c|Page %%p of %%t"
> NoCarrierRetrys: 3
> MaxRecvPages: 25
> ModemType: Class2 # use class 2 interface
> ModemRate: 19200 # 38.4 works fine
> ModemFlowControl: rtscts # default
> ModemNoFlowCmd: AT&H0 # disable flow control
> ModemHardFlowCmd: AT&H3 # hardware flow control
> ModemSoftFlowCmd: AT&H4 # software flow control
> ModemSetupDTRCmd: AT&D2 # DTR off causes modem to hang
> up
> ModemSetupDCDCmd: AT&C1 # DCD tracks carrier
> ModemSetupAACmd: AT+FAA=1 # enable in current class
> ModemSendFillOrder: LSB2MSB # as expected
> ModemRecvFillOrder: MSB2LSB # opposite of what makes sense
> Class2RecvDataTrigger: "\022" # a la 2388-B
> ModemResetCmds: AT&B1&N0&S0*F0S18=3S38.3=1S39=0
Useless stuff. Use
ModemResetCmds: ATZS38.3=1
instead.
> ModemDialCmd: ATDT%s # no '@' 'cuz then busy not
> recognized
> NoCarrierRetrys: 3 # retry 3 times on no carrier
> ModemSetVolumeCmd: "ATM0 ATM1L1 ATM1L3 ATM1L5 ATM1L7"
> PagerSetupCmds: AT&K0&N15 # use V.22 at 1200 bps (PageNet)
>
> #Class2DCCQueryCmd: "!(0,1),(0-5),(0-4),(0-2),(0,1),(0),(0),(0-7)"
>
> example error message:
> Fax3Decode2D: recvq/fax15356.tif: Bad code word at scanline 133 (x
> 1728).
> Fax3Decode2D: recvq/fax15356.tif: Bad code word at scanline 135 (x
> 1728).
> Fax3Decode2D: recvq/fax15356.tif: Bad code word at scanline 222 (x
> 1728).
> Fax3Decode2D: recvq/fax15356.tif: Bad code word at scanline 223 (x
> 1728).
> Fax3Decode2D: recvq/fax15356.tif: Uncompressed data (not supported) at
> scanline 224 (x 349).
> Fax3Decode2D: recvq/fax15356.tif: Bad code word at scanline 226 (x
> 1438).
> --snip 30 lines
> Fax3Decode2D: recvq/fax15356.tif: Uncompressed data (not supported) at
> scanline 776 (x 650).
> Fax3Decode2D: recvq/fax15356.tif: Bad code word at scanline 777 (x
> 1728).
Fax transmission is not reliable, and errors sometimes happen. The quality
checking is not enabled in your config, so Hylafax just stores received
data "as is" with errors. I recommend you the following (will likely be
included into the new Hylafax beta):
[---cut---]
#
# ECM is not implemented in U1496 despite AT+FCC=? says
#
Class2DCCQueryCmd: "!(0,1),(0-5),(0-4),(0-2),(0,1),(0),(0),(0-7)"
#
# Quality Checking is not implemented in U1496 despite AT+FCQ=? says
#
Class2CQQueryCmd: "!(0),(0)"
#
# Disable unnecessary, not implemented and possibly dangerous commands
#
Class2BORCmd: "AT"
Class2PIECmd: "AT"
Class2PHCTOCmd: "AT"
Class2TBCCmd: "AT"
[---cut---]
Also note what with current Hylafax you will suffer from "endless RTN" bug,
but it's quite another story :-)
Hope to hear from you soon,
Dmitry
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null
