#dotclock

Many years ago, I pulled an LCD out of a GPS unit from the days before cars and smartphones having navigation features. This LCD is a color LCD with a backlight. It’s a very different technology, and much more challenging to interface to. I can’t even find a proper datasheet for the module.

this is the wrap-up post for the prototyping phase of the little project that i've been calling 'projekt' over the past few weeks. i will be posting pics and a video of it working in quick succession over the next few posts, starting with this one.

this is a picture of the prototype shortly before i completed all it's required wiring and before i hooked up the control pins to the arduino. you can see that i've actually colour-coded the wires carrying the current from Vcc and those bringing them to Gnd. (red & black) the only things missing are some of the IC I/O pins which i later pulled to either 5V or GND depending on what the datasheet recommended.

i later hooked it up to the arduino and uploaded a sketch to turn on every output to test the matrix. as you can see, it lit up in a brilliant fashion after the shift register was initialized. this was one of the more significant milestones of the project since it was after close to 72 hours of painstaking work and seeing it light up on the first time without any problems was truly a very satisfying experience, and one that was quite memorable for me. you can see a pair of decoupling capacitors on the edge of the board. the display is emitting white light (with a slightly bluish tint) as all three LEDs (red, green and blue) in each pixel is currently switched on.

i later measured the total current draw of the prototype using my DMM and it came to around 400mA. i believe this was due to the current-limiting factor of the USB interface it was running off. needless to say, this is probably *not* the maximum brightness of the matrix as the absolute maximum points it to having a 3.84 ampere draw. however, i suspect this will make it extremely blinding and cause some lifespan issues. large current draw will not be an issue however, as i will explain in a later dotClock post.

as i mentioned in an earlier post, i have given the prototype deeper consideration and have since branched out into two separate projects, of which i'm referring to internally as dashClock and dotClock. in the process of embarking on this prototype journey, i realized that the control circuit for a single 8x8 matrix, while not extremely complex, was very repetitive, greatly increasing it's intricateness. (the amount of cabling present on the breadboard is testament to that)

the prospect of scaling the project into a 32x8 matrix onto a soldered perfboard was enough to convince me to branch out into a side-project involving seven-segment displays (SSDs) instead (which, for all intents and purposes, are much easier to control than LED matrices). since i only got one try (or at most, a few) on a soldered perfboard, a simpler circuit involving SSDs seemed to be a more logical intermediate step for me so that i could acquire the experience i would need to pull off the 32x8 matrix.