SD storage shouldn't be required unless you want historical logging of
data on the device itself. If you just want the LCD to display the
latest readings it should be possible to do that by using global
variables to store the readings, and then reference those variables in
the routine that sends the values to the LCD.
--
Jonathan Oxer
Ph +61 4 3851 6600
* Freetronics (www.freetronics.com)
* Arduino Shield List (www.shieldlist.org)
* Practical Arduino (www.practicalarduino.com)
While I haven't implemented an LCD on any of my displays, I do know Andy's Pebble does just this using the Aiko components of the code. They aren't in the SEGmeter codeline at the moment, however they could be re-inserted as new handlers.
From what I understand, the LCD just outputs the current value in the global buffer and updates at the same rate it's changing.
Sam.
> --
> You received this message because you are subscribed to the Google Groups "Aiko distributed platform" group.
> To post to this group, send email to aiko-p...@googlegroups.com.
> To unsubscribe from this group, send email to aiko-platfor...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/aiko-platform?hl=en.
>
On 2010-12-20 22:30 , Robb01 wrote:
> I am interested in adding an LCD display to the Segmeter with a pushbutton
As Sam mentioned, there is existing code in the Aiko code base for both
these functions.
The Aiko LCD code supports either a directly connected LCD screen that
uses 6 (or 7) Arduino pins ... or an LCD screen connected via an 8-bit
shift register/latch that requires only 3 Arduino pins (the source code
provides documentation ... it's the same as the Pebble hardware).
Also, as Sam noted, the sensor value poll rate and LCD display rate are
linked. I intend to allow different rates for sensor polling, display
updates and (serial) communications transmission in an upcoming version
of the software.
> The display would go to sleep after a delay until
> the next time the p/button is pressed.
This could be managed by another Aiko timer handler.
> The aiko-node.pde includes lots of code for displaying the data from
> the arduino but will it suffice to have the LCD-displayed variables
> stored as memory variables in the code or would a separate storage
> device e.g. SD card etc. be required?
As Jon mentioned, global variable storage is sufficient for your
application.
In trying to create a modular system, I have a strong preference against
global variables. Unfortunately, the Arduino development environment is
less flexible than working in a completely unrestricted C / C++
development environment.
I intend to provide a structure for specifically managing sensor output
variables for display and communications purposes that promotes
modularity ... and avoids potential collisions in a global name space.
Just have to be careful about the limited RAM space in an ATMega processor.
--
-O- cheers = /\ /\/ /) `/ =
--O -- http://www.geekscape.org --
OOO -- an...@geekscape.org -- http://twitter.com/geekscape --
Hey guys
Thanks for your replies. Looks like I have some work to do on the
breadboard!
Is there any advantage one way or another between the 7 pin connection
to the LCD vs the 3 -pin connection method via the MC14094 shift/latch
register - apart from the obvious one of using up a larger number of
available arduino pins?