<\/span>What You\u2019ll Need to Know<\/span><\/h3>\n\n\n\nTo get the most out of this Lab, you should be familiar with the basics of programming an Arduino microcontroller. If you\u2019re not, review the Digital Input and Output Lab<\/a>, and perhaps the Getting Started with Arduino guide<\/a>. You should also understand asynchronous serial communication<\/a> and how it differs from synchronous serial communication<\/a>. <\/p>\n\n\n\n<\/span>Things You\u2019ll Need<\/span><\/h3>\n\n\n\nFigures 1-6 list the components you will need.<\/p>\n\n\n\n
![\"Photo](\"https:\/\/itp.nyu.edu\/physcomp\/wp-content\/uploads\/pcomp-kit-f2019-arduino-nano-33-iot-150x150.jpg\")
Figure 1. An Arduino Nano 33 IoT.<\/figcaption><\/figure><\/div>\n\n\n\n![\"Three](\"https:\/\/itp.nyu.edu\/physcomp\/wp-content\/uploads\/hookup_wire2-150x150.jpg\")
<\/a>Figure 2. 22AWG solid core hookup wires.<\/figcaption><\/figure><\/div>\n\n\n\n![\"A](\"https:\/\/itp.nyu.edu\/physcomp\/wp-content\/uploads\/breadboard_short-e1532116106284-150x150.jpg\")
<\/a>Figure 3. A short solderless breadboard.<\/figcaption><\/figure><\/div>\n\n\n\n![\"Photo](\"https:\/\/itp.nyu.edu\/physcomp\/wp-content\/uploads\/SSD1306_OLED-150x150.jpg\")
Figure 4. SSD1306 OLED display<\/figcaption><\/figure><\/div>\n\n\n\n![\"Photo](\"https:\/\/itp.nyu.edu\/physcomp\/wp-content\/uploads\/pcomp-kit-f2019-potentiometer-150x150.jpg\")
Figure 5. Potentiometer<\/figcaption><\/figure><\/div>\n\n\n\n
\n\n\n\n<\/span>The Circuit<\/span><\/h2>\n\n\n\nThe circuit for this lab consists of:<\/p>\n\n\n\n
- the microcontroller<\/li>
- a potentiometer. You can use any analog sensor you choose, however.<\/li>
- an SSD1306 OLED breakout board<\/li><\/ul>\n\n\n\n
There are many breakout boards that use the SSD1306 OLED: Adafruit<\/a>, Sparkfun <\/a>, DFRobot<\/a>, Crystalfontz<\/a>, MakerFocus<\/a>, Amazon<\/a>, and many others. It typically comes in a 128×32 pixel version and a 128×64 pixel version. Solomon Systech makes other variations on this display as well, like the SSD1309 or the 1315. They come with different resolutions, different physical sizes, and different features. <\/p>\n\n\n\nMost of the SSD1206 displays have all blue pixels, but there are some models on the market have one section of yellow pixels and the rest blue. You can\u2019t change the color of the pixels, so be aware of what you are buying and choose what you need. If you need a board with all blue pixels, don’t get the one with the yellow section.<\/p>\n\n\n\n
Connect the display’s voltage and ground pins to your voltage and ground buses, and the I2C clock (SCL) and I2C serial data (SDA) pins to your microcontroller\u2019s corresponding I2C pins as shown in Figure 6-7. The schematic, Figure 6, is the same for both the Uno and the Nano. For the Arduino Uno or the Arduino Nano boards, the I2C pins are pins A4 (SDA) and A5(SCL). This is the same connection for almost any I2C device.<\/p>\n\n\n\n
Connect the potentiometer’s two outside connections to power and ground, respectively. Connect the middle pin (the wiper) to the Arduino’s pin A0. You’ll use the potentiometer to generate something to display on the screen. <\/p>\n\n\n\n
Once you’ve got the circuit wired as shown in Figures 6-7, you’re ready to program the microcontroller.<\/p>\n\n\n\n![\"](\"https:\/\/itp.nyu.edu\/physcomp\/wp-content\/uploads\/Nano_SSD1306_OLED_bb.png\")
Figure 6. Breadboard view of a potentiometer and an SSD1306 OLED screen attached to a Nano 33 IoT. The potentiometer is connected to pin A0. The screen’s SDA pin is connected to pin A4 and the SCL pin is connected to pin A5.<\/figcaption><\/figure>\n\n\n\n![\"Schematic](\"https:\/\/itp.nyu.edu\/physcomp\/wp-content\/uploads\/Nano_SSD1306_OLED_schem.png\")
Figure 7. Schematic drawing of a potentiometer and an SSD1306 OLED screen attached to a Nano 33 IoT. The schematic is the same for an Uno. The potentiometer is connected to pin A0. The screen’s SDA pin is connected to pin A4 and the SCL pin is connected to pin A5.<\/figcaption><\/figure><\/div>\n\n\n\n<\/span>Program the Microcontroller<\/span><\/h2>\n\n\n\nThere are many libraries available for controlling the SSD1306 OLED screens. Adafruit\u2019s SSD1306 library<\/a> works well with all the SSD1306 displays, both the 128×64 and 128×32 models. Adafruit’s library is consistent with many of their other display libraries, and they make a lot of them. So it’s a good place to start. It doesn’t work with other SSD13xx models though. For example, Sparkfun makes a Micro OLED with the SSD1309, which has a 64×48 resolution. It requires a different library. <\/p>\n\n\n\nThe u8g2 library<\/a> by Oli Kraus, is intended as a universal monochrome display library for OLED, eInk, TFT, and other displays. It supports some SSD130x boards, but not all. It’s a pretty good library, but lacks some of the features of the Adafruit library. The examples included here use the Adafruit library. You’ll also need the Adafruit_GFX library which supports graphics across a number of small displays. <\/p>\n\n\n\n<\/span>Import the Libraries<\/span><\/h3>\n\n\n\nAt the start of your sketch, import the libraries and set up a variable to hold the display driver instance like so:<\/p>\n\n\n
\n#include <Wire.h>\n#include <Adafruit_SSD1306.h>\n#include <Adafruit_GFX.h>\n\nconst int SCREEN_WIDTH = 128; \/\/ OLED display width, in pixels\nconst int SCREEN_HEIGHT = 64; \/\/ OLED display height, in pixels\n\n\/\/ initialize the display:\nAdafruit_SSD1306 display(SCREEN_WIDTH, SCREEN_HEIGHT);\n<\/pre><\/div>\n\n\n<\/span>Initialize the Display<\/span><\/h3>\n\n\n\nIn the setup, you need to check that the display is working. If it fails, it’s a good idea to stop and notify the user. Since there’s no user interface in this basic sketch, you’ll use the Serial Monitor. <\/p>\n\n\n
\nvoid setup() {\n \/\/ initialize serial and wait for serial monitor to open:\n Serial.begin(9600);\n if (!Serial) delay(3000);\n \/\/ first parameter of begin() sets voltage source.\n \/\/ SSD1306_SWITCHCAPVCC is for 3.3V\n \/\/ second parameter is I2C address, which is\n \/\/ 0x3C, or 3D for some 128x64 modules:\n if (!display.begin(SSD1306_SWITCHCAPVCC, 0x3C)) {\n Serial.println("Display setup failed");\n while (true);\n }\n Serial.println("Display is good to go");\n}\n<\/pre><\/div>\n\n\n<\/span>Print to the Display<\/span><\/h3>\n\n\n\nYou can print to the display by giving it a text size and cursor position and then using .print()<\/code> or .println()<\/code>. The loop below reads analog input 0, then prints the time in seconds on the first line and the sensor reading on the second. <\/p>\n\n\n\nThe function which actually updates the display is called .display()<\/code>. All of the other functions update a buffer in the microcontroller’s memory. So you can make all the changes you want with commands like .print()<\/code>, .setCursor()<\/code>, .clearDisplay()<\/code>, and so forth, but you will only see the changes when you call .display()<\/code>. This is typical of many display libraries. <\/p>\n\n\n\nIn the code below, you’ll clear the display, then set the size to twice the default, then move the cursor to the top left. Then you print the seconds since the sketch started, move the cursor down a line, and print the analog 0 sensor reading. Finally, you push it all to the display using .display()<\/code>:<\/p>\n\n\n\nvoid loop() {\n int sensorReading = analogRead(A0);\n \/\/ clear the display:\n display.clearDisplay();\n \/\/ set the text size to 2:\n display.setTextSize(2);\n \/\/ set the text color to white:\n display.setTextColor(SSD1306_WHITE);\n\n \/\/ move the cursor to 0,0:\n display.setCursor(0, 0);\n \/\/ print the seconds:\n display.print("secs:");\n display.print(millis() \/ 1000);\n\n \/\/ move the cursor down 20 pixels:\n display.setCursor(0, 20);\n \/\/ print a sensor reading:\n display.print("sensor:");\n display.print(sensorReading);\n \/\/ push everything out to the screen:\n display.display();\n}\n<\/pre><\/div>\n\n\nHere’s a link to the full sketch<\/a>. <\/p>\n\n\n\nThe SSD1306 is a monochrome display, but you still have to set the color to see anything display, because the library defaults to no colors. For a list of what SSD1306_WHITE<\/code> and the other constants in the library mean, see this link<\/a>. <\/p>\n\n\n\n<\/span>Fonts<\/span><\/h2>\n\n\n\nThe default font of the library is not terribly attractive, and gets blocky when you increase the size. But you can add fonts. The Adafruit_GFX library includes many fonts compatible with lots of their display libraries. Search for this library in the library manager and include it to use the fonts. They have a good tutorial on using fonts<\/a> as well. The short version is as follows. First, include the font you want to use with your library includes like so:<\/p>\n\n\n\n#include<Fonts\/FreeSans9pt7b.h>\n<\/pre><\/div>\n\n\nNext, in your setup()<\/code> or whenever you want to switch fonts, use the .setFont()<\/code> function like so:<\/p>\n\n\n\n display.setFont(&FreeSans9pt7b);\n<\/pre><\/div>\n\n\nThe text will now appear using your chosen font. Here’s a link to an example using one of the Adafruit_GFX fonts<\/a>. <\/p>\n\n\n\nOne of the nice things about using custom fonts is if you pick the right size for your screen, you don’t need to use .setTextSize()<\/code>, so you can avoid pixelating your font. Note that custom fonts generally measure pixel height from the baseline. So, to position a 16-point font at the top of the screen, for example, position it with a few pixels at the top to spare: at (0, 20), not (0,0). <\/p>\n\n\n\nYou can also use more custom fonts by generating them from this OLED display custom font generator<\/a>. For “Library Version” choose “Adafruit GFX Font”. This will generate a custom header file that you include with your sketch. Make a new tab in the IDE, give the tab a name like font.h<\/code>, and include it at the top of your code with the other library header files. The font name will be at the bottom of the header file. For example, if you generated the Dialog Font, Plain, 16 point, the font name would be Dialog_plain_16<\/code> and you’d include it just like the one above, like so:<\/p>\n\n\n\n display.setFont(&Dialog_plain_16);\n<\/pre><\/div>\n\n\nThe text will now appear using your custom font. Here’s a link to an example using a custom-generated font<\/a>. <\/p>\n\n\n\n<\/span>Graphics<\/span><\/h2>\n\n\n\nThere are many libraries for graphics on small displays. Typically these displays don’t have a fast refresh rate, so you can’t exactly create fast action games on them, but they can be good for simple graphic informational displays. Different display libraries will have slightingly different naming schemes for their graphics, but you can usually count on being able to draw points, lines, rectangles, circles, and sometimes rounded rects and triangles. You can generally also count on functions like drawRect()<\/code> vs. fillRect()<\/code> depending on whether you want a filled rectangle or not. All libraries will include methods for setting a color, clearing a screen, and filling the screen with a color. Most will also include commands for rotating the graphics display. Here’s the Adafruit_GFX library graphics primitives<\/a> tutorial as an example.<\/p>\n\n\n\nRemember, all of your commands are only executed when you call .display()<\/code>. <\/p>\n\n\n\nHere’s a link to a graphic example that graphs the sensor reading<\/a>. If you haven’t already included the Adafruit_GFX library, you will need to for this.<\/p>\n\n\n\n<\/span>Displaying QR Codes<\/span><\/h2>\n\n\n\nOne way you can use the graphic capabilities of any small display is to show QR codes. QR codes can contain any string of text you want in a machine-readable form. Though we’re used to generating QR codes to supply web addresses (URLs), you can also send plain text strings, phone numbers, passcodes or other test-based information as well. On microcontroller-based devices, they can be a way to transfer identifying information like IP or MAC addresses, Bluetooth LE service UUIDs, or anything else your mobile phone or tablet might need to know about your microcontroller device in order to communicate with it.<\/p>\n\n\n\n
QR codes can be generated from a text string and translated to a microcontroller display using Richard Moore\u2019s qrcode library for Arduino<\/a> and the graphics library for your particular display.<\/p>\n\n\n\nLike any library, you need to include the qrcode library at the top of your code like so:<\/p>\n\n\n
\n#include <qrcode.h>\n<\/pre><\/div>\n\n\n<\/span>Determining QR Code Block Size<\/span><\/h3>\n\n\n\nA QR code’s block size<\/strong> is the height and width of each of the blocks in the code. It depends size depends on the number of blocks per side. The length of the string you plan to display and a few other factors affect the block size. Here’s a table<\/a> which lays out how the string length, error correction, and QR code version affect the the pixel dimensions of a QR code. Here’s a simpler version<\/a> in the documentation for the qrcode library. A long string or higher levels of error correction can result in largee QR codes than you can fit on a small display. The library’s .size()<\/code> function can give you the number of blocks in your QR code. <\/p>\n\n\n\nQR Codes need a “quiet zone” around the block in order to be readable to another device, so you can’t fill your display’s entire length or width with a QR code. <\/p>\n\n\n\n
Here’s a good rule of thumb to get a block size that you can fit on your display:<\/p>\n\n\n\n
- Set the QR version and the QR error level<\/li>
- Start with an arbitrary offset. The larger your offset, the smaller the QR code can be.<\/li>
- Subtract twice the offset width (also arbitrary) from the display’s smallest dimension (64px, in the case of the SSD1306)<\/li>
- divide by the qrcode.size<\/li><\/ul>\n\n\n\n
Here’s a function to generate a QR code. It will take a String object, the QR code version you want to use, and the QR code error level you want, then it will generate a QRCode object, and display it on the display using the display library’s .fillRect()<\/code> function:<\/p>\n\n\n\nvoid displayQrCode(String message) {\n \/\/ Create the QR code\n QRCode qrcode;\n int qrVersion = 3;\n int qrErrorLevel = ECC_MEDIUM;\n int offset = 2;\n int backgroundColor = SSD1306_BLACK;\n int foregroundColor = SSD1306_WHITE;\n\n \/\/ allocate QR code memory:\n byte qrcodeBytes[qrcode_getBufferSize(qrVersion)];\n \/\/ initialize the QR code text:\n qrcode_initText(&qrcode, qrcodeBytes, qrVersion, qrErrorLevel, message.c_str());\n \/\/ calculate the QR code block size:\n int blockSize = (display.height() - (offset * 2)) \/ qrcode.size;\n \/\/ fill the screen with the background color:\n display.fillScreen(backgroundColor);\n\n \/\/ read the bytes of the QR code and set the blocks light or dark, accordingly:\n \/\/ vertical loop:\n for (byte y = 0; y < qrcode.size; y++) {\n \/\/ horizontal loop:\n for (byte x = 0; x < qrcode.size; x++) {\n \/\/ calculate the block's X and Y positions:\n int blockX = (x * blockSize) + offset;\n int blockY = (y * blockSize) + offset;\n \/\/ read the block value from the QRcode:\n int blockValue = qrcode_getModule(&qrcode, x, y);\n \/\/ set the default block color:\n int blockColor = backgroundColor;\n \/\/ if the block value is 1, set color to foreground color instead:\n if (blockValue == 1) {\n blockColor = foregroundColor;\n }\n \/\/ display the block on the screen:\n display.fillRect(blockX, blockY, blockSize, blockSize, blockColor);\n }\n }\n \/\/ refresh the display here, after the nested loops:\n display.display();\n \/\/ print the message:\n Serial.println(message);\n}\n<\/pre><\/div>\n\n\nHere’s a link to a full sketch to generate QR codes<\/a> on an SSD1306 display. Upload it to your Nano, then open the serial monitor and enter a string to display. Then scan the QR Code with your phone’s QR scanning app. You should be able to read short strings of text, up to 50 or so characters. You can also send URLs, phone numbers, or anything else your phone’s QR code reader can interpret. <\/p>\n\n\n\nThe shorter the string, the easier it is for your QR code scanner to read it. This is why many URLs you see on QR codes in public use URL shorteners.<\/p>\n\n\n\n
<\/span>Conclusion<\/span><\/h2>\n\n\n\nEven though the SSD1306 is a small, low resolution monochrome display, it packs a lot of potential for the price. Adding an informational display can improve many devices, and by adding a QR code, you have the possibility to add many more features through the web, Bluetooth, and more. For more on microcntroller displays, see this repository<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"Many common electronic devices feature small screens for status updates, control feedback, and so forth. These displays feature many different technologies. Lately, one of the most common is the OLED display. These displays are matrices of organic LEDs, each pixel being comprised of one to three LEDS. Small displays typically use either the SPI or … Continue reading “Lab: OLED Screen Display using I2C”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":313,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"categories":[41,15,54],"tags":[64,67,65,66],"class_list":["post-9358","page","type-page","status-publish","hentry","category-i2c","category-lab","category-microcontrollers","tag-display","tag-graphics","tag-oled","tag-ssd1306"],"_links":{"self":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358"}],"collection":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/comments?post=9358"}],"version-history":[{"count":27,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358\/revisions"}],"predecessor-version":[{"id":10749,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358\/revisions\/10749"}],"wp:attachment":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/media?parent=9358"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/categories?post=9358"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/tags?post=9358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/span>Things You\u2019ll Need<\/span><\/h3>\n\n\n\nFigures 1-6 list the components you will need.<\/p>\n\n\n\n
Figure 1. An Arduino Nano 33 IoT.<\/figcaption><\/figure><\/div>\n\n\n\n<\/a>Figure 2. 22AWG solid core hookup wires.<\/figcaption><\/figure><\/div>\n\n\n\n<\/a>Figure 3. A short solderless breadboard.<\/figcaption><\/figure><\/div>\n\n\n\nFigure 4. SSD1306 OLED display<\/figcaption><\/figure><\/div>\n\n\n\nFigure 5. Potentiometer<\/figcaption><\/figure><\/div>\n\n\n\n
\n\n\n\n<\/span>The Circuit<\/span><\/h2>\n\n\n\nThe circuit for this lab consists of:<\/p>\n\n\n\n
- the microcontroller<\/li>
- a potentiometer. You can use any analog sensor you choose, however.<\/li>
- an SSD1306 OLED breakout board<\/li><\/ul>\n\n\n\n
There are many breakout boards that use the SSD1306 OLED: Adafruit<\/a>, Sparkfun <\/a>, DFRobot<\/a>, Crystalfontz<\/a>, MakerFocus<\/a>, Amazon<\/a>, and many others. It typically comes in a 128×32 pixel version and a 128×64 pixel version. Solomon Systech makes other variations on this display as well, like the SSD1309 or the 1315. They come with different resolutions, different physical sizes, and different features. <\/p>\n\n\n\nMost of the SSD1206 displays have all blue pixels, but there are some models on the market have one section of yellow pixels and the rest blue. You can\u2019t change the color of the pixels, so be aware of what you are buying and choose what you need. If you need a board with all blue pixels, don’t get the one with the yellow section.<\/p>\n\n\n\n
Connect the display’s voltage and ground pins to your voltage and ground buses, and the I2C clock (SCL) and I2C serial data (SDA) pins to your microcontroller\u2019s corresponding I2C pins as shown in Figure 6-7. The schematic, Figure 6, is the same for both the Uno and the Nano. For the Arduino Uno or the Arduino Nano boards, the I2C pins are pins A4 (SDA) and A5(SCL). This is the same connection for almost any I2C device.<\/p>\n\n\n\n
Connect the potentiometer’s two outside connections to power and ground, respectively. Connect the middle pin (the wiper) to the Arduino’s pin A0. You’ll use the potentiometer to generate something to display on the screen. <\/p>\n\n\n\n
Once you’ve got the circuit wired as shown in Figures 6-7, you’re ready to program the microcontroller.<\/p>\n\n\n\nFigure 6. Breadboard view of a potentiometer and an SSD1306 OLED screen attached to a Nano 33 IoT. The potentiometer is connected to pin A0. The screen’s SDA pin is connected to pin A4 and the SCL pin is connected to pin A5.<\/figcaption><\/figure>\n\n\n\nFigure 7. Schematic drawing of a potentiometer and an SSD1306 OLED screen attached to a Nano 33 IoT. The schematic is the same for an Uno. The potentiometer is connected to pin A0. The screen’s SDA pin is connected to pin A4 and the SCL pin is connected to pin A5.<\/figcaption><\/figure><\/div>\n\n\n\n<\/span>Program the Microcontroller<\/span><\/h2>\n\n\n\nThere are many libraries available for controlling the SSD1306 OLED screens. Adafruit\u2019s SSD1306 library<\/a> works well with all the SSD1306 displays, both the 128×64 and 128×32 models. Adafruit’s library is consistent with many of their other display libraries, and they make a lot of them. So it’s a good place to start. It doesn’t work with other SSD13xx models though. For example, Sparkfun makes a Micro OLED with the SSD1309, which has a 64×48 resolution. It requires a different library. <\/p>\n\n\n\nThe u8g2 library<\/a> by Oli Kraus, is intended as a universal monochrome display library for OLED, eInk, TFT, and other displays. It supports some SSD130x boards, but not all. It’s a pretty good library, but lacks some of the features of the Adafruit library. The examples included here use the Adafruit library. You’ll also need the Adafruit_GFX library which supports graphics across a number of small displays. <\/p>\n\n\n\n<\/span>Import the Libraries<\/span><\/h3>\n\n\n\nAt the start of your sketch, import the libraries and set up a variable to hold the display driver instance like so:<\/p>\n\n\n
\n#include <Wire.h>\n#include <Adafruit_SSD1306.h>\n#include <Adafruit_GFX.h>\n\nconst int SCREEN_WIDTH = 128; \/\/ OLED display width, in pixels\nconst int SCREEN_HEIGHT = 64; \/\/ OLED display height, in pixels\n\n\/\/ initialize the display:\nAdafruit_SSD1306 display(SCREEN_WIDTH, SCREEN_HEIGHT);\n<\/pre><\/div>\n\n\n<\/span>Initialize the Display<\/span><\/h3>\n\n\n\nIn the setup, you need to check that the display is working. If it fails, it’s a good idea to stop and notify the user. Since there’s no user interface in this basic sketch, you’ll use the Serial Monitor. <\/p>\n\n\n
\nvoid setup() {\n \/\/ initialize serial and wait for serial monitor to open:\n Serial.begin(9600);\n if (!Serial) delay(3000);\n \/\/ first parameter of begin() sets voltage source.\n \/\/ SSD1306_SWITCHCAPVCC is for 3.3V\n \/\/ second parameter is I2C address, which is\n \/\/ 0x3C, or 3D for some 128x64 modules:\n if (!display.begin(SSD1306_SWITCHCAPVCC, 0x3C)) {\n Serial.println("Display setup failed");\n while (true);\n }\n Serial.println("Display is good to go");\n}\n<\/pre><\/div>\n\n\n<\/span>Print to the Display<\/span><\/h3>\n\n\n\nYou can print to the display by giving it a text size and cursor position and then using .print()<\/code> or .println()<\/code>. The loop below reads analog input 0, then prints the time in seconds on the first line and the sensor reading on the second. <\/p>\n\n\n\nThe function which actually updates the display is called .display()<\/code>. All of the other functions update a buffer in the microcontroller’s memory. So you can make all the changes you want with commands like .print()<\/code>, .setCursor()<\/code>, .clearDisplay()<\/code>, and so forth, but you will only see the changes when you call .display()<\/code>. This is typical of many display libraries. <\/p>\n\n\n\nIn the code below, you’ll clear the display, then set the size to twice the default, then move the cursor to the top left. Then you print the seconds since the sketch started, move the cursor down a line, and print the analog 0 sensor reading. Finally, you push it all to the display using .display()<\/code>:<\/p>\n\n\n\nvoid loop() {\n int sensorReading = analogRead(A0);\n \/\/ clear the display:\n display.clearDisplay();\n \/\/ set the text size to 2:\n display.setTextSize(2);\n \/\/ set the text color to white:\n display.setTextColor(SSD1306_WHITE);\n\n \/\/ move the cursor to 0,0:\n display.setCursor(0, 0);\n \/\/ print the seconds:\n display.print("secs:");\n display.print(millis() \/ 1000);\n\n \/\/ move the cursor down 20 pixels:\n display.setCursor(0, 20);\n \/\/ print a sensor reading:\n display.print("sensor:");\n display.print(sensorReading);\n \/\/ push everything out to the screen:\n display.display();\n}\n<\/pre><\/div>\n\n\nHere’s a link to the full sketch<\/a>. <\/p>\n\n\n\nThe SSD1306 is a monochrome display, but you still have to set the color to see anything display, because the library defaults to no colors. For a list of what SSD1306_WHITE<\/code> and the other constants in the library mean, see this link<\/a>. <\/p>\n\n\n\n<\/span>Fonts<\/span><\/h2>\n\n\n\nThe default font of the library is not terribly attractive, and gets blocky when you increase the size. But you can add fonts. The Adafruit_GFX library includes many fonts compatible with lots of their display libraries. Search for this library in the library manager and include it to use the fonts. They have a good tutorial on using fonts<\/a> as well. The short version is as follows. First, include the font you want to use with your library includes like so:<\/p>\n\n\n\n#include<Fonts\/FreeSans9pt7b.h>\n<\/pre><\/div>\n\n\nNext, in your setup()<\/code> or whenever you want to switch fonts, use the .setFont()<\/code> function like so:<\/p>\n\n\n\n display.setFont(&FreeSans9pt7b);\n<\/pre><\/div>\n\n\nThe text will now appear using your chosen font. Here’s a link to an example using one of the Adafruit_GFX fonts<\/a>. <\/p>\n\n\n\nOne of the nice things about using custom fonts is if you pick the right size for your screen, you don’t need to use .setTextSize()<\/code>, so you can avoid pixelating your font. Note that custom fonts generally measure pixel height from the baseline. So, to position a 16-point font at the top of the screen, for example, position it with a few pixels at the top to spare: at (0, 20), not (0,0). <\/p>\n\n\n\nYou can also use more custom fonts by generating them from this OLED display custom font generator<\/a>. For “Library Version” choose “Adafruit GFX Font”. This will generate a custom header file that you include with your sketch. Make a new tab in the IDE, give the tab a name like font.h<\/code>, and include it at the top of your code with the other library header files. The font name will be at the bottom of the header file. For example, if you generated the Dialog Font, Plain, 16 point, the font name would be Dialog_plain_16<\/code> and you’d include it just like the one above, like so:<\/p>\n\n\n\n display.setFont(&Dialog_plain_16);\n<\/pre><\/div>\n\n\nThe text will now appear using your custom font. Here’s a link to an example using a custom-generated font<\/a>. <\/p>\n\n\n\n<\/span>Graphics<\/span><\/h2>\n\n\n\nThere are many libraries for graphics on small displays. Typically these displays don’t have a fast refresh rate, so you can’t exactly create fast action games on them, but they can be good for simple graphic informational displays. Different display libraries will have slightingly different naming schemes for their graphics, but you can usually count on being able to draw points, lines, rectangles, circles, and sometimes rounded rects and triangles. You can generally also count on functions like drawRect()<\/code> vs. fillRect()<\/code> depending on whether you want a filled rectangle or not. All libraries will include methods for setting a color, clearing a screen, and filling the screen with a color. Most will also include commands for rotating the graphics display. Here’s the Adafruit_GFX library graphics primitives<\/a> tutorial as an example.<\/p>\n\n\n\nRemember, all of your commands are only executed when you call .display()<\/code>. <\/p>\n\n\n\nHere’s a link to a graphic example that graphs the sensor reading<\/a>. If you haven’t already included the Adafruit_GFX library, you will need to for this.<\/p>\n\n\n\n<\/span>Displaying QR Codes<\/span><\/h2>\n\n\n\nOne way you can use the graphic capabilities of any small display is to show QR codes. QR codes can contain any string of text you want in a machine-readable form. Though we’re used to generating QR codes to supply web addresses (URLs), you can also send plain text strings, phone numbers, passcodes or other test-based information as well. On microcontroller-based devices, they can be a way to transfer identifying information like IP or MAC addresses, Bluetooth LE service UUIDs, or anything else your mobile phone or tablet might need to know about your microcontroller device in order to communicate with it.<\/p>\n\n\n\n
QR codes can be generated from a text string and translated to a microcontroller display using Richard Moore\u2019s qrcode library for Arduino<\/a> and the graphics library for your particular display.<\/p>\n\n\n\nLike any library, you need to include the qrcode library at the top of your code like so:<\/p>\n\n\n
\n#include <qrcode.h>\n<\/pre><\/div>\n\n\n<\/span>Determining QR Code Block Size<\/span><\/h3>\n\n\n\nA QR code’s block size<\/strong> is the height and width of each of the blocks in the code. It depends size depends on the number of blocks per side. The length of the string you plan to display and a few other factors affect the block size. Here’s a table<\/a> which lays out how the string length, error correction, and QR code version affect the the pixel dimensions of a QR code. Here’s a simpler version<\/a> in the documentation for the qrcode library. A long string or higher levels of error correction can result in largee QR codes than you can fit on a small display. The library’s .size()<\/code> function can give you the number of blocks in your QR code. <\/p>\n\n\n\nQR Codes need a “quiet zone” around the block in order to be readable to another device, so you can’t fill your display’s entire length or width with a QR code. <\/p>\n\n\n\n
Here’s a good rule of thumb to get a block size that you can fit on your display:<\/p>\n\n\n\n
- Set the QR version and the QR error level<\/li>
- Start with an arbitrary offset. The larger your offset, the smaller the QR code can be.<\/li>
- Subtract twice the offset width (also arbitrary) from the display’s smallest dimension (64px, in the case of the SSD1306)<\/li>
- divide by the qrcode.size<\/li><\/ul>\n\n\n\n
Here’s a function to generate a QR code. It will take a String object, the QR code version you want to use, and the QR code error level you want, then it will generate a QRCode object, and display it on the display using the display library’s .fillRect()<\/code> function:<\/p>\n\n\n\nvoid displayQrCode(String message) {\n \/\/ Create the QR code\n QRCode qrcode;\n int qrVersion = 3;\n int qrErrorLevel = ECC_MEDIUM;\n int offset = 2;\n int backgroundColor = SSD1306_BLACK;\n int foregroundColor = SSD1306_WHITE;\n\n \/\/ allocate QR code memory:\n byte qrcodeBytes[qrcode_getBufferSize(qrVersion)];\n \/\/ initialize the QR code text:\n qrcode_initText(&qrcode, qrcodeBytes, qrVersion, qrErrorLevel, message.c_str());\n \/\/ calculate the QR code block size:\n int blockSize = (display.height() - (offset * 2)) \/ qrcode.size;\n \/\/ fill the screen with the background color:\n display.fillScreen(backgroundColor);\n\n \/\/ read the bytes of the QR code and set the blocks light or dark, accordingly:\n \/\/ vertical loop:\n for (byte y = 0; y < qrcode.size; y++) {\n \/\/ horizontal loop:\n for (byte x = 0; x < qrcode.size; x++) {\n \/\/ calculate the block's X and Y positions:\n int blockX = (x * blockSize) + offset;\n int blockY = (y * blockSize) + offset;\n \/\/ read the block value from the QRcode:\n int blockValue = qrcode_getModule(&qrcode, x, y);\n \/\/ set the default block color:\n int blockColor = backgroundColor;\n \/\/ if the block value is 1, set color to foreground color instead:\n if (blockValue == 1) {\n blockColor = foregroundColor;\n }\n \/\/ display the block on the screen:\n display.fillRect(blockX, blockY, blockSize, blockSize, blockColor);\n }\n }\n \/\/ refresh the display here, after the nested loops:\n display.display();\n \/\/ print the message:\n Serial.println(message);\n}\n<\/pre><\/div>\n\n\nHere’s a link to a full sketch to generate QR codes<\/a> on an SSD1306 display. Upload it to your Nano, then open the serial monitor and enter a string to display. Then scan the QR Code with your phone’s QR scanning app. You should be able to read short strings of text, up to 50 or so characters. You can also send URLs, phone numbers, or anything else your phone’s QR code reader can interpret. <\/p>\n\n\n\nThe shorter the string, the easier it is for your QR code scanner to read it. This is why many URLs you see on QR codes in public use URL shorteners.<\/p>\n\n\n\n
<\/span>Conclusion<\/span><\/h2>\n\n\n\nEven though the SSD1306 is a small, low resolution monochrome display, it packs a lot of potential for the price. Adding an informational display can improve many devices, and by adding a QR code, you have the possibility to add many more features through the web, Bluetooth, and more. For more on microcntroller displays, see this repository<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"Many common electronic devices feature small screens for status updates, control feedback, and so forth. These displays feature many different technologies. Lately, one of the most common is the OLED display. These displays are matrices of organic LEDs, each pixel being comprised of one to three LEDS. Small displays typically use either the SPI or … Continue reading “Lab: OLED Screen Display using I2C”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":313,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"categories":[41,15,54],"tags":[64,67,65,66],"class_list":["post-9358","page","type-page","status-publish","hentry","category-i2c","category-lab","category-microcontrollers","tag-display","tag-graphics","tag-oled","tag-ssd1306"],"_links":{"self":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358"}],"collection":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/comments?post=9358"}],"version-history":[{"count":27,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358\/revisions"}],"predecessor-version":[{"id":10749,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358\/revisions\/10749"}],"wp:attachment":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/media?parent=9358"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/categories?post=9358"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/tags?post=9358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/a><\/a>\n\n\n\n
<\/span>The Circuit<\/span><\/h2>\n\n\n\nThe circuit for this lab consists of:<\/p>\n\n\n\n
- the microcontroller<\/li>
- a potentiometer. You can use any analog sensor you choose, however.<\/li>
- an SSD1306 OLED breakout board<\/li><\/ul>\n\n\n\n
There are many breakout boards that use the SSD1306 OLED: Adafruit<\/a>, Sparkfun <\/a>, DFRobot<\/a>, Crystalfontz<\/a>, MakerFocus<\/a>, Amazon<\/a>, and many others. It typically comes in a 128×32 pixel version and a 128×64 pixel version. Solomon Systech makes other variations on this display as well, like the SSD1309 or the 1315. They come with different resolutions, different physical sizes, and different features. <\/p>\n\n\n\nMost of the SSD1206 displays have all blue pixels, but there are some models on the market have one section of yellow pixels and the rest blue. You can\u2019t change the color of the pixels, so be aware of what you are buying and choose what you need. If you need a board with all blue pixels, don’t get the one with the yellow section.<\/p>\n\n\n\n
Connect the display’s voltage and ground pins to your voltage and ground buses, and the I2C clock (SCL) and I2C serial data (SDA) pins to your microcontroller\u2019s corresponding I2C pins as shown in Figure 6-7. The schematic, Figure 6, is the same for both the Uno and the Nano. For the Arduino Uno or the Arduino Nano boards, the I2C pins are pins A4 (SDA) and A5(SCL). This is the same connection for almost any I2C device.<\/p>\n\n\n\n
Connect the potentiometer’s two outside connections to power and ground, respectively. Connect the middle pin (the wiper) to the Arduino’s pin A0. You’ll use the potentiometer to generate something to display on the screen. <\/p>\n\n\n\n
Once you’ve got the circuit wired as shown in Figures 6-7, you’re ready to program the microcontroller.<\/p>\n\n\n\nFigure 6. Breadboard view of a potentiometer and an SSD1306 OLED screen attached to a Nano 33 IoT. The potentiometer is connected to pin A0. The screen’s SDA pin is connected to pin A4 and the SCL pin is connected to pin A5.<\/figcaption><\/figure>\n\n\n\nFigure 7. Schematic drawing of a potentiometer and an SSD1306 OLED screen attached to a Nano 33 IoT. The schematic is the same for an Uno. The potentiometer is connected to pin A0. The screen’s SDA pin is connected to pin A4 and the SCL pin is connected to pin A5.<\/figcaption><\/figure><\/div>\n\n\n\n<\/span>Program the Microcontroller<\/span><\/h2>\n\n\n\nThere are many libraries available for controlling the SSD1306 OLED screens. Adafruit\u2019s SSD1306 library<\/a> works well with all the SSD1306 displays, both the 128×64 and 128×32 models. Adafruit’s library is consistent with many of their other display libraries, and they make a lot of them. So it’s a good place to start. It doesn’t work with other SSD13xx models though. For example, Sparkfun makes a Micro OLED with the SSD1309, which has a 64×48 resolution. It requires a different library. <\/p>\n\n\n\nThe u8g2 library<\/a> by Oli Kraus, is intended as a universal monochrome display library for OLED, eInk, TFT, and other displays. It supports some SSD130x boards, but not all. It’s a pretty good library, but lacks some of the features of the Adafruit library. The examples included here use the Adafruit library. You’ll also need the Adafruit_GFX library which supports graphics across a number of small displays. <\/p>\n\n\n\n<\/span>Import the Libraries<\/span><\/h3>\n\n\n\nAt the start of your sketch, import the libraries and set up a variable to hold the display driver instance like so:<\/p>\n\n\n
\n#include <Wire.h>\n#include <Adafruit_SSD1306.h>\n#include <Adafruit_GFX.h>\n\nconst int SCREEN_WIDTH = 128; \/\/ OLED display width, in pixels\nconst int SCREEN_HEIGHT = 64; \/\/ OLED display height, in pixels\n\n\/\/ initialize the display:\nAdafruit_SSD1306 display(SCREEN_WIDTH, SCREEN_HEIGHT);\n<\/pre><\/div>\n\n\n<\/span>Initialize the Display<\/span><\/h3>\n\n\n\nIn the setup, you need to check that the display is working. If it fails, it’s a good idea to stop and notify the user. Since there’s no user interface in this basic sketch, you’ll use the Serial Monitor. <\/p>\n\n\n
\nvoid setup() {\n \/\/ initialize serial and wait for serial monitor to open:\n Serial.begin(9600);\n if (!Serial) delay(3000);\n \/\/ first parameter of begin() sets voltage source.\n \/\/ SSD1306_SWITCHCAPVCC is for 3.3V\n \/\/ second parameter is I2C address, which is\n \/\/ 0x3C, or 3D for some 128x64 modules:\n if (!display.begin(SSD1306_SWITCHCAPVCC, 0x3C)) {\n Serial.println("Display setup failed");\n while (true);\n }\n Serial.println("Display is good to go");\n}\n<\/pre><\/div>\n\n\n<\/span>Print to the Display<\/span><\/h3>\n\n\n\nYou can print to the display by giving it a text size and cursor position and then using .print()<\/code> or .println()<\/code>. The loop below reads analog input 0, then prints the time in seconds on the first line and the sensor reading on the second. <\/p>\n\n\n\nThe function which actually updates the display is called .display()<\/code>. All of the other functions update a buffer in the microcontroller’s memory. So you can make all the changes you want with commands like .print()<\/code>, .setCursor()<\/code>, .clearDisplay()<\/code>, and so forth, but you will only see the changes when you call .display()<\/code>. This is typical of many display libraries. <\/p>\n\n\n\nIn the code below, you’ll clear the display, then set the size to twice the default, then move the cursor to the top left. Then you print the seconds since the sketch started, move the cursor down a line, and print the analog 0 sensor reading. Finally, you push it all to the display using .display()<\/code>:<\/p>\n\n\n\nvoid loop() {\n int sensorReading = analogRead(A0);\n \/\/ clear the display:\n display.clearDisplay();\n \/\/ set the text size to 2:\n display.setTextSize(2);\n \/\/ set the text color to white:\n display.setTextColor(SSD1306_WHITE);\n\n \/\/ move the cursor to 0,0:\n display.setCursor(0, 0);\n \/\/ print the seconds:\n display.print("secs:");\n display.print(millis() \/ 1000);\n\n \/\/ move the cursor down 20 pixels:\n display.setCursor(0, 20);\n \/\/ print a sensor reading:\n display.print("sensor:");\n display.print(sensorReading);\n \/\/ push everything out to the screen:\n display.display();\n}\n<\/pre><\/div>\n\n\nHere’s a link to the full sketch<\/a>. <\/p>\n\n\n\nThe SSD1306 is a monochrome display, but you still have to set the color to see anything display, because the library defaults to no colors. For a list of what SSD1306_WHITE<\/code> and the other constants in the library mean, see this link<\/a>. <\/p>\n\n\n\n<\/span>Fonts<\/span><\/h2>\n\n\n\nThe default font of the library is not terribly attractive, and gets blocky when you increase the size. But you can add fonts. The Adafruit_GFX library includes many fonts compatible with lots of their display libraries. Search for this library in the library manager and include it to use the fonts. They have a good tutorial on using fonts<\/a> as well. The short version is as follows. First, include the font you want to use with your library includes like so:<\/p>\n\n\n\n#include<Fonts\/FreeSans9pt7b.h>\n<\/pre><\/div>\n\n\nNext, in your setup()<\/code> or whenever you want to switch fonts, use the .setFont()<\/code> function like so:<\/p>\n\n\n\n display.setFont(&FreeSans9pt7b);\n<\/pre><\/div>\n\n\nThe text will now appear using your chosen font. Here’s a link to an example using one of the Adafruit_GFX fonts<\/a>. <\/p>\n\n\n\nOne of the nice things about using custom fonts is if you pick the right size for your screen, you don’t need to use .setTextSize()<\/code>, so you can avoid pixelating your font. Note that custom fonts generally measure pixel height from the baseline. So, to position a 16-point font at the top of the screen, for example, position it with a few pixels at the top to spare: at (0, 20), not (0,0). <\/p>\n\n\n\nYou can also use more custom fonts by generating them from this OLED display custom font generator<\/a>. For “Library Version” choose “Adafruit GFX Font”. This will generate a custom header file that you include with your sketch. Make a new tab in the IDE, give the tab a name like font.h<\/code>, and include it at the top of your code with the other library header files. The font name will be at the bottom of the header file. For example, if you generated the Dialog Font, Plain, 16 point, the font name would be Dialog_plain_16<\/code> and you’d include it just like the one above, like so:<\/p>\n\n\n\n display.setFont(&Dialog_plain_16);\n<\/pre><\/div>\n\n\nThe text will now appear using your custom font. Here’s a link to an example using a custom-generated font<\/a>. <\/p>\n\n\n\n<\/span>Graphics<\/span><\/h2>\n\n\n\nThere are many libraries for graphics on small displays. Typically these displays don’t have a fast refresh rate, so you can’t exactly create fast action games on them, but they can be good for simple graphic informational displays. Different display libraries will have slightingly different naming schemes for their graphics, but you can usually count on being able to draw points, lines, rectangles, circles, and sometimes rounded rects and triangles. You can generally also count on functions like drawRect()<\/code> vs. fillRect()<\/code> depending on whether you want a filled rectangle or not. All libraries will include methods for setting a color, clearing a screen, and filling the screen with a color. Most will also include commands for rotating the graphics display. Here’s the Adafruit_GFX library graphics primitives<\/a> tutorial as an example.<\/p>\n\n\n\nRemember, all of your commands are only executed when you call .display()<\/code>. <\/p>\n\n\n\nHere’s a link to a graphic example that graphs the sensor reading<\/a>. If you haven’t already included the Adafruit_GFX library, you will need to for this.<\/p>\n\n\n\n<\/span>Displaying QR Codes<\/span><\/h2>\n\n\n\nOne way you can use the graphic capabilities of any small display is to show QR codes. QR codes can contain any string of text you want in a machine-readable form. Though we’re used to generating QR codes to supply web addresses (URLs), you can also send plain text strings, phone numbers, passcodes or other test-based information as well. On microcontroller-based devices, they can be a way to transfer identifying information like IP or MAC addresses, Bluetooth LE service UUIDs, or anything else your mobile phone or tablet might need to know about your microcontroller device in order to communicate with it.<\/p>\n\n\n\n
QR codes can be generated from a text string and translated to a microcontroller display using Richard Moore\u2019s qrcode library for Arduino<\/a> and the graphics library for your particular display.<\/p>\n\n\n\nLike any library, you need to include the qrcode library at the top of your code like so:<\/p>\n\n\n
\n#include <qrcode.h>\n<\/pre><\/div>\n\n\n<\/span>Determining QR Code Block Size<\/span><\/h3>\n\n\n\nA QR code’s block size<\/strong> is the height and width of each of the blocks in the code. It depends size depends on the number of blocks per side. The length of the string you plan to display and a few other factors affect the block size. Here’s a table<\/a> which lays out how the string length, error correction, and QR code version affect the the pixel dimensions of a QR code. Here’s a simpler version<\/a> in the documentation for the qrcode library. A long string or higher levels of error correction can result in largee QR codes than you can fit on a small display. The library’s .size()<\/code> function can give you the number of blocks in your QR code. <\/p>\n\n\n\nQR Codes need a “quiet zone” around the block in order to be readable to another device, so you can’t fill your display’s entire length or width with a QR code. <\/p>\n\n\n\n
Here’s a good rule of thumb to get a block size that you can fit on your display:<\/p>\n\n\n\n
- Set the QR version and the QR error level<\/li>
- Start with an arbitrary offset. The larger your offset, the smaller the QR code can be.<\/li>
- Subtract twice the offset width (also arbitrary) from the display’s smallest dimension (64px, in the case of the SSD1306)<\/li>
- divide by the qrcode.size<\/li><\/ul>\n\n\n\n
Here’s a function to generate a QR code. It will take a String object, the QR code version you want to use, and the QR code error level you want, then it will generate a QRCode object, and display it on the display using the display library’s .fillRect()<\/code> function:<\/p>\n\n\n\nvoid displayQrCode(String message) {\n \/\/ Create the QR code\n QRCode qrcode;\n int qrVersion = 3;\n int qrErrorLevel = ECC_MEDIUM;\n int offset = 2;\n int backgroundColor = SSD1306_BLACK;\n int foregroundColor = SSD1306_WHITE;\n\n \/\/ allocate QR code memory:\n byte qrcodeBytes[qrcode_getBufferSize(qrVersion)];\n \/\/ initialize the QR code text:\n qrcode_initText(&qrcode, qrcodeBytes, qrVersion, qrErrorLevel, message.c_str());\n \/\/ calculate the QR code block size:\n int blockSize = (display.height() - (offset * 2)) \/ qrcode.size;\n \/\/ fill the screen with the background color:\n display.fillScreen(backgroundColor);\n\n \/\/ read the bytes of the QR code and set the blocks light or dark, accordingly:\n \/\/ vertical loop:\n for (byte y = 0; y < qrcode.size; y++) {\n \/\/ horizontal loop:\n for (byte x = 0; x < qrcode.size; x++) {\n \/\/ calculate the block's X and Y positions:\n int blockX = (x * blockSize) + offset;\n int blockY = (y * blockSize) + offset;\n \/\/ read the block value from the QRcode:\n int blockValue = qrcode_getModule(&qrcode, x, y);\n \/\/ set the default block color:\n int blockColor = backgroundColor;\n \/\/ if the block value is 1, set color to foreground color instead:\n if (blockValue == 1) {\n blockColor = foregroundColor;\n }\n \/\/ display the block on the screen:\n display.fillRect(blockX, blockY, blockSize, blockSize, blockColor);\n }\n }\n \/\/ refresh the display here, after the nested loops:\n display.display();\n \/\/ print the message:\n Serial.println(message);\n}\n<\/pre><\/div>\n\n\nHere’s a link to a full sketch to generate QR codes<\/a> on an SSD1306 display. Upload it to your Nano, then open the serial monitor and enter a string to display. Then scan the QR Code with your phone’s QR scanning app. You should be able to read short strings of text, up to 50 or so characters. You can also send URLs, phone numbers, or anything else your phone’s QR code reader can interpret. <\/p>\n\n\n\nThe shorter the string, the easier it is for your QR code scanner to read it. This is why many URLs you see on QR codes in public use URL shorteners.<\/p>\n\n\n\n
<\/span>Conclusion<\/span><\/h2>\n\n\n\nEven though the SSD1306 is a small, low resolution monochrome display, it packs a lot of potential for the price. Adding an informational display can improve many devices, and by adding a QR code, you have the possibility to add many more features through the web, Bluetooth, and more. For more on microcntroller displays, see this repository<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"Many common electronic devices feature small screens for status updates, control feedback, and so forth. These displays feature many different technologies. Lately, one of the most common is the OLED display. These displays are matrices of organic LEDs, each pixel being comprised of one to three LEDS. Small displays typically use either the SPI or … Continue reading “Lab: OLED Screen Display using I2C”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":313,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"categories":[41,15,54],"tags":[64,67,65,66],"class_list":["post-9358","page","type-page","status-publish","hentry","category-i2c","category-lab","category-microcontrollers","tag-display","tag-graphics","tag-oled","tag-ssd1306"],"_links":{"self":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358"}],"collection":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/comments?post=9358"}],"version-history":[{"count":27,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358\/revisions"}],"predecessor-version":[{"id":10749,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358\/revisions\/10749"}],"wp:attachment":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/media?parent=9358"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/categories?post=9358"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/tags?post=9358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
There are many breakout boards that use the SSD1306 OLED: Adafruit<\/a>, Sparkfun <\/a>, DFRobot<\/a>, Crystalfontz<\/a>, MakerFocus<\/a>, Amazon<\/a>, and many others. It typically comes in a 128×32 pixel version and a 128×64 pixel version. Solomon Systech makes other variations on this display as well, like the SSD1309 or the 1315. They come with different resolutions, different physical sizes, and different features. <\/p>\n\n\n\n Most of the SSD1206 displays have all blue pixels, but there are some models on the market have one section of yellow pixels and the rest blue. You can\u2019t change the color of the pixels, so be aware of what you are buying and choose what you need. If you need a board with all blue pixels, don’t get the one with the yellow section.<\/p>\n\n\n\n Connect the display’s voltage and ground pins to your voltage and ground buses, and the I2C clock (SCL) and I2C serial data (SDA) pins to your microcontroller\u2019s corresponding I2C pins as shown in Figure 6-7. The schematic, Figure 6, is the same for both the Uno and the Nano. For the Arduino Uno or the Arduino Nano boards, the I2C pins are pins A4 (SDA) and A5(SCL). This is the same connection for almost any I2C device.<\/p>\n\n\n\n Connect the potentiometer’s two outside connections to power and ground, respectively. Connect the middle pin (the wiper) to the Arduino’s pin A0. You’ll use the potentiometer to generate something to display on the screen. <\/p>\n\n\n\n Once you’ve got the circuit wired as shown in Figures 6-7, you’re ready to program the microcontroller.<\/p>\n\n\n\n There are many libraries available for controlling the SSD1306 OLED screens. Adafruit\u2019s SSD1306 library<\/a> works well with all the SSD1306 displays, both the 128×64 and 128×32 models. Adafruit’s library is consistent with many of their other display libraries, and they make a lot of them. So it’s a good place to start. It doesn’t work with other SSD13xx models though. For example, Sparkfun makes a Micro OLED with the SSD1309, which has a 64×48 resolution. It requires a different library. <\/p>\n\n\n\n The u8g2 library<\/a> by Oli Kraus, is intended as a universal monochrome display library for OLED, eInk, TFT, and other displays. It supports some SSD130x boards, but not all. It’s a pretty good library, but lacks some of the features of the Adafruit library. The examples included here use the Adafruit library. You’ll also need the Adafruit_GFX library which supports graphics across a number of small displays. <\/p>\n\n\n\n At the start of your sketch, import the libraries and set up a variable to hold the display driver instance like so:<\/p>\n\n\n In the setup, you need to check that the display is working. If it fails, it’s a good idea to stop and notify the user. Since there’s no user interface in this basic sketch, you’ll use the Serial Monitor. <\/p>\n\n\n You can print to the display by giving it a text size and cursor position and then using The function which actually updates the display is called In the code below, you’ll clear the display, then set the size to twice the default, then move the cursor to the top left. Then you print the seconds since the sketch started, move the cursor down a line, and print the analog 0 sensor reading. Finally, you push it all to the display using Here’s a link to the full sketch<\/a>. <\/p>\n\n\n\n The SSD1306 is a monochrome display, but you still have to set the color to see anything display, because the library defaults to no colors. For a list of what The default font of the library is not terribly attractive, and gets blocky when you increase the size. But you can add fonts. The Adafruit_GFX library includes many fonts compatible with lots of their display libraries. Search for this library in the library manager and include it to use the fonts. They have a good tutorial on using fonts<\/a> as well. The short version is as follows. First, include the font you want to use with your library includes like so:<\/p>\n\n\n Next, in your The text will now appear using your chosen font. Here’s a link to an example using one of the Adafruit_GFX fonts<\/a>. <\/p>\n\n\n\n One of the nice things about using custom fonts is if you pick the right size for your screen, you don’t need to use You can also use more custom fonts by generating them from this OLED display custom font generator<\/a>. For “Library Version” choose “Adafruit GFX Font”. This will generate a custom header file that you include with your sketch. Make a new tab in the IDE, give the tab a name like The text will now appear using your custom font. Here’s a link to an example using a custom-generated font<\/a>. <\/p>\n\n\n\n There are many libraries for graphics on small displays. Typically these displays don’t have a fast refresh rate, so you can’t exactly create fast action games on them, but they can be good for simple graphic informational displays. Different display libraries will have slightingly different naming schemes for their graphics, but you can usually count on being able to draw points, lines, rectangles, circles, and sometimes rounded rects and triangles. You can generally also count on functions like Remember, all of your commands are only executed when you call Here’s a link to a graphic example that graphs the sensor reading<\/a>. If you haven’t already included the Adafruit_GFX library, you will need to for this.<\/p>\n\n\n\n One way you can use the graphic capabilities of any small display is to show QR codes. QR codes can contain any string of text you want in a machine-readable form. Though we’re used to generating QR codes to supply web addresses (URLs), you can also send plain text strings, phone numbers, passcodes or other test-based information as well. On microcontroller-based devices, they can be a way to transfer identifying information like IP or MAC addresses, Bluetooth LE service UUIDs, or anything else your mobile phone or tablet might need to know about your microcontroller device in order to communicate with it.<\/p>\n\n\n\n QR codes can be generated from a text string and translated to a microcontroller display using Richard Moore\u2019s qrcode library for Arduino<\/a> and the graphics library for your particular display.<\/p>\n\n\n\n Like any library, you need to include the qrcode library at the top of your code like so:<\/p>\n\n\n A QR code’s block size<\/strong> is the height and width of each of the blocks in the code. It depends size depends on the number of blocks per side. The length of the string you plan to display and a few other factors affect the block size. Here’s a table<\/a> which lays out how the string length, error correction, and QR code version affect the the pixel dimensions of a QR code. Here’s a simpler version<\/a> in the documentation for the qrcode library. A long string or higher levels of error correction can result in largee QR codes than you can fit on a small display. The library’s QR Codes need a “quiet zone” around the block in order to be readable to another device, so you can’t fill your display’s entire length or width with a QR code. <\/p>\n\n\n\n Here’s a good rule of thumb to get a block size that you can fit on your display:<\/p>\n\n\n\n Here’s a function to generate a QR code. It will take a String object, the QR code version you want to use, and the QR code error level you want, then it will generate a QRCode object, and display it on the display using the display library’s Here’s a link to a full sketch to generate QR codes<\/a> on an SSD1306 display. Upload it to your Nano, then open the serial monitor and enter a string to display. Then scan the QR Code with your phone’s QR scanning app. You should be able to read short strings of text, up to 50 or so characters. You can also send URLs, phone numbers, or anything else your phone’s QR code reader can interpret. <\/p>\n\n\n\n The shorter the string, the easier it is for your QR code scanner to read it. This is why many URLs you see on QR codes in public use URL shorteners.<\/p>\n\n\n\n Even though the SSD1306 is a small, low resolution monochrome display, it packs a lot of potential for the price. Adding an informational display can improve many devices, and by adding a QR code, you have the possibility to add many more features through the web, Bluetooth, and more. For more on microcntroller displays, see this repository<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Many common electronic devices feature small screens for status updates, control feedback, and so forth. These displays feature many different technologies. Lately, one of the most common is the OLED display. These displays are matrices of organic LEDs, each pixel being comprised of one to three LEDS. Small displays typically use either the SPI or … Continue reading “Lab: OLED Screen Display using I2C”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":313,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"categories":[41,15,54],"tags":[64,67,65,66],"class_list":["post-9358","page","type-page","status-publish","hentry","category-i2c","category-lab","category-microcontrollers","tag-display","tag-graphics","tag-oled","tag-ssd1306"],"_links":{"self":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358"}],"collection":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/comments?post=9358"}],"version-history":[{"count":27,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358\/revisions"}],"predecessor-version":[{"id":10749,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/9358\/revisions\/10749"}],"wp:attachment":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/media?parent=9358"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/categories?post=9358"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/tags?post=9358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/span>Program the Microcontroller<\/span><\/h2>\n\n\n\n
<\/span>Import the Libraries<\/span><\/h3>\n\n\n\n
\n#include <Wire.h>\n#include <Adafruit_SSD1306.h>\n#include <Adafruit_GFX.h>\n\nconst int SCREEN_WIDTH = 128; \/\/ OLED display width, in pixels\nconst int SCREEN_HEIGHT = 64; \/\/ OLED display height, in pixels\n\n\/\/ initialize the display:\nAdafruit_SSD1306 display(SCREEN_WIDTH, SCREEN_HEIGHT);\n<\/pre><\/div>\n\n\n
<\/span>Initialize the Display<\/span><\/h3>\n\n\n\n
\nvoid setup() {\n \/\/ initialize serial and wait for serial monitor to open:\n Serial.begin(9600);\n if (!Serial) delay(3000);\n \/\/ first parameter of begin() sets voltage source.\n \/\/ SSD1306_SWITCHCAPVCC is for 3.3V\n \/\/ second parameter is I2C address, which is\n \/\/ 0x3C, or 3D for some 128x64 modules:\n if (!display.begin(SSD1306_SWITCHCAPVCC, 0x3C)) {\n Serial.println("Display setup failed");\n while (true);\n }\n Serial.println("Display is good to go");\n}\n<\/pre><\/div>\n\n\n<\/span>Print to the Display<\/span><\/h3>\n\n\n\n
.print()<\/code> or .println()<\/code>. The loop below reads analog input 0, then prints the time in seconds on the first line and the sensor reading on the second. <\/p>\n\n\n\n.display()<\/code>. All of the other functions update a buffer in the microcontroller’s memory. So you can make all the changes you want with commands like .print()<\/code>, .setCursor()<\/code>, .clearDisplay()<\/code>, and so forth, but you will only see the changes when you call .display()<\/code>. This is typical of many display libraries. <\/p>\n\n\n\n.display()<\/code>:<\/p>\n\n\n\nvoid loop() {\n int sensorReading = analogRead(A0);\n \/\/ clear the display:\n display.clearDisplay();\n \/\/ set the text size to 2:\n display.setTextSize(2);\n \/\/ set the text color to white:\n display.setTextColor(SSD1306_WHITE);\n\n \/\/ move the cursor to 0,0:\n display.setCursor(0, 0);\n \/\/ print the seconds:\n display.print("secs:");\n display.print(millis() \/ 1000);\n\n \/\/ move the cursor down 20 pixels:\n display.setCursor(0, 20);\n \/\/ print a sensor reading:\n display.print("sensor:");\n display.print(sensorReading);\n \/\/ push everything out to the screen:\n display.display();\n}\n<\/pre><\/div>\n\n\nSSD1306_WHITE<\/code> and the other constants in the library mean, see this link<\/a>. <\/p>\n\n\n\n<\/span>Fonts<\/span><\/h2>\n\n\n\n
\n#include<Fonts\/FreeSans9pt7b.h>\n<\/pre><\/div>\n\n\n
setup()<\/code> or whenever you want to switch fonts, use the .setFont()<\/code> function like so:<\/p>\n\n\n\n display.setFont(&FreeSans9pt7b);\n<\/pre><\/div>\n\n\n
.setTextSize()<\/code>, so you can avoid pixelating your font. Note that custom fonts generally measure pixel height from the baseline. So, to position a 16-point font at the top of the screen, for example, position it with a few pixels at the top to spare: at (0, 20), not (0,0). <\/p>\n\n\n\nfont.h<\/code>, and include it at the top of your code with the other library header files. The font name will be at the bottom of the header file. For example, if you generated the Dialog Font, Plain, 16 point, the font name would be Dialog_plain_16<\/code> and you’d include it just like the one above, like so:<\/p>\n\n\n\n display.setFont(&Dialog_plain_16);\n<\/pre><\/div>\n\n\n
<\/span>Graphics<\/span><\/h2>\n\n\n\n
drawRect()<\/code> vs. fillRect()<\/code> depending on whether you want a filled rectangle or not. All libraries will include methods for setting a color, clearing a screen, and filling the screen with a color. Most will also include commands for rotating the graphics display. Here’s the Adafruit_GFX library graphics primitives<\/a> tutorial as an example.<\/p>\n\n\n\n.display()<\/code>. <\/p>\n\n\n\n<\/span>Displaying QR Codes<\/span><\/h2>\n\n\n\n
\n#include <qrcode.h>\n<\/pre><\/div>\n\n\n
<\/span>Determining QR Code Block Size<\/span><\/h3>\n\n\n\n
.size()<\/code> function can give you the number of blocks in your QR code. <\/p>\n\n\n\n.fillRect()<\/code> function:<\/p>\n\n\n\nvoid displayQrCode(String message) {\n \/\/ Create the QR code\n QRCode qrcode;\n int qrVersion = 3;\n int qrErrorLevel = ECC_MEDIUM;\n int offset = 2;\n int backgroundColor = SSD1306_BLACK;\n int foregroundColor = SSD1306_WHITE;\n\n \/\/ allocate QR code memory:\n byte qrcodeBytes[qrcode_getBufferSize(qrVersion)];\n \/\/ initialize the QR code text:\n qrcode_initText(&qrcode, qrcodeBytes, qrVersion, qrErrorLevel, message.c_str());\n \/\/ calculate the QR code block size:\n int blockSize = (display.height() - (offset * 2)) \/ qrcode.size;\n \/\/ fill the screen with the background color:\n display.fillScreen(backgroundColor);\n\n \/\/ read the bytes of the QR code and set the blocks light or dark, accordingly:\n \/\/ vertical loop:\n for (byte y = 0; y < qrcode.size; y++) {\n \/\/ horizontal loop:\n for (byte x = 0; x < qrcode.size; x++) {\n \/\/ calculate the block's X and Y positions:\n int blockX = (x * blockSize) + offset;\n int blockY = (y * blockSize) + offset;\n \/\/ read the block value from the QRcode:\n int blockValue = qrcode_getModule(&qrcode, x, y);\n \/\/ set the default block color:\n int blockColor = backgroundColor;\n \/\/ if the block value is 1, set color to foreground color instead:\n if (blockValue == 1) {\n blockColor = foregroundColor;\n }\n \/\/ display the block on the screen:\n display.fillRect(blockX, blockY, blockSize, blockSize, blockColor);\n }\n }\n \/\/ refresh the display here, after the nested loops:\n display.display();\n \/\/ print the message:\n Serial.println(message);\n}\n<\/pre><\/div>\n\n\n<\/span>Conclusion<\/span><\/h2>\n\n\n\n