FIWARE Global Summit - FIROS: Helping Robots to be Context Aware
•
0 likes•457 views
Presentation by Peter Detzner Automation and Embedded Systems, Fraunhofer-Institut für Material Fluss und Logistik IML FIWARE Global Summit 27-28 November 2018 Malaga, Spain
Recommended
More Related Content
Similar to FIWARE Global Summit - FIROS: Helping Robots to be Context Aware
Similar to FIWARE Global Summit - FIROS: Helping Robots to be Context Aware (20)
More from FIWARE
More from FIWARE (20)
Recently uploaded
Recently uploaded (20)
FIWARE Global Summit - FIROS: Helping Robots to be Context Aware
- 1. FIROS: Helping Robots to be Context Aware Peter Detzner Research Associate Fraunhofer Institue for Materialflow and Logistics Dortmund
- 2. L4MS goal is to help SME’s & Mid- caps to reduce the installation cost and time of mobile robots by a factor of 10
- 3. OPIL – In a nutshell
- 4. OPIL – In a nutshell Open Plattform Innovation Logistics
- 5. OPIL – In a nutshell Physical Nodes Software System Layer Cyber Physical Middleware IoT NodesLayer1Layer2Layer3 OPIL Task Planner HMI Sensing & Perception Context Management Robot Agent NodeRobot Agent Node Robot Agent NodeRobot Agent NodeHuman Agent Node Robot Agent NodeRobot Agent NodeSensor Agent Node Layer0 Robot Agent NodeRobot Agent NodeAGV Robot Agent NodeRobot Agent NodeHuman Robot Agent NodeRobot Agent NodeSensor Robot Agent Node Open Plattform Innovation Logistics
- 6. OPIL – In a nutshell Physical Nodes Software System Layer Cyber Physical Middleware IoT NodesLayer1Layer2Layer3 OPIL Task Planner HMI Sensing & Perception Context Management Robot Agent NodeRobot Agent Node Robot Agent NodeRobot Agent NodeHuman Agent Node Robot Agent NodeRobot Agent NodeSensor Agent Node Layer0 Robot Agent NodeRobot Agent NodeAGV Robot Agent NodeRobot Agent NodeHuman Robot Agent NodeRobot Agent NodeSensor Robot Agent Node Open Plattform Innovation Logistics
- 7. OPIL – In a nutshell Physical Nodes Software System Layer Cyber Physical Middleware IoT NodesLayer1Layer2Layer3 OPIL Task Planner HMI Sensing & Perception Context Management Robot Agent NodeRobot Agent Node Robot Agent NodeRobot Agent NodeHuman Agent Node Robot Agent NodeRobot Agent NodeSensor Agent Node Layer0 Robot Agent NodeRobot Agent NodeAGV Robot Agent NodeRobot Agent NodeHuman Robot Agent NodeRobot Agent NodeSensor Robot Agent Node Open Plattform Innovation Logistics
- 8. OPIL – In a nutshell Physical Nodes Software System Layer Cyber Physical Middleware IoT NodesLayer1Layer2Layer3 OPIL Task Planner HMI Sensing & Perception Context Management Robot Agent NodeRobot Agent Node Robot Agent NodeRobot Agent NodeHuman Agent Node Robot Agent NodeRobot Agent NodeSensor Agent Node Layer0 Robot Agent NodeRobot Agent NodeAGV Robot Agent NodeRobot Agent NodeHuman Robot Agent NodeRobot Agent NodeSensor Robot Agent Node Open Plattform Innovation Logistics
- 9. What are the problems with FIROS? • Not maintened anymore • Documentation is lacking • Response time ~3months (based upon 1 Issue ) • What else do we don‘t like about it?! Source: https://www.pexels.com/search/desert/
- 10. What are the problems with FIROS? • Not maintened anymore • Documentation is lacking • Response time ~3months (based upon 1 Issue ) • What else do we don‘t like about it?! Source: https://www.pexels.com/search/desert/
- 11. What are the problems with FIROS? • Not maintened anymore • Documentation is lacking • Response time ~3months (based upon 1 Issue ) • What else do we don‘t like about it?! Source: https://www.pexels.com/search/desert/
- 12. What are the problems with FIROS? • Not maintened anymore • Documentation is lacking • Response time ~3months (based upon 1 Issue ) • What else do we don‘t like about it?! Source: https://www.pexels.com/search/desert/
- 13. What are the problems with FIROS? • Not maintened anymore • Documentation is lacking • Response time ~3months (based upon 1 Issue ) • What else do we don‘t like about it?! Source: https://www.pexels.com/search/desert/
- 14. What we dont like about it • Lack of readability (Nested Entities) • No standard Data-Types like in JSON • Based on NGSIv1 API (deprecated in Orion 2.0.0) • Robot Definitions
- 15. What we dont like about it • Lack of readability (Nested Entities) • No standard Data-Types like in JSON • Based on NGSIv1 API (deprecated in Orion 2.0.0) • Robot Definitions
- 16. What we dont like about it • Lack of readability (Nested Entities) • No standard Data-Types like in JSON • Based on NGSIv1 API (deprecated in Orion 2.0.0) • Robot Definitions
- 17. What we dont like about it • Lack of readability (Nested Entities) • No standard Data-Types like in JSON • Based on NGSIv1 API (deprecated in Orion 2.0.0) • Robot Definitions
- 18. What we dont like about it • Lack of readability (Nested Entities) • No standard Data-Types like in JSON • Based on NGSIv1 API (deprecated in Orion 2.0.0) • Robot Definitions
- 19. A simplified look at the architecture
- 20. Nested Entities • We like Standards but lets make it easier • Usage of JSON datatypes (where possible) • Still precise (MetaData) • ROS definitions are not required anymore
- 21. Nested Entities • We like Standards but lets make it easier • Usage of JSON datatypes (where possible) • Still precise (MetaData) • ROS definitions are not required anymore
- 22. Nested Entities • We like Standards but lets make it easier • Usage of JSON datatypes (where possible) • Still precise (MetaData) • ROS definitions are not required anymore
- 23. Nested Entities • We like Standards but lets make it easier • Usage of JSON datatypes (where possible) • Still precise (MetaData) • ROS definitions are not required anymore
- 24. Next Steps • Fraunhofer Fork of Firos (https://github.com/iml130/firos) • Making it available as a ROS package (http://wiki.ros.org/Packages) • Maybe a Generic Enabler for the Fiware Ecosystem?!
- 25. Next Steps • Fraunhofer Fork of Firos (https://github.com/iml130/firos) • Making it available as a ROS package (http://wiki.ros.org/Packages) • Maybe a Generic Enabler for the Fiware Ecosystem?!
- 26. Next Steps • Fraunhofer Fork of Firos (https://github.com/iml130/firos) • Making it available as a ROS package (http://wiki.ros.org/Packages) • Maybe a Generic Enabler for the Fiware Ecosystem?!
- 27. Next Steps • Fraunhofer Fork of Firos (https://github.com/iml130/firos) • Making it available as a ROS package (http://wiki.ros.org/Packages) • Maybe a Generic Enabler for the Fiware Ecosystem?!
- 28. More Information? Get in touch with us • Fraunhofer IML Website: • https://www.iml.fraunhofer.de/en.html • Our Department: • https://www.iml.fraunhofer.de/en/fields_of_activity/material-flow- systems/automation_embedded_systems.html • Fraunhofer IML@GitHub: • https://github.com/iml130/
- 29. L4MS at your service H2020 Innovation Action - This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 767642 Project Coordinator