Peter Kaptein

Hardware is becoming a commodity. Complex machines and powerful electronics that might have cost several thousands of euro’s can now be bought for a fraction of that price.

This development is creating new trends and new shifts in the fields of energy, wireless communication, the production of goods and foods and the so-called “Smart Spaces” which are part of the Roomware Project.

Taking these trends, Peter Kaptein from The Roomware Project will look at the possibilities people are getting for an increase of control, independence and quality in their personal life.

Taking Smart Spaces and domotica, Kaptein will focus on the fields that matter: improving the quality of life for people with disabilities and increasing safety on hazardous places.

Topics are:
- Trends in the next 5 to 10 years
- Do It Yourself Energy
- Do it yourself fabrication (Fablabs, return of craftmenship)
- Domotica and Smart Spaces
- New possibilities due to the increasing speed of wireless networks
- The possible next step for mobile phones: replacing our laptop as a thin client
- Increase in quality of products and goods
- Increase in quality of life
- Increase in safety
- Relevance

Next10 is a leading conference regarding new techbnologies and the web. This years conference will be held May 11 and May 12, 2010

Read more about this in this background article

On the Music and Bits Music Hackday we introduced together with the University of Eindhoven and Joris Zaalberg the first alpha of the Roomware XBee Mediator.

XBee?

An XBee (see image) is a device that uses a wireless protocol to transfer data. It has six analog and four digital ports allowing you to read data from sensors connected to the XBee and send data to other devices (like an Arduino board) to communicate.

Roomware Mediator?

In the new structure with the Roomware Socket Server we decided to separate the intelligence from the Server. In this structure, the server only passes the data and each and every devices “directly” communicates to any other device.

A Roomware Mediator:

1. Understands how to communicate to the device you connect to your Roomware Network Application
2. Understands how to communicate with the Roomware Server
3. Understands how to translate any input into action regarding the device it represents

Two parts

In the setup we chose for the XBee, we have:

1. A XBee Mediator (“Mediator A”) running on a computer, reading the input directly from the XBee’s via an XBee hub
2. A XBee Mediator Proxy running on the other side (“Application B”), representing “Mediator A”.

Writing and reading the pins on each XBee device

For each XBee connected to “Mediator A” a XBee Proxy Object is created in “Application B”, offering all the pins of the original XBee.

All data the XBee measures and broadcasts is directly available on the XBee Proxy Object. Vice versa: when you set the value on a pin on the XBee Proxy Object, this will be reflected on the actual XBee device.

See more about this in this post here.

In our strive to provide an open structure for people to build their own Roomware solutions, we have included Web Sockets (see here for more insight on the subject) into the structure. The next period we will work on adding this to the basic library of solutions.
You can find the current source code for the Roomware server and for the Java Clients here.

No dependency on one technology

With WebSockets, you do not need the Roomware Server or Roomware Socket Server to do your work.

HTML5 now included

Where – until recently – only Java and Flash Applications allowed you to build web based applications capable of using the push-technology of Sockets, by using WebSockets, HTML5 applications will also be able to connect and communicate directly with Roomware Applications

Simple structure, simple deployment

The aim is to make it as simple as possible for users to use any kind of Push-technology like Sockets and WebSockets by offering a ready to go library with which the user only has to state which type of protocol he or she wants to use.

So when defining a Roomware Connection, the choice for your Roomware Applacitions in Java, Flash and .NET will be defined like this:

roomwareConnection.protocol = RoomwareConnection.WEBSOCKET;
or:
roomwareConnection.protocol = RoomwareConnection.UTPSOCKET;

At thursday, November 26, 2009 Peter Kaptein (Instant Interfaces) and Valerie Ivangorodsky (Vivango) of the Roomware Project offered the “Connection point” also deployed for the Cabellero Factory Business Event 2009  and the Music & Bits event last October. The NIMA MEE was held in the Brandboxx in Almere. In total there were over 250 people present that day.

The Nima MEE 2009 presented three finialists x 4 categories (Absolute Excellence, Innovation to the max, Completely Customer Connected and Most MVO).

Nima asked the Roomware project to install the Connection point to enable their visitors (over 250 marketing professionals) to exchange their contact data. The system works by scanning the QR-codes and deciphering them into readable text. When two people show their code the system perceives that as a match and sends an e-mail. Person “A” will receive the contact data of “B” and “B” the contact data of “A”.

This was possible via QR-codes produced by Peter Kaptein and printed on a second badge which could be scanned by the QR-code scanner. The QR-codes contained the full name, the function and the e-mail address of the person. There were more than 30 e-mail exchanges between people.