Git Product home page Git Product logo

Comments (5)

EAGrahamJr avatar EAGrahamJr commented on September 22, 2024

I was attempting to tackle this and it got ugly really fast.

  • The I2C interfaces typically take a "data" and "command" prefix
  • The SPI interface (apparently) uses the dcPin to differentiate
  • The constructors got out of hand very quickly trying to preserve the existing structure

These are my thoughts, but since it's not my project and not my API, I will leave it to your discretion:

Recommendations:

  • Move the data and command methods to the SsdOledCommunicationChannel objects
    • the SPI implementation would add the dcPin and resetPin devices
    • the I2C implementation would add the command and data prefixes
  • Simplify the constructors, e.g.
     SsdOled(SsdOledCommunicationChannel channel, int width, int height, int type)
  • Put all of the "initialization sequences" into arrays and send at once, instead of the current one-at-a-time setup
    protected SsdOled(...) {
        this.device = device;
        // init sequence
        this.device.command(getInitializationSequence());
    }
    protected abstract byte[] getInitializationSequence();
  • SSD1306 might get a bit tricky because there are two variants: 64 and 32 height
    • there's also a lot of overlap with an SSD1337 which is 128 x 128 (the command set looks to be almost identical, but still working on that)

from diozero.

EAGrahamJr avatar EAGrahamJr commented on September 22, 2024

Additional note: since I don't have any of the Colour 😀 OLED, I won't be able to test any changes against what's already there.

from diozero.

mattjlewis avatar mattjlewis commented on September 22, 2024

Yes, a tricky one. I recall someone contributed the barebones of the I2C code. I typically use SPI for OLED coms hence cannot personally confirm whether it works or not via I2C. The ones I have could be both SPI and I2C, let me check. Also, it could be related to the fact that it is 128x32 rather than the 128x64 one that I test with.

from diozero.

EAGrahamJr avatar EAGrahamJr commented on September 22, 2024

Oh, it definitely is - I'm referring to the CircuitPython drivers and some of the init/offsets are just slightly different.

If you can at least check that I didn't break anything, I think what I'm doing will work.

from diozero.

EAGrahamJr avatar EAGrahamJr commented on September 22, 2024

BTW, I was the one that had started the I2C channel.

small-oled

from diozero.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.