Hi Maarten,

When I sent this email, I hadn=B4t received =

the email saying it has another PIC 16F88
controlling the LCD and serial communications. :>)

This LCD controller implementation is nice when
you have just two pins for I/O.

"and not Myke's two pin interface... I never had much luck with that"
What kind of problems did you experience with this implementation?

Best regards,

Rubens


At 11:10 28/8/2006, you wrote:
>>
>> Try this LCD controller:
>>
>> http://www.myke.com/lcd.htm
>>
>> Less code and pins, using just a cheap CI 74LS174.
>
>
>Please explain how serial access to an LCD reduces the code size compared =
to
>full parallel access? I know it reduces the number of pins (though I would
>go for a three pin interface with a normal shift register, and not Myke's
>two pin interface... I never had much luck with that) but in my experience,
>it increases the code size: instead of a simple "move data to port, toggle
>enable" you now have to shift each bit separately and then toggle enable.
>
>In Brent's case it doesn't really help either, as it would still result in=
 a
>redesign of his PCB, which is the thing he is trying to avoid.
>
>I do appreciate seeing the old example from Myke Predko coming back, though
>(I liked his book a lot).
>
>Greetings,
>Maarten Hofman.
>-- =

>http://www.piclist.com PIC/SX FAQ & list archive
>View/change your membership options at
>http://mailman.mit.edu/mailman/listinfo/piclist

-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist