You may need it in case the encoder has an internal pull up resistor.
Ok, I see you seem to have a model of the MCP23017 where you setup your address pins not by wiring, but with small switches, very convenient! You put them all in “1” position, hence the 0x27 address. If you want to use the 0x20 address (not mandatory), switch them all to “0” and setup the address it the corresponding webconf dropdown.
1 Like
Actually it’s the opposite. By setting the 3 DIP switches to on,on,on I’m getting 0x20.
The encoders work without the vcc but it seems to have mapped the switch to left and right. It worked properly when I had the vcc connected.
It was similar in my case with my encoders with pull up resistors. Without connecting VCC they reacted somehow, but had some weird stepping behavior and did mix up decrement, increment and push somehow.
It is likely that if you look at the down side of the encoder pcb you’ll find some resistors in between the pcb lanes, which would probably measure something like 10 kOhm.
Alternatively you could desolder the pcb. For myself I opted against that kind of solution.
Hello Again,
So I’ve managed to wire up all my encoders. I had an extra one so I also wired it up for a total of 5 encoders.
I can confirm that they are all working (at least doing somethign), the part I haven’t solved is how to set the commands that’s triggered when I turn or push the encoders.
These switches are for the encoder push buttons, yes?
In order to adjust what these switches are doing, do I change that under the keyboard binding?
Is this how the switches and buttons are assigned a command? Maybe I’m missing something here.
I can see that backspace/escape is set to be triggered by zynswitch1, but none of my encoders are triggering that “back” command.
The wiring is labeled “V5 Zynpot Switch” but that is not assigned to anything in the keyboard binding, so I’m not too sure how the encoders are being programmed to trigger commands (adjust volume, balance, mute, solo, etc.)
I’m trying to solve this stuff on my own but can’t find the relevant info in the adding encoders wiki. Adding Encoders - ZynthianWiki
In section 3"1.1.3.1 Addressing" What is this referring to? I don’t see anything in the wiring section that refers to ch, back, LS, select. Is it for the switch action, short, bold, long?
Thanks again.
I’m not an expert in these things, maybe somebody else could clarify things better. But as far as I understand, the zynthian operating system has context specific preconfigured actions depending on which screen you are at a given time for exactly 4 encoders. For example, in the engine screen you adjust the plugin parameters, in the mixer menu you might adjust chain volume and pan and so on. You can look up these actions here, no need to configure further:
What you see in your screenshot is the setup for your encoder push action configured as the prefered default. So the context specific short, bold, long press action is applied to short, bold, long press (see manual above). So, if your goal is the default behaviour of zynthian, no action is required.
Keybindings are another thing (literally computer keyboard bindings connected to a zynthian).
I have no idea how to configure custom actions of a fifth encoder. I’m not sure though, if it is intended by the operating system, at least for the encoder movement. You might be able to use the push button for any of the other virtual buttons, if that is intended.
Oh yeah. I think you’re correct. Seems like the 4 encoders are pre-programmed. Maybe I’ll find some buttons to fill the remaining 4 pins on the expansion card.
Thanks!
Hardware switches are configured in HARDWARE ->Wiring page of webconf.
2 Likes
If you’re eager to add 4 switches, the Zynthian V4 layout might be suitable for you. If you want all the 20 V5 buttons without further wiring and you have a touchscreen build in, you could test the virtual buttons you can enable in the webconf “Display” section or just stick to the default touch screen actions.
There is a fair bit of zynthian history built into this area and differing approaches were adopted.
One early concept was using MIDI events to trigger stuff and this was developed but it became apparent that there was a conceptual level that needed addressing hense the UI actions.
The basic concept of how a device behaves is defined in hardware, because that’s exactly what it is.
Personally I would tend to go straight for custom and then save it under your own naming convention rather than try to adapt/adopt one of the existing templates. They are designed for specific zynthian kit configurations and whilst everything is available to see, there’s no magic, it’s best to learn quite what you are doing.
Frequently the problems come down to your own desired operation. I like having audio record on a toggle S1 button and so it goes there, but defining a work environment is frequently evolutionary so it’s better to keep good versioning habits.
I’ve got a zynthian pedal board with a zynaptik i/o board connected to 8 Yellow LED switches. I’ve had these LED’s flashing along with zynseq (CV’s and triggers from MIDI ) and changing Patches with the push buttons, all from the hardware config and a couple of zs3 files.
Mind you I haen’t tried that out recently so it might need reviewing.
There is a basic logic to it all and it’s remained consistent so decide which one of the functional modes you want. There is a lot of flexibility.
1 Like
Ok. thank you both. I was messing with the custom functions earlier and got a better idea of how it can control the ui. Between the encoders and the touch screen, I can now get around to the different menus pretty easily.
…
You can do everything with touch only and everything with 4 encoders with switches (v4). Specific documentation is written for each mode. Select in top right of guide in wiki.
3 Likes
I ended up getting a wireless keypad along with the encoders. The default key binding works quite well.
1 Like