Six months on, what progress has been made?

Eclipse M2M Industry Working Group making swift progress

Chris Mayer

Half a year on from forming, how far has the Eclipse M2M Industry Working Group gone into providing tools and frameworks for emerging M2M technology? Seemingly very

It’s been around six months since we first reported the collaboration of Band XI, Eurotech, IBM, and Sierra Wireless in the Eclipse M2M IWG, but what progress has been made towards the open source M2M platform?

Well seemingly a lot, according to a recent announcement from the Eclipse Foundation, detailing just what had been done so far towards realising that goal of an open ‘internet of things’ for M2M applications, servers and devices.

Arguably the most substantial building block so far is the Java and C/C++ source code for the MQTT client reference implementation within the Eclipse Paho project. Paho, proposed back in 2011, is a device connectivity project that will ultimately create open source tools to enable smarter machine-to-machine messaging over low bandwidth networks, and deliver emerging requirements of M2M integration with Web and Enterprise middleware and applications. As you can imagine the scope is pretty huge here, but it’s already received industry-wide backing.

Eclipse Paho provides the reference implementation for the MQTT protocol and a MQTT Lua language client implementation has also been proposed by Andy Gelme. Lua is of course an increasingly popular language for embedded devices, so this is logical progression showing some great strides.

But that’s not all. Eclipse Koneki, a similar sort of project provides Lua development tools and an Eclipse-based IDE (similar to the Java one), plus an integrated simulator for the OMA-DM device management protocol. The simulator allows developers to test interactions between a simulated M2M device running in Eclipse, and an OMA-DM server.

Aside from the two projects we already knew about, the industry working group has brought another idea to the table, with the source code for a new M2M application framework being made available. This new framework is designed to provide a consistent workflow for M2M development, and to allow M2M applications to interact with different device types and communication protocols. This expansion is very much welcomed and gives yet further scope to these trio of projects. By creating a consistent framework, we should see interoperability across M2M applications but also connectivity with other messaging protocols.

The potential here is huge for a superb open base for M2M technology, and with tools, frameworks and project all looking strong, we’re sure six months further down the line, we’ll see something in action.

Inline Feedbacks
View all comments