AnyDisplay Supported Displays

Here’s my initial list of displays which will be supported by AnyDisplay. Currently working on a breakout board for the Sharp MLCD devices which should make these easier to work with.

Display Type Price Size Resolution Colors Controller
Sharp LS013B4DN02 PNLC $20.43 28×32 96×96 Mono
Sharp LS027B7DH01 HR-TFT $45.25 62×42 400×240 Mono
Liquidware Touchshield Slide OLED     320×240 RGB666
EA DOGM128W-6 FSTN $18.00 55×46 128×64 Mono ST7565R
EA DOGXL160W-7 FSTN $35.98 78×61 160×104 Mono UC1610
FSTN $18.55 49×48 160×100 4 bit gray ST7528i
ScreenKey TFT128 TFT n/a 35×30 128×128 RGB565  
Nokia 6100 TFT $4.95 27×27 128×128 RGB565 PCF8833
Osram Pictiva OLED n/a 92×19 288×48 8 bit gray

6 thoughts on “AnyDisplay Supported Displays”

  1. Dear Steve,

    I’m Matteo Trivellato a senior FIW engineer at Delta ohm s.r.l. in Italy.
    I would like to work with the new display by Sharp LS027B7DH01 using an msp430 to interface with it. Unfortunately I did not find any graphical display library that helps using it.
    From your blog it seams that you are working on a display library (AnyDisplay) that could be used to interface with LS027B7DH01. Could you please give me more details on your work? Where is it possible to buy your AnyDisplay library?

    Thanks in advance for your help.


    1. AnyDisplay is still in the planning stages. I’m doing this for fun, not for profit – be patient.

      The display is actually quite easy to drive; check out the datasheet on

      A couple of points to keep in mind:

      First, the device uses a 5vdc supply but is clocked at 3.3v. It seems to be fairly tolerant of 5vdc data, but I wouldn’t deploy in this configuration.

      Second, remember to toggle VCOM. Again, read the data sheet.

      Finally, keep in mind that the minimum updateable unit is a single line. For the LS027B7DH01, this means a chunk of 400 bits. Because of this, you really need a memory buffer to effectively use the display. This is tricky on a memory constrained MCU, as a simple linear buffer will consume about 12KB.

  2. Hi Steve – just wrnieodng what’s going on with py-openzwave at this point. Your fork at github doesn’t show much activity – just wrnieodng if you’re still active with it or not. Thanks!

    1. My code was merged with Marten Daamen’s trunk last summer, I haven’t had much opportunity to play with it since then. I believe there have been a couple of minor changes posted since I last did a pull. The core OpenZWave project has continued in active development, so I would expect some growing pains 😛

Leave a Reply

Your email address will not be published. Required fields are marked *