Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unexpected_ball_on_playfield event is causing ball count to be greater than balls_installed in the game preventing a game from being started. #1605

Open
mythmaker9 opened this issue Oct 12, 2021 · 1 comment

Comments

@mythmaker9
Copy link

If a ball device on the playfield registers a switch hit unexpected due to a temporary or unknown hardware issue, MPF is throwing this event:
EventManager : Event: ======'unexpected_ball_on_playfield'====== Args={}

This is causing MPF to report a ball on the playfield and ultimate increase the ball count in the game.

This occurs even if a hardcoded value is set in the machine configuration such as:
machine:
balls_installed: 3
min_balls: 3

This will prevent any games from being started ever on the game even if this switch hit only happened once temporarily or is an intermittent issue (think light hitting an opto, etc).

@jabdoa2
Copy link
Collaborator

jabdoa2 commented Oct 13, 2021

Capping balls at balls_installed might work. Maybe even a max_balls parameter? But that would require additional warnings/error states when we actually find more balls than expected.

This will prevent any games from being started ever on the game even if this switch hit only happened once temporarily or is an intermittent issue (think light hitting an opto, etc).

That is only partially true. If you enable ball search it will resolve this condition (disabled by default to prevent it from hurting builders).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants