

Something you would expect with I2C comms. Another thing the working display appears to have pull up resistors connected to SCL and SDA. On closer inspection of both displays it becomes apparent this is the case the working display (blue PCB) but not with the non working display (yellow).
#My power co. 2in1 usb joystick serial#
The data sheet stipulates that D1 and D2 should then be connected together to act as the serial data line. When configured for I2C mode D0 acts as the serial clock input. Both displays have BS0 and BS2 are tied to GND while BS2 is tied to the positive supply which as expected sets the mode to I2C. The protocol selection pins BS0-BS2 allow different protocols to be selected. Interestingly it turns out the controller supports communication over I2C, SPI (3 and 4 wire) and parallel. The 3.3V regulator provides the required logic voltage. The working display using 910K while the non working display opting to use 560K.

The brightness current is set by the resistor between IREF and GND. These are connected between C1P/C1N and C2P/C2N and can be seen on both displays.īoth VCC and VCOMH have decoupling capacitors down to GND as outlined in the data sheet. The controller has an internal charge pump regulator circuit for generating the 7.5V required by the display. A stabilization capacitor should be connected between this pin and VSS when the converter is used. A capacitor should be connected between this pin and VSS. When I2Cmode is selected, D2 & D1 should be tired together andserve as SDAout & SDAin.ĬOM signal high voltage. When I2Cmode is selected, D0 is theserial clock input SCL. In I2C mode, this pin acts as SA0 for slave address selection. I have also labelled them on the pictures above. The pin out for the connections to the display can be seen below. Next step was to start reading the data sheet to see how this controller is configured. One thing that strikes you straight away is the lack of components on the new display (yellow PCB) compared with the old display (blue PCB). First thing was to look at the two displays see how they compare. Wrong! Come on things are never that simple.
#My power co. 2in1 usb joystick drivers#
When the display arrived I assumed since both modules used the same display drivers the code I had already written would work out of the box. As I was already ordering from Hobby King I decided to bundle one in with my order. Turns out the MultiWii flight controller (Arduino based flight controller originally using gyroscopes and accelerometers from the Wii controllers) uses an add-on OLED display module which no surprise features a 128×64 OLED display driven but the SSD1306 controller. Having decided to use these displays on another project I am currently working on I found them on the R/C model site HobbyKing. The internet is rife with examples of code for driving these displays so I had it up and running with fairly minimal effort. The display I used had a Systech SSD1306 controller fitted. These modules are great because the provide a clear and vivid display while requiring no back lighting. In a recent project I used a small 128×64 pixel OLED display module.
