Safety velocity limits in ROS - Step-by-Step Execution

Concept Flow - Safety velocity limits

Receive velocity command

↓

Check velocity against limits

↓

Limit velocity

↓

Send safe velocity command

The system receives a velocity command, checks if it exceeds safety limits, limits it if needed, then sends the safe command.

Execution Sample

ROS

velocity_cmd = 5.0
max_velocity = 3.0
if velocity_cmd > max_velocity:
    safe_velocity = max_velocity
else:
    safe_velocity = velocity_cmd
send_velocity(safe_velocity)

This code limits the velocity command to a maximum safe velocity before sending it.

Execution Table

Step	velocity_cmd	max_velocity	Condition velocity_cmd > max_velocity	Action	safe_velocity	Output
1	5.0	3.0	5.0 > 3.0 is True	Limit velocity to max_velocity	3.0	send_velocity(3.0)
2	2.0	3.0	2.0 > 3.0 is False	Pass velocity as is	2.0	send_velocity(2.0)
3	3.0	3.0	3.0 > 3.0 is False	Pass velocity as is	3.0	send_velocity(3.0)
4	3.5	3.0	3.5 > 3.0 is True	Limit velocity to max_velocity	3.0	send_velocity(3.0)
Exit	-	-	No more commands	-	-	-

💡 Execution stops after processing all velocity commands.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
velocity_cmd	5.0	5.0	2.0	3.0	3.5	3.5
safe_velocity	-	3.0	2.0	3.0	3.0	3.0

Key Moments - 2 Insights

Why do we limit velocity only when velocity_cmd > max_velocity?

Because only when the commanded velocity is higher than the safe max, we need to reduce it. Otherwise, the command is safe to send as is (see execution_table rows 1 and 2).

What happens if velocity_cmd equals max_velocity?

The condition velocity_cmd > max_velocity is false, so the velocity is passed unchanged (see execution_table row 3).

Visual Quiz - 3 Questions

Look at the execution_table at step 1. What is the safe_velocity value sent?

A 3.0

B 5.0

C 2.0

D 0.0

💡 Hint

Check the safe_velocity column at step 1 in execution_table.

At which step does the velocity_cmd pass without limiting because it is not greater than max_velocity?

A Step 1

B Step 2

C Step 4

D Exit

💡 Hint

Look for where the condition velocity_cmd > max_velocity is false in execution_table.

If max_velocity changed to 4.0, what would safe_velocity be at step 4?

A 3.0

B 4.0

C 3.5

D 5.0

💡 Hint

Compare velocity_cmd and new max_velocity at step 4 in variable_tracker.

Concept Snapshot

Safety velocity limits:
- Receive velocity command
- Check if command > max limit
- If yes, limit to max
- Else, pass as is
- Send safe velocity command

Full Transcript

This example shows how a robot system ensures safety by limiting velocity commands. It receives a velocity command, compares it to a maximum safe velocity, and if the command is too high, it reduces it to the maximum allowed. Otherwise, it sends the command unchanged. This prevents unsafe speeds. The execution table traces different velocity commands and how they are handled step-by-step. Variables track the command and safe velocity values. Key moments clarify why limiting happens only when needed and what occurs at boundary values. The quiz tests understanding of these steps and variable changes.

Practice

1. What is the main purpose of safety velocity limits in ROS?

easy

A. To keep robot speeds within safe ranges

B. To increase the robot's maximum speed

C. To disable robot movement completely

D. To control the robot's battery usage

Solution

1. Step 1: Understand the role of safety velocity limits

   Safety velocity limits are designed to prevent the robot from moving too fast, ensuring safety.

2. Step 2: Identify the correct purpose

   Among the options, only keeping speeds safe matches the purpose of safety velocity limits.

3. Final Answer:

   To keep robot speeds within safe ranges -> Option A

4. Quick Check:

   Safety velocity limits = keep speeds safe [OK]

Hint: Safety limits control max speed, not disable or increase it [OK]

Common Mistakes:

• Thinking safety limits increase speed
• Confusing safety limits with power control
• Assuming safety limits stop all movement

2. Which ROS parameter syntax correctly sets a maximum linear velocity limit to 0.5 m/s?

easy

A. max_linear_velocity 0.5

B. max_linear_velocity = 0.5

C. max_linear_velocity->0.5

D. max_linear_velocity: 0.5

Solution

1. Step 1: Recall ROS parameter YAML syntax

   ROS parameters in YAML use colon and space, like param_name: value.

2. Step 2: Match syntax to options

   Only max_linear_velocity: 0.5 uses correct YAML syntax for setting parameters.

3. Final Answer:

   max_linear_velocity: 0.5 -> Option D

4. Quick Check:

   ROS YAML param = key: value [OK]

Hint: ROS params use colon and space, not equals or arrows [OK]

Common Mistakes:

• Using equals sign instead of colon
• Omitting colon and space
• Using arrow notation which is invalid

3. Given this ROS node snippet setting velocity limits:

velocity_limits:
  max_linear: 1.0
  max_angular: 0.5

robot_velocity:
  linear: 1.2
  angular: 0.4

What will be the effective linear velocity after applying safety limits?

medium

A. 1.0 m/s

B. 1.2 m/s

C. 0.5 m/s

D. 0.4 m/s

Solution

1. Step 1: Compare robot velocity to max limits

   The robot's linear velocity is 1.2 m/s, which exceeds the max_linear limit of 1.0 m/s.

2. Step 2: Apply safety velocity limit

   The effective linear velocity must be capped at the max_linear limit, 1.0 m/s.

3. Final Answer:

   1.0 m/s -> Option A

4. Quick Check:

   Velocity capped at max_linear = 1.0 [OK]

Hint: If velocity > max limit, use max limit value [OK]

Common Mistakes:

• Using original velocity without capping
• Confusing angular and linear limits
• Choosing the lower angular limit for linear velocity

4. You wrote this YAML for velocity limits but the robot ignores the limits:

velocity_limits:
  max_linear = 0.8
  max_angular: 0.4

What is the likely error?

medium

A. Incorrect indentation for max_angular

B. Missing quotes around numbers

C. Using '=' instead of ':' for max_linear

D. Parameter names must be uppercase

Solution

1. Step 1: Check YAML syntax for parameters

   YAML requires colon and space to assign values, not equals sign.

2. Step 2: Identify the error in max_linear line

   Using '=' instead of ':' causes the parameter to be ignored or cause parsing errors.

3. Final Answer:

   Using '=' instead of ':' for max_linear -> Option C

4. Quick Check:

   YAML param syntax = colon, not equals [OK]

Hint: YAML uses colon, not equals, to assign values [OK]

Common Mistakes:

• Using equals sign in YAML
• Forgetting indentation rules
• Thinking quotes are mandatory for numbers

5. You want to set different safety velocity limits for two robot modes: normal and cautious. Which YAML structure correctly defines max linear velocities for both modes?

hard

A. velocity_limits:
normal:
max_linear: 1.0
cautious:
max_linear: 0.5

B. velocity_limits:
max_linear:
normal: 1.0
cautious: 0.5

C. velocity_limits:
normal_max_linear: 1.0
cautious_max_linear: 0.5

D. velocity_limits:
max_linear_normal: 1.0
max_linear_cautious: 0.5

Solution

1. Step 1: Understand hierarchical YAML for modes

   Grouping limits under max_linear with mode keys is clear and scalable.

2. Step 2: Compare options for clarity and structure

   velocity_limits:
     max_linear:
       normal: 1.0
       cautious: 0.5

   nests modes under max_linear, which is a common pattern for related parameters.

3. Final Answer:

   velocity_limits: max_linear: normal: 1.0 cautious: 0.5 -> Option B

4. Quick Check:

   Nested keys for modes under max_linear =

   velocity_limits:
     max_linear:
       normal: 1.0
       cautious: 0.5

   [OK]

Hint: Nest modes under max_linear for clear grouped limits [OK]

Common Mistakes:

• Using flat keys with mode suffixes
• Not grouping related parameters
• Confusing key names and structure