Connect OLED Screens and I²C Sensors
Over 100ft Away!

Use the IO Expander and accessories to connect OLED Screens and I²C Sensors over a 100ft away.

Need to add OLED screens at the sensors location for meaningful reporting that are too far away from your project?

Too many sensors to connect on the I2C bus? Then you need the IO Expander! With the 1-Wire^® to I²C adapter, add as many I²C buses as needed on your 1-Wire^® bus.

Need multiple 1-Wire^® buses? The IO Expander will support up to 16 at the same time.

Need even more? Then link up to 255 IO Expanders together; the IO Expander truly delivers extreme connectivity!

Feature List

• Use Cheap 128x64 OLED Screens.
• Use Multiple OLED Screens on a Single 1-Wire^® Bus.
• Use Different OLED Screen Sizes.
• Add as many I²C Buses as Needed.
• Never run out of I²C Address. Just add another I²C Bus.
• Easy to use Graphics Commands.
• 1-Wire^® Standard and Overdrive for fast screen updates.
• No 1-Wire^® Driver Required. Save Code Space.
• No OLED Drivers Required. Save Code Space.
• No OLED Fonts Required. Save Code Space.
• No DS18B20 Temperature Driver Required. Save Code Space.
• No I²C Sensor Drivers Required. Save Code Space.
• No Extra Power Supply Needed.
• Easy to connect RJ11 phone wire.
• Easy to add Sensors on 1-Wire^® Bus.
• Hot Pluggable 1-Wire^® Bus.

Parts used to build the OLED demo.

• IO Expander
• 1-Wire^® to I²C.
• 1-Wire^® Junction
• Splitter
• Arduino Nano.
• RJ11 Keystone Screw Terminal Jack.
• 50ft 4C4P RJ11 Wire.
• 7ft 4C4P RJ11 Wire.
• DHT22 Temperature/Humidity Sensor.
• I²C Si7021 Temperature/Humidity Sensor.
• SSD1306 128x32 OLED 0.91".
• SSD1306 128x64 OLED 0.96".
• SSD1106 128x64 OLED 1.3". Note: Screens are fragile! Make sure you order them in cases.
• SSD1309 128x64 OLED 2.42".
• 2.54mm Header Wire.

Wiring Diagram

Overhead View

Arduino code to run this demo.

SSD1309 128x64 OLED 2.42".

The documentation for the larger 2.42" OLED is not good, so I've added some additional information on how to properly use it with the 1-Wire^® to I²C adapter.

The display comes shipped by default as SPI so the first thing you have to do is convert it to I²C. This means you need to get the solder iron out and remove and add some SMD 0603 resistors.

1. Remove R4 and put it on R3.
2. Add 0 ohm resistor at R5 and R7.
3. Add jumper to CS-DS. This will effectively GND DC for I²C address selection of 0x3C. If you would like to use the alternate I²C address of 0x3D then remove the jumper and connect DC to VCC (3V3) instead.
4. Connect a wire from RES pin to the unjumpered pin of PL1 (D2) on the 1-Wire^® to I²C adapter. This will be used as a GPIO line to send a required reset pulse after power up of the OLED display.

This display controller requires a reset pulse on the RES pin to be sent after VCC is stable. According to the SSD1309 display controller you must set RES LOW for at least 3us and then HIGH. It's also useful to have access to a reset line on this display in the event of a panel lockup, where you can reset and reinitialize it without having to power down your whole system.

To send a reset pulse using the IO Expander use the gpio command on the selected pin and specify a duration.
Here we use the [g]pio command on pin [1] as an [o]utput of [0] or low for [10]ms. After the duration the pin will remain high.

>g1o0,10
ok
>

The larger 2.42 OLED display uses a simple internal switch-cap charge pump that converts the incoming 3V3 to a high 15V voltage drive for the OLEDs.  The display draws on average about 50mA from the 3.3V supply but the required inrush, especially over longer cable lengths requires that you add an additional 470uF electrolytic capacitor across VCC and GND on the incoming 3V3.  Make sure you connect the minus side to GND!  If you are using header connectors, just insert the capacitor into the pins.

For the smaller SSD1106 1.3" it also uses an internal charge pump that converts the incoming 3V3 to 7V to drive the OLEDs, so for longer cable lengths you will also need to add an additional 100uF electrolytic capacitor at the incoming 3V3.

This demo uses Splitters as 1-Wire^® stubs to connect the 1-Wire^® to I²C adapters to the OLED displays and I²C Si7021 sensor.

Splitter used as two 1-Wire^® drops on D1 and D2, with R1 and R2 as 100Ω

In order to connect as many 1-Wire^® sensors on to a single wire the OLED screen and sensors are connected to the 1-Wire^® bus as stubs, but there is an impedance mismatch at the branch point. Reflections from the end of the stub return to the main trunk, delayed only by the time it takes for the signal to travel the length of the stub. These reflections can then cause problems for the other slaves on the network. A resistor in series with the stub will reduce the severity of the mismatch and the amplitude of the reflected energy. The resistor mitigates adverse effects from stub-generated reflections on the main trunk

Guidelines for Reliable Long Line 1-Wire^® Networks

1-Wire^® Protocol

In order to efficiently run OLED displays, the IO Expander supports actively driven 1-Wire^® Overdrive speeds of up to 75.47kHz at over 100ft! If you need to go several hundred feet then you can still fall back to the slower standard speed of 15.38kHz. Native Temperature sensors like the DS18B20 do not support the Overdrive speed so can you mix devices with different speeds and the IO Expander will automatically change speeds to match the device on the same 1-Wire^® bus. The Overdrive speed is slower than the 400kHz on the I2C bus that is connected to the OLED screens, but it is fast enough for sensor status reporting right at the sensor location.

In order to use Overdrive speeds you must use a strong pullup of 2.2k as close to the CPU IO pin as possible.  For this demo we used pin 4 which already came with a 2.2k pullup, but for pin 2 we need to add one.  The simplest way is to solder a 2.2k 0603 resistor between the pins on the RJ11 plug on the port on the underside of the IO Expander PCB.

The IO Expander supports three different commands to control 1-Wire^® devices.

On the [o]newire bus on pin [4], [f]ind all the ROMs.

>o4f
28ffe835c3160376
28ffea20c316034c
28ff19f4c2160300
28fffd34c3160357
197a28030000002e
19ad200300000051
19ed200300000024
198f1103000000c0
>

 [i]2c devices on pin [4], [f]ind all the ROMs.

>i4f
197a28030000002e
19ad200300000051
19ed200300000024
198f1103000000c0
>

[t]emperature devices on pin [4], [f]ind all the ROMs.

>t4f
28ffe835c3160376
28ffea20c316034c
28ff19f4c2160300
28fffd34c3160357
>

So how hard is it to use the IO Expander? Judge for yourself by example.

[t]emperature sensor on pin [4] [s]elect ROM [76]. Perform a [t]ermperature conver[t], and finally do a [t]emperature [r]ead.

>t4s76;tt;tr
28ffe835c3160376
ok
17.9375
>

It's that easy!

Hot Pluggable!

One of the unique features of the IO Expander is that it has been designed to support hot pluggable devices. This means that if you have a sensor or OLED display go bad on you, you don't have to power down your system to replace it. While it is still powered remove the RJ11 plug and reconnect a new sensor or OLED screen. Also for this to happen you have to make sure that your code has been written to detect and reinitialize.  Some sensors don't have the necessary protection, so do this at your own risk. Any 1-Wire^® connection should be ok, as the 1-Wire^® driver on the IO Expander has been specially written to support this unique feature.

So get your IO Expander today and build your system!

1-Wire is a registered trademark of Maxim Integrated Products, Inc.