Summary: CM11 is possibly being discontinued so my work is on hold.
Details:
The CM11 serial interface spec is kicking around on the net, including wiring. The cable required is smaller than the XM10. But I just hacked the cable that comes with the CM11 (serial cable not usb). I wrote some Java code to test it, but had problems with spurious messages. I then attached it to an Arduino and wrote some code using both soft serial (2 versions) and hard serial for communicating with the device. Eventually I was able to make some sense of the protocol, but I was still getting extra characters being sent. Tip: there are also quite often some ‘device lost power messages’ that need to be responded to and I think battery things too.
Next I hooked up the CM11 -> arduino -> ioBridge SB. The reason for this is a bit complicated. Basically the CM11 protocol is quite chatty. Currently the ioBridge doesn’t support response messages on the Serial API. So when you receive a message you need a variable serial message widget to be able to send the response. So I tried to use the arduino as an interceptor. The whole thing was a bit fragile, so I decided to wait and see if the ioBridge crew will support response message on the Serial API. There was also talk at the of ioBridge implementing something 2 way. Then I found out the CM11 had been pulled anyway. The replacement part is USB based which means starting from scratch again. Sure I can buy a USB->serial board, and request the extended protocol docs, but I’m starting to realise that this is going to be well beyond most of my targeted client base.
I think for this to work properly it would be better as a smartboard talking to the X10PRO-PSC05 or the CM15Pro (recommended CM11 replacement). Or even the existing supported XM10 which the ioBridge x10 SB currently talks too, is a 2-way interface. So maybe it could be a firmware update?
