Re: [PMP] Printer MIB question

Ira McDonald <blueroofmusic@gmail.com> Mon, 14 September 2009 19:20 UTC

Return-Path: <pmp-bounces@pwg.org>
X-Original-To: ietfarch-printmib-archive@core3.amsl.com
Delivered-To: ietfarch-printmib-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9F053A67B3 for <ietfarch-printmib-archive@core3.amsl.com>; Mon, 14 Sep 2009 12:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jlW+qpFLffWe for <ietfarch-printmib-archive@core3.amsl.com>; Mon, 14 Sep 2009 12:20:57 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 80C0A3A681D for <printmib-archive@lists.ietf.org>; Mon, 14 Sep 2009 12:20:57 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 615D779F96; Mon, 14 Sep 2009 15:21:31 -0400 (EDT)
X-Original-To: pmp@pwg.org
Delivered-To: pmp@pwg.org
Received: from mail-bw0-f226.google.com (mail-bw0-f226.google.com [209.85.218.226]) by pwg.org (Postfix) with ESMTP id E12FC79F92 for <pmp@pwg.org>; Mon, 14 Sep 2009 15:21:18 -0400 (EDT)
Received: by bwz26 with SMTP id 26so2146678bwz.47 for <pmp@pwg.org>; Mon, 14 Sep 2009 12:21:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LdrDqJ+XujVkS2P9IUddj5jtDLhlN3QFhm+BYZ/zacU=; b=J+Nt1/C6z9CagcuTW2joI52g+O3wLGTMlEWE9fiStmDpMbR8lFRM0MyKZ22PAUAHHe uovPnW8kW46ihxDZ+YXE8JAHxnNAf7sf8807ugfMtA+AKEoI8KWsCy5K6k2hV/xZ4iip 3KKVcfaHYuM6oFyY+UcCVNiV5m0L8OSKLPGH4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JPg5cfs4V9t+/LqOQQ0aCxQcS86S+ZvEvLUaprcw8NSASQg2NnBtfEfVZ0HzWA9Lr8 MEtfOPB7oCfLW//Er+M573a24S7WE0c80MHfErh/w6BWuKdCMrKW0SXvSsjNQElUGbMX FCQoSPc9B8nwY3j6f2JKST9a5KXu/np+i7OQU=
MIME-Version: 1.0
Received: by 10.204.163.19 with SMTP id y19mr5360340bkx.30.1252956077233; Mon, 14 Sep 2009 12:21:17 -0700 (PDT)
In-Reply-To: <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local>
References: <002e01ca355e$db4c7760$91e56620$@net> <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local>
Date: Mon, 14 Sep 2009 15:21:17 -0400
Message-ID: <e395be80909141221x3ccaadcbu492cfd10a9226270@mail.gmail.com>
Subject: Re: [PMP] Printer MIB question
From: Ira McDonald <blueroofmusic@gmail.com>
To: Christian Christiansen <cc@euroform.dk>, Ira McDonald <blueroofmusic@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
X-pwg-MailScanner: Found to be clean, Found to be clean
Cc: pmp@pwg.org, farouk.boujnah@gmail.com
X-BeenThere: pmp@pwg.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Printer MIB <pmp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/listinfo/pmp>, <mailto:pmp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/archives/pmp>
List-Post: <mailto:pmp@pwg.org>
List-Help: <mailto:pmp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/pmp>, <mailto:pmp-request@pwg.org?subject=subscribe>
Sender: pmp-bounces@pwg.org
Errors-To: pmp-bounces@pwg.org
X-pwg-MailScanner-Information: Please contact the ISP for more information
X-pwg-MailScanner-ID: 615D779F96.321C8
X-pwg-MailScanner-From: pmp-bounces@pwg.org

Hi folks,

No - Bill Wagner had it right in his original reply.

Right after Bill's previous quotation, RFC2790 says:

  "Bits are numbered starting with the most significant
  bit of the first byte being bit 0, the least significant bit
  of the first byte being bit 7, the most significant bit of
  the second byte being bit 8..."

Read the above carefully!

Bit 0 (0x8000) and bit 14 (0x0004) are set.

Cheers,
- Ira (co-editor of Printer MIB v2, RFC 3805)

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434



On Mon, Sep 14, 2009 at 1:55 PM, Christian Christiansen <cc@euroform.dk> wrote:
> If the endian is correct then, the value 8004 has a binary representation as
> follows:
>
> 1000 0000 0000 0100
>
> That means to me that bit 15 is on and bit 2 is on. However bit 15 is NOT
> defined in RFC2790
>
> So the interpretation would be
>
> “LowToner”
>
>
>
> If the endian is wrong the the value is 0480 and it has a binary
> representation as follows:
>
> 0000 0100 1000 0000
>
> That means to me that bit 10 is on and bit 7 is on.
>
> In this case the interpretation would be
>
> “serviceRequested”
>
> “markerSupplyMissing”
>
>
>
> Christian Christiansen
>
>
>
>
>
> ________________________________
>
> From: pmp-bounces@pwg.org [mailto:pmp-bounces@pwg.org] On Behalf Of William
> Wagner
> Sent: 14. september 2009 19:15
> To: farouk.boujnah@gmail.com
> Cc: pmp@pwg.org
> Subject: [PMP] Printer MIB question
>
>
>
> With regard to the question that you sent to hastings@cp10.es.xerox.com,
> szilles@mv.us.adobe.com, don@lexmark.com, jgyllens@hpdmd48.boi.hp.com, it
> has been forwarded to the Printer Working Group “PMP” mail list, which deals
> with printer MIB issues. You may well have responses from other members, but
> if I understand your question, it is how to interpret the response to  OID
> [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the
> hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The
> object value is “bit coded” as follows, and your program is interpreting the
> response in hexadecimal.
>
>    lowPaper              0
>
>    noPaper               1
>
>                 lowToner              2
>
>                 noToner               3
>
>                 doorOpen              4
>
>                 jammed                5
>
>                 offline               6
>
>                 serviceRequested      7
>
>                 inputTrayMissing      8
>
>                 outputTrayMissing     9
>
>                 markerSupplyMissing  10
>
>                 outputNearFull       11
>
>                 outputFull           12
>
>                 inputTrayEmpty       13
>
>                 overduePreventMaint  14
>
>
>
> But remember that, in the MIB, bits are numbered starting with the most
> significant bit of the first byte being bit 0,
>
>
>
> To interpret 80 04, it may be easiest conceptually to covert the value to
> binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0
> and bit 13, low paper and input tray empty.
>
>
>
> Hope this helps. Note also that the current Printer MIB is RFC3805, although
> some printers still support only the earlier verson.
>
>
>
> Bill Wagner/ Chair, Printer Working Group WIMS/PMP
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> _______________________________________________
> pmp mailing list
> pmp@pwg.org
> https://www.pwg.org/mailman/listinfo/pmp
>
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
pmp mailing list
pmp@pwg.org
https://www.pwg.org/mailman/listinfo/pmp