Archive | IOTOPE:node RSS for this section

IOTOPE for Android

Worried that it’s a bit quite on the IOTOPE front. We’ll don’t be. We hard at work evolving the platform. What’s more exciting is that we will have our first “in the field” roll-out of the technology in November. I can’t say a lot about this particular case yet, but I can tell you a bit about how it will impact the platform.

Two important building blocks are still missing for this particular use case:

  1. NXP Mifare Classic read/write support
  2. An Android application
  3. The server

As the server here is of minor importance we’re concentrating on the Android and Mifare Classic support. Both are developed in parallel. But the nice thing about the Android platform is that you can reuse our Java code we’ve written for IOTOPE:node. So all the Mifare Classic code we’re written for the Android app will also enhance IOTOPE:node.

Because the platform needs to mature, we’re also hardening the code by writing unit test for all the the components. By using the TDD (Test Driven Development) approach it makes it also a lot easier to develop the NFC interactions. You don’t need the actual hardware and NFC tag anymore to add or enhance a feature.

As you see, a lot of work, but we’re excited to see our first real deployment in a few months.


Maintenance release 2 of IOTOPE:node Dry Fish release

The second maintenance release is available for download. The following issues are fixed

– New Application ( to execute external applications )
– More stable poll thread
– Should work out of the box for Mac now

Special thanks for Bert for reporting testing and contributing Mac OS-X fixes.

Download the latest release here:

Welcome Touchatag users

It’s become public, the Touchatag service is closing September 30th, a sad day for the NFC landscape. But loyal Touchatag users probably had noticed that the service hasn’t evolved for over two years. That’s why I started IOTOPE in the first place, to start a new beginning.

An a few months ago we had our first 0.1 release. The is the desktop (serverless version) of IOTOPE. And, yes, you’ll notice the 0. version and it’s certainly not production ready. But it’s ready for the enthusiast to start and play with it. Too give valuable feedback and start building at a bright new NFC future for consumers.

Next week we’ll see a new release that will have a more stable polling thread and we’ll cleanup our repository at github so you can build the complete IOTOPE node distribution yourself.

So if you are a Touchatag user looking for a new home, why not join IOTOPE. Go over to our Google Group and be the first to start the discussion about what you would like to see. And make sure you follow us on twitter (@IOTOPE) and Google+.

Oh, BTW. One more nice thing: IOTOPE will be open source under the relex Apache License.

Bugfix release 1 of IOTOPE:node Dry Fish release

The first bugfix release is available for download. The following things are fixed

– Fixed Windows batch when IO:Node was installed in a path with spaces
– Fixed NPE when the localhost:4242/ui was used without trailing slash
– Fixed Unstable reader when a none-NFC reader was available
– Added Untested Unix/Mac bash script

Special thanks for Barbara for reporting the NPE and reader problem, Bart for supplying the new windows batch file.

First connection between IOTOPE node and server

First message from IOTOPE server

It’s alive, the first tag event has been send from IOTOPE:node to the server in our lab. Although it’s still quite brain-dead it’s always nice to see it’s first movements.

We’re hard at work to define a clean REST interface, so IOTOPE:node can talk too IOTOPE:server, but also make it possible for other systems to integrate with us.

Also expect a small patch on IOTOPE:node with a few bug fixes in the coming days.

First IOTOPE:node Dry Fish release

The first IOTOPE:node release is upon us. If you got the right equipment  (an ACR122 like NFC reader) give it a spin.

Only the Windows batch file is tested, so anyone that likes to contribute the Mac/UX script?

Also make sure to read the README for hints!