midi controlling capabililty while using a multiple small lcd module

Y

yummymetalman

New member
hello i am newbi here specially in teensy module.. i am currently planning in making a midi controller for a pedal board that has a midi capability or even connecting to pc for a software midi controll for software guitar effects.
now, plan is i want to make a midi controll pedal that has a 12 buttons, 2 for the bank selectors, 10 for the effects.
each effects button will have a small lcd screen indicating the effects that you assign from your main pedal will reflect to that screen along with the banks also and all of this using a teensy board or controlling multiple of them for the lcd also..

my question is how do i possibly do that? may the code lines are hard but its possible to make it right? it has to be.
i hope you can help me with this
thank you so much!!!!

​

​

 
Of everything that you have described, the LCD screens are likely to be the biggest challenge, but even those can be tamed. You'll probably want to look for an LCD screen that uses the SPI interface, such as <this> one. The key here is that all of the screens will share their SCLK (data clock) pin, their MOSI (data from the Teensy to the screens) pin, their D/C (data or control selection) pin, and their RST (reset) pin. The CS (chip select) pin to each LCD screen will be unique, allowing you to select a specific LCD screen to write to.

I would suggest that you buy just two of whichever LCD screen you choose. Start with example sketches, etc. for the LCD screen that you have chosen, & get just one of them working (i.e. get to where you can reliably write to the single LCD screen). When you have that well under control, then connect up the second LCD screen & get to where you can selectively & reliably write to each of the LCD screens individually. If/when you're happy with that, then you can finally get the total number of LCD screens that your full project will have & add them each, one by one, verifying that you can write to each of them as you go.

Good luck & feel free to ask any other questions !!

Mark J Culross
KD5RXT
 
Personally I would use OLED screens such as this. Square ones are available a little cheaper. They are driven by I2C which is slower than SPI, but I suspect that speed is not a priority as they will (I guess) not be changed very frequently. Using I2C they could be easier to drive and dependant upon the modules chosen more than one can be addressed by the same two I2C lines,
 
kd5rxt-mark said:
Of everything that you have described, the LCD screens are likely to be the biggest challenge, but even those can be tamed. You'll probably want to look for an LCD screen that uses the SPI interface, such as <this> one. The key here is that all of the screens will share their SCLK (data clock) pin, their MOSI (data from the Teensy to the screens) pin, their D/C (data or control selection) pin, and their RST (reset) pin. The CS (chip select) pin to each LCD screen will be unique, allowing you to select a specific LCD screen to write to.

I would suggest that you buy just two of whichever LCD screen you choose. Start with example sketches, etc. for the LCD screen that you have chosen, & get just one of them working (i.e. get to where you can reliably write to the single LCD screen). When you have that well under control, then connect up the second LCD screen & get to where you can selectively & reliably write to each of the LCD screens individually. If/when you're happy with that, then you can finally get the total number of LCD screens that your full project will have & add them each, one by one, verifying that you can write to each of them as you go.

Good luck & feel free to ask any other questions !!

Mark J Culross
KD5RXT
Click to expand...
Thank you for your reply sir.. this will help me so much. Thank you!!
 
BriComp said:
Personally I would use OLED screens such as this. Square ones are available a little cheaper. They are driven by I2C which is slower than SPI, but I suspect that speed is not a priority as they will (I guess) not be changed very frequently. Using I2C they could be easier to drive and dependant upon the modules chosen more than one can be addressed by the same two I2C lines,
Click to expand...
Thank you sir.. i will all try the suggestions i may get in this forum. Thanks sir
 
I would suggest you use 0.9 inch i2c OLED displays as these are perfect for your task. You want multiple displays, so best thing is to get that workig first. Take a look a this tutorial: https://dronebotworkshop.com/multiple-i2c-bus/
once you have that working, you now want to develop your buttons. i suggest a similar multiplex approach which will use 4 pins to control the multiplexer and one pin for the signal to read the buttons for your first 16 buttons. For every extra 16 inputs you just add another mux and use one more pin on your teensy.
Now you have the screens and buttons working move on to the midi...

good luck!
 
You must log in or register to reply here.
Back
Top