What's Your Pi Plan??

My plan is to use RasPi for ... everything.

It's the first Linux device with Ethernet at a price that makes it viable to "buy a ton of them, use one per task".

Among the candidate applications:

- Home automation, networked controls and sensors on everything from lights to appliances (currently use X10).

- Home security, all PIRs, door and window triggers and the alarms networked and calling out to cellphone.

- Home entertainment, with the usual XBMC or MythTV in the living room and slave nodes around the house.

- High level access/monitoring of 3D printer (low-level realtime control is done by a dedicated microcontroller).

- Thin client workstations in all rooms, linked to the main home computer systems.

- Voice recognition and control, recognized commands routed to wherever is appropriate over the network.

- Servers for many different things, one RasPi per application:  for example a wiki for my cooking recipes.

- Experimental RasPi clusters.  I have a background in parallelism and concurrency, this is going to be fun.

- Music making, controlling my many dumb MIDI devices and giving them a level of musical intelligence.

- Open gaming system.  It's early days in this scene, but with millions of RasPi around, the day will come. :-)

And so on ...

My plan is to use RasPi for ... everything.

It's the first Linux device with Ethernet at a price that makes it viable to "buy a ton of them, use one per task".

Among the candidate applications:

- Home automation, networked controls and sensors on everything from lights to appliances (currently use X10).

- Home security, all PIRs, door and window triggers and the alarms networked and calling out to cellphone.

- Home entertainment, with the usual XBMC or MythTV in the living room and slave nodes around the house.

- High level access/monitoring of 3D printer (low-level realtime control is done by a dedicated microcontroller).

- Thin client workstations in all rooms, linked to the main home computer systems.

- Voice recognition and control, recognized commands routed to wherever is appropriate over the network.

- Servers for many different things, one RasPi per application:  for example a wiki for my cooking recipes.

- Experimental RasPi clusters.  I have a background in parallelism and concurrency, this is going to be fun.

- Music making, controlling my many dumb MIDI devices and giving them a level of musical intelligence.

- Open gaming system.  It's early days in this scene, but with millions of RasPi around, the day will come. :-)

And so on ...

Morgaine Dinova wrote:

 

...

 

Among the candidate applications:

 

...

- Experimental RasPi clusters.  I have a background in parallelism and concurrency, this is going to be fun.

...

Yes! A cluster of RPi's :-)

I want to do this as well - would be great for experimenting with parallelizable algorithms, distributed <whatever> systems... How often do you get the chance to test the stuff you write on a cluster of machines? Not often in my world - with the RPi I can easily set up 10 machines and start experimenting :-)

Cool stuff!

Jesper Juhl wrote:

 

Morgaine Dinova wrote:

 

...

 

Among the candidate applications:

 

...

- Experimental RasPi clusters.  I have a background in parallelism and concurrency, this is going to be fun.

...

Yes! A cluster of RPi's :-)

I want to do this as well - would be great for experimenting with parallelizable algorithms, distributed <whatever> systems... How often do you get the chance to test the stuff you write on a cluster of machines? Not often in my world - with the RPi I can easily set up 10 machines and start experimenting :-)

Cool stuff!

About the ARM11 architecture: it is not designed for large calculations even an intel atom will probably outperform the processing power of 10 Raspi's see http://infocenter.arm.com/help/topic/com.arm.doc.ddi0333h/index.html..

ed, your answer to Jesper and myself seems to imply that you equate clusters with High Performance Computing.  Well some clusters are used for HPC, certainly, but that's not all a cluster can do.  A cluster is a general purpose computing architecture that can run any program that doesn't require shared state between processors, since the nodes of a normal cluster share no memory.

There are countless non-HPC applications that can run on clusters.  For a start, any application that runs on a single machine but wants a backup node in case of failure, or which wants multiple replicas for load sharing, can be run on a cluster.  In these cases there is still a 1:1:1 mapping between a user, an application and a processor, so there is no concurrency in the actual application.  Clusters work fine in such a role, and are simple to configure.

More ambitious non-HPC cluster applications are those which can harness the parallelism available in a cluster to speed up the application (as in HPC), or to give the application high availability through redundancy, or most recently, to run applications in fully concurrent but non-SMP languages.

The latter are becoming quite popular nowadays.  Erlang has been in use for decades for writing applications that demand extremely high availability, and the same Erlang program will run happily on single core, multicore, or on clusters, making use of as many cores as are available.  Many other concurrent languages have joined Erlang recently as a result of the "multicore revolution", including Scala, Clojure, Haskell, F#, Go, and lots of others, and most of them run as happily on clusters as on SMP multicore systems.

There's a lot of fun to be had with clusters outside of HPC, and Raspberry Pi is certainly a viable candidate for it.

My plan now is to just forget about it.

We were wound up and presented with an impossible situation, told to set our closks for a really early time and the websites crashed.

All this for what is actualy a prototype board that was not laid out taking everything into consideration.

No mounting facilities, connections at all sorts of levels and now does not even meet basic standards for selling it in the UK.

And to top it off, I have not even had an expected delivery date let alone if my order will actually be filled this side of May.

I give up - I'll find something else to occupy my time and buy one when the next version is actually available to order and receive within the same week/month.

So given that background on the pi, forget about it is my plan.

While you're factually correct, MattyLad, it's not the end of the world.  Those of us who have been around for a long time recognized the ultra-hype early on and ignored it during the long Rpi gestation, in the same way that we filter out advertising on roads automatically.  You and many others were taken in by it, which is unfortunate.

Rpi is on a sounder footing now, with volume production being organized and proper certification carried out.  Every engineer can tell you when the device will be available:  when it's ready.  All other answers have been supplied by promoters and fanbois, the promoters for very worthwhile motives (education), and the fanbois for ... well just because they're fanbois, and thinking doesn't apply.

In due course the boards will be in stock at the two distributors, and everything will be hunky dory.  Until then, I suggest not to get agitated by what remains of the hype and wishful thinking, just sit back and let the project unwind until the nice little board becomes available ex-stock without order size restrictions.

That's when interesting things will really happen, when there are hundreds of thousands of Rpi out there, not now in 1st-batch and pre-ordering days.

Morgaine.

here, here Morgaine. Couldn't have put it better myself!!

When I first saw the RPi, home automation was one of the first things I though of.  It's such an inexpensive but powerful device.  I like your thinking