Hello Everyone,
I am looking for some advice on using multiple OLED's in a project (at least 8 x 0.96" displays).
Ultimately, the project will be a cessna style com/nav/adf/ap stack using a Teensy in Flight Sim 'mode' (what a combo by the way, X-Plane 11, Teensy plugin and Teensy - absolutely marvelous). I have prototyped Nav/Com using 7-Seg LEDs and it works fine but the displays are large and difficult to panel mount tightly so the final project is taking up too much space (I am not looking to replicate a cockpit - just abstract away from using mouse/mouse wheel in the sim). After that I would like to use the same type of displays (and experience gained) to make a 757 style autopilot MCU / Radio stack. Of course, Teensy based!
I managed to get a few cheap 0.96" OLEDs from Amazon that use I2C but all have the same address and no obvious way to 'chip select' (4 wire only Vcc Gnd, Sda Scl)
(https://www.amazon.co.uk/gp/product/B07BDFXFRK/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1). The form factor is perfect but reading through various library docs suggests using more than one of these will cause issues, if it is possible at all.
Could anyone suggest the best way to plan this project or suggest what OLED module to use (the 0.96" seem limited but they fit perfectly). Should I use SPI displays or some other protocol? Is this achievable with one Teensy or should I look to have a micro per display (maybe a nano or LC connected by serial/SPI/I2C to the controlling teensy?) or should I just wait until libraries catch up with using multiple OLEDs.
Sorry for asking such a mundane question. I always find my way through code eventually but find selecting hardware a nightmare My coding ability is OKAY but bit bashing and the like is beyond me.
As a separate question, is it appropriate to submit a final project to this forum for review/suggestions/criticism. My prototype Nav Panel works but I'm sure it the code could be refactored and then it may be useful to others?
Love the Teensy, thanks for all the hard work making it so accessible to folk like me ;-)))
Mike
I am looking for some advice on using multiple OLED's in a project (at least 8 x 0.96" displays).
Ultimately, the project will be a cessna style com/nav/adf/ap stack using a Teensy in Flight Sim 'mode' (what a combo by the way, X-Plane 11, Teensy plugin and Teensy - absolutely marvelous). I have prototyped Nav/Com using 7-Seg LEDs and it works fine but the displays are large and difficult to panel mount tightly so the final project is taking up too much space (I am not looking to replicate a cockpit - just abstract away from using mouse/mouse wheel in the sim). After that I would like to use the same type of displays (and experience gained) to make a 757 style autopilot MCU / Radio stack. Of course, Teensy based!
I managed to get a few cheap 0.96" OLEDs from Amazon that use I2C but all have the same address and no obvious way to 'chip select' (4 wire only Vcc Gnd, Sda Scl)
(https://www.amazon.co.uk/gp/product/B07BDFXFRK/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1). The form factor is perfect but reading through various library docs suggests using more than one of these will cause issues, if it is possible at all.
Could anyone suggest the best way to plan this project or suggest what OLED module to use (the 0.96" seem limited but they fit perfectly). Should I use SPI displays or some other protocol? Is this achievable with one Teensy or should I look to have a micro per display (maybe a nano or LC connected by serial/SPI/I2C to the controlling teensy?) or should I just wait until libraries catch up with using multiple OLEDs.
Sorry for asking such a mundane question. I always find my way through code eventually but find selecting hardware a nightmare My coding ability is OKAY but bit bashing and the like is beyond me.
As a separate question, is it appropriate to submit a final project to this forum for review/suggestions/criticism. My prototype Nav Panel works but I'm sure it the code could be refactored and then it may be useful to others?
Love the Teensy, thanks for all the hard work making it so accessible to folk like me ;-)))
Mike