Unbelievably, there is still demand for the Dual LED matrix shield for Arduino, which also pressures me to maintain and upgrade the supporting software, usually on client's request.
And that is how the Mondrian clock got a couple of new display modes: one picked directly from the Cube clock, showing just hours and minutes, the other one an improvement of the same, with the addition of a red dot moving around the rectangular clock face to indicate the seconds.
The display mode changes when both buttons are pressed simultaneously.

Here is the clock in action.


The Mondrian clock uses the Dual LED matrix shield and wsduino (as an RTC-equipped and XBee-supporting Arduino-compatible).
The code is available here. There is no GPS support, but that can be copied and adapted from the previous version of Mondrian software.

Note that the LED matrix shield was designed to accommodate either the common-anode or the common-cathode LED matrices, by soldering the correct LED driver, either A2982 or ULN2803 respectively. In the software, use either one of these defines:
#define _COMMON_ANODE_
//#define _COMMON_CATHODE_
The only user interface on the shield is the pair of buttons. Pressing the left one will increment the hours, the right one will increment the minutes, while the seconds are always reset.
By pressing both buttons at once, the display mode cycles through Mondrian mode (red hours, green minutes, orange seconds), 24-hour mode (HH:MM in green), 12-hour mode (HH:MM in orange), and moving second red dot (12-hour, HH:MM in green, more square font).

Unbelievably, there is still demand for the Dual LED matrix shield for Arduino, which also pressures me to maintain and upgrade the supporting software, usually on client's request.
And that is how the Mondrian clock got a couple of new display modes: one picked directly from the Cube clock, showing just hours and minutes, the other one an improvement of the same, with the addition of a red dot moving around the rectangular clock face to indicate the seconds.
The display mode changes when both buttons are pressed simultaneously.

Here is the clock in action.


The Mondrian clock uses the Dual LED matrix shield and wsduino (as an RTC-equipped and XBee-supporting Arduino-compatible).
The code is available here. There is no GPS support, but that can be copied and adapted from the previous version of Mondrian software.

Note that the LED matrix shield was designed to accommodate either the common-anode or the common-cathode LED matrices, by soldering the correct LED driver, either A2982 or ULN2803 respectively. In the software, use either one of these defines:
#define _COMMON_ANODE_
//#define _COMMON_CATHODE_
The only user interface on the shield is the pair of buttons. Pressing the left one will increment the hours, the right one will increment the minutes, while the seconds are always reset.
By pressing both buttons at once, the display mode cycles through Mondrian mode (red hours, green minutes, orange seconds), 24-hour mode (HH:MM in green), 12-hour mode (HH:MM in orange), and moving second red dot (12-hour, HH:MM in green, more square font).

This would make a nice replacement for the original glass-domed WiseClock.


















I named it CubeClock for the simple reason that it is encased in a baseball display case, found on ebay for about $5.
It includes Wiseduino (with on-board RTC), a LiPo battery shield (I used the one from seeedstudio, but others should work too), a prototype shield with the cheap "orientation sensor" introduced here, and the bi-color LED mini-display shield.

The bottom board is the Wiseduino, secured to the box with 2 screws. The other shields are just stacked on top of each other. The battery shield from seeedstudio, discussed here, uses a 1,000mAh LiPo battery (did not come with the shield), attached to the shield itself with plastic ties. The clock can be turned on or off (to save the battery) from the power switch on the Wiseduino.

CubeClock can also be powered through the USB cable plugged into the battery shield (which also charges the LiPo battery), as shown below.















A closer look is shown in the next photo. The 2 buttons on the mini display shield and the power switch are on the opposite side. They are accessible after the top of box is removed, as is the FTDI connector.















The current sketch running on CubeClock is almost identical to the one on SillyClock (and IllyClock, for that matter), since the mini display shield uses almost the same schematic as the dual bi-color LED matrix shield.
The next release of the software should involve the "2-axis tilt sensor" (already connected on pin A3) to change the display according to its orientation. It could also include the displaying of messages from the 32KB EEPROM on the Wiseduino board (as does the glass-domed WiseClock).

Other ideas:

• add infrared receiver (on D2, with interrupt; code picked from WiseClock);
• add buzzer (on D16/A2, the only pin left unused at this point) for alarm clock functionality (half-implemented in the software already).