Local editorial preview · InnoWorks Press
InnoWorks Press
Robotics with ROS 2 front cover

INNOWORKS PRESS · REVIEW EDITION

Computing and systems

Robotics with ROS 2

Messages, Motion and Real Systems

A robot needs more than a destination. Its measurements must belong to the right time, its coordinates to a named frame and its commands to a valid operating window. This manuscript begins with a bounded inspection task and develops the communication and reasoning around it. ROS 2 workspaces, nodes, messages, transforms, simulation, estimation, control, navigation and recorded failures become parts of one system. Explicit unknown and cancellation states keep the teaching example honest about what a simulation has established and what still requires runtime or physical testing.

Manuscript and companion under editorial and technical review. This local preview does not announce publication or sale.

Inside the book

A route through the ideas

Who it is for

Engineering students and robotics learners preparing to reason about communicating robotic systems and inspect their behaviour.

  1. Begin with a bounded robot task
  2. Workspaces and reproducible builds
  3. Nodes and interfaces
  4. Messages and communication quality
  5. Time and command validity
  6. Coordinate frames and transforms
  7. Describe and simulate a robot
  8. Sense and estimate motion
  9. Control motion within limits
  10. Navigate with changing observations
  11. Record and investigate failures
  12. Integrate and defend the system

Chapter titles follow the current review manuscript. Final pagination and edition details remain subject to review.

From the opening chapter

Begin with an idea

Our inspection base has one teaching objective: traverse a short, marked route in a simulated room and record why it accepted, rejected or cancelled each request. "Build an autonomous robot" is too broad to test. A bounded task identifies a start condition, a permissible operating region, a goal condition and the circumstances in which the attempt must end without success.

Define the simulation workspace as a rectangle in a named map frame. Define the goal as a pose tolerance rather than a perfect coordinate. For example, the teaching evaluator may require the estimated base position to lie within 0.10 metres of a goal for one simulated second. This is a software exercise threshold. It is not a measured positioning capability or a safe clearance for real equipment.

The definition must also say what success does not mean. Reaching a coordinate does not prove that the robot inspected anything. An inspection task requires a separate observation, a quality rule and an association between the observation and the place where it was acquired. For this book, the inspection record is a simulated marker reading. Keep route completion and observation validity as separate outputs.

Beyond the page

Make the idea work

Read. Predict. Experiment. Explain.

Move between the explanation and a working investigation. Each chapter provides a question, inspectable code or a model, and practice that asks you to explain the result.

  1. Read the argument before running the calculation.
  2. Change an input or assumption and inspect the result.
  3. Explain what the model supports, and what it leaves open.
Open the chapter companion →

Chapter QR codes connect the print proof to these materials. The online edition is being prepared locally; public links require a verified release.

About the author

Akash Chatake

Akash Shivadas Chatake writes and teaches across machine learning, artificial intelligence, computation and mathematics. His books connect an explanation with a question the reader can investigate, moving between the mathematical idea and the practical work it makes possible.

Explore the author’s work ↗