Difference between revisions of "Printer Evaluation 1"

From FreekiWiki
Jump to navigation Jump to search
 
(26 intermediate revisions by one other user not shown)
Line 1: Line 1:
This is my scratch page for revising printer testing, it will be messy right now and shouldn't have anything that links to it yet - [[User:Darin|Darin]]Darin
+
This is my scratch page for revising printer testing, it will be messy right now and shouldn't have anything that links to it yet - [[User:Darin|Darin]]
  
 
=Printers=
 
=Printers=
By printers we mean things that only print.
+
[[Printer Triage]]
  
==Jets==
+
==Inkjet Printers==
 +
==Laserjet Printers==
 +
|match a power supply
 +
|check for lose/missing vital parts
 +
|check for lose/missing cosmetics.
 +
|power up with paper in it
 +
|check for ready status
 +
|check for grinding noises
  
We put all HP 900s and above on the shelves for testing.
+
?Apple Printers?
 +
?Cannon Wide Format?
  
Everything else gets a black "X" and goes on the Recyclables shelf.
+
*Okidata: all Okidata printers should be stored in their own area, no need to eval/build/triage.
  
==Lasers==
+
<graphviz>
 +
digraph{
  
All HP Laserjet 4 and above we put on the incoming shelves for testing.
+
start [label="START HERE"]
 +
power [label="Can you find a power cord/supply for this printer?", shape=box]
 +
paper [label="Place paper in the tray or\n manual feed if it doesn't have a tray.\nTurn the unit on."]
 +
grind [label="Did it make grinding noises?", shape=box]
 +
ready [label="Does it come up to\nReady to Print?", shape=box]
 +
codes [label="If there are Error codes\nReseat Toner, Paper Tray and\ncheck paper path for jams.\nPower on again."]
 +
code50 [label="If there is an error code 50\nreseat the fuser and leave it on for 20min."]
 +
strip [label="Mark with an X and strip it for parts."]
 +
build [label="Mark in a hidden place (underside) and set aside for Printer Build."]
  
For all the others we pull the paper and the toner, put them in their bins and put the machine on the Recyclables shelves. If the toner is something we use in house (all the in house bins are labeled under the right set of shelves) we'll keep it. Otherwise they go in the toner bin under the left set of shelves.
+
 
 +
start -> power
 +
power -> strip [label=no]
 +
power -> paper [label=yes]
 +
paper -> grind
 +
grind -> strip [label=yes]
 +
grind -> ready [label=no]
 +
ready -> build [label=yes]
 +
ready -> codes [label=no]
 +
codes -> code50
 +
code50 -> paper
 +
}
 +
</graphviz>
 +
 
 +
-If it still does not come up ready to print
 +
--If it has a paper jam or fuser (50) error comment this and set aside for [[Printer Build 1]]
 +
--If it has no messages on the LCD (just stars or dashes) and the mainboard was replaced (if possible) mark with an X then run through [[Printer Parting 1]].
 +
 
 +
Is it missing essential parts (paper drawer, fuser, toner, etc)?
 +
 
 +
Is it missing cosmetic parts: covers, lids?
 +
 
 +
Does it have lose parts, missing screws?
 +
 
 +
Laser Printer Reject Types:
 +
 
 +
doesn't power on at all
 +
bad mainboard
 +
paper jam
 +
fuser error
 +
missing essential parts
 +
missing cosmetics
 +
won't pass paper path test
 +
 
 +
==Dot Matrix Printers==
 +
==Other types of printers==
  
 
=Fax Machines=
 
=Fax Machines=
 +
 +
=Scanners=
 +
 +
=PSC (All-in-one printer, scanner, copier)=
 +
 +
=Copiers=
 +
 +
=Darin's List=
 +
Printerland:
 +
 +
find people to help with organization (Ian)
 +
get an eval system started to move testing along
 +
giant eval/build chart then split it into eval and build.
 +
organize parts storage
 +
implement parts storage into triage
 +
set QC standards for build
 +
paper towel dispenser and recycling bin (like in the restroom) for rubber restore/alcohol.
 +
 +
oversight to impliment a more formal printerland program.
 +
advice from people who set up build program?
 +
any committee(s) need to approve anything?
 +
 +
set up a class? will it need any pre-reqs? (classes like command line or adoption?)
 +
build program volunteers?
 +
printer adoption program?
 +
 +
temporary space to store printers while implementing new system.
 +
permanent changes to storage in printerland, possibly including new area for incoming.
 +
 +
 +
[[Category: Printers]]

Latest revision as of 16:35, 6 July 2010

This is my scratch page for revising printer testing, it will be messy right now and shouldn't have anything that links to it yet - Darin

Printers

Printer Triage

Inkjet Printers

Laserjet Printers

|match a power supply |check for lose/missing vital parts |check for lose/missing cosmetics. |power up with paper in it |check for ready status |check for grinding noises

?Apple Printers? ?Cannon Wide Format?

  • Okidata: all Okidata printers should be stored in their own area, no need to eval/build/triage.

This is a graph with borders and nodes. Maybe there is an Imagemap used so the nodes may be linking to some Pages.

-If it still does not come up ready to print --If it has a paper jam or fuser (50) error comment this and set aside for Printer Build 1 --If it has no messages on the LCD (just stars or dashes) and the mainboard was replaced (if possible) mark with an X then run through Printer Parting 1.

Is it missing essential parts (paper drawer, fuser, toner, etc)?

Is it missing cosmetic parts: covers, lids?

Does it have lose parts, missing screws?

Laser Printer Reject Types:

doesn't power on at all bad mainboard paper jam fuser error missing essential parts missing cosmetics won't pass paper path test

Dot Matrix Printers

Other types of printers

Fax Machines

Scanners

PSC (All-in-one printer, scanner, copier)

Copiers

Darin's List

Printerland:

find people to help with organization (Ian) get an eval system started to move testing along giant eval/build chart then split it into eval and build. organize parts storage implement parts storage into triage set QC standards for build paper towel dispenser and recycling bin (like in the restroom) for rubber restore/alcohol.

oversight to impliment a more formal printerland program. advice from people who set up build program? any committee(s) need to approve anything?

set up a class? will it need any pre-reqs? (classes like command line or adoption?) build program volunteers? printer adoption program?

temporary space to store printers while implementing new system. permanent changes to storage in printerland, possibly including new area for incoming.