Machine displays “Exact Change Only”

Refill coin tubes and confirm the mech recognizes tube levels. A single empty tube can trigger “exact change” even if other tubes are full.

Verify prices are not set to amounts that require change your float cannot support. Adjust pricing or coin float settings so the machine can return change for common bill inputs.

If the condition persists, inspect tube sensors and run the coin mech calibration routine. Replace any failed tube sensors or a worn acceptor that misreads coin counts.

• Confirm each tube reports the correct count in service mode.
• Test payouts using a bill to verify change is available.
• Check for stuck coins in the payout chute.

• Maintain a minimum coin float at each visit.
• Avoid pricing that requires rare coins to make change.
• Clean the payout path to prevent coin jams.

• Tube sensors fail after recalibration.
• Payout motor does not run when commanded.
• Change issues persist across multiple machines.

• Confirm all steps are documented so the next technician can reproduce the results.
• Capture before/after metrics (errors cleared, sales restored, or uptime improved).
• Review machine, reader, or route settings to ensure they match location standards.

• Skipping a controlled test leads to false positives.
• Updating hardware without documenting configuration changes.
• Forgetting to verify payout, refund, or reconciliation data after changes.

• Run a final test with known-good inputs.
• Log the outcome with date, time, and device identifiers.
• Schedule a follow-up check if the location has high traffic or seasonal demand.

<!-- expanded:v2 -->

• Document changes with time, machine ID, and location name.
• Verify settings, pricing, and service modes after each fix.
• Capture before/after results to confirm resolution.

• Test with known-good inputs and controlled conditions.
• Validate telemetry, alerts, and payment logs where applicable.
• Confirm location expectations and update the site contact.

• Configuration drift after firmware or component swaps.
• Inconsistent power or network conditions at the location.
• Gaps in preventive maintenance routines.

• Monitor for 7 days and note any repeat errors.
• Schedule follow-up if the site is high-traffic.
• Escalate with full logs and photos if issues repeat.

• Inspect harness integrity, connectors, and power supply stability.
• Review error codes against the OEM manual before swapping parts.
• Compare with a known-good component to isolate the fault.

• Clean sensors monthly and replace wear parts on schedule.
• Log firmware versions and configuration baselines.