Graphical Displays with PBP3

[richard]

its not i2c its spi , there is no need for pullups.
one thing i notice is my display cannot be reset with a pic pin it just won't pull the pin low enough . shit design.
so i have included no reset function. to test i always power the display off/on as it can go to gaga land easily.

in general a shit display if you don't have need for the usual "LCD commands" it can support along with graphics in parallel i/f mode
or the reduced pin count of the serial i/f.
the 20pin h64128 is better imo

[rocket_troy]

I have a few 18F26K83s that I've used for various projects. Worth trying one of these? They can source/sink twice the current on each pin apparently.

Scrub that... Different architecture

Troy

[richard]

how good is your power supply and your connections ?
reset wont help here if it starts up ok
if you want you can pm me to get my address to send a display to be evaluated

[rocket_troy]

Power supply going into the PIC was a PicKit2 and that doesn't appear to be the issue. I was doing all these tests on a 18F26K22 SOIC package. After you mentioned the power requirements issues, I tried it on the larger DIP package and that appears to have fixed the show-stopping issue of screen regeneration. FILLRECT still doesn't work correctly, but that's a peripheral issue for me. I can at least now use these displays for the apps I had in mind.

Thanks again for all the assistance Richard.

Troy

[richard]

on q43 chips i have to set the high slew rate settings on for really highspeed spi
the k22 has slew rate control SLRCON.2 for portc , can't hurt to try

[rocket_troy]

Worked! I can now run things on the smaller package.

Legend!

Troy

[rocket_troy]

Richard,
Curious Question:
I was feeding a 10bit rotary encoder into the PIC (RB0-RB5 & RA0-RA3) with the display connected and I was stumped to figure out why I wasn't getting any input signal into the PortA pins and also 1 of the PortB pins. After a while I realised they were acting as outputs not inputs even though I declared them as inputs before the display initialisation. After some head scratching, I tried setting their TRIS status *after* the display initialisation and that appeared to fix that. So, I think I can maybe see where the PortB pin may have been set (behind the scenes), but can't see where the PortA pins where set as outputs? Does that have anything to do with the LCDOUT command call in the initialisation instructions?

Troy