Ledtranceguy Blog, LEDs, Trance and other EDM, and Festivals

Note, you will need the LiquidCrystal_SR_LCD3 driver from the NewLiquidCrytal Library.

You will also need the Aiko Library: https://github.com/geekscape/aiko_arduino .

Pebble v2 requires at least the IDE 0.23 (untested) but 1.0 or better is recommended. The code is of course arduino 1.0 compatible.

At the LCA 2012 Arduino Miniconf, we got to build a new toy, a Freetronics Pebble v2 (schematics here). This was a refresh of the Pebble V1 (schematics here) which was the target of the very first arduino miniconf I missed in 2010.

This new Pebble had even more hardware to program against and was a much more compact design due to the use of a bunch of SMT parts (actually there are 2 arduinos on the board, one is dedicated to usb/serial communications, removing the need for an ftdi chip).

Like good hacking projects and conferences, the design and software were improved until the last minute, and Andy worked all night before the conf to get us his demo code (along with bits from Luke and others).
Andy wrote the very cool aiko event handler for arduino. You give it a list of callback functions and it'll do its best to call them on the interval you gave it (interval in milliseconds). For arduino folks, with Aiko, code looks like this:

void setup(void) {
  Serial.begin(DEFAULT_BAUD_RATE);
  // Call LCD init early so that others can write to it.
  lcdInitialize();

  Events.addHandler(clockHandler, 1000);
  Events.addHandler(lightHandler, 1000); // Aim for 250 ms
  Events.addHandler(rotaryEncoderHandler, 100);
  Events.addHandler(serialHandler, 30); // Sufficient for 38,400 baud
  Events.addHandler(temperatureHandler, 1000); // Aim for 250 ms
  Events.addHandler(touchPanelHandler, 250); // Aim for 50 ms
  Events.addHandler(rgbLedFadeHandler, 10); // Can run slower.
  // Call LCD last so that it can display variables that just changed.
  Events.addHandler(lcdHandler, 1000); // Aim for 100 ms
}

void loop(void) {
  Events.loop();
}

So Andy got us working code to test our hardware, but of course it wasn't fully optimized (hell, code never is). So, that gave me a chance to do some arduino programming to see what could be improved. It was a good learning experience.

After a bunch of work, here is what I was able to do:

Here is the end result:

Again, the code: https://github.com/marcmerlin/aiko_pebble_v2

Here's a quick man page :)

pop up menu with selection cursor

backlight menu

LED color change delay menu

Note that I as read on http://www.circuitsathome.com/mcu/rotary-encoder-interrupt-service-routine-for-avr-micros and have seen with multiple decoding errors in my rotary encoder test code (shown below), it is probably a good idea to add a couple of small caps around the encoder's feet:

And that's it folks, that was fun :)

Oh, actually I also made a repository of small demo code I wrote for the Pebble v2: https://github.com/marcmerlin/pebble_v2_demos .

All the code is arduino 1.0 compatible

After coming back from the Arduino Miniconf at Linux.conf.au, I ended up with a freshly soldered freetronics pebble v2.

Like the Pebble V1 (schematics here), it uses MC14094 8 bit shift register to drive the LCD using only 3 wires instead of 6 or more.

The Pebble designers thankfully used the same shift register wiring than shown on the LCD3wire page on arduino playground. However, the code that came with it only had limited functionality for talking to the LCD, and the code on the LCD3wires page is also limited in functionality (on top of being incompatible with arduino 1.0).

So, I ended up finding Francisco Malpartida's cool work on virtualizing the stock arduino LiquidCrystal library (very featureful and optimized timings). In turn, Ragnar used that codebase to design his own shift register library for 2 or 3 wires.

Ragnar's wiring and code is somewhat complex because it exploits some interesting hacks:

In other words, if you have a non latching shift register, use his code and wiring. If you have a latching shift register, you should use the code from this page and the more widespread LCD3Wires wiring.

So, where does this bring us?
I used Malpartida and Ragnar's work to make an LCD3Wire hardware driver for the NewLiquidCrystal Library. This brings full library support to the pebbles as well as other folks who use the reference wiring from LCD3wires.

I called the new library NewLiquidCrystal in the hopes that it will become the new de facto library in standard arduino one day. My code is here: https://github.com/marcmerlin/NewLiquidCrystal and includes the new LiquidCrystal_SR_LCD3 driver I wrote. To be clear, all the code came from Francisco Malpartida's work, I built on top of it to write my LiquidCrystal_SR_LCD3.cpp driver for LCD3Wires compatible hardware.

I also wrote an extended LiquidCrystal Demo which should work on all liquidcrystal supported devices (baring the character count).

Here is a demo of my popup menu code that works with a rotary button (cursor showing what is currently selected if you click on it)

I'm now working with Francisco to get my code included in his tree, and if we're lucky that code may eventually get included in the standard arduino libraries as a faster and more flexible LiquidCrystal replacement.