Note I am using ‘just’ the out of the box Pi + Pisound hat without extra hardware, and just the Zynthian OS vangelis without the custom button scripts that Blokas provides.
Might be worth seeing if a temporary soldered GPIO17 connection, but I would check the mapping because the GPIO pins on the Pi do not directly relate to the settings in the zynconf interface which are BCM based.
You are probably best to disconnect the card from the edge connector and put a multimeter connected to 0V pin on the edge cnnector and then go hunting for the appropriate pin on the edge connector whilst repeatably pressing the button to see which pin it’s actually connected to.
I was taught that electrons don’t read and can’t identify wire colours so the only real way to be sure is a multimeter.
The secret with this sort of endeavour is make sure the device is securely mounted and you are comfortably able to access the pins with the multimeter probe without the probe leads moving the circuit board whilst you frantically grab for the meter itself as it falls off the table at the same time….
You get the picture.
Once you know which pin you are talking to it should be reasonably painless from there. . .
So as far as I understand, this is no different than connecting a button directly to the relevant GPIO pin and ground. My guess is it’s now a config error on my behalf.
Is this a pure , whatever that means, zynthian install. ? There are no entries in /boot/firmware/config.txt.
It might be worth connecting the two devices and check the actual pin involved to see if it’s changing as you press the button with both onnected.
You could have a short circuit on one side that presents the 3.3V appearing and dissappearing at the paropriate times.
It’s easy to start believing the pernitious Gods of zynthian extract great joy from our desperate attempts but surely not even they could be so fickle.
There is always a reason and it is very, very rarely personalised,.
Simply electrons going where you don’t expect them to.
Solved! I tried all possible GPIO on the original Pisound/Pi4 combo. The winner is 0. My original diagnostics must have been wrong. This configuration makes the button work with short, bold, long support.
As one of my multimeter leads broke while attempting to test this, I reproduced the working configuration on the stand-alone Pi 4 and a breadboard setup.
It shows that GPIO 17 … is configured as 0 in webconf (same config as above). As @wyleu has pondered before, the magic of raspberry GPIO numbering schemes.
And behold, the result is a working button:
DEBUG:zynthian_gui.zynswitch_short: Short Switch 4
I could configure it to send MIDI, and manually learn in sooperlooper. Unless is there a built-in webconf wiring config that would directly call the single button mode, skipping the need for manual midi learn?
