Insaion Announces Free Tier and Documentation for Robotics

UBTECH’s Walker S2 is a humanoid robot that does something no robot has done before: it swaps its own battery autonomously. 🔋🤖 When power runs low, Walker finds a charged battery, replaces it on the spot, and keeps working—no human help, no downtime. Already being tested in factories, it runs 24/7, monitors its own limits, and solves its own problems. Automation just hit a whole new level.

A Complete Guide to Setup Docker for ROS 2 Jazzy Projects? If you’ve ever spent hours fixing dependencies, re-installing ROS 2, or chasing “works on my machine” bugs… you should definitely check this tutorial! Automatic Addison has published The Complete Guide to Docker for ROS 2 Jazzy Projects, a step-by-step tutorial to: ✅ Set up Docker for ROS 2 ✅ Build portable, reproducible robotics environments ✅ Run RViz, ROS 2 nodes, multi-container projects with Docker compose Docker lets you package your entire ROS 2 setup into a container that runs the same way on any laptop, robot, or server. No more fragile environments. 🔗 Check the tutorial and start dockerising your ROS 2 project! https://lnkd.in/d4dR8de7 Are you already using Docker on your ROS 2 applications? Let's connect and share robotics insights 🔽 #ROS2 #Robotics #Docker

Ever got your SSH session to your robot dropped? While developing a robot, you often need to run an application over WiFi or overnight. This means, if your SSH session drops, your application will also be killed, or become a zombie [failed to be closed fully] which can hold onto the hardware you are testing and prevent to reconnect to it. This is where 𝐭𝐦𝐮𝐱 comes in! Tmux is a Terminal multiplexer, running in your terminal itself. While it provides you with multiple windows, and panes as expected, it also bring 𝐬𝐞𝐬𝐬𝐢𝐨𝐧𝐬 by default. Tmux sessions can be connected to by 𝐦𝐮𝐥𝐭𝐢𝐩𝐥𝐞 𝐮𝐬𝐞𝐫𝐬 simultaneously, detached, reattached and if your SSH connection drops, you can just 𝐫𝐞𝐚𝐭𝐭𝐚𝐜𝐡 to it once the connection comes back. Tmux is a primordial tool for Robotics, to avoid running 10 terminals and forget what actually runs on the robot and what 𝐨𝐭𝐡𝐞𝐫𝐬 may run on it. It can also be scripted. I highly recommend you to have a default view for all your robots where all devs can find themselves, such as "First window is the behavior, second the navigation, third the sensor dashboard". NOTE: Remember to use Linux service (or rc.init) for production. Tmux is only for development... except if you have a dashboard TUI on device in a tmux in a service ofc.

A Terminal UI to monitor your ROS 2 systems? Managing nodes, topics, and parameters in ROS 2 can be powerful, but sometimes the monitoring multiple terminal and commands can be less than smooth. That’s why Xiandi Shan, Harumo Sasatake, and Ryosuke Tajima built lazyros, a lightweight terminal UI that makes working with ROS 2 Humble more intuitive and efficient. What are the features? ✅ View and manage nodes and lifecycles ✅ Inspect topics, services, and parameters ✅ Built-in log/echo with highlight and search ✅ Fast, keyboard-driven navigation ✅ Easy to install via pipx or pip ✅ Runs right in your terminal 🔗 Check the project and monitor your ROS 2 systems! https://lnkd.in/dfpFxuag Which tools are you using for ROS 2 development? Let's connect and share robotics insights 🔽 #Robotics #ROS2

Like many people in the robotics community, I’ve been fascinated by the SO-ARM101; a low-cost, 3D-printable arm that makes exploring manipulation tasks more accessible. I built support for it in Viam, so I could integrate it with all the other components and services on the platform. I've documented the complete process in a hands-on tutorial: https://lnkd.in/eNp8EqXr Along with the driver for the arm, a big part of this project was reducing the complexity of getting started, mainly the motor setup and joint calibration. This led to building a web application that connects to the robot and provides a visual guide for those tasks. Now you can manage your arm anywhere! This is just the beginning to explore what’s possible when you bring together accessible hardware and software for developers. What manipulation tasks would you want to tackle first with an accessible setup like this? What other hardware should I integrate with the SO-ARM101?

✨ Monthly Learning Update ✨ After learning the basics of ROS, I wanted to move beyond theory and build something practical. Earlier, I was controlling my ESP32-based car using Bluetooth and a webserver — but the system wasn’t truly real-time. So, I decided to rebuild it with ROS 2 and micro-ROS. Here’s what I implemented: 🔹 Created a micro-ROS based car subscribed to the cmd_vel topic, allowing me to control it directly through ROS messages. 🔹 Set up a WebSocket bridge and forwarded it via ngrok, enabling global access. 🔹 Built a simple website interface (hosted on Vercel) that communicates with the WebSocket and publishes to cmd_vel. 🔹 Result: I can now control my car from anywhere in the world 🌍 in real time. Tools & Tech: ROS 2 Jazzy, micro-ROS Jazzy, micro-ROS Agent, ngrok, Vercel This project gave me hands-on experience with real-time robotics communication, networking, and system integration, and I’m excited to keep pushing further into advanced robotics. #ROS2 #microROS #Robotics #Automation #LearningByDoing #Networking

Fun Fact Friday at Bolt Automation In 1854, mathematician George Boole published An Investigation into the Laws of Thought, a groundbreaking work that laid the foundation for modern computing and robotics. Today, Boolean logic drives the smart workflows we build at Bolt Automation. From conditional triggers to precision-based decision trees, Boole’s legacy lives on in every automated process we deploy. -Innovation starts with logic. -Watch how 19th-century theory powers 21st-century automation. #Automation #BooleanLogic #FunFactFriday #BoltAutomation #TechHistory #SmartWorkflow

The wide applicability of a Collaborative Robot comes from its incredible flexibility. Unlike a heavy industrial robot that is bolted down and caged in, a Cobot can be: Deployed and redeployed to new tasks in hours, not weeks. Mounted on mobile carts to move between workstations. Easily programmed by existing staff for a high mix of products. This agility is why it has such a wide range of applications. #FlexibleAutomation #AgileManufacturing #CollaborativeRobot #Cobot #AutomationSolutions #IndustrialRobot

The wide applicability of a Collaborative Robot comes from its incredible flexibility. Unlike a heavy industrial robot that is bolted down and caged in, a Cobot can be: Deployed and redeployed to new tasks in hours, not weeks. Mounted on mobile carts to move between workstations. Easily programmed by existing staff for a high mix of products. This agility is why it has such a wide range of applications. #FlexibleAutomation #AgileManufacturing #CollaborativeRobot #Cobot #AutomationSolutions #IndustrialRobot

Ros 2: A Robotics Framework #snsinstitution #snsdesignthinkers #snsdesignthinking #snsct What ROS 2 Means for Me In simple terms, ROS 2 is the software framework that enables all my different parts to work together. Think of my camera, my arm motors, and my leg joints as separate entities. Without a way to communicate, they would just be a collection of disconnected components. ROS 2 solves this by creating a network of nodes, which are like the individual apps running on my internal computer. For example, my vision system is a node that processes camera data to identify objects. My locomotion system is another node that controls my legs. My conversation node handles processing human speech. These nodes don't need to know how the others work; they just need to communicate. This is where ROS 2's Data Distribution Service (DDS) comes in. It allows these nodes to send and receive information seamlessly, ensuring that a command to move my arm is delivered without any lag, even while my vision system is busy analyzing my surroundings.