🚀 go-pugleaf

Thanks for the sugestions, but i dont think the LCD has anything to do with the WriteFile not returning problem.

Well, i just proved it anyway... the problem still occours if i unplug the LCD from the serial port.

"Martin Moeller" <martin.moeller@moema.it> wrote:
>
>"MWP" <mwp@overclockers.com.au> ha scritto nel messaggio
>news:3ec28814$1@newsgroups.borland.com...
>>
>> Its a:
>> http://www.crystalfontz.com/products/633/index.html
>>
>
>That's a module with a standard glass and a lot of add-ons. Such simple
>screens have normally build in controllers (if at all), with either 4 bit
>parallel or syncro interface (clock+data). All module interface jobs are run
>by a cpu on the pcb, using btw a Dallas DS16xx family RTC & Powerfailure
>controller. It's presumably quite small, so 19200 baude are a bit
>optimistic/at risk. Can you reduce it? Try within 4800.
>
>> Yup... this is what im doing.
>> Although, im not quite sure what the timeout values should be.
>
>Your timeout should be very high (several seconds, just not to hang there
>forever if n characters are not received), but do not 'hammer' on the LCD
>controller (try 200ms, i.e. 5/sec). Further, make sure you handle
>transmission errors (CE_.. ) properly.
>
>More than ever convinced it's an LCD's firmware bug. Their performance specs
>are too optimistic: slow it down.
>
>Rgds, Martin
>
>