Im running the examples without modification, Ive matched the pins and use the same on my Arduino Nanohttp://code.google.com/p/ht1632c/source/browse/examples/geometry/geometry.pdehttp://code.google.com/p/ht1632c/source/browse/examples/line/line.pdehttp://code.google.com/p/ht1632c/source/browse/examples/fill/fill.pdehttp://code.google.com/p/ht1632c/source/browse/examples/circles/circles.pde

Im pretty sure ive done it before with the same results, when this first happened I thought maybe one of the displays was broken, but I remember they show the same result in both configurations.Will test to swap the displays and post results in a couple of hours.

Hi team, I have two Sure 3216 displays and there is no way to have them working OK.I have tried several codes I found on the forum (and elsewhere) but there is allways something wrong with characters being displayed at the wrong position.

Can any of you tell me where can I find a simple code that works flowlessly with 2 displays?

I just want to be able to plot dots on a 32x32 matrix, no funcy graphics and/or characters, just dots!!!

the issue with this displays is not that the code most people are using is wrong ... I got a couple of displays from a friend today and I had the same issues explained by @eslin. After reading the code and realizing there was nothing bad in it, I realized that the 74hc164 chip is sending the output from pin QD directly to CS_OUTPUT. This means there is no delay between CS_OUTPUT in one SURE display and the CS_INPUT in the next when you daisy chain the displays.

The proper way of doing this would have been if the manufacturer had used QE as the CS_OUTPUT. Once you have the display, there is actually a patch for this without cutting anything. I also realized that the capacitor C1 is not mounted on the board. Adding a 1nF capacitor there did the magic for me. It delayed the load of the CS_INPUT enough to stop the bug of happening.

This is what Don (a customer) said in an email regarding the same issue:I did look at the clocking relationships on the scope.The clock to data hold timing on the HC164 was marginal, 2ns, versus -2ns typical and 4ns minimum. Meaning it will probably work, but it's not certain. CLK, DATA and WR are buffered through 2 sections of an HC04, with a delay of 11ns, but CS_OUT is not, so with every successive board in a chain this timing degrades. They ran out of HC04 gates. Installing the 10pf capacitor at C1 might help, but it's not ideal.

Hey all, I'm surprised to see this thread still on the first page =). I've been away, work has taken up most of my time, and I am getting laid off due to a reduction in force, but as soon as I get a new job I'll be revisiting this page, and continuing work on my bluetooth code. Florinc, thanks for the nod on your site, just noticed it today. I had issues with my circuits working 100% in the past (custom boards, had issues with usb working) but I'll be grabbing another arduino uno and working everything out again in to make sure everything works 100%. I've also been busy on another android project for a client, but when that wraps up I'll work on my github repo to update all code/examples.

Glad to see the community is still active in this thread, take care all!

My first major project (looking for people who would like to help contribute) Bluetooth Sure 32x16 LED Displays!: https://github.com/evanric

I have to mention this, because I've been banging my head against this for days: The latest version(s) of this library will not work on the Arduino Leonardo! I have a Duemilanove and it works fine on that. Until the lightbulb popped up over my head and I decided to try it on the Duemilanove I was ready to pull out what little hair I have left!