IoT development (APIcon 2014 presentation)
•Télécharger en tant que PPTX, PDF•
2 j'aime•1,563 vues
An overview of the Eclipse IoT projects, and IoT in general. Examples of development tools and frameworks for Java, JavaScript, and Lua.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (8)
Similaire à IoT development (APIcon 2014 presentation)
Similaire à IoT development (APIcon 2014 presentation) (20)
Plus de Mike Milinkovich
Dernier
Dernier (20)
IoT development (APIcon 2014 presentation)
- 1. Developing for the Internet of Things Mike Milinkovich Executive Director, Eclipse Foundation & IoT Hobbyist APIcon – San Francisco May 28, 2014
- 2. Major Caveat! Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.02
- 3. Major Caveat! Please pray to whichever deity controls the wireless at the Hilton for its blessings on this talk Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.03
- 4. Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.04
- 5. Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.05
- 6. IoT Today Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.06
- 7. It Is Complicated! OEM Enterprise Applications Devices Vendor 1 ? ? ? ? ? Wireless Services Vendor 2 Backend Server Vendor 3 Developer A Developer B Developer C Machine ERP Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.07
- 8. It Is Complicated! Consumers Devices Vendor 1 ? ? ? ? ? Wireless Services Vendor 2 Backend Server Vendor 3 Developer A Developer B Developer C Machine Solution Vendor4 Solution Vendor5 Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.08
- 9. I want the internet of MY things Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.09
- 10. Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.010 silos
- 11. http://www.flickr.com/photos/brunauto/5687363705 fragmentation 11 Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.0
- 12. lock-in http://www.flickr.com/photos/photosightfaces/8152791780/ 12 Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.0
- 13. http://www.flickr.com/photos/90514086@N00/952121271/ http://www.flickr.com/photos/cyberslayer/952121271 complexity 13 Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.0
- 14. Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.014
- 15. Open Ecosystem IoT Third Party Ecosystem Open IoT application framework and runtimes Open IoT communication protocols Internet of Things Open IoT development tools … $ $ $ $ $ $ Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.015
- 16. Open Wins Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.016
- 17. Developer Engagement Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.017
- 18. Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.018
- 19. Open Wins Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.019
- 20. Open Hardware Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.020
- 21. protocolsframeworks tools Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.021
- 22. CoAP Lightweight M2M ETSi M2M Wakaama OM2M protocols Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.022
- 23. Sandbox Servers http://iot.eclipse.org/sandbox.html Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.023
- 24. - Java and OSGi based framework for IoT and M2M Gateways - Java and OSGi based framework for home automation integration - Java and OSGi based framework for building SCADA systems - Bridge between HTTP, MQTT and CoAP (JavaScript and node.js) - Lua based framework for building M2M gateways frameworks Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.024
- 25. tools Lua Tools Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.025
- 26. BUILDING BLOCKS FOR IOT Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.026
- 27. BUILDING BLOCKS FOR IOT … for building what? Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.027
- 28. Cloud by Andrew Lynne from The Noun Project Thermometer by Lemon Liu from The Noun Project Fluorescent Light Bulb by Dmitriy Lagunov from The Noun Project Water by Gilad Fried from The Noun Project Mosquitto broker Building… SENSOR NETWORKS Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.028 MQTT Network
- 29. Demo #1 Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.029
- 30. Arduino Sensors Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.030
- 31. USB Modbus ArduinoRaspberryPi Lua + Mihini Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.031
- 32. USB Modbus MQTT ArduinoRaspberryPi Lua + Mihini 802.11n Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.032
- 33. USB Modbus MQTT ArduinoRaspberryPi Lua + Mihini Koneki – Lua development tools 802.11n Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.033
- 34. USB Modbus MQTT ArduinoRaspberryPi MQTT Lua + Mihini Koneki – Lua development tools 802.11n Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.034
- 35. Ponte broker CoAP Network Building… SENSOR NETWORKS (2) Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.035 MQTT Network
- 36. Cloud by Andrew Lynne from The Noun Project Thermometer by Lemon Liu from The Noun Project Fluorescent Light Bulb by Dmitriy Lagunov from The Noun Project CoAP Network LWM2M server (e.g. OM2M, Leshan) wakaama wakaama wakaama Building… DEVICE MANAGEMENT battery level avail. memory … firmware reboot … Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.036
- 37. Android UI X10 Serial … Bluetooth Building… HOME AUTOMATION ZigBee Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.037
- 38. USB Modbus MQTT ArduinoRaspberryPi MQTT Lua + Mihini Koneki – Lua development tools MQTT Android 802.11n Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.038
- 39. Not A Great Tooling Experience + Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.039
- 40. My Real World Problem Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.040
- 41. Cottage Monitoring Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.041
- 42. My Real World Problem First Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.042
- 43. tools for the web on the web code.everywhere = true; Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.043
- 44. The Orion Project: A Browser Based Open Tooling Platform Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.044
- 45. Why and What is Orion? Initiated a little over 3 years ago A change from other Eclipse projects A shift to Web based application delivery The Web is the Platform Complex IDEs replaced by Web workflows Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.045
- 46. OrionHub (Demo #2) Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.046
- 47. + Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.047
- 48. + Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.048
- 49. Simple Server Code /** MQTT client configuration **/ var mqtt = require('mqtt'); var mqttClient = mqtt.createClient(1883, 'iot.eclipse.org'); mqttClient.subscribe('/ottylake.net/cottage/sensor/command/#'); var parseSerialInput = function(data) { console.log('--> data received: ' + data); try { var parsedData = JSON.parse(data); for(var key in parsedData) { mqttClient.publish('/ottylake.net/cottage/sensor/data/' + key, '' + parsedData[key]); } } catch (e) {} }; Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.049
- 50. Hacking My Cottage Demo Orion & IoT (Demo #3) Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.050
- 51. Serial ArduinoRaspberryPi MQTT Android MQTT 4G Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.051
- 52. Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.052
- 53. Get Involved! • EclipseCon France – June 18-19, Toulouse • EclipseCon Europe – October 28-30, Stuttgart • EclipseCon North America – March 9-12, SFO Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.053
- 54. Thanks! Mike Milinkovich mike.milinkovich@eclipse.org @mmilinkov Code at https://gist.github.com/mmilinkov/public Learn more: – iot.eclipse.org – eclipse.org/orion – orionhub.org Copyright (c) 2014 Eclipse Foundation, licensed under the EPL-1.054
Notes de l'éditeur
- So I am sure that everyone has heard of the Internet of Things. In fact, it’s pretty hard to avoid hearing about it these days.
- But when you start throwing around trillions and trillions of dollars, you’re going to attract every shyster, carpetbagger and Sand Hill VC to your adventure, and IoT is no different.
- But the reality is that today IoT is in its infancy, and in fact so far the baby has colic. -
- In particular, the level of complexity is very intimidating. To put together a solution, an IoT vendor needs to work with a lot of very different companies across the various tiers.
- From the perspective of the consumer it is even worse. Most of the solutions we’re seeing today in IoT are closed, and vendor specific. Nest being a pretty good example of what I’m talking about.
- The IoT is going to be enabling greater and greater influence of machines over our lives. It is super important for our personal privacy and liberty that we put the individual at the center of the IoT. It will be critically important that the key infrastructure of the IoT be open. And by open I mean open source, not the kind of walled garden “open” that the world of telco standards lives in.
- Lots of proprietary silos. Proprietary SDKS, proprietary protocols, proprietary solutions
- We need to get to an open ecosystem of IoT technology based on common frameworks, protocols and tools. Companies needs to make their money building value add solutions on top of these common technologies. Openness does not mean no profit. A lot of profit has been made by using the common Internet technology. However, the profit has been made after a common set of Internet building blocks were in place. Ex. Apache Web Serve and Linux run the Internet.
- Openness will always win over closed proprietary. This is especially true for technology that is expected to be broadly adopted. In fact the Internet was created on open standards and open source software. There are enough cases studies and proof points that technology based on the principles of openness make it much easier and faster for technology to be adopted. It is the transactional costs of proprietary solutions, ex bi-lateral agreements, purchase costs, competitiveness that limit adoption of technology.
- Two trends I think will help drive an open IoT ecosystem: 1. Developers are getting engaged and they will select open solutions. IoT is fun for geeks but they don’t have the money or time to navigate proprietary SDKS or protocols. They won’t tolerate it. They will migrate to open solutions.
- There has been a very important trend in the last 5-10 years that can’t be ignored in any technology industry and that is the importance of developers. Gone are the days of the top-down sales and procurement approach to technology distribution. Developers have become incredibly important in determining the success of new technology. If a technology is embraced by a large developer community the adoption of the technology will increase. A recent book by Stephen O’Grady documents the rise of the importance of the developer. His point is that developer are certainly the New Kingmakers for technology adoption.
- Another example in the software developer area was the Web Services vs REST protocols and styles. Clearly REST has won over Web services. The lesson here is that developers are picking technology winners these days, and they clearly prefer open source choices. It will be very interesting to watch the collision between the reality of IoT and developer-led technology adoption when it collides with the telcos and industrials how are going to be largely driving the first generation of IoT adoption.
- The second major trend… 2. Open hardware has significantly lowered the barriers for developers to prototype and experiment. 5 years ago it was impossible to have an open source project that focused on IoT. There was no place to run the code. Developers would need to buy reasonably expensive hardware to just test their code.
- Eclipse IoT is initiative to create an open source community and collaboration that will enable an open ecosystem. 13 main open source project now that focus on frameworks, protocols and tools.
- Surprisingly, for an Eclipse-based community there are very few IoT or M2M-specific tools at Eclipse.
- Of course what I really want to be able to do is to be able to hack on my cottage from anywhere in the world. In particular, needing to be physically present to change the code running on my Arduino is a major pain in the backside.
- The initial IBM contribution to Eclipse in January 2011 Externally you can see this in Google Docs, GMail, Dropbox, Facebook - This is second nature to people now, Latest HTML5 capable browsers and CSS3, JavaScript Virtual Machines are extremely competent. Not all web IDEs follow this model as you’ll see in upcoming slides