One Model to Rule Them All
summary
Describes using Eclipse Vorto to model device capabilities as reusable information models and function blocks, then run platform-specific code generators to produce integration artifacts for Eclipse Paho/Hono and Ditto; demo shows a Raspberry Pi smart scale where about 90% of messaging and serialisation code is generated and ~10% of device-sensor wiring is hand-coded. Claims a model+generator ecosystem plus a shared repository cuts integration time and lets platform providers supply generators for their stack.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:42Multiple Platforms
- 1:15What is a Negative Platform
- 2:45Why is it important to support multiple platforms
- 4:40How do we support multiple platforms
- 5:40Scenario
- 7:00What makes this scenario work
- 8:48Advantages
- 10:30How
- 10:55Bordeaux
- 11:55Volta
- 12:57Information Models
- 13:55Function Blocks
- 19:12Creating an Information Model
- 23:20Platform Specific Integration
- 25:02Bari Integration
- 26:40Python Integration
- 30:25Python Code
- 33:43Modification
- 36:32IOT Platforms
- 38:45Generator
related talks
25mImplementing IoT Architectures with Open Source Software
32mAn Eclipse Automotive Stack for rapid-prototyping Software Defined Vehicles
30mEclipse IoT and Eclipse Edge Native: Making Sense of the Puzzle
54mImplementing IoT Architectures with Open Source
25mModel-Driven IoT App Stores: Deploying Customizable Software Products to Heterogeneous Devices
51mLeveraging Eclipse Sparkplug to Accelerate DataOps and Machine Modeling into AWS Services
38mHow to Tame My Edge Devices?
47mFrom "Can't" to "Can" with Kanto