1,019
edits
Changes
Jump to navigation
Jump to search
no edit summary
Line 232:
Line 232:
====MCP23017 INT-A Pin ====
−====MCP23017 INT-B Pin ====
−====Zynaptik Config====
−====ADS1115 I2C Address ====
−====MCP4728 I2C Address ====
−==Encoders directly connected to GPIO Pins==
−This is the original approach used from the start the Encoder were connected directly to GPIO pins on the Raspberry Pi. It is not considered as the recommended approach.
−Please see the 23017 approach described below.
−[[File:Zynthian-amp3-open.jpg|300px|frame|center|Zynthian-amp3-open]]
−<br clear=all>
−==Encoders connected using a MCP23017 chip==
−As an interface grows ( when 4 user definable switches were added to V3 (?) we had already moved away from the direct encoder route in favour of a much more efficient way of reading encoders and switches, which passed off some of the effort to another piece of silicon. The MCP23017 16 port I2C multiplexer. This board meant the communication between the Raspberry Pi and this 20 pinned chip could be handled by only a few wires at the Pi end, and a standard form of communication called I2C.
−The zynaptik-3 board from zynthian provides all the interfaces for encoders and the extra switches introduced, along with MIDI interfaces and Control voltage and digital ins and outs which represents the official implementation of this sort of approach.
−[[File:Zynaptik-3.jpg|center|thumb]]
−But this isn't the only option there are several MCP23017 boards available, and you can make your own with stripboard. The zynthian will work with pretty much any of these boards as long a it presents enough Input pins to cover the encoders. Zynthian needs a minimum of 12 i/0 pins for encoders and their switches.
−<br clear=all>
<br>
<br>
+
+
+
+====MCP23017 INT-A Pin ====
+====MCP23017 INT-B Pin ====
+
+====Zynaptik Config====
+
+====ADS1115 I2C Address ====
+
+====MCP4728 I2C Address ====
+
+==Encoders directly connected to GPIO Pins==
+
+This is the original approach used from the start the Encoder were connected directly to GPIO pins on the Raspberry Pi. It is not considered as the recommended approach.
+
+Please see the 23017 approach described below.
+
+[[File:Zynthian-amp3-open.jpg|300px|frame|center|Zynthian-amp3-open]]
+
+<br clear=all>
+
+==Encoders connected using a MCP23017 chip==
+As an interface grows ( when 4 user definable switches were added to V3 (?) we had already moved away from the direct encoder route in favour of a much more efficient way of reading encoders and switches, which passed off some of the effort to another piece of silicon. The MCP23017 16 port I2C multiplexer. This board meant the communication between the Raspberry Pi and this 20 pinned chip could be handled by only a few wires at the Pi end, and a standard form of communication called I2C.
+
+The zynaptik-3 board from zynthian provides all the interfaces for encoders and the extra switches introduced, along with MIDI interfaces and Control voltage and digital ins and outs which represents the official implementation of this sort of approach.
+
+[[File:Zynaptik-3.jpg|center|thumb]]
+
+
+But this isn't the only option there are several MCP23017 boards available, and you can make your own with stripboard. The zynthian will work with pretty much any of these boards as long a it presents enough Input pins to cover the encoders. Zynthian needs a minimum of 12 i/0 pins for encoders and their switches.
+<br clear=all>
+
===MCP23017 pins===
===MCP23017 pins===
Line 325:
Line 358:
Make Notes!!
Make Notes!!
−=== Connecting via the GPIO Pins. ===
=== Connecting via the GPIO Pins. ===