Tech insights

IoT devices have a variety of protocols to interact with each other. These include bluetooth, X10, zigbee, insteon, Radio frequency (RF), NFC, Infrared(IR) etc. Traditionally to bridge the gap between internet and IoT,  people came up with Gateway architecture. The devices talk to the gateway using proprietary protocols. The gateway then relays this information on the internet. I call this hammer and nail architecture to highlight the deficiency of the design. One always need both hammer and nail to get started. And since each manufacturer uses his own proprietary protocol and no manufacturer produces all the devices that you might need, one ended up with several gateway devices. And if the maufacturer goes bankrupt or stop producing/supporting those devices, the devices end up as garbage. Additionally, one would like complete control over access to a device restricting usage only to authorized users. Security wasn't a major issue when you had only single device ...

Internet started as a network of computers talking to each other. As evolution goes, each network defined it's own languare for effective communication (targetting a specific purpose) leading to a plethora of protocols like FTP, telnet, SMTP, POP3, IMAP, SNMP etc. This was fine till there were only a handful of hosts providing these services. But how could one talk to hosts if one didn't know about their existence? With number of hosts growing, a need to organize the information was felt. Hence came Archie, gopher and WAIS. However, it wasn't till HTTP or the World Wide Web (WWW) that Internet reached its full potential. Before that, as popular perception goes, computer, and by extension, Internet was only meant for Geeks / programmers. So what was it about WWW that changed how people looked at computers. - It is easy to get started One need not remember the host. One get started from a portal like Yahoo or search engine like google and reach their destinat...

I've started an effort to port mbed API to MSP430 https://github.com/atamariya/mbed . Though mbed is primarily targeted towards ARM, the API is still useful. - The C++ API is very clean promoting understanding and re-usability (e.g. SPI example here https://mbed.org/handbook/SPI ) - Good documentation and community involvement in developing libraries. - Code size and performance are important. However, the first focus is functionality. The good thing is - once performance improvement is done at HAL or API layer, it is immediately available to all the programs using it with just one re-compile.