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

HT16K33 - display() and clear() not working correctly #52

Open
ckoessler opened this issue Jun 5, 2017 · 14 comments
Open

HT16K33 - display() and clear() not working correctly #52

ckoessler opened this issue Jun 5, 2017 · 14 comments
Labels

Comments

@ckoessler
Copy link

I am trying the ht16k33 driver on a raspberry pi3 running preview 3 and the version 0.3 of the driver. My display is the Adafruit 1.2" 7-segment LED HT16K33 Backpack.

When sending the command clear(), the last digit on the display still light up some segments (cf picture)
clear

I then ran some other test with different texts. Here are the results.

xoxo
"XOXO"

abcd
"abcd"

Digits from "0000" to "9999"
0000
1111
2222
3333
4444
5555
6666
7777
8888
9999

@proppy
Copy link
Contributor

proppy commented Jun 5, 2017

@ckoessler can you confirm how you wired the display to the Raspberry Pi?

@ckoessler
Copy link
Author

@proppy
SCL -> Pin5 (SCL)
SDA -> Pin3 (SDA)
GND -> Pin6 (GND)
+5V -> Pin4 (5v)
V_IO -> Pin1 (3.3V)

@proppy proppy added the bug label Jun 5, 2017
@ckoessler
Copy link
Author

@proppy were you able to reproduce the problem?

@proppy
Copy link
Contributor

proppy commented Jun 6, 2017

@ckoessler I don't have the part to test this yet, but I'd be curious if you've got the same issue with another ht16k33 based peripherals (if you happen to have one).

@ckoessler
Copy link
Author

@proppy I don't have any other. I am curious as well and wondering if I just have a bad display. If this is the case I need to send it back ASAP...

@proppy
Copy link
Contributor

proppy commented Jun 6, 2017

/cc @beriberikix who recently stole my Adafruit 1.2" 7-segment LED HT16K33 Backpack, can you try reproducing this issue with this sample:
https://github.com/androidthings/drivers-samples/tree/master/ht16k33

@ckoessler
Copy link
Author

@proppy I'm sending back my display and switching to another model. Hopefully one of you will be able to check if the code has a bug or not. Thanks!

@beriberikix
Copy link

@proppy I don't have the an AThings device setup at the moment - do you want me to send the 7seg display to you?

@proppy
Copy link
Contributor

proppy commented Jun 19, 2017

@beriberikix can you send it to @mangini @jdkoren or @devunwired that way they can try to reproduce the issue.

@beriberikix
Copy link

beriberikix commented Jun 19, 2017

Just a thought - have you verified that the pins are providing enough current to drive the display? Also, have you tested it with a well-known, working code, like that for Arduino provided by Adafruit?

@ckoessler
Copy link
Author

I only have one pi3 loaded with AT. In doubt, I assumed I had a bad display and sent it back before the end of the return window. I won't be able to test changes.

@beriberikix
Copy link

I can confirm something isn't working correctly. I too saw weird behavior using the contrib-driver, while it worked perfectly fine with code from Adafruit on an Arduino.
img_20170619_205045
img_20170619_210459

@jumoog
Copy link

jumoog commented Aug 5, 2017

I have the same problem with the Grove-LCD RBG Backlight

maybe we write too fast?

@mangini
Copy link
Contributor

mangini commented Aug 8, 2017

@beriberikix Can you confirm that no exception was thrown? In the past I had weird characters showing up when my code threw an exception, probably because the whole process went down before finishing writing to the bus. Also, are you getting this issue consistently, or randomly?

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

5 participants