Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ux1701x device demo - unexpected screen output #89

Open
wangdino opened this issue Aug 22, 2018 · 3 comments
Open

ux1701x device demo - unexpected screen output #89

wangdino opened this issue Aug 22, 2018 · 3 comments
Labels

Comments

@wangdino
Copy link

wangdino commented Aug 22, 2018

Hello, first of all thanks for the great lib and examples.

I have a 12864 LCD with UC1701X IC and I have it connected to a RPi3B+ (running latest Raspbian) following the wiring documentation here:
https://luma-lcd.readthedocs.io/en/latest/install.html#connecting-the-display

image

Also following the instructions I've installed luma.lcd and cloned luma.examples locally.

So I tried to run demo.py under examples folder, giving the GPIO pins based on how the wiring was connected:
python examples/demo.py -d uc1701x -i spi --gpio-data-command 23 --gpio-reset 24

No error was output, I think it's only showing the routine output:

Version: luma.lcd 1.0.3 (luma.core 1.7.2)
Display: uc1701x
Interface: spi
Dimensions: 128 x 64

Testing basic canvas graphics...
Testing contrast (dim/bright cycles)...
Testing display ON/OFF...
Testing clear display...
Testing screen updates...

However, on the other side - on the actual LCD screen, there was no response / action during most of the time, except:
When "Testing display ON/OFF..." the screen flickered like this:
img_0299
When "Testing screen updates..." the following characters were shown:
img_0301
And the characters moved from right side to the left side.

So I'm guessing the wiring connection is fine because otherwise nothing would be shown on screen. But since there's no error message it's difficult for me to further diagnose where could go wrong.

Any insight is appreciated.

@thijstriemstra
Copy link
Collaborator

ping @rm-hull

@rm-hull
Copy link
Owner

rm-hull commented Oct 30, 2020

Looks like there is some cross-talk on the SPI lines to me. Is there another program also using the same SPI bus ?

@wangdino
Copy link
Author

wangdino commented Nov 1, 2020

It's been a while so I can't say for sure but it's highly unlikely. I was testing using a fresh system (raspbian) so there was hardly anything that would be fighting on the same SPI bus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants