Hylafax Mailing List Archives

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

Re: [hylafax-users] class1 modem and modem capabilities



At 10:26 PM 7/13/01 +0200, Giulio Orsero wrote:
>hylafax-4.1 + some patches (bugzilla id: tsieop-52 eom-117 cid-139 eop-152
>bulk-153 faxqcl-160 log-51 dso-141 dest-172)
>
>Class1/rockwell modem, no particular settings in config.devid (standard
class1).
>
>ati0 -> 56000
>ati3 -> V2.083-K56_DLS
>at+fclass=? -> 0,1,1.0
>
>managed with faxgetty.
>
>2 issues:
>
>1) Why 'Supports "Class 2' ?? This is just a curiosity since the modem is
>actually used in class1 and works fine.
>
>FaxGetty[2072]: MODEM Supports "Data"
>FaxGetty[2072]: MODEM Supports "Class 1"
>FaxGetty[2072]: MODEM Supports "Class 2"

faxgetty must be misinterpreting the DCC response.  Prolly somewhere here:

(faxd/Class1.c++)
/*
 * Check if the modem is a Class 1 modem and,
 * if so, configure it for use.
 */
bool
Class1Modem::setupModem()
{
    if (!selectBaudRate(conf.maxRate, conf.flowControl, conf.flowControl))
        return (false);
    // Query service support information
    fxStr s;
    if (doQuery(conf.classQueryCmd, s, 500) && FaxModem::parseRange(s,
modemSer$
        traceBits(modemServices & SERVICE_ALL, serviceNames);
    if ((modemServices & SERVICE_CLASS1) == 0)
        return (false);
    atCmd(conf.class1Cmd);
....

As you're aware, it's not terribly bad, but it is erronious output.


>2) Why not 2-D MMR too? I think I'd save on connection time.
>...
>FaxGetty[2072]: MODEM Supports unlimited page length
>FaxGetty[2072]: MODEM Supports 1-D MR
>FaxGetty[2072]: MODEM Supports 2-D MR

Again, faxgetty is misinterpreting the DCC response somewhere near here:

(faxd/FaxModem.c++)
/*
 * Trace a modem's capabilities.
 */
void
FaxModem::traceModemParams()
{
    traceBits(modemParams.vr, Class2Params::verticalResNames);
    traceBits(modemParams.br, Class2Params::bitRateNames);
    traceBits(modemParams.wd, Class2Params::pageWidthNames);
    traceBits(modemParams.ln, Class2Params::pageLengthNames);
    traceBits(modemParams.df, Class2Params::dataFormatNames);
    if (supportsECM())
        traceBits(modemParams.ec, Class2Params::ecmNames);
    if (modemParams.bf & BIT(BF_ENABLE))
        modemSupports("binary file transfer");
    traceBits(modemParams.st, Class2Params::scanlineTimeNames);
....

However, I highly suspect that HylaFAX is still utilizing 2-D MMR
whenever/if possible.  This here is merely a listing, and not a setting.

Can you list your DCC response? (AT+FDCC=?)  Does this even work on a Class
1 modem, though?
Maybe it's AT+FTM=? on a Class 1 modem...

Lee.



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



Home
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