Intro to ROS in AI & Artificial Intelligence

In ROS, a robot's software is split into many small, independent programs called Nodes. One node might handle the LiDAR data, another handles the motor control, and another performs path planning. This modularity is ROS's greatest strength. If your object detection node crashes, the rest of the robot can still function (or at least perform a safe emergency stop). It also means you can develop each node in different languages—one in C++ for speed, another in Python for AI—and they will communicate seamlessly.

Nodes communicate using the Publisher/Subscriber pattern. A node 'Publishes' messages to a specific Topic (like /camera/images). Any other node that needs that data simply 'Subscribes' to that topic. This is an 'Asynchronous' communication method—the publisher doesn't care who is listening, and the subscriber doesn't care who is sending. This decoupling allows you to build massive, complex systems that are still easy to debug and maintain.

While Topics are great for continuous streams of data, sometimes you need a 1-to-1 interaction. Services use a Request/Response pattern (like an API call) for quick tasks like 'Turn on the lights'. Actions are for long-running goals that might take minutes to complete, such as 'Navigate to the loading dock'. Actions are superior to services for complex tasks because they allow the node to send Feedback (e.g., 'I am 50% there') and allow the user to Cancel the task if an emergency occurs.

Building a robot from scratch is hard. ROS (Robot Operating System) provides the plumbing and tools you need to connect sensors, processors, and actuators into a single, unified system.

ROS is based on a 'Node' architecture. Each process (like reading a camera) is a Node that communicates with others through 'Topics'.

When a node wants data, it 'Subscribes' to a Topic. This allows for a modular system where you can swap out an AI model without changing your camera driver.

Checkpoint: In ROS, what is a 'Node'?

• →A physical wire
• →An independent process or program that performs a specific task within the robot's system

ROS also provides 'Services' for 1-to-1 requests and 'Actions' for long-running tasks like 'Go to the kitchen', which provide feedback as they execute.

By mastering ROS, you join a global community of developers and gain access to thousands of ready-made packages for navigation, vision, and simulation.

Checkpoint: What is a 'Topic' in ROS?

• →The battery status
• →A named bus over which nodes exchange messages using the Publisher/Subscriber pattern

ROS mastered! You've learned the middleware. Ready to dive into the math of Localization with Kalman Filters?

Route a Real ROS Topic Message. Finish checking whether a subscriber should receive a message published on a given topic.