1,019
edits
Changes
→How does the zynthian understand the encoders?
Line 257:
Line 257:
The I2C bus allows many devices to be connected to it and communicate. One of these devices is the MCP4728 chip which is a four channel Digital to Analog Converter ( DtoA) which means that control voltages can be generated and controlled by a zynthian parameter or the sequencer and the values used to control an external voltage controlled device. So a zynthian connected foot pedal opening and closing the filter on a separate Eurorack synth via the control voltage input to provide A Wah Wah effect.
The I2C bus allows many devices to be connected to it and communicate. One of these devices is the MCP4728 chip which is a four channel Digital to Analog Converter ( DtoA) which means that control voltages can be generated and controlled by a zynthian parameter or the sequencer and the values used to control an external voltage controlled device. So a zynthian connected foot pedal opening and closing the filter on a separate Eurorack synth via the control voltage input to provide A Wah Wah effect.
<br>
<br>
+
+
+==Which setting do I choose?==
+
+Start with custom.
+
+And do not expect to just get it right first time. We frequently see people in pursuit of the official settings, expecting them to match and it all just works. However with the combination of hardware, often being attempted for the first time and the flexible configuration options the odds of you hitting it randomly are pretty small.
+
+A methodical approach is what you should adopt.
+
+First use the Select Encoder push switch. This is the most frequently used switch and attempt to just get it working. You can enter -1 ( 0 is actually a used value) into the webconf screen to get zynthian to ignore other pins. And purely concentrate on that one pin and switch.
+If using a MCP23017 be sure you have a recognised response from 12cdetect -y 1 whilst GPIO you will have to check rigourously. But don't attempt anything else, tempting as it might be to get anything else working.
+
+Next add the Encoder pins for the SELECT encoder.
+After this you will have one encoder working and it will confirm if you have de-bounce issues or that it is going the correct way.
+
+Then proceed to the other Encoders.
+
+BACK is probably the next one to do Switch first encoder pins second.
+
+If whilst doing GPIO connections you find a pin that obstinately refused to work then try a different pin. Raspberry Pi does occasional magic in this area and I've had pins that have worked perfectly in the past just stop working along with the attached encoder.
+
+Remember
+ Make Notes!!
+
+You will probably be revisiting all this for some reason, normally expansion, at some later date and it is frustrating to have to work it all out again from scratch.
==Encoders directly connected to GPIO Pins==
==Encoders directly connected to GPIO Pins==