fix: remove line breaking mypinballs segment displays #1880
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This might be another naive PR from our side, but we have been trying to get our "mypinballs" segment displays going and have been running into a strange issue. The displays were initializing as expected, but any value we entered only ever displayed
" 0"
and was the case for all 4 displays we're running. I reached out to the guy who wrote the MyPinballs firmware and he provided instructions for the formats the displays expect which is as such:Control Code
:Display ID
:Integer Value to Display
So to display a score of 500 on the 2nd display, the value is
1:2:500
. We were able to confirm our displays are working by simply connecting from the terminal as such:echo "1:1:1234567\n" > /dev/ttyACM1
.With this confirmed, we looked at the MyPinballs mpf source and noticed this curious piece:
As a hunch, I removed the line... and instantly our attract values displayed. Further, starting a game reinitialized the displays and switch hits were scoring. I'm wondering if there are perhaps different versions of the MyPinballs segment display controller or maybe other updates downstream broke the existing implementation? Anyone else running these displays that could test against the
0.57.x
branch and report back?