The parallel LCD is significantly faster since you can the .String
attribute. The newer compiler and firmware makes the LCD object much
more robust too. The V.5 compiler will have intermittent problems with
missing characters in the LCD object when writing to the LCD. V.6
corrected them and the C.1 firmware made it even better.
DLC
rtstofer wrote:
>>> I must admit, the current way works but takes over 1 second to display
>>> text on all 4 lines. I'm going to spend tonight adding in cursor
>>> control and other bits and pieces. One thing I might as well ask now
>>> (I'll try reading the manual in a bit) How would you turn a numeric
>>> value into a string of characters. (I was hoping to display sensor
>>> readings on the LCD display?
>>>
>>> Cheers,
>>>
>>> Jas
>>>
>
> Yup! That's the same slow speed I was talking about earlier (in this
> thread?). I wrote some code for an LCD and an Ultrasonic Ranger (in
> the Files section as LCDRanger.osc) a few years ago and I wasn't
> impressed with the writing speed.
>
> It's too bad the OOPic doesn't use the I2C hardware for things beyond
> oDDELink.
>
> I have never tried the standard 14 pin LCD. I wonder if it writes faster.
>
> Richard
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
--
------------------------------------------------------
Dennis Clark ooPIC Tech Support
www.oopic.com
------------------------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment