contrib-drivers icon indicating copy to clipboard operation
contrib-drivers copied to clipboard

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

Open ckoessler opened this issue 8 years ago • 14 comments

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

ckoessler avatar Jun 05 '17 18:06 ckoessler

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

proppy avatar Jun 05 '17 20:06 proppy

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

ckoessler avatar Jun 05 '17 20:06 ckoessler

@proppy were you able to reproduce the problem?

ckoessler avatar Jun 06 '17 18:06 ckoessler

@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).

proppy avatar Jun 06 '17 18:06 proppy

@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...

ckoessler avatar Jun 06 '17 18:06 ckoessler

/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

proppy avatar Jun 06 '17 18:06 proppy

@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!

ckoessler avatar Jun 07 '17 16:06 ckoessler

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

beriberikix avatar Jun 18 '17 23:06 beriberikix

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

proppy avatar Jun 19 '17 21:06 proppy

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?

beriberikix avatar Jun 19 '17 22:06 beriberikix

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.

ckoessler avatar Jun 19 '17 22:06 ckoessler

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

beriberikix avatar Jun 20 '17 04:06 beriberikix

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

maybe we write too fast?

jumoog avatar Aug 05 '17 12:08 jumoog

@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?

mangini avatar Aug 08 '17 00:08 mangini