diff --git a/README.md b/README.md index 455612b..8a3d8bf 100644 --- a/README.md +++ b/README.md @@ -46,6 +46,8 @@ The nature of this project is to be open-ended and community driven. my r_e_c_u_ langolierz@gmail.com +also facebook user group : https://www.facebook.com/groups/114465402691215/ + all feedback is appreciated. if you want to donate to this project you can do so with the above email via paypal : everything i receive will go into improving __r_e_c_u_r__. cheers to Leo Browning for the 3d modelling and vector art and to Ben Caldwell for heaps of help with the code! [vectorfront]: ./documentation/vectorfront_keys.png diff --git a/documentation/exploring_feature_notes/cv_gate_and_serial_midi_input.md b/documentation/exploring_feature_notes/cv_gate_and_serial_midi_input.md index 3991810..e5f8dfa 100644 --- a/documentation/exploring_feature_notes/cv_gate_and_serial_midi_input.md +++ b/documentation/exploring_feature_notes/cv_gate_and_serial_midi_input.md @@ -8,7 +8,26 @@ i believe it is possible to read midi in from an i/o pin (that can read serial) the [adafruit tft display] mentioned above also uses the gpios to connect to the pi - in particular it uses 5 spi pins and two standard pin outs. by cross referencing the [raspi gpio] docs it does not use either of the rx serial pin , which would be needed if i were to receive midi directly (rather than through usb), it also leaves plenty of pins for receiving cv from a [mcp3008] through software spi for example. it is likely that my gpio lcd screen communicates with the pi in a similar way and that i could figure out a way to connect these extensions if desired. +what follows is the interface of cheep lcd from the shop page : + +PIN NO.| SYMBOL | DESCRIPTION +--- | --- | --- +1, 17| 3.3V | Power positive (3.3V power input) +2, 4 | 5V | Power positive (5V power input) +3, 5, 7, 8, 10, 12, 13, 15, 16 | NC | NC +6, 9, 14, 20, 25 | GND | Ground +11 | TP_IRQ | Touch Panel interrupt, low level while the Touch Panel detects touching +18 | LCD_RS | Instruction/Data Register selection +19 | LCD_SI / TP_SI | SPI data input of LCD/Touch Panel +21 | TP_SO | SPI data output of Touch Panel +22 | RST | Reset +23 | LCD_SCK / TP_SCK | SPI clock of LCD/Touch Panel +24 | LCD_CS | LCD chip selection, low active +26 | TP_CS | Touch Panel chip selection, low active + +from this i should b able to work out which pins i can use for midi in and for analog-to-digital inputs (also piCapture needs some inputs too) + [instructable]: http://www.instructables.com/id/PiMiDi-A-Raspberry-Pi-Midi-Box-or-How-I-Learned-to/ [adafruit tft display]: https://www.adafruit.com/product/2441 [raspi gpio]: https://www.raspberrypi.org/documentation/usage/gpio/ -[mcp3008]: https://learn.adafruit.com/raspberry-pi-analog-to-digital-converters/mcp3008 \ No newline at end of file +[mcp3008]: https://learn.adafruit.com/raspberry-pi-analog-to-digital-converters/mcp3008 diff --git a/documentation/faq.md b/documentation/faq.md index 84b0c84..f286868 100644 --- a/documentation/faq.md +++ b/documentation/faq.md @@ -1,3 +1,4 @@ + # frequently asked questions a place to document the questions and thoughts asked about r_e_c_u_r so far. if you have any other questions please ask them in the fb group or get in touch directly. @@ -40,4 +41,5 @@ to get to these you will probably need a usb keyboard (a usb mouse can help too) [.keymap]: /dotfiles/.keymap [keypad_action_mapping.json]: /json_files/keypad_action_mapping.json [develop page]: /documentation/develop_docs.md -[build]: /documentation/build_docs.md \ No newline at end of file +[build]: /documentation/build_docs.md +