Jam Code 72-81 is a staple unit misfeed on Konica Minolta bizhub machines with a connected staple finisher. It belongs to the broader 72-xx finisher jam code range, but where general 72-0x codes address the finisher’s overall internal transport path (the relay rollers carrying a sheet from the machine-to-finisher interface toward its destination), 72-81 is scoped specifically to the staple compiler section — the tray-and-alignment assembly inside the finisher where individual sheets are collected, jogged square, and held until the complete set is stapled and ejected to the stack tray. This is a mechanically distinct zone from the finisher’s general transport path, with its own sensors, its own alignment mechanism, and its own eject drive, all specific to the stapling function and not present on finisher configurations without staple capability.
The official Konica Minolta description states precisely:
A sheet being added to the staple compiler stack, or the completed stapled set being ejected from the compiler, did not reach the expected detection point within the specified timing window. The staple unit’s compiling, aligning, or ejecting sequence did not complete correctly.
Translated into field language: by the time a sheet reaches the staple compiler, it has already been successfully transported through the entire base machine paper path and across the machine-to-finisher interface, and it has already been successfully carried through the finisher’s own general transport section to the point where the staple function takes over — everything covered under the general 72-0x transport codes is confirmed functional. From here, the staple compiler section performs a job that no other part of the print pipeline performs: it must receive each sheet of a multi-page set one at a time, allow it to settle into a stacking tray, square it against alignment plates (jogging) so that the finished set has clean, even edges, hold the accumulating stack until the last sheet of the set has arrived, drive the stapling mechanism through the assembled stack at the correct position, and then eject the completed, stapled set out to the finisher’s stack tray — all before the next set’s first sheet begins arriving. 72-81 fires when any step in this specific sequence — a sheet failing to reach its expected position in the compiler, or the completed set failing to eject within its expected window — does not complete correctly.
This makes 72-81 diagnostically distinct from the general finisher transport codes in an important way: the compiler section’s function is not simple point-to-point conveyance, it is accumulation and alignment — mechanically closer to a small, purpose-built stacking and finishing mechanism than to a transport roller pair. Its failure modes are correspondingly different: jogger plate mistiming or mechanical binding, paddle/assist roller wear specific to settling sheets into the stack rather than driving them point-to-point, staple carriage interference with the stack or eject path, and eject-mechanism faults that have no equivalent anywhere in the general transport path documented elsewhere in this series.
| Field | Details |
|---|---|
| Jam Code | 72-81 |
| General Category | Staple Finisher Misfeed — scoped to the staple compiler section specifically: sheet accumulation, alignment/jogging, and completed-set ejection. Distinct from the general finisher transport codes (72-0x range) that cover the path leading up to the compiler |
| What is confirmed functional when 72-81 fires | The entire base machine paper path, the machine-to-finisher interface handoff, and the finisher’s own general internal transport leading to the compiler entrance. All of this is confirmed by the sheet having reached the compiler section at all. None of it requires investigation for 72-81 |
| Critical distinction from 72-01 (general finisher transport) | 72-01 and the general 72-0x range address a sheet failing to transport through the finisher’s relay path toward its destination. 72-81 addresses a sheet that HAS reached the staple compiler but then failed within the compiler’s own accumulation, alignment, or eject sequence — a functionally different mechanism performing a different job (holding and squaring a growing stack, not simple conveyance) |
| Two distinct sub-conditions within 72-81 | (A) An individual sheet being added to the compiling stack failed to reach its correct settled/aligned position within the timing window — the compiler failed to receive that sheet correctly. (B) The completed, stapled set failed to eject from the compiler to the stack tray within the timing window after the staple operation completed — the compiler failed to release the finished set. These have different likely causes and are distinguished by where the paper/set is physically found when the fault is cleared |
| Detection Logic | The finisher’s own controller (independent from the base machine’s engine board) monitors the compiler entrance/stack sensor as each sheet is added, and monitors the compiler exit/stack-tray sensor as a completed set is ejected. If a sheet does not reach the expected stacked/aligned position within the timing window after being released from the finisher’s general transport into the compiler, or if a completed set does not clear the compiler exit sensor within the timing window after the eject mechanism is commanded, 72-81 is logged |
| Key Components | Compiler tray (the surface where sheets accumulate before stapling); compiler entrance/stack sensor (confirms each incoming sheet has settled into the compiling stack); jogger plates (front and rear alignment plates that square the stack after each sheet arrives); jogger drive motor(s); paddle wheel or stack-assist roller (helps each incoming sheet settle fully into the compiler against the trailing-edge stop); trailing-edge stopper; staple carriage/head assembly (drives the staple through the assembled stack at the programmed position); staple carriage drive motor; eject mechanism (paddle, belt, or roller assembly that drives the completed set out of the compiler toward the stack tray); compiler exit/stack-tray sensor (confirms the completed set has cleared the compiler); finisher controller board (independent of the base machine engine board — refer to finisher SM for exact designation) |
| Severity | High for any job using the staple function specifically; jobs sent to the finisher without stapling requested (simple stack or sort jobs bypassing the compiler) may be unaffected, which is a useful diagnostic test to confirm the fault is compiler-specific rather than a broader finisher transport issue; may be intermittent (correlating with specific set sizes/page counts or specific media) before becoming consistent |
| Related Jam Codes | 72-0x (general finisher transport section — for comparison, faults occurring before the sheet reaches the compiler), any distinct punch-unit-specific or booklet-path-specific finisher codes on finishers equipped with those additional functions (refer to finisher SM, as these use their own mechanisms distinct from the staple compiler), any staple-cartridge-empty or staple-jam-specific fault codes the finisher may report separately from a paper misfeed (refer to finisher SM to distinguish a staple mechanism fault from a paper transport fault within the same general compiler area) |
All Affected Finisher Models and Component References
Staple finisher options across the bizhub lineup vary in capacity (typical set sizes range from 30–50 sheets depending on finisher model), in whether they include additional functions such as punch or saddle-stitch booklet-making alongside stapling, and in the exact mechanical layout of the compiler, jogger, and eject assemblies. The component designations below use general functional naming consistent with the staple finisher options commonly paired with bizhub machines (FS-5xx and FN-1xx series designations, among others, depending on base machine platform and region) — always confirm the exact sensor designations, motor/clutch references, and Service Mode or finisher-diagnostic-mode check codes against the specific finisher unit’s own service manual, since these are documented separately from the base machine SM and vary between finisher models.
| Finisher Class | Typical Set Capacity | Compiler Entrance Sensor | Jogger Mechanism | Eject Mechanism | Compiler Exit Sensor | Finisher Controller |
|---|---|---|---|---|---|---|
| Standard staple finisher (e.g., FS-5xx class) | ~30–50 sheets, model-dependent | PS_CMP-IN or equivalent — refer to finisher SM | Front/rear jogger plates, motor-driven — refer to finisher SM for motor designation | Paddle or belt-driven eject assembly — refer to finisher SM | PS_CMP-OUT or equivalent — refer to finisher SM | Finisher-specific controller board — refer to finisher SM |
| High-capacity staple finisher (e.g., FS-5xx HC variants) | Higher rated capacity than standard class — refer to finisher SM | PS_CMP-IN or equivalent — refer to finisher SM | Front/rear jogger plates, motor-driven — refer to finisher SM | Paddle or belt-driven eject assembly, may include stack-tray elevator coordination — refer to finisher SM | PS_CMP-OUT or equivalent — refer to finisher SM | Finisher-specific controller board — refer to finisher SM |
| Multi-function finisher with punch and/or booklet (e.g., FN-1xx class) | Model-dependent — refer to finisher SM | PS_CMP-IN or equivalent — refer to finisher SM | Front/rear jogger plates, motor-driven; may share drive with punch registration on multi-function units — refer to finisher SM | Paddle or belt-driven eject assembly; booklet-equipped units have a separate saddle-stitch path not covered by this code — refer to finisher SM | PS_CMP-OUT or equivalent — refer to finisher SM | Finisher-specific controller board — refer to finisher SM |
Finisher model class names above are illustrative of the general categories of staple finisher commonly paired with bizhub machines. Confirm the exact finisher model attached to the specific machine you are servicing, and use that unit’s own service manual for every specific sensor designation, connector reference, motor/clutch part number, and diagnostic-mode check code before performing any hands-on test.
ℹ️ First diagnostic split — which sub-condition of 72-81 applies: Before any component inspection, determine which of the two sub-conditions occurred. If a single sheet is found within the compiler, not fully settled/aligned, with the rest of the set (if any sheets had already accumulated) sitting correctly stacked beneath or around it: this is sub-condition A — an individual sheet failed to reach its correct position when added to the stack. Investigate the compiler entrance path, paddle/assist roller, and jogger timing (Steps 3–4). If a complete, correctly-stapled set is found still sitting in the compiler, not ejected to the stack tray: this is sub-condition B — the eject mechanism failed to release the finished set. Investigate the eject mechanism and compiler exit sensor specifically (Step 5), and check whether the staple operation itself completed correctly, since a staple carriage that has not fully retracted can physically obstruct the eject path.
Understanding the Staple Compiler Sequence — Why 72-81 Occurs
The staple compiler performs a fundamentally different function from any transport zone covered elsewhere in this series. Rather than simply conveying a single sheet from one point to another, it must manage an accumulating, growing stack of sheets — potentially dozens for a large set — settling, aligning, and holding them in registration with each other until the complete set is ready to be stapled and released as a single unit.
The general sequence for each sheet added to a set is:
- The sheet arrives from the finisher’s general transport section and is released into the compiler tray
- A paddle wheel or stack-assist roller helps drive the sheet’s trailing edge fully back against the trailing-edge stopper, ensuring consistent registration in the direction of paper travel regardless of the sheet’s exact arrival speed or any minor variation from print job to print job
- The compiler entrance/stack sensor confirms the sheet has settled into the stacking position within the expected timing window
- The jogger plates — front and rear alignment plates — cycle inward against the sheet’s side edges and then retract, squaring that sheet (and, by extension, the growing stack beneath it) laterally. This jogging cycle typically repeats after every sheet, or after every few sheets depending on the finisher’s specific programming
- Once the final sheet of the set has arrived and been jogged, the staple carriage drives through the assembled stack at the programmed staple position(s) and completes the staple operation
- The eject mechanism then drives the completed, stapled set out of the compiler toward the finisher’s stack tray, and the compiler exit sensor confirms the set has cleared the compiler, allowing the next set’s first sheet to begin arriving
Six root cause categories produce 72-81, ordered by frequency in field-installed staple finishers:
- Category 1 — Paddle wheel or stack-assist roller wear (dominant cause of sub-condition A — individual sheet failing to settle correctly): The paddle wheel or assist roller responsible for driving each incoming sheet’s trailing edge back against the stopper has worn, lost grip, or become contaminated, and can no longer reliably settle every sheet into correct registration — particularly on longer sets where accumulated sheets create more resistance for a new sheet settling on top, or on curled/stiff media that resists settling cleanly. This produces the classic escalation pattern familiar from roller-wear faults elsewhere in this series: intermittent failure on longer sets or specific media first, progressing to more frequent failure as wear continues
- Category 2 — Jogger plate mistiming, binding, or mechanical wear: The jogger plates fail to complete their alignment cycle correctly — either from a mechanical binding issue preventing full plate travel, from a drive motor or belt fault affecting jogger motion, or from a timing fault where the jogger cycles at the wrong point in the sequence (for example, attempting to jog before an incoming sheet has fully settled, catching the sheet’s edge and displacing it rather than squaring it). This category can produce either sub-condition A (a specific sheet displaced or folded by a mistimed jogger cycle) and is confirmed by inspecting jogger plate travel and cycling behavior directly, generally via the finisher’s own diagnostic mode
- Category 3 — Eject mechanism fault (dominant cause of sub-condition B — completed set failing to eject): The paddle, belt, or roller assembly responsible for driving the completed set out of the compiler has failed, lost drive force, or is not receiving the eject command correctly from the finisher controller. This produces a complete, correctly-assembled and stapled set sitting in the compiler, never ejected — confirmed by finding an intact stapled set (not a single displaced sheet) when the jam is cleared
- Category 4 — Staple carriage obstruction of the eject path: The staple carriage/head assembly, after completing the staple operation, fails to fully retract to its home/clear position, physically obstructing the path the completed set must travel to be ejected. This produces sub-condition B with the additional diagnostic signature that the staple carriage itself is found out of its normal resting position when the compiler is inspected — distinguishing this from a pure eject-mechanism drive fault (Category 3), since here the eject mechanism itself may be fully functional but has nowhere to drive the set
- Category 5 — Foreign object, staple waste, or accumulated debris in the compiler: Loose staples from a previous misfire, fragments from a previous paper jam in the compiler area, or general paper dust/debris accumulation can obstruct either the sheet-settling process (sub-condition A) or the eject path (sub-condition B), depending on exactly where the obstruction sits. This category is confirmed by thorough visual inspection of the compiler tray surface and the eject path once access is gained
- Category 6 — Compiler entrance or exit sensor contamination or failure: The relevant sensor is contaminated or has failed in a state that does not correctly reflect the true condition of the compiler, producing a false 72-81 despite the sheet or set having actually been correctly positioned/ejected. Confirmed by direct inspection and toggle-testing of the sensor once the compiler is confirmed physically clear
Step 1 — Confirm the Fault Is Staple-Compiler-Specific
- Where the finisher and job settings allow, run a test job to the finisher without requesting stapling (a simple stack or sort job using the same general finisher transport path but bypassing the compiler function) to confirm the finisher’s general transport is functioning normally and the fault is isolated to the staple compiler specifically
- Note the page count of the set that was being processed when 72-81 occurred, and whether the fault correlates with longer sets specifically — a correlation with set length points toward Category 1 (paddle/assist roller wear, more likely to reveal itself as stack height increases) rather than a hard mechanical fault that would be expected to occur regardless of set size
Step 2 — Access the Compiler and Classify the Sub-Condition
- Per the finisher SM access procedure (typically a front cover or dedicated compiler access panel on the finisher unit), open access to the compiler tray
- Observe what is physically present before removing anything:
- A single sheet found displaced, folded, or not aligned with the rest of an accumulated stack: Sub-condition A. Proceed to Steps 3 and 4
- A complete, evenly stacked, and correctly stapled set found sitting in the compiler, not advanced toward the stack tray: Sub-condition B. Proceed to Step 5, and specifically check the staple carriage position as part of that inspection
- No paper found at all despite the fault being logged: Sensor fault (Category 6). Proceed to Step 6
- Remove any paper found per the finisher SM’s specific guidance for this compiler — some finishers require the jogger plates to be manually retracted or a specific release mechanism to be used before paper can be safely removed without disturbing the mechanism’s calibrated home positions
- Inspect the compiler tray surface and the eject path for loose staples, debris, or fragments before closing any access panel
Step 3 — Inspect the Paddle Wheel / Stack-Assist Roller
For sub-condition A, this is the primary inspection target.
- Per the finisher SM, locate and inspect the paddle wheel or stack-assist roller responsible for settling incoming sheets against the trailing-edge stopper
- Inspect for surface wear, glazing, or contamination using the same general criteria (matte vs. worn/glazed surface) established throughout this series for transport components, adapted to this component’s specific settling function rather than point-to-point conveyance
- Confirm correct rotation timing and force via the finisher’s diagnostic mode if available, per the SM
- Clean or replace per the finisher SM’s documented procedure and part reference
Step 4 — Inspect Jogger Plate Operation
- Per the finisher SM diagnostic mode, cycle the jogger plates through their full alignment travel and observe for smooth, complete, correctly-timed motion on both front and rear plates
- Inspect for mechanical binding, debris in the plate travel path, or a worn/damaged drive belt or motor coupling specific to the jogger mechanism
- If jogger timing relative to sheet arrival is suspected (jogging before a sheet has fully settled), refer to the finisher SM for any adjustable timing parameter and confirm it is at the correct specified value
Step 5 — Inspect the Eject Mechanism and Staple Carriage Position
For sub-condition B, this step covers both possible causes: a genuine eject-drive fault (Category 3) and a staple-carriage obstruction (Category 4).
- Visually confirm the staple carriage/head assembly has returned to its normal home/resting position after the staple operation, per the finisher SM’s illustration of correct resting position. A carriage not fully retracted confirms Category 4 — investigate the carriage’s own return mechanism per the finisher SM before addressing the eject mechanism itself, since the eject mechanism may be entirely healthy but obstructed
- With the carriage confirmed correctly retracted, inspect the eject mechanism (paddle, belt, or roller assembly) for wear, drive fault, or obstruction, using the finisher’s diagnostic mode to command an eject cycle directly and observe for correct, complete motion
- Clean, repair, or replace per the finisher SM’s documented procedure based on findings
Step 6 — Verify Compiler Entrance/Exit Sensors
- Per the finisher SM, identify the correct sensor for the sub-condition observed (entrance sensor for sub-condition A investigation, exit sensor for sub-condition B) and its diagnostic-mode check procedure
- With the compiler confirmed physically clear, verify the sensor reads the correct clear state and toggles correctly on manual paper insertion/removal
- Clean, reseat, or replace only per the finisher SM’s guidance and documented procedure
Quick Reference — Troubleshooting by Symptom
| Symptom | Sub-Condition | Most Likely Cause | First Action |
|---|---|---|---|
| 72-81 with a single sheet found displaced/folded within an otherwise correctly stacked set; correlates with longer sets specifically | A | Paddle wheel / stack-assist roller wear — insufficient settling force as stack height increases | Inspect paddle wheel/assist roller for wear or contamination per finisher SM; clean or replace |
| 72-81 with a complete, correctly-stapled set found sitting in the compiler, not ejected; staple carriage visibly not in home position | B | Staple carriage failed to fully retract, physically obstructing the eject path | Investigate carriage return mechanism per finisher SM before addressing eject drive; confirm carriage reaches home position on a diagnostic-mode cycle |
| 72-81 with a complete, correctly-stapled set found sitting in the compiler, not ejected; staple carriage confirmed in home position | B | Eject mechanism drive fault — paddle/belt/roller not receiving or transmitting the eject command correctly | Command an eject cycle directly via finisher diagnostic mode; inspect eject mechanism for wear or drive fault per finisher SM |
| 72-81 with a sheet found folded specifically at the jogger plate position, edges not evenly squared | A | Jogger plate mistiming (jogging before sheet fully settled) or mechanical binding | Cycle jogger plates via diagnostic mode and observe timing and completeness of travel; check for binding or debris in plate travel path |
| 72-81 with loose staples or debris visible in the compiler tray | A or B | Foreign object/staple waste obstructing sheet settling or the eject path | Thorough visual inspection and cleaning of the compiler tray and eject path per finisher SM |
| 72-81 with no paper found; relevant sensor reads “blocked” in finisher diagnostic mode with compiler confirmed clear | Sensor fault | Compiler entrance or exit sensor contamination or electrical failure | Clean sensor per finisher SM; reseat harness connector if accessible; replace only if unresolved after these steps |
| 72-81 does not occur on non-staple (simple stack/sort) jobs to the same finisher | N/A — confirms scope | Confirms the fault is isolated to the staple compiler function specifically | Proceed with compiler-specific diagnosis; general finisher transport hardware is not implicated |
Understanding the Relationship Between 72-81 and the General 72-xx Finisher Code Range
Jam Code 72-81 sits within the broader finisher jam code range but addresses a functionally distinct mechanism from the general transport codes (72-0x) covering the finisher’s path leading up to the compiler:
- 72-0x (general finisher transport) — addresses whether a sheet successfully transports through the finisher’s relay path from the machine-to-finisher interface toward its destination, using simple point-to-point conveyance logic mechanically similar to transport zones covered elsewhere in this series
- 72-81 (staple compiler) — addresses whether the staple compiler’s accumulation, alignment, and eject sequence completes correctly — a fundamentally different mechanical function (stacking, squaring, and releasing a growing multi-sheet set) with its own dedicated components not present in the general transport path. This article
A sheet or set producing 72-81 has, by definition, already succeeded at everything covered under the general 72-0x range — it reached the compiler. This means a technician should never need to investigate general finisher transport hardware for a 72-81 fault, and should instead move directly to the compiler-specific components: paddle wheel, joggers, staple carriage, and eject mechanism.
Preventing Jam Code 72-81 From Recurring
- Include compiler-specific component inspection — paddle wheel/assist roller condition, jogger plate travel, and eject mechanism function — in finisher PM visits, per the finisher SM’s recommended PM scope, separate from and in addition to general finisher transport roller inspection
- Clear staple waste and general debris from the compiler tray and eject path on the schedule specified in the finisher SM, since this is a debris source specific to the stapling function
- Verify staple carriage return-to-home behavior periodically, particularly on finishers with high staple-cycle counts, since carriage return mechanism wear can develop gradually before producing a full obstruction event
- Track whether 72-81 correlates with specific set sizes over time, since a pattern of failure specifically on longer sets is an early indicator of paddle wheel/assist roller wear that can be addressed proactively before it produces failures on standard-length sets as well
- Document finisher compiler component service history separately in the machine’s or finisher’s service log, per the finisher SM’s tracking recommendations
Professional Technician Summary
Jam Code 72-81 is a staple compiler misfeed — a fault occurring within the finisher’s stapling-specific accumulation, alignment, and eject sequence, after the sheet or set has already successfully completed the entire base machine paper path and the finisher’s own general internal transport. This is a mechanically distinct zone from general finisher transport, performing a fundamentally different function — stacking and squaring a growing multi-sheet set rather than simple point-to-point conveyance — with its own dedicated components.
The first diagnostic action is determining which of two sub-conditions applies: a single sheet failing to settle correctly into an accumulating stack (sub-condition A, pointing toward paddle wheel/assist roller wear or jogger timing issues), or a completed, correctly-stapled set failing to eject from the compiler (sub-condition B, pointing toward either a staple carriage retraction fault physically obstructing the eject path, or a genuine eject mechanism drive fault). These sub-conditions are distinguished immediately by what is physically found in the compiler when the fault is cleared, and they point to different components for investigation.
Always confirm the fault does not occur on non-staple finisher jobs first, to isolate the compiler as the correct diagnostic scope before any component-level work begins. And because staple finisher designs and their exact component naming vary across the bizhub lineup, confirm every specific sensor designation, motor reference, and diagnostic-mode check code against the specific finisher unit’s own service manual before proceeding with hands-on diagnosis.