Coin mechanism keeps jamming

Empty the coin box and remove the coin mech. Inspect the coin path for bent coins, foreign objects, or sticky residue. Use compressed air to clear the acceptor and tube openings, then wipe the coin track with a dry cloth.

Verify coin tubes are seated and aligned, and that the tube sensors read correctly. Low tube levels can trigger payout errors or “exact change” conditions that feel like jams. Refill tubes to the recommended float and confirm the coin mech sees each denomination.

If jams continue, run a calibration or coin-learning cycle per the mech manual. Replace damaged tube sensors or the entire acceptor if coins repeatedly route to reject or bind in the gate.

• Check coin tube levels and confirm the mech reports full status.
• Inspect the return gate for binding or slow movement.
• Test acceptance with multiple coins from each denomination.

• Clean the coin path quarterly and replace worn coin tubing as needed.
• Keep coin floats consistent to avoid payout failures.
• Remove foreign coins during service to prevent jams.

• Coins reject across all denominations after calibration.
• Repeated jams after swapping the acceptor.
• Visible damage to the coin track or gate mechanism.

<!-- 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.