Re: [hylafax-users] HylaFAX performance vs regular fax machine.

[Lee Howard <faxguy@deanox.com>]

At 06:52 PM 9/4/01 -0400, Joe Matuscak wrote:
>On Tue, 4 Sep 2001, Lee Howard wrote:

>> HylaFAX always sends in 1-D the first time it sends to any particular
>> destination.  Once we have communicated with the remote, then successive
>> calls to that destination use 2-D, if available.
>
>The logs show that its using 1-D every time. Is there a file that tracks
>numbers called?

/var/spool/hylafax/info/* are the files that track what the capabilities
were for a particular number.

Hopefully you find an "supports2DEncoding:yes" entry in the file pertaining
to your intended destination.

>> Another question is whether or not your modem can do 2-D...
>
>Is there a way to test that?  I looked at the Multitech user doc and didnt
>see anything that mentioned it either way.

Unfortunately, they don't document the important things most of the time,
and you have to actually query the modem to find out.  For me, the easiest
thing to do is to set the ServerTracing to 0xFFF and then restart faxgetty,
and then peer at the system log to see the capabilities of the modem.  It
should read something like:

Sep  4 17:45:33 server FaxGetty[31708]: <-- [12:AT+FCLASS=?\r]
Sep  4 17:45:33 server FaxGetty[31708]: --> [9:0,1,2,1.0]
Sep  4 17:45:33 server FaxGetty[31708]: --> [2:OK]
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports "Data"
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports "Class 1"
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports "Class 2"
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports "Class 1.0"
Sep  4 17:45:33 server FaxGetty[31708]: <-- [12:AT+FCLASS=1\r]
Sep  4 17:45:33 server FaxGetty[31708]: --> [2:OK]
Sep  4 17:45:33 server FaxGetty[31708]: MODEM: Mfr Rockwell
Sep  4 17:45:33 server FaxGetty[31708]: <-- [5:ATI3\r]
Sep  4 17:45:33 server FaxGetty[31708]: --> [17:V2.300-V90_2M_DLP]
Sep  4 17:45:33 server FaxGetty[31708]: --> [2:OK]
Sep  4 17:45:33 server FaxGetty[31708]: MODEM: Model RC288DPi
Sep  4 17:45:33 server FaxGetty[31708]: MODEM: Revision V2.300-V90_2M_DLP
Sep  4 17:45:33 server FaxGetty[31708]: <-- [9:AT+FTM=?\r]
Sep  4 17:45:33 server FaxGetty[31708]: -->
[41:3,24,48,72,73,74,96,97,98,121,122,145,146]
Sep  4 17:45:33 server FaxGetty[31708]: --> [2:OK]
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 3.85 line/mm
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 7.7 line/mm
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 2400 bit/s
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 4800 bit/s
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 7200 bit/s
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 9600 bit/s
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 12000 bit/s
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 14400 bit/s
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports page width 1728
pixels in 215 mm
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports page width 2048
pixels in 255 mm
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports page width 2432
pixels in 303 mm
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports A4 page length (297 mm)
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports B4 page length (364 mm)
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports unlimited page length
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 1-D MR
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 2-D MR
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 0 ms/scanline
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 5 ms/scanline
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 10 ms, 5 ms/scanline
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 10 ms/scanline
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 20 ms, 10 ms/scanline
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 20 ms/scanline
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 40 ms, 20 ms/scanline
Sep  4 17:45:33 server FaxGetty[31708]: MODEM Supports 40 ms/scanline

Notice, however, that modem capabilities may be different when running
under Class 1 than when running under Class 2.  Note that we have to do
"AT+FCLASS=1" before querying the modem capabilities.

>Sep 04 16:44:31.34: [  880]: <-- [12:AT+FCLASS=2\r]
>Sep 04 16:44:31.35: [  880]: --> [2:OK]
....
>Sep 04 16:44:31.38: [  880]: <-- [24:AT+FDCC=1,5,2,2,0,0,0,0\r]
>Sep 04 16:44:31.40: [  880]: --> [2:OK]
....
>Sep 04 16:44:31.41: [  880]: <-- [12:AT+FCLASS=2\r]
>Sep 04 16:44:31.53: [  880]: --> [2:OK]
....
>Sep 04 16:44:31.89: [  880]: <-- [24:AT+FDCC=1,5,2,2,0,0,0,0\r]
>Sep 04 16:44:32.01: [  880]: --> [2:OK]

I'm in a bit unfamiliar territory when working with Class 2, but I'm
confused as to why we give the +FCLASS=2 and the +FDCC= commands twice...
anyway, this here is significant and the source of your troubles.

The capabilities string is in the format of:
	VR,BR,WD,LN,DF,EC,BF,ST
You can look this up in a Class 2 commands manual somewhere if you want to
know the specifics of all the commands, but the problem you're experiencing
lies in the "DF" entry.  DF values correspond to:
	0 = 1-D modified Huffman
	1 = 2-D modified Read
	2 = 2-D uncompressed mode
	3 = 2-D modified Read
And corresponding this to your log, you can see that either you are
deliberately limiting the modem to 1-D, or the modem plainly doesn't
support it.  You'll know which of these applies if you look at that syslog
output, or if you go to a terminal session (minicom) and issue "AT+FDCC=?"
If your modem actually supports 2-D, then the problem would lie with your
config file having a Class2DCCCmd or Class2DCCQueryCmd entry that is
forcing the issue.  You may also have a Use2D=no entry in your etc/config
file.

>Sep 04 16:44:47.05: [  880]: REMOTE best format 2-D MR
....
>Sep 04 16:44:47.05: [  880]: USE 1-D MR

This basically is saying that the remote supports 2-D, but we choose 1-D
because we don't support it.

I have seen cases where 2-D wasn't supported in Class 2, but it was in
Class 1... strangely enough, so if it is the modem's restriction, you may
want to try Class 1.

Lee.



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null