[Question] - Drop Down Target Compatibility?

[friedrickjoel]

Trying to get this going with System Alpha board today (WAV trigger board not getting power for some reason, will investigate later, only mention because I can't hear anything that might be useful for troubleshooting) ... but I have retro-fit / converted the 6 standup targets to drop downs (using the updated magnetic ones, not horseshoe) and the code doesn't seem to ever pop them back up... at least from what I can tell so far without being able to hear anything.

Wondering your thoughts on how well your code would work with them being drop downs. I was going to use AI to help me locate code /add code that would trigger them (as well as boot to original code by default). But wanted to get your opinion on whether this is something reasonable to do with your code base. My alternative is to just move it over to my Black Knight :)

Thanks!
Joel

EDIT: Sound is working now (this is cool!)

[MrEkted]

Hi Joel, Here are my standard diagnostics for WAV trigger issues: https://www.pinballrefresh.com/blog/diagnosing-sound-issues I haven't added drop target code to FP25 yet -- my machine is just standups. I'd be happy to take a stab at it, but it would make you the guinea pig. Are you comfortable testing out new, speculative code? If so, let me know. If not, there's someone else who has drops and has volunteered but he doesn't have his machine running the new code yet so it could be a while. Meanwhile, you're going to need that WAV trigger working! If you could go into the solenoid test (original code is fine) and tell me which numbers correspond to which solenoids (especially the drop target resets, but also the ones before and after), that would be helpful. Take care, Dick

…

On Tue, Jun 16, 2026 at 4:23 PM Joel ***@***.***> wrote: *friedrickjoel* created an issue (RetroPinUpgrade/FP25#1) <#1> Trying to get this going with System Alpha board today (WAV trigger board not getting power for some reason (will investigate later, only mention because I can't hear anything that might be useful for troubleshooting)... but I have retro-fit / converted the 6 standup targets to drop downs (using the updated magnetic ones, not horseshoe) and the code doesn't seem to ever pop them back up... at least from what I can tell so far without being able to hear anything. Wondering your thoughts on how well your code would work with them being drop downs. I was going to use AI to help me locate code /add code that would trigger them (as well as boot to original code by default). But wanted to get your opinion on whether this is something reasonable to do with your code base. My alternative is to just move it over to my Black Knight :) Thanks! Joel — Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIYTXUQWPG4S5LKEZDXJJUD5AGUFDA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG43TMMZTGM4DDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYTXUTNDKXSIVG7VQAED5L5AGUFDAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNBQGY2DIMZQGA5US43TOVSTWNBWG43TMMZTGM4DDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AIYTXUQ4KJFRG6PHC37UJRD5AGUFDA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG43TMMZTGM4DDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AIYTXUUKO77ANUQRT475UPD5AGUFDA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG43TMMZTGM4DDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[tjrat]

Dick, I think you got my Email crossed with Joel's. I am the dot matrix display guy. tom

________________________________ From: Dick Hamill ***@***.***> Sent: Tuesday, June 16, 2026 10:09 PM To: RetroPinUpgrade/FP25 ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [RetroPinUpgrade/FP25] [Question] - Drop Down Target Compatibility? (Issue #1) [https://github.com/ghavatar/u/36781010?s=20&v=4]MrEkted left a comment (RetroPinUpgrade/FP25#1)<#1 (comment)> Hi Joel, Here are my standard diagnostics for WAV trigger issues: https://www.pinballrefresh.com/blog/diagnosing-sound-issues I haven't added drop target code to FP25 yet -- my machine is just standups. I'd be happy to take a stab at it, but it would make you the guinea pig. Are you comfortable testing out new, speculative code? If so, let me know. If not, there's someone else who has drops and has volunteered but he doesn't have his machine running the new code yet so it could be a while. Meanwhile, you're going to need that WAV trigger working! If you could go into the solenoid test (original code is fine) and tell me which numbers correspond to which solenoids (especially the drop target resets, but also the ones before and after), that would be helpful. Take care, Dick

On Tue, Jun 16, 2026 at 4:23 PM Joel ***@***.***> wrote: *friedrickjoel* created an issue (RetroPinUpgrade/FP25#1) <#1> Trying to get this going with System Alpha board today (WAV trigger board not getting power for some reason (will investigate later, only mention because I can't hear anything that might be useful for troubleshooting)... but I have retro-fit / converted the 6 standup targets to drop downs (using the updated magnetic ones, not horseshoe) and the code doesn't seem to ever pop them back up... at least from what I can tell so far without being able to hear anything. Wondering your thoughts on how well your code would work with them being drop downs. I was going to use AI to help me locate code /add code that would trigger them (as well as boot to original code by default). But wanted to get your opinion on whether this is something reasonable to do with your code base. My alternative is to just move it over to my Black Knight :) Thanks! Joel — Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIYTXUQWPG4S5LKEZDXJJUD5AGUFDA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG43TMMZTGM4DDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYTXUTNDKXSIVG7VQAED5L5AGUFDAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNBQGY2DIMZQGA5US43TOVSTWNBWG43TMMZTGM4DDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AIYTXUQ4KJFRG6PHC37UJRD5AGUFDA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG43TMMZTGM4DDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AIYTXUUKO77ANUQRT475UPD5AGUFDA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG43TMMZTGM4DDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#1?email_source=notifications&email_token=A6TC6DZW3BOZNEWGILDDKML5AH4V3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZSGUZDMNBQHE32M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4725264097>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6TC6D3UXDDBX6IMZ4DKYV35AH4V3AVCNFSNUABGKJSXA33TNF2G64TZHMYTCNBQGY2DIMZQGA5US43TOVSTWNBWG43TMMZTGM4DDILWAI>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/A6TC6D7JKLDRBUASNPO66335AH4V3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZSGUZDMNBQHE32M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/A6TC6DZUHCCRNBBTXHMVIRL5AH4V3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZSGUZDMNBQHE32M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[friedrickjoel]

Hi Dick, thanks for the quick response!

I am comfortable trying out experimental code, in fact I was headed down the path of testing my own changes eventually. I code C# daily, but C++/Arduino is new to me. I began a starter Arduino kit with my 10 year old a few weeks ago, which gave me the confidence to try out FP25 in the first place.

My initial idea was to just detect all targets down and fire the solenoid,, but figured since the code is assuming standups it might need to fire for every drop-down, every time... this was the main reason I posted the question, I was worried more rules might need to be built for them than I could handle beyond a simple detect/fire.

At any rate, I will post switch and solenoid numbers (there's some "10-point" switches behind the drop downs too) and if you eventually take a look at it and have something to try at some point, great. If not, no worries. I might poke around and see what I can do as well.

Thanks for putting all this together, it's very, very cool.

Oh, I did get my WAV trigger working, the cause of the 'problem' is beyond embarrassing, I'll just go with 'operator error'.

Joel

Tom/tjrat - I am posting this on GitHub, not via e-mail. If you get this message maybe you're subscribed to this repo?

[MrEkted]

I've never felt older in my life. I don't know what's going on here!
Joel - maybe you can switch to email -- dickhamill@gmail.com
Tom - so sorry -- hope you're well!