2013-12-10 22:19:06.754005+00 by Dan Lyke 1 comments
If the promised IoT hasn't materialized in 3 decades, maybe the current attention to the possibilities of it is a bit of a bubble?
Spurred by far too many "Internet of Things" and "Machine to Machine" in my Twitter feed, and an exchange between @Columbina and @Medley which led to http://www.mondaynote.com/2013...net-of-things-look-it-must-work/
[ related topics: Interactive Drama ]
comments in ascending chronological order (reverse):
#Comment Re: made: 2013-12-10 23:33:28.088868+00 by: meuon [edit history]
Echelon's NES system is easily one of the hardest things in the world to integrate with. 32char GUIDS for everything via fat XML interfaces and some of the worst internal command queing I've ever seen. Their LonTalk power line carrier protocol is one of the better "power line carriers", see: http://www.lonmark.org/ for a better view, but PLC's (Power Line Carrier) has inherent issues and limits. It works very well in specific circumstances. Hopping transformers, signal loss due to interference, harmonics... On the good side, when implemented properly is has decent security capabilities, which are often turned off on implementation because the people involved find it a hassle to manage keys.
Let me explain, in Echelon NES speak: ERROR = 'f27e59fb29f140c2a62b0167e016bac1' in some circumstances, and ERROR = 'EEA3A69129524261B2873B7E77736B5D' in another and ERROR = '6814825A626A46aaAA7F6AE8252AAA08' in another.. and...
Loads of fun to debug looking at raw data.
Heck, my big accomplishment this morning was figuring out that MTN.bj's cellular network only handles pure 7 bit ASCII. I was trying to send proper French messages, Silly me. Their competitor Moov.bj handles 8 bit ASCII aka ISO 8859-1, which might be a reason they are very popular, and the 2 major cell networks in the country have issues relaying messages.
Digressing more: I want a .bj domain...