Deployment

Summarized using AI

ROS - ecosystem for things

Wojciech Ziniewicz • March 12, 2016 • Wrocław, Poland

In this presentation, Wojciech Ziniewicz discusses ROS (Robot Operating System), which he refers to as an "ecosystem for things" and integrates its applications in the realm of the Internet of Things (IoT). The talk begins with a playful introduction to the misconceptions surrounding IoT devices through a game where the audience guesses which product is fictitious, illustrating the creativity and absurdity in current IoT products.

Key Points Discussed:
- Current State of IoT: Ziniewicz reflects on how the early optimism in IoT has encountered challenges, leading to many products being perceived as primitive and lacking in utility.
- Security Concerns: He stresses the importance of security in IoT devices, highlighting issues like unsecured servers and the potential for devices to be hijacked if they are poorly maintained.
- Standardization Issues: The lack of universal standards and protocols is a significant hurdle, causing many devices to operate on non-standardized frameworks and complicating maintenance.
- Technical Limitations: Challenges such as energy consumption, hardware limitations, battery life, and communication protocol inefficiencies are underscored.
- Role of ROS: Ziniewicz positions ROS as a solution to these complexities, explaining its flexibility, robustness, and ability to integrate various programming languages and communication protocols. He points out that the EU recognized the need for regulation and viewed ROS as a stable backbone, particularly for autonomous systems.
- Developer-Friendly Environment: Developers favor ROS for its ability to abstract complex issues and allow for easy portability across platforms. Ziniewicz mentions tools like Snap in Ubuntu for deployment practices that increase resilience.
- Demo Showcase: The presentation includes a demonstration of DOM synchronization between browsers, showcasing the practical use of ROS in integrated communications.

Conclusions and Takeaways:
- The presentation concludes with an emphasis on the ongoing need for better standardization, security, and maintenance practices within the IoT ecosystem.
- It encourages developers to leverage the capabilities of ROS to meet these challenges effectively and improve the overall efficacy of IoT devices.
- Ziniewicz invites audience questions, indicating an open discussion about the future of IoT and ROS implementation.

ROS - ecosystem for things
Wojciech Ziniewicz • March 12, 2016 • Wrocław, Poland

wroclove.rb 2016

00:00:14.610 Hello everyone, today I will be talking about ROS, an ecosystem for things. Before we dive in, I'd like to know how many of you have heard of ROS? Please raise your hands.
00:00:20.880 Great! It's good to see that many of you are familiar with it. So, originally, the name of this ecosystem was 'Ecosystem for Things,' but I like to refer to it as 'Middleware for Things,' which is a term often used by BMW.
00:00:28.470 Now, let’s play a small game. I will mention some products, and you need to tell me which one is fake. For example, we have a robot that reveals your home Wi-Fi password using a screwdriver.
00:00:42.180 Another product is a pipette that analyzes your home to infer the likelihood of disease or health issues. Think of a device that connects to a toilet with a web server for management purposes.
00:00:54.540 Or perhaps a smart TV that can break itself, or a magic device that casts viruses out of your computer. There’s also the iKettle, which lets you boil water while asking if you’d like a cup of tea.
00:01:12.330 And we have yoga pants that vibrate to give you feedback on your poses. So, can anyone guess which product is fake? It’s surprising to note that the screwdriver device wasn’t true when I first wrote my presentation, but I discovered during research that they are working on it.
00:01:41.670 This highlights how different people envision the Internet of Things. In 2012, when wearables, cars, and smart devices were trending, the picture seemed bright. However, in 2016, things have changed, and some of the implementations feel rather primitive.
00:02:29.790 Let’s go back to the Niagara server I mentioned earlier, which does exist. How many of you know what Shodan.io is?
00:02:36.010 Shodan is a search engine for finding Internet of Things devices that are connected online. It scans the internet and takes screenshots of devices, often revealing their default passwords, like those for cameras or bathrooms operated by the Internet.
00:03:01.680 Statistics indicate that there are almost 2,500 unsecure servers in the United States. These expose devices to potential attacks, showing the pressing security issues surrounding the Internet of Things.
00:03:20.490 Another point is the lack of known standards and protocols for these devices. As depicted in a well-known XKCD comic, the Internet of Things tends to include numerous bespoke, non-standard frameworks that companies create without sharing.
00:04:49.600 This results in significant maintainability issues. You can't truly update a device if there are no standard methods for doing so, similar to how web applications can be updated dynamically.
00:05:41.210 Security is another major concern; often, companies use their own bespoke frameworks, which are typically hard to update with security patches. If a device is compromised, someone with physical access can do a lot of damage.
00:07:03.830 Energy consumption also complicates the situation. Most devices need to be energy-efficient, but that often hampers their functionality. Hardware limitations persist in IoT devices.
00:09:29.750 Regarding security, the lack of proper encryption in many IoT devices can turn them into potential spying tools, as pointed out by officials.
00:11:32.390 It's crucial to reckon with the challenges facing the Internet of Things. After first mentions in 2000, progress was slow and many products, like internet-connected refrigerators, failed to meet user needs. In essence, battery life often continues to pose a problem.
00:12:43.240 Remote machine reboots expose devices to risks, causing lapses in security and accessibility.
00:13:55.250 Furthermore, we see various wireless communication protocols being used, such as ZigBee and their limitations when scaling device networks.
00:14:52.290 In all these complexities, ROS can come into play more substantially. It positions itself as an ideal candidate to handle the complexities of IoT due to its flexibility and robustness.
00:17:10.060 The European Union recognized that existing free markets didn't provide common standards, proclaiming the need for regulation. They recommended using ROS, which has proven to be a stable backbone, especially for autonomous driving systems.
00:19:06.050 Countless organizations have integrated ROS, including manufacturers focusing heavily on mechatronics. ROS serves as a communication layer for various protocols across automobiles.
00:21:01.150 Developers favor ROS because it abstracts complexities. Users can leverage its publisher/subscriber model without heavy concerns about hardware specifications.
00:22:32.330 Most ROS implementations are in C++ and Python, generally allowing great portability across platforms. This means a software implementation could be reused across multiple devices.
00:24:27.950 As I touch on software transparency, the ease of deployment becomes vital for maintaining robust solutions over time.
00:26:37.530 Good practices in deployment utilize tools like Snap in Ubuntu, allowing for transactional updates and rollbacks, and consequently enhancing overall system resilience.
00:28:20.840 The concept of ROS as an operating system may seem convoluted. However, it encompasses many tools and environments that aid deployment management and orchestration.
00:31:24.460 Developers can integrate virtually any programming language with ROS, thereby adding versatility to the operating environment.
00:33:42.630 Today, I’d like to showcase a straightforward demo of DOM synchronization between browsers, using ROS for integrated communications.
00:35:12.470 Does anyone have any questions? Feel free to ask as I wrap this up.
00:37:18.400 Thank you all for being here today!
Explore all talks recorded at wroclove.rb 2016
+27