Thursday, 26 May 2011

Interactive Play Terminal - Software Installation & Testing

Since all the hardware was in place, I started installing all the O/S's.
A quick split of the 80 GB HDD into two (three actually) partitions, 50 GB for hungry Windows and 30 for Edubuntu and it's swap partition.

Windows
Well, windows started very promisingly indeed. The O/S was installed and running in about 20 minutes which I found impressive considering the age of the hardware. It was not plain sailing however. I hadn't realised just how old Win7 has become until it was time for the updates.

The first installment was a hefty bunch of 77 updates, followed by another 12, then SP1 and finally a handful of updates after that. This operation, unfortunately, took over 3 hours if one includes the 5-6 reboots required.

Nonetheless, the monitor's touch device installed with no issues and the same was the case with ATi's X600 GPU. I also briefly used a wireless USB dongle just to make sure that I would have remote data should I ever need it, after installation. Again, no need for drivers and everything worked out of the box.

Edubuntu
I will start work on installing Edubuntu today and hopefully things should be quicker than Windows at the early stages (although I have a creeping fear that eventually I'll end up tweaking and configuring much much more than I would have to in Windows).

Wednesday, 25 May 2011

Interactive Play Terminal - Hardware and (Basic) Software

Having previously established that professionally made kiosks were beyond my means ($500 budget, remember?) and regarding kids apps on a tab too feeble a solution, I chose the natural path of a computer and a touchscreen monitor. In this post I'll go through my choices as well as other available options to anyone thinking of attempting a similar job.

  • Hardware
Our hardware considerations are primarily driven by the apps to be ran on the kiosk. As most of them are very spartan in their requirements, let's look at the operating systems requirements. Our two options are Windows and Linux (Mac's O/S's are not meant to run outside Apple hardware so I left it out altogether). Surprisingly, even Windows 7 (the most touch-friendly  version at this point in time) has remarkably low spec requirements. Briefly:
  • Windows 7 (Home Premium):
    • 1GHz 32-bit CPU (OK, here Microsoft is getting ridiculous as 2+ GHz is more like it but it's indicative of the point)
    • 1 GB RAM
    • 16 GB HDD space
  • Linux (Edubuntu)
    • 1GHz 32-bit CPU
    • 512 MB RAM (1 GB recommended)
    • 20 GB HDD space
    • OpenGL hardware acceleration GPU for 3D effects (optional)
Looking at the above, it's pretty clear that any PC of the last decade (i.e. going all the way back to 2002) would/could suffice. On a related note, any laptop from the last 5-6 years would also cut it (3D and hardware acceleration could be patchy due to Intel's old(er) GMA's that weren't too focused on graphics power at all).

In my case, as with many other projects, I went to the "scrapyard" of our company's IT department and started a rummage through. It's incredible what dated hardware one can find in a company's "unwanted" piles. In my case, I was given slim desktop recently decommissioned after 6 years of hard slog. So here's what I got for free:

Dell Optiplex GX620

 Here's what this little gem came with (apart from a lorryload of cemented dust):
  • 3.0 GHz P4 (Yes, there used to be a Pentium line and they tended to be pretty good at the time)
  • 2 GB of RAM (I know, it's the slow-go DDR2 variety but multitasking isn't a factor here)
  • 80 GB HDD (Yippie, enough space for a couple of partitions)
  • An X600 ATi GPU (Although produced in 2004, t still works with Windows Aero and Unity's Shell)
Probably not a very modern box but it will do nicely. As I wrote above most 5-year old laptops would be able to do the same while providing a more compact form factor. I'd personally gravitate towards an old laptop, however, given that the box came for free, I couldn't resist it.

Screen

The screen  is meant to be the only interacting device so it needs to be touch-capable (multi touch is a bonus although depending on age, single touch may be more appropriate at the start). It also needs to be supported by the underlying O/S's be it Win or Linux. Ideal size for such a screen would be anywhere between 14" and 19".

I looked through several examples and must conceed that 3M's screens are the most widely supported and adopted by the industry. However, the normative word here being "industry" it also means exorbitant pricing. A 3M 15" touch monitor could set you back as much as $500 alone!  It certainly delivers on important points like chemical and weather resistance as well as having a solid warranty for 3 years. However, this is no POS terminal and costs have to be kept in check.

I then turned to consumer touchscreens which have begun to trickle into the market. With some astonishment I realised that consumer touch displays don't come in small sizes. There's virtually no consumer (i.e. affordable) touchscreen monitor below the 21" size! Again, with the primary focus on costs, I turned to HP's 2310ti which is a massive 23" screen with fullHD which is certainly overkill spec-wise, until one sees that these babies go for just under $300.
HP 2310ti



Other interesting tidbits of this screen:
  • Certified to work on Win7 with multi-touch
  • Has been reported as working with Ubuntu's Natty (11.04)
  • USB connector for the touch interface
  • Integrated speakers (quite important if you don't want to shell out for extra speakers)

  • Software
I intended to use both Win7 and Edubuntu (Ubuntu's Education-focused distro) for different reasons for each. For example:
  • Win 7
    • Any and all  BIOS upgrades on the Dell box can only happen via Windows (or fiddling with USB sticks)
    • Certified multi-touch out of the box
    • Group Policies enabling flexibility on set-up user accounts and layouts
    • Many games are Windows only (although I fail to see why!)
  • Edubuntu
    • A Linux distro specifically targetted at educational environments (and that's what the aim of this project is, to be educational instead of nonsensical)
    • Variety of ready made tools for administration and management
    • A multitude of packages aimed at toddlers to play with
    • Natively running all of Android apps (there seems to be an explosion of kid-friendly apps and Linux is the best place to exprience them)
    • Significantly leaner O/S requirements
Right now, I'm in the process of installing the two O/S's, backing them up and getting them ready for tweaking. Once I'm done, I'll start the next post on customisation for purpose. While the posts have been  relatively spartan picture-wise, expect many many shots of the ongoing tinkering....

Interactive Play Terminal - Choices, choices

When it comes to this sort of thing there's no lack of choices. From the entirely professional from the likes of Fingabox, Orgacontrol and Protouch all the way to the hotch-potch amateur-ish option of a few kid-friendly apps on one's favourite smartphone or fondleslab.

In this case price is a major factor. The pros will sell you their wares for upwards of $5'000 depending on options which (by my meagre means) immediately sets them outside my reach. It's understandable to want a retail open-to-the-public grade of kiosk for public establishments but the requirements and costs are overkill for a small corner in a living room.

On the other end, I toyed with the idea of a fondleslab with kids apps on it. (I deliberately excluded a smart phone as its screen is too small and the phone too portable). From a price point of view, a decent (read Tegra 2 SoC) tab retails at $500+ that's notwithstanding any further costs for the apps themselves etc. So, I'd shell upwards of $500 and end up with a 10" screen with limited upgrade potential and somewhat limited on the kinds of apps I could install and use.

After the two above, the choice was almost made by itself. Get a piss-poor mini desktop and a consumer touchscreen and that's it!

In the next post I'll go through the hardware options and choices made.

Interactive Play Terminal - The Rationale

So how did the decision to make of those interactive kiosks at home, came about?
Well, as anyone with a touchscreen device and a baby/toddler can attest, young ones just take to touch interfaces a lot more naturally than with keyboards or mice. Mice are too cumbersome, and the link between mouse and pointer movement is not immediately apparent.

I've watched my and  many other toddlers, become glued to the screen and pay no attention to the vast colourful playground around them. Understandably, sceptics would say the classic "Do we want our children glued to the screen?" Certainly not! But on the other hand, I'd rather what time they do spend glued to a screen was not fiddling around with things they could break or play angry birds ad infinitum. (Or worse, watch TV like couch potatoes)

Another reason I wanted to publish this series, is that there's precious little on the net on how to go about making such a platform.

So here's my shortlist of priorities in no particular order (thank my ADHD for this!):
  • A reasonable budget (somewhere south of $500 should do it)
  • A completely locked up user environment, i.e.
    • Keeping everything necessary locked and/or restricted (ideal for a kiosk application)
    • Minimise the grown-up's intervention (I don't want to have to intervene every few seconds, interrupting the toddler's play time, to return them to the proper screen or close inadvertently opened windows)
  •  Touch input solely ( at below 2 years old, a keyboard and mouse are not needed)
  • A variety of instructive and developmental games (one can only play the same game for so long)
  • Physical safety (sturdy, stable enclosure, elimination of wires, electrical safety, grounding, splash resistance etc )
  • Easily monitored (The control-freak dad in me will elaborate on this later)
I think this just about covers all important considerations. Although if you think I've missed something, please comment.

The very first

   Hello to all of you out there whoever you are (well, mostly bots, but I digress...).
I have been toying with the idea to start a blog for a while but due to the joys of parenthood and the added bonus of ADHD I haven't come round to it yet.

So what's this blog going to be about? I do have some ideas but how these will evolve and fuse into the final outcome is difficult to tell yet. As the title goes, I've been a tinkerer all my life (although I was a serial destroyer during my younger years), and I like to make and put stuff together to make life easier for me and my long-suffering family. I'm much into computers and technology in general but approach the whole thing from a "dumb user's" perspective i.e. while I love to understand how things are done, I consider them well made when knowing anything about their construction is unnecessary. "Convoluted", I hear you say? Probably, in a nutshell, I love technology but the ultimate tech is as K.I.S.S. as possible.

I intend to write about all the little (and not so little) projects that undertake every now and again as well as to share interesting tidbits of info from wherever I come across them.

So to start with, I intend to report on the latest little project I embarked on, a home-made, interactive kiosk for a curious little toddler of 18 months. You have probably come across the type in the play areas of restaurants and other public places. Here's what the professional trade quivalents look like:
(c) Fingabox, www.fingabox.co.uk
(c) Orgacontrol, www.orgacontrol.net
So, let the journey begin, read on for all the funny, frustrating and instructive moments to come....