Keyboard Shortcut for "User" doesn't bypass button mappings you don't want for the keyboard.

[thorr2]

I have an arcade cabinet with buttons on the front of it for Start 1P, Start 2P and coin slots and other buttons. All these buttons are sending keyboard presses. I also have buttons that send keyboard combinations for the three MiSTer button functions, Reset, OSD and User.

When mapping joystick button controls in a core for the front panel buttons on my cabinet for coin, etc., the User button I made that uses the keyboard combination for User works to bypass joystick directions, but when I get to the buttons, I have to use the physical User button on the MiSTer to bypass mapping those buttons.

Can you make it so the keyboard User combination will bypass all the keyboard buttons that I don't want to map? I think it might be thinking the first time I use the User button that it is mapping it to something and it won't use it later to bypass anything because it is already in use. I am not sure.

[sorgelig]

If you make arcade cabinet by yourself then why simply don't wire USER button from I/O boards?
It's not a good idea to take off the key from keyboard.

[thorr2]

I tried this, two different times just to be sure. In my arcade cabinet I have the Antonio Villena board and for some reason, long wires connected to the GPIO pins or button connections results in the wrong behavior. All three buttons act like reset. I could go through an additional circuit to try to eliminate the problem but I didn't want to try to make it work and wreck something. Thanks!

…

On Fri, May 26, 2023, 12:50 PM Alexey Melnikov ***@***.***> wrote: If you make arcade cabinet by yourself then why simply don't wire USER button from I/O boards? — Reply to this email directly, view it on GitHub <#784 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMVRPLTBQXNL7BT5VTOQCLTXIECPHANCNFSM6AAAAAAYQPXRNY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[sorgelig]

Internal FPGA pullup resistors are about 100kOhm which may be too weak for extremely long wires. You can add 10KOhm pullup resistors to 3.3v per button which should work fine.
Make sure you connected it correctly because acting as reset for every button looks suspicious.

[thorr2]

Thanks! What I actually did was mount one of these to the MiSTer case and solder the four connectors on it to the ground and three button functions: https://www.amazon.com/gp/product/B089222S84 I used this cable with it that I will eventually wire to the buttons on the arcade cabinet: https://www.amazon.com/gp/product/B0813C1FFD With just the jack wired, and no cable plugged in, it works fine with the MiSTer's buttons. As soon as I plug in the 4-wire cable, even if I use a short one, I get the strange behavior when pressing the buttons directly on the MiSTer or connecting the ground wire and another wire on the cable. I tested the connectivity with my meter and it all seems correct with no beep connectivity or ohms between any of the wires. With the MiSTer off (and on), I only get a beep with my meter with the ground and the correct other wire when I press the correct MiSTer button for the wire. All three buttons make my meter beep when it is connected to the appropriate wire and ground on the cable. So the cabling seems correct.

Just to be clear so I don't blow something up, with using the 4-wire jack above, are you suggesting that I leave the existing soldering to the jack and each button and ground in place and additionally solder three 10K resistors between each of the three non-ground connections on the jack and +3.3V? I am pretty sure this is correct, but wanted to ask to be sure.

Thanks again!

[sorgelig]

Just to be clear so I don't blow something up, with using the 4-wire jack above, are you suggesting that I leave the existing soldering to the jack and each button and ground in place and additionally solder three 10K resistors between each of the three non-ground connections on the jack and +3.3V? I am pretty sure this is correct, but wanted to ask to be sure.

that's correct.

[thorr2]

I did the mod and unfortunately it is behaving the same way. I wired directly to the GPIO pins from the jack with push on GPIO connectors to pins 13,15,17 and 12 for ground, plus the three 10K resisitors between 13,15, and 17 to 29 for VCC. I can't explain it. I will reach out to Antonio Villena and see if he has any ideas what might be causing the issue with his version of the I/O board. Thanks again for all of your help. I really appreciate it.