Reader stuck in idle mode

Restart the reader and confirm MDB connection. Check power supply stability and verify the reader receives continuous power during idle periods.

If idle persists, update firmware and re-pair the device in the portal. Also confirm the machine is set to accept cashless and that the reader is assigned to the correct machine type.

• Confirm the reader is marked “online” and active.
• Verify the device profile matches the machine type.
• Review any idle or timeout alerts.

• Reseat power and MDB cables.
• Test with a known-good reader to isolate the issue.
• Verify the machine controller enables cashless mode.

• Provide device ID and firmware version.
• Include photos of wiring and controller connections.
• Note the exact time idle mode began.

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

• Verify the reader is paired to the correct machine ID.
• Confirm MoMa configuration and device firmware are current.

• Ensure alert thresholds align to route service windows.