Padreug
9eeb7f29b4
Served from the extension's static dir and linked from the dashboard header. The glossary is keyed by raw code (78 42, 82 00, …) with the class, what it means, and what to do inside the unit; the guide covers bays/ops ownership, the authorize/capture lifecycle, the cash-out hold, owed-cash resolution, and alerts.
98 lines
7.4 KiB
HTML
98 lines
7.4 KiB
HTML
<!doctype html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||
<title>bitSpire — Dispenser error glossary</title>
|
||
<style>
|
||
:root { color-scheme: light dark; }
|
||
body { font: 15px/1.5 system-ui, sans-serif; max-width: 52rem; margin: 2rem auto; padding: 0 1rem; }
|
||
h1 { font-size: 1.6rem; } h2 { font-size: 1.2rem; margin-top: 2.2rem; border-bottom: 1px solid #8884; padding-bottom: .3rem; }
|
||
code { font-family: ui-monospace, monospace; background: #8882; padding: .05em .35em; border-radius: 3px; }
|
||
.cls { font-weight: 600; } .terminal { color: #c62828; } .recoverable { color: #ef6c00; } .inventory { color: #2e7d32; }
|
||
dl { margin: .5rem 0 0; } dt { font-weight: 600; margin-top: .6rem; } dd { margin: .2rem 0 0 1.2rem; }
|
||
.entry { margin-top: 1.4rem; padding: .6rem .9rem; border-left: 3px solid #8884; }
|
||
.entry:target { border-left-color: #1976d2; background: #1976d20d; }
|
||
small { color: #777; }
|
||
</style>
|
||
</head>
|
||
<body>
|
||
<h1>Dispenser error glossary</h1>
|
||
<p>Every dispense failure a machine reports carries an <strong>error code</strong> (the family — which driver), a <strong>raw code</strong> (what the hardware said), and a <strong>class</strong> that decides what the machine did next:</p>
|
||
<dl>
|
||
<dt><span class="cls terminal">terminal</span></dt>
|
||
<dd>The transport path is compromised. The machine has <strong>taken cash-out out of service</strong> and will stay that way until you open it. Clear the path, then record a <em>Recount</em> (which also fixes the bay count) or press <em>Resume cash-out</em>. Re-initialising the dispenser does not move a stuck note, so a restart will not clear this.</dd>
|
||
<dt><span class="cls recoverable">recoverable</span></dt>
|
||
<dd>This bay or this note. The customer still sees a fault screen if they were short-changed, but the machine stays in service. Check the bay named in the report and the reject tray.</dd>
|
||
<dt><span class="cls inventory">inventory</span></dt>
|
||
<dd>Nothing was asked of the hardware — the request could not be met from the bays. Not a hardware fault. If this happens after payment, the customer is still owed (see the worklist).</dd>
|
||
</dl>
|
||
<p><strong>Whatever the class, a report that is not <code>dispense_confirmed</code> after a payment means a customer is owed money.</strong> The worklist shows it as <em>Cash owed</em> (nothing dispensed) or <em>Partial dispense</em> (some notes out). Nothing has been distributed; the funds are in the machine wallet. Resolve by dispensing the shortfall at the machine (the machine reports the remediation and the settlement completes) or by paying the customer by hand and recording it with <em>Settle off-machine</em>.</p>
|
||
|
||
<h2>Fujitsu F53 / F56 (error code <code>F56DispenseError</code>)</h2>
|
||
<p><small>Codes are the two bytes the BDU returns after a failed bill count. Source: Fujitsu Frontech F56-BDU Error Code List (K3KD03234–K3KD03236-0001, ed. E02) and field observations. An unknown code is treated as terminal until it has been decoded.</small></p>
|
||
|
||
<div class="entry" id="78-42">
|
||
<h3><code>78 42</code> — note stopped at the cassette exit <span class="cls terminal">terminal</span></h3>
|
||
<p>A note left the bay and stopped in the transport just past the cassette. The counters report <em>0 dispensed, 0 rejected</em> because the note completed neither path — so the bay count is also one high until you recount.</p>
|
||
<p><strong>What to do:</strong> open the unit, remove the note from the transport path, check the cassette is seated, then <em>Recount</em> the bay (this releases the cash-out hold and corrects the count). First seen: sintra, 2026-10-09 — a 20 EUR note, customer paid 40 EUR and received nothing.</p>
|
||
</div>
|
||
|
||
<div class="entry" id="82-00">
|
||
<h3><code>82 00</code> — bill length check failed (long) <span class="cls recoverable">recoverable</span></h3>
|
||
<p>The BDU measured a note longer than the accept window configured for that denomination and rejected it. Repeated on every pick from one bay, it is almost always the <em>configured window</em>, not the notes: a GTQ Tejo rejected 5 of 5 on every pick in 2026-09 because the window was ±5 mm where the identical-size USD note has ±10.</p>
|
||
<p><strong>What to do:</strong> empty the reject tray and look at the notes. Single notes → window too narrow; report it. Pairs → the separator is worn (offset double-pick) and the narrow window is doing its job.</p>
|
||
</div>
|
||
|
||
<div class="entry" id="83-00">
|
||
<h3><code>83 00</code> — bill length check failed (short) <span class="cls recoverable">recoverable</span></h3>
|
||
<p>As above, measured short. Torn or folded notes, or the wrong denomination loaded in the bay.</p>
|
||
</div>
|
||
|
||
<div class="entry" id="84-00">
|
||
<h3><code>84 00</code> — bill thickness check failed <span class="cls recoverable">recoverable</span></h3>
|
||
<p>Two notes stuck together, or a taped/damaged note. Check the reject tray.</p>
|
||
</div>
|
||
|
||
<div class="entry" id="85">
|
||
<h3><code>85 0n</code> — pick from another safe <span class="cls recoverable">recoverable</span></h3>
|
||
<p>A note arrived from a bay other than the one commanded (<code>n</code> = which). Usually a cassette not fully latched.</p>
|
||
</div>
|
||
|
||
<div class="entry" id="86-00">
|
||
<h3><code>86 00</code> — bill spacing error <span class="cls recoverable">recoverable</span></h3>
|
||
<p>Notes too close together on the transport. Often follows a worn feed roller.</p>
|
||
</div>
|
||
|
||
<div class="entry" id="b5">
|
||
<h3><code>B5 ..</code> — reject box overflow <span class="cls terminal">terminal</span></h3>
|
||
<p>The reject tray is full; nothing more can be rejected, so nothing more can be dispensed safely.</p>
|
||
<p><strong>What to do:</strong> empty the reject tray, count what is in it (those notes left a bay), <em>Recount</em>.</p>
|
||
</div>
|
||
|
||
<div class="entry" id="f56dispenseerror">
|
||
<h3>Unrecognised code <span class="cls terminal">terminal</span></h3>
|
||
<p>A code not yet in this table. The machine treats it as a jam — cash-out held — until someone decodes it. Please report the raw code with what you found inside the unit so it can be added.</p>
|
||
</div>
|
||
|
||
<div class="entry" id="dispensetimeout">
|
||
<h3><code>DispenseTimeout</code> — dispenser did not answer <span class="cls terminal">terminal</span></h3>
|
||
<p>No frame came back within the dispense timeout (serial timeout, port closed, framing error). The transport state is unknown; the bay counts are flagged unverified.</p>
|
||
</div>
|
||
|
||
<h2>Puloon LCDM (error code <code>PuloonDispenseError</code>)</h2>
|
||
<p>No decode table yet; every Puloon fault is treated as <span class="cls terminal">terminal</span>. The raw code is whatever the driver returned — report it.</p>
|
||
|
||
<h2>Software-side codes</h2>
|
||
<div class="entry" id="insufficientinventory">
|
||
<h3><code>InsufficientInventory</code> / <code>NoCassetteForDenomination</code> <span class="cls inventory">inventory</span></h3>
|
||
<p>The request could not be met from the bays as the machine believes them to be. After a payment this still leaves the customer owed; before one, the sale is simply refused. If the bays physically hold more than the machine thinks, <em>Recount</em>.</p>
|
||
</div>
|
||
<div class="entry" id="dispenseshort">
|
||
<h3><code>DispenseShort</code> <span class="cls inventory">inventory</span></h3>
|
||
<p>The dispenser returned fewer notes than requested and reported no error. The customer is owed the difference.</p>
|
||
</div>
|
||
|
||
<p><small>Reference: bitspire <code>docs/adr/005-cash-out-dispense-outcome.md</code>, Decisions 3–7.</small></p>
|
||
</body>
|
||
</html>
|