The SparkFun Qwiic OLED Display can display up to three lines of text and features 128x32 pixels in a small 0.91” (diagonal) frame. As an OLED, this display does not have a back light layer (unlike LCDs) and therefore it’s thinner, consumes less power, and has higher contrast.
Thanks to an I2C command structure, the board's firmware maintains speed by updating only the part of the screen that changes This is the same concept use with "Dirty Rectangles" or "Bit blit" operations in computer graphics.
The SparkFun Qwiic Connect System is an ecosystem of I2C sensors, actuators, shields and cables that make prototyping faster and less prone to error. All Qwiic-enabled boards use a common 1mm pitch, 4-pin JST connector. This reduces the amount of required PCB space, and polarized connections mean you can’t hook it up wrong.
If a board needs code or communicates somehow, you're going to need to know how to program or interface with it. The programming skill is all about communication and code.
Skill Level: Competent - The toolchain for programming is a bit more complex and will examples may not be explicitly provided for you. You will be required to have a fundamental knowledge of programming and be required to provide your own code. You may need to modify existing libraries or code to work with your specific hardware. Sensor and hardware interfaces will be SPI or I2C.
See all skill levels
If it requires power, you need to know how much, what all the pins do, and how to hook it up. You may need to reference datasheets, schematics, and know the ins and outs of electronics.
Skill Level: Rookie - You may be required to know a bit more about the component, such as orientation, or how to hook it up, in addition to power requirements. You will need to understand polarized components.
See all skill levels
Based on 4 ratings:
1 of 1 found this helpful:
This tiny (tinier than expected) and bright display added an inexpensive way for my ATmega32u4 project to provide visual feedback to the end user. It also helped by eliminating the need for using a PC and Serial Monitor during troubleshooting. Because of the small size of the display, I found that setting the display to show two lines of 2x size text works better than three lines of 1x size text.
What I did not like was having to download additional libraries in order to use it with the Arduino IDE. Hopefully future releases of Arduino IDE will allow automatic library download/install. For example, when I add #include <Adafruit_SSD1306.h> to my code to allow communication with this display, future version of Arduino IDE can automatically download the necessary libraries instead of providing me with error message.
The small and slim design of this display makes this display my first choice for a quick drop-in debug, monitoring or sensor data screen especially for projects where I don't need a big display or want it only on the Qwiic bus while getting the rest of the project to work. Really compact and efficient design. Good job here! Even thinking about using it for a new wearable project.
Great display overall; works as well as other Zio products, and the shape was also more convenient for attaching to different wearables and other objects. The red color pcb is a fun change
I think I'm "competent" in programming with Arduino IDE, in so far as I have a handful of other things I've installed libraries for off of the github. A few different temp/hu sensors, clocks, servos, etc. The IDE these days is pretty easy, aside from having to remove that annoying little - in the folder name beforehand. All those libraries install, and the examples just compile and work. When I #include them into my own code, they just work like the examples.
I have no idea why these libraries don't like playing on my computer (Linux) but I chased error messages for maybe an hour before giving up. Can't find the I2C header..Can't find the SPI header..after chasing those around, variables came up out of scope, even though they were global in the header...
Aside from that, the documentation is Alice's Wonderland of links. Maybe I'm spoiled with products that have all the libraries, schematics, eagle files, and everything else that could possibly be needed all under the Documents tab of the product listing? Finding yet another library that is supposed to support the other two on a page 3 links away from the product page was the last straw for me, especially since it was the 3rd library that didn't play well in my sketchbook. Does it really have to take three imported libraries, anyway?
I believe either the libraries need improvement or the coding skills need to be upgraded. I'm glad I anticipated this problem and bought the LCD with backpack, extra 10 bucks for a product that just works so I can get on with it.