Difference between revisions of "UWatch"

From OpenCircuits
Jump to navigation Jump to search
(more proposed displays)
(another µWatch wiki)
Line 1: Line 1:
 
== µWatch unofficial FAQs ==
 
== µWatch unofficial FAQs ==
 +
 +
''Late breaking news: there is now [http://www.calcwatch.com/wiki another µWatch wiki]; is that the Official µWatch wiki? Feel free to move all the content on this page to that wiki. --[[User:DavidCary|DavidCary]] 15:58, 19 November 2009 (UTC)''
  
 
The uWatch is an RPN and Algebraic scientific calculator watch that you can build yourself.
 
The uWatch is an RPN and Algebraic scientific calculator watch that you can build yourself.

Revision as of 08:58, 19 November 2009

µWatch unofficial FAQs

Late breaking news: there is now another µWatch wiki; is that the Official µWatch wiki? Feel free to move all the content on this page to that wiki. --DavidCary 15:58, 19 November 2009 (UTC)

The uWatch is an RPN and Algebraic scientific calculator watch that you can build yourself. The software is open source under the GPL license at Sourceforge. I'm assuming you've already read the official uWatch FAQ, so we'll jump right into some more technical details.

display

The history of the uWatch mentions the 53mm x 20mm compact 16x2 line LCD that convinced David L. Jones that the uWatch project was actually doable with off-the-shelf components. If you are doing low-level programming of the uWatch, such as making "custom characters", you might want to look at the datasheet (via "Moon Phases").

Alas, that original display pulls about 2 mA, more power than anything else on the uWatch -- even the CPU uses less power (at 250 KHz). That's the main reason the current uWatch cannot run the display continuously (like a standard watch), but much be explicitly "turned on" every time you want to read the time.

The current uWatch2 rough draft seems likely to use the Newhaven NHD-C12832A1Z-FSW-FBW-3V3 128x32 Pixels display. Which uses less than 100uA which would enable a continuous display watch. The "white LED backlight" uses 30 mA at 3.0 V but is still very usable at much lower currents.

Proposed displays:

Some threads discussing diplays: "Hardware Stuff » Why not a smaller LCD...",

buttons

The buttons are crucial for a calculator watch. It is difficult to compromise between:

  • fast typing speed:
    • it's much faster to have lots of buttons, so you can directly push a button for "tan" than to scroll through some soft menu searching for it.
    • large buttons are generally faster to rapidly punch than tiny, closely-packed buttons
  • physical size:
    • We want something that is not too heavy and bulky to wear on the wrist. This means lots of large buttons are not going to happen.

The first uWatch prototype used surface-mount buttons. The original uWatch for sale uses the (through hole!) Panasonic EVQ-PJG05Q switch for its buttons. [1] (current price)

  • please tell us about other buttons that would be appropriate
  • ... capacitive touch "buttons" ? ...
  • ...

processor

The processor is, perhaps surprisingly, not a crucial choice. In the last few years, several companies have released processors that meet the stringent low-power and other requirements (which are????). In theory, since most of the software is written in the C programming language, it is theoretically easy to port the software to a different CPU.

The original uWatch uses the 16 bit Microchip PIC24FJ64GA004. It uses 50uA at 32KHz, ... (FIXME)... uA at 250 KHz.

Other proposed processors have been discussed on this thread: "Hardware Stuff » Ideas for Mk2 watch".

... the Microchip "Extreme Low Power Microcontrollers" claim to have "Real-time Clock/Calendar down to 500 nA". http://www.microchip.com/xlp

further reading


Retrieved from "http://www.opencircuits.com/index.php?title=UWatch&oldid=19028"