Tag Archives: devices

M2M Community at EclipseCon

Day 2 of EclipseCon 2013 and we’ve already been seeing some strong interest in the M2M community and the kinds of projects we have been working on!

The story so far

There were two Β M2M events on day one. The first was the M2M tutorial featuring some real hardware (Raspberry Pi and Arduino), using the Koneki Lua Development Tooling to deploy scripts to the embedded Mihini runtime on the Pi to drive and take input from sensors over Modbus. I cheated a little and mixed in a bit of MQTT using the Paho Lua client, to have my kit publishing temperature and light data to a broker instead πŸ™‚ It is early days for Eclipse Mihini, but it was a really slick demo and tutorial, and I’m looking forward to playing with this a lot more.

The evening Birds of a Feather session gave a group of us a couple of open hours to hack around with our Pi and Arduino kits. My own efforts were slightly thwarted by a European soldering iron and a 110V power supply, so I wasn’t able to assemble the add-on board I wanted for my Raspberry Pi, but I’ll get back to that in the future. For those looking to explore their new Raspberry Pis and hardware / GPIO interaction from Java, take a look at the pi4j project.

Building a community

One useful “war story” that was told today was in Benjamin CabΓ©’s Building the M2M Community talk. The slides will follow, but it was good to hear about the progress of the community and projects involved (yes, ok, I’m a Committer on one of them…) and also to hear about his “Community Manager Toolbox” for tracking and responding to community discussions. I use a very similar set of tools when I engage with the Cloud Foundry and MQTT communities (and others that I’m involved with).

Here’s a summary:

  • Slideshare – monitor who favourites and downloads slides related to your project
  • Twitter – monitor hashtags, engage complainers
  • YouTube – screencasts, demos, build channel to aggregate content
  • StackOverflow – answer questionss (even old ones), find answers that need to be complemented)
  • Github – monitor forks, stars, look for people using your tech (include Gists)
  • Google Alerts
  • IFTTT – e.g. if Eclipse wiki changes get Gtalk notification recipe
  • Google Analytics for your site
  • LinkedIn – monitor groups, post news and relay blog posts

In short: Engage the community. Be very public about what you are working on and where the roadmap is going. Get management buy-in for your projects to persuade them of the value of opening them to the community (use metrics to demonstrate take-up).

Working on standards

The other thing that has been going on today “behind the scenes” at EclipseCon has been the first meeting of the OASIS MQTT Technical Committee. It is exciting to see that Richard Coppen and Raphael Cohn have been elected as co chairs of the group, with seven sponsoring organisations from across the technology and messaging market and 35 publically-visible members – lots of interest in MQTT!



MQTT goes free – a personal Q&A

There has been a lot of coverage over the past couple of days of some exciting announcements that I’ve been involved with at work. I’ve spent the past three days at EclipseCon Europe 2011, which doubled as the 10th birthday celebration for the Eclipse initiative. It was a funny feeling, because Eclipse started just a few weeks after I first joined IBM, and although I’ve used it and watch it “grow up”, I’ve never done EclipseCon before. The reason I’ve been out there for three days this time (as a WebSphere Messaging guy rather than a Rational tooling or build person, for example) was to get involved with activities around these announcements.

It’s all about machine-to-machine (or M2M) communications, Smarter Planet, and the Internet of Things.

Before I dive in to this, a few clarifications. First, I’m being described in a couple of news stories as “an IBM distinguished engineer”, and whilst I wish that was true, I’ve yet to ascend to those heights! Also, there are various numbers being quoted – note that the figures in the press release were not invented by IBM, the headline number of an expected 50 billion connected devices by 2020 comes from a recent study conducted by Ericsson AB. Oh, and this isn’t about a “new” protocol – MQTT has been in use since 1999.

The other clarification is that some articles seem to suggest that IBM is out to create some kind of new, alternative, Web – that’s not what has been announced, and I’m certainly not aware of any such plan! It’s about connecting “things” – sensors, mobile devices, embedded systems, even small appliances or medical devices for example – to the Web and the associated platform and ecosystem of technologies, not about reinventing or recreating them. I’m personally a huge fan of the Web as a platform πŸ™‚

Oh, and of course, the obligatory “all opinions expressed are my own” – this is my understanding of where things are going, although of course I’m talking about events I’m directly involved in!

So what is this all about?

Two things.

1. On Nov 2, IBM, Eurotech, Sierra Wireless and Eclipse formed a new M2M Industry Working Group at Eclipse. Sierra had already started the “Koneki” project at Eclipse to work on M2M tools, and the Working Group will look at a range of topics together, such as M2M tooling, software components, open communication and messaging protocols, data formats, and APIs.

2. On Nov 3, IBM and Eurotech announced the donation of their C and Java clients for MQTT to a new Eclipse project called “Paho” which is under proposal in the incubator – with code expected to hit the repository within the next couple of months. MQTT is being given to Eclipse to live within the M2M ecosystem that is emerging there, and to provide an avenue for adoption of the protocol as a more pervasive standard for connected devices.

How is that news? Isn’t MQTT already open / free?

Technically… kinda, sorta πŸ™‚

The MQTT specification has been published under a royalty-free license for some time, and that has led to a fantastic community contributing a range of different projects. IBM and Eurotech took this approach from early on, because it wouldn’t have been possible to compile and support code on every embedded platform that might come along – far simpler to set the protocol free.

Initially the specification was hidden away in the WebSphere Message Broker documentation, but last year it was republished, moved to a new home on developerWorks, and the license was clarified.

In August, IBM and Eurotech announced their intention to take MQTT to a standards organisation. The specific organisation has not yet been finalised, but this is also an important step in ensuring that MQTT is not “just” an IBM protocol, but something of general use which the community can feel comfortable with. If you’d like to join that discussion then there’s a Get Involved page on the mqtt.org community site.

The missing piece was code – a reference implementation, if you like. That’s one reason why the Eclipse Paho announcement is significant.

Why else is this significant?

Well, here are some of my musings on that one:

  • it shows IBM is serious, by committing code and open sourcing it (as with the original Eclipse donation in 2001);
  • the M2M Industry Working Group exists to foster the discussion in this space;
  • it makes high-quality reference Java and C client implementations freely available in source form, with a good Java implementation something that has been particularly lacking;
  • it creates an opportunity for Eclipse projects to use MQTT, and to develop tools on top of it.

The press release and Paho project proposals aren’t clear (to me) – what exactly is being donated?

IBM is seeding Eclipse Paho with C and Java client implementations of MQTT. Eurotech is donating a framework and sample applications which device and client developers can use when integrating and testing messaging components.

Why C and Java clients (aren’t they “dying” languages?) Where’s my Perl and Ruby code?!

IBM had previously made some C and Java code available in some SupportPacs, but those are outdated and the license for reuse was never clear.

It’s important to realise that this stuff came from the embedded world of 10 (and more) years ago, and continues to be applied in that industrial space. That category of device typically runs some kind of realtime Java-based OS, or a Linux-based or other runtime with a GCC toolchain for the CPU in question. C and Java are genuinely the most useful implementations to get out there. Oh, and on that “those old languages” thing – I think you’ll find they are very widely used (Android, iOS etc run variants of sorts, most non-web app development is likely to be in one or the other).

We’re very fortunate that clients libraries for a wide range of languages already exist thanks to the MQTT community – see the list at mqtt.org!

Hold on… don’t we need a broker / server / gateway?

Yes. But, one step at a time! πŸ™‚

There are brokers available for free today, either as precompiled binaries or as full Open Source implementations, so this is not a dead end from day one.

The Paho project scope outlines the intention to add a broker to the project in the future, and to host an M2M sandbox for developers as well. That is where we are today, and this position will evolve over time.

Why Eclipse?

10 years of Eclipse The Eclipse Foundation has been a fantastic success story (oh, and, Happy 10th Birthday, Eclipse!). As the scope of their mission has broadened beyond an IDE to the web, build environments, and all kinds of other tools, it was a good place for Sierra Wireless to kick off the Eclipse Koneki M2M tools project, and is now a natural place for this primarily M2M protocol to be hosted under Paho. As James Governor notes in his write-up of the news:

… the Eclipse Public License is designed to support derivative works and embedding, while the Eclipse Foundation can provide the stewardship of same. One of the main reasons Eclipse has been so successful is that rather than separate software from specification it brings them together – in freely available open source code – while still allowing for proprietary extensions which vendors can sell.

How quickly will the code donation happen?

The Paho proposal tentatively includes dates in November and December 2011 – there will need to be various approvals as code is accepted into Eclipse, so that may “flex” a little, but it is all in the pipeline.

OK… Why MQTT? Why not HTTP/XMPP/AMQP/PubSubHubbub/WebSockets/etcetcetc?

To answer this one adequately I’d probably end up addressing each individual difference between protocols in turn, and if you’ve heard me speak about MQTT I’ve covered some of this before – so I’ll keep this answer relatively brief. I will admit that I’ve been asked about all of these by journalists in the past couple of days.

There is space for a range of protocols to coexist, because they address different areas. In the messaging space, we’ve found over time that whilst efforts to create a single protocol have been made, that has often ended up as focused around a particular set of qualities of service, and not optimised to cover the the whole range of them.

For example, if we look at IBM’s own messaging protocols – there are several. There’s WebSphere MQ which is all about reliable, transactional, solid, clusterable, enterprise, JMS and other APIs, etc etc.. WMQ itself isn’t ideal for very high-speed in-memory or multicast scenarios, so there is also WMQ Low Latency (interoperable with the new multicast feature in WMQ 7.1, but a separate protocol). Neither WMQ LLM or WMQ scales down to unreliable device networks and embedded systems, so there is WMQ Telemetry (aka MQTT), which was specifically designed for constrained devices and networks, and that can interoperate with the main queue manager, too. Oh, and sometimes you want to deal with files (WMQ File Transfer Edition), or access message data via HTTP (WMQ HTTP Bridge). You need to address a range of requirements in a messaging story.

So why not those others? In this case, IBM believes that MQTT is ideally-suited to the Smarter Planet Instrumented->Interconnected layer – it’s tiny, not synchronous and brittle, isn’t specific to the web as it is all about data rather than documents, XML etc etc. In these scenarios, REST principles may add an overhead. Oh, and it has been around for over 10 years, and has been proven across a range of industries and in a range of extreme conditions. IBM’s commercial implementation is known to scale to hundreds of thousands of connected devices, and we know that is the direction that this space is heading.

Congratulations! / Thank you!

Thanks, but don’t congratulate or thank me! I’m familiar with this stuff, I’ve coded with this stuff, but I didn’t invent it and I didn’t write it. There are some amazing folks at both IBM and Eurotech (and some who have moved on) who started this all off in 1999, and who have helped to implement solutions using this protocol since then, and who have of course developed it. Several of them are on Twitter if you want to say hi! And huge thanks again to the community of folks that formed around mqtt.org and contributed client and server implementations – that absolutely helped to move things forward to this point.


That, hopefully helps to clarify a few things and answers some of the questions I’ve seen via Twitter, forums, and mailing lists over the past few days. It has been something of a blur, to be honest, but a lot of fun. I’m looking forward to the next stage – working with the community more, working with our friends at Eurotech, Sierra Wireless and elsewhere, and making the M2M space much more real.

For more, here are a bunch of stories I’ve seen in the past couple of days… no particular order, just my cut-and-paste list!

Haptic fantastic

Yesterday I got the opportunity to play around with a haptic device, which basically provides a force feedback / touch user interface to various 3D technologies. These included navigating a virtual world, and building 3D objects. I’ve written about it more over on eightbar, but it was so cool that I wanted to include the video over here as well.

Just to explain what is going on in the video, as it may not be entirely clear! The demos use a Novint Falcon gaming controller. To quote Anarkik, it is “like a small grounded ‘robot’ and provides the ‘force feedback’ that gives the uncanny sense of touching a virtual object. This device replaces the mouse and also provides more natural and coherent movement in 3 dimensions.” At the start, several of us have a go with the controller to drive an avatar around an OpenSim island running on the local machine, using Anarkik’s software. Around the middle of the video, we switch to using the Cre8 tool to do some simple modelling. In particular, we change the surface hardness of a sphere (where it becomes more or less soft to the touch); and then go inside the sphere and extrude the shape by pulling the controller around. Finally, there’s a brief look at some fabricated items modelled using the same software.

By the way, this was another clip edited with iMovie 09, which I’m increasingly impressed with – I need to do a screencast to show some of the nicer more advanced features that I’ve discovered! πŸ™‚