One checklist item (beside the coin debounce issue) is to run through all my component testing scripts and add missing components.
Today, my testing script exercises one complete game, and mimic all three balls scoring and exercising all devices but it does not exercise the service menu options fully. That is one large script instead of a series of smaller components that link together for a larger. Ideally the series would exercise led shows or dmd shows or bonus countdown or high scores or replays individually.
I need to add all the testing script so that I can confidently regression test the machine and help future proof it.
There may be future OPP board updates, or mpf updates that I want to use or try out and the only way I can safely test is by having my testing script ready.
Luckily I have a dedicated testing environment consisting of a Virtualized Linux host running MPF 0.55, and dedicated dual stm32 boards, and neopixel LED that mirror my production machine(s). My testing process will use the virtualized playfield (mpf monitor) and (mpf both -x) and (mpf both #with stm32 boards) sessions.
Lastly, I would like to trial using a raspberry pi as my production master cpu rather than a Intel i5 machine. The pi has a smaller foot print and GPIO's and cheaper then the Intel I5. Pulling the Intel cpu and swapping in a Pi 3 would fit the theme of my my "man cave". I have a jukebox powered by a pi, a mame project powered by a pi, so I want a pinball machine power by a pi. Only one issue to confirm is will the pi be fast enough for my production game.