ROS master and roscore - Step-by-Step Execution

Concept Flow - ROS master and roscore

Start roscore

↓

ROS Master starts

↓

Nodes register with Master

↓

Nodes communicate via Master

↓

roscore runs until stopped

roscore starts the ROS Master, which manages node registration and communication until roscore stops.

Execution Sample

ROS

roscore
# Starts ROS Master
# Nodes register and communicate
# roscore runs until stopped

This command launches roscore, which starts the ROS Master to coordinate nodes.

Execution Table

Step	Action	Result	System State
1	Run 'roscore' command	ROS Master process starts	Master active, no nodes registered
2	Node A starts and registers	Node A registered with Master	Master active, Node A registered
3	Node B starts and registers	Node B registered with Master	Master active, Nodes A and B registered
4	Node A sends message to Node B via Master	Message routed successfully	Master active, communication ongoing
5	Stop roscore	ROS Master shuts down	Master inactive, nodes disconnected

💡 roscore stops, ROS Master shuts down, nodes lose coordination

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
ROS Master	inactive	active	active	active	active	inactive
Registered Nodes	none	Node A	Node A, Node B	Node A, Node B	Node A, Node B	none
Communication	none	none	none	message sent	message sent	none

Key Moments - 3 Insights

Why do nodes need to register with the ROS Master?

Nodes register so the Master can track them and enable communication, as shown in steps 2 and 3 of the execution table.

What happens if roscore is stopped while nodes are running?

Stopping roscore shuts down the Master, disconnecting nodes and stopping communication, as seen in step 5.

Does the ROS Master handle message content between nodes?

No, the Master only coordinates connections; actual message passing happens directly between nodes after coordination.

Visual Quiz - 3 Questions

Look at the execution table, what is the system state after step 3?

A Master inactive, no nodes registered

B Master active, Nodes A and B registered

C Master active, no nodes registered

D Master inactive, Nodes A and B registered

💡 Hint

Check the 'System State' column at step 3 in the execution table

At which step does the ROS Master become inactive?

A Step 1

B Step 3

C Step 5

D Step 4

💡 Hint

Look at the 'ROS Master' variable in variable_tracker and the 'Action' column in execution_table

If Node C registers after step 3, how would the 'Registered Nodes' variable change after step 4?

A Node A, Node B, Node C

B Node C only

C Node A, Node B

D No change

💡 Hint

Refer to how nodes register in steps 2 and 3 in variable_tracker

Concept Snapshot

roscore command starts the ROS Master process
ROS Master manages node registration and communication
Nodes register with Master to communicate
roscore runs until stopped, then Master shuts down
Stopping roscore disconnects all nodes

Full Transcript

Starting roscore launches the ROS Master, which is the central coordinator for all ROS nodes. Nodes must register with the Master to be known and to communicate with each other. The Master keeps track of all active nodes and helps route messages between them. When roscore is stopped, the Master shuts down, and nodes lose their coordination and communication ability. This flow ensures a central point for managing distributed ROS nodes.

Practice

1. What is the main role of the ROS master in a ROS system?

easy

A. It controls the robot's motors directly.

B. It helps different robot parts find and communicate with each other.

C. It stores sensor data permanently.

D. It provides a graphical user interface for robot control.

Solution

1. Step 1: Understand the function of ROS master

   The ROS master acts as a central directory that helps nodes find each other to communicate.

2. Step 2: Compare options with this role

   Only It helps different robot parts find and communicate with each other. describes this role correctly; others describe unrelated functions.

3. Final Answer:

   It helps different robot parts find and communicate with each other. -> Option B

4. Quick Check:

   ROS master = central communication helper [OK]

Hint: Remember ROS master is like a phone book for robot parts [OK]

Common Mistakes:

• Thinking ROS master controls hardware directly
• Confusing ROS master with data storage
• Assuming ROS master provides UI

2. Which command do you run first to start the ROS master and essential services?

easy

A. rosnode start

B. rosrun master start

C. roslaunch master.launch

D. roscore

Solution

1. Step 1: Identify the command to start ROS master

   The command roscore starts the ROS master and essential services.

2. Step 2: Check other commands

   Other commands either don't exist or do not start the master service.

3. Final Answer:

   roscore -> Option D

4. Quick Check:

   Start ROS master with roscore [OK]

Hint: Always run roscore first to start ROS master [OK]

Common Mistakes:

• Trying to start master with rosnode or rosrun
• Confusing roslaunch with roscore
• Assuming master starts automatically

3. What will happen if you try to run a ROS node before running roscore?

medium

A. The node will fail to communicate because the ROS master is not running.

B. The node will run normally and communicate with other nodes.

C. The node will start the ROS master automatically.

D. The node will run but only in offline mode.

Solution

1. Step 1: Understand the role of roscore

   roscore must be running to provide the ROS master service for nodes to communicate.

2. Step 2: Analyze node behavior without roscore

   If roscore is not running, nodes cannot register or find others, so communication fails.

3. Final Answer:

   The node will fail to communicate because the ROS master is not running. -> Option A

4. Quick Check:

   Node needs roscore running to communicate [OK]

Hint: No roscore means no communication for nodes [OK]

Common Mistakes:

• Assuming nodes auto-start roscore
• Thinking nodes run offline automatically
• Believing nodes communicate without master

4. You ran roscore but your nodes still cannot communicate. What is a likely cause?

medium

A. You forgot to source the ROS setup file in your terminal.

B. You ran roscore twice.

C. Your robot hardware is turned off.

D. You used the wrong ROS version.

Solution

1. Step 1: Check environment setup

   For nodes to find the ROS master, the terminal must source the ROS setup file to set environment variables.

2. Step 2: Evaluate other options

   Running roscore twice causes errors but not communication failure; hardware off or wrong version may cause other issues but not this specific problem.

3. Final Answer:

   You forgot to source the ROS setup file in your terminal. -> Option A

4. Quick Check:

   Source setup file to connect nodes [OK]

Hint: Always source ROS setup before running nodes [OK]

Common Mistakes:

• Ignoring environment setup
• Assuming hardware affects communication directly
• Thinking roscore can be run multiple times safely

5. You want to run multiple ROS nodes on different machines. What must you ensure about roscore and network settings?

hard

A. Run roscore on all machines but disable the network.

B. Run roscore separately on each machine with default settings.

C. Run roscore on one machine and set all machines to use its IP address for ROS master.

D. Run roscore only on the machine with the robot hardware.

Solution

1. Step 1: Understand ROS master role in multi-machine setup

   Only one ROS master should run, and all nodes must connect to it using its IP address.

2. Step 2: Analyze network requirements

   All machines must be networked so nodes can communicate via the ROS master IP.

3. Final Answer:

   Run roscore on one machine and set all machines to use its IP address for ROS master. -> Option C

4. Quick Check:

   One roscore, shared IP for multi-machine ROS [OK]

Hint: One roscore, share its IP with all machines [OK]

Common Mistakes:

• Running multiple roscore instances causing conflicts
• Ignoring network setup for multi-machine communication
• Assuming roscore runs automatically on all machines