-
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 8 replies
-
I believe this may belong in discussion. Please move if so! |
Beta Was this translation helpful? Give feedback.
-
Try powering the display from 3.3v. |
Beta Was this translation helpful? Give feedback.
-
Also, I find that Dupont cables are not the most reliable. Soldering directly to the solder points of the display may result in a more stable display. |
Beta Was this translation helpful? Give feedback.
-
Hello, The output you're seeing is definitely not random, I have the exact same output on my display! I am using a Raspberry Pi Model 2B. Also, my particular model display won't run at all when powered at 3.3v, so that is not an option/solution. Something I noticed when writing a driver for this exact display a few months ago, that this particular unit is a bit sluggish to respond compared to others I have worked with (i.e. time required with data on bus and enable pin high is long). It might be completely unrelated but, I'm curious. Is there a way that I could tweak the delay times on the driver to experiment/investigate? |
Beta Was this translation helpful? Give feedback.
-
Looks like using the correct pin layout did the trick. Thanks for the help everyone! |
Beta Was this translation helpful? Give feedback.
-
With our brand new i2c display support, things should be a lot easier thanks to @diyelectromusic 👍 |
Beta Was this translation helpful? Give feedback.
Looks like using the correct pin layout did the trick. Thanks for the help everyone!