Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3346

Kyocera MFP Waste Toner always reads 1%

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Poller
    • CentOS Linux release 7.8.2003 (Core)
      Observium Professional 20.5.10439 (rolling)

    Description

      The printer supply monitor of all Kyocera models company-wide report the "Waste Toner Box" at 1%, which trips an alert that the supply is nearing empty – even after being replaced with a new/empty waste box – making it impossible to track.

      I don't know if this is similar to the Ricoh issue OBS-2047 or not, but that might be a place to look for clues?

      Attachments

        1. kyocera_discovery.txt
          66 kB
        2. kyocera_graph.png
          kyocera_graph.png
          32 kB
        3. kyocera_obs.png
          kyocera_obs.png
          6 kB
        4. kyocera_poller.txt
          93 kB
        5. kyocera_toner.png
          kyocera_toner.png
          6 kB

        Issue Links

          mentions

          Bug - A problem which impairs or prevents the functions of the product. OBS-2047 Ricoh MP C4000 showing unknown values

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed
          relates to

          Vendor Bug - This is vendor specific issue, not possible to be fixed inside our project. OBS-4122 Kyocera MFP Wrong Page Count?

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            [OBS-3346] Kyocera MFP Waste Toner always reads 1%
            bot Observium Bot made changes -
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            landy Mike Stupalov made changes -
            Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            landy Mike Stupalov added a comment -

            Waste toner shows 80% in this case.

            landy Mike Stupalov added a comment - Waste toner shows 80% in this case.
            landy Mike Stupalov made changes -
            Status Original: In Review [ 10101 ] New: In Progress [ 3 ]
            landy Mike Stupalov made changes -
            Link New: This issue relates to OBS-4122 [ OBS-4122 ]
            landy Mike Stupalov made changes -
            Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
            NegwerIT Scott Driemeier-Showers added a comment -

            I (obviously) can't speak for everyone; but it seems to me that this being a non-graphed "OK/NOT OK" measure would be acceptable and give us the ability to alert based on "NOT OK".  And, yes, I know I oversimplified things in that description.

            Thanks!

            NegwerIT Scott Driemeier-Showers added a comment - I (obviously) can't speak for everyone; but it seems to me that this being a non-graphed "OK/NOT OK" measure would be acceptable and give us the ability to alert based on "NOT OK".  And, yes, I know I oversimplified things in that description. Thanks!
            adama Adam Armstrong made changes -
            Comment [ {{ /**}}
            {{ * .1.3.6.1.2.1.43.11.1.1.9 prtMarkerSuppliesLevel}}
            {{ * The value (-1) means other and specifically indicates that the sub-unit places}}
            {{ * no restrictions on this parameter. The value (-2) means unknown.}}
            {{ * A value of (-3) means that the printer knows that there is some supply/remaining space,}}
            {{ * respectively.}}
            {{ */}}
            {{ switch ($level)}}
            {{ {}}
            {{ case '-1':}}
            {{ $level = 100; // Unlimit}}
            {{ break;}}
            {{ case '-2':}}
            {{ $level = 0; // Unknown}}
            {{ break;}}
            {{ case '-3':}}
            {{ $level = 1; // This is wrong SuppliesLevel (1%), but better than nothing}}
            {{ break;}}
            {{ }}} ]
            adama Adam Armstrong added a comment - - edited

            In the code we handle this like so : 

            I think changing -3 to 100 might suffice, though it's also giving some incorrect information

            switch ($level)

            { case '-1': $level = 100; // Unlimit break; case '-2': $level = 0; // Unknown break; case '-3': $level = 1; // This is wrong SuppliesLevel (1%), but better than nothing break; }
            adama Adam Armstrong added a comment - - edited In the code we handle this like so :  I think changing -3 to 100 might suffice, though it's also giving some incorrect information switch ($level) { case '-1': $level = 100; // Unlimit break; case '-2': $level = 0; // Unknown break; case '-3': $level = 1; // This is wrong SuppliesLevel (1%), but better than nothing break; }
            landy Mike Stupalov made changes -
            Status Original: In Progress [ 3 ] New: Pending Response [ 10000 ]

            People

              landy Mike Stupalov
              NegwerIT Scott Driemeier-Showers
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: