Fine-tuning ball device timing
Related Config File Sections:
The default timeouts in
very conservative and usually too long. You might have noticed delays
after the eject of the second ball when starting a multiball. This is
caused by the default
eject_timeouts setting which will cause the ball
device to wait
10s until the ball is confirmed to be on the playfield.
Only after that the next ball will be ejected because before that
timeout the ball may return back into the device (e.g. roll back in the
To minimize delays during ejects to the playfield you need to measure
the maximum time the ball may take to return after an eject. Set
eject_timeouts to that value but not lower. If you set it lower the
ball may become confirmed and then you end up with two simultanious ball
inside the plunger lane. In case that time is still too long you might
be able to use
confirm_eject_switch (but that might require a hardware
Also, please note that this only applies to devices ejecting to a playfield. If you are ejecting into another device (e.g. trough to plunger lane) the timeout does not really matter because the ball will be confirmed once it hits the target device.
Something missing or wrong? You can fix it!
This website is edited by people like you! Is something wrong or missing? Is something out of date, or can you explain it better?
Please help us! You can fix it yourself and be an official "open source" contributor!
It's easy! See our Beginner's guide to editing the docs.
Page navigation via the keyboard: < >
You can navigate this site via the keyboard. There are two modes:
General navigation, when search is not focused:
- F , S , / : open search dialog
- P , , : go to previous page
- N , . : go to next page
While using the search function:
- Down , Up : select next / previous result
- Esc , Tab : close search
- Enter : go to highlighted page in the results