Keyboard teleoperation (teleop_twist_keyboard) in ROS - Performance & Optimization

Performance: Keyboard teleoperation (teleop_twist_keyboard)

MEDIUM IMPACT

This concept affects the responsiveness and smoothness of robot control commands sent from keyboard input to the robot system.

Sending velocity commands to a robot via keyboard input

ROS

import curses

stdscr = curses.initscr()
curses.cbreak()
stdscr.nodelay(True)

while True:
    key = stdscr.getch()
    if key == ord('w'):
        publish_velocity(1.0, 0.0)
    elif key == ord('s'):
        publish_velocity(-1.0, 0.0)
    # non-blocking input allows continuous command sending

Non-blocking keyboard input allows continuous reading and sending of commands without waiting, improving responsiveness.

📈 Performance GainReduces input lag, improves INP by enabling immediate reaction to key presses.

Sending velocity commands to a robot via keyboard input

ROS

while True:
    key = input()
    if key == 'w':
        publish_velocity(1.0, 0.0)
    elif key == 's':
        publish_velocity(-1.0, 0.0)
    # blocking input() call waits for enter key

Using blocking input() waits for the user to press enter, causing delayed command sending and poor responsiveness.

📉 Performance CostBlocks input processing until enter key, causing high input latency and poor INP.

Performance Comparison

Pattern	Input Handling	Command Latency	Responsiveness	Verdict
Blocking input() call	Blocks until enter pressed	High latency	Poor responsiveness	[X] Bad
Non-blocking input with curses	Continuous input polling	Low latency	Smooth responsiveness	[OK] Good

Rendering Pipeline

Keyboard teleoperation input flows through the input event handling stage, then triggers command publishing to the robot system. Efficient input handling reduces delays in this pipeline.

→Input Handling

→Command Processing

→Network Transmission

⚠️ BottleneckBlocking input calls cause delays in Input Handling stage.

Core Web Vital Affected

INP

This concept affects the responsiveness and smoothness of robot control commands sent from keyboard input to the robot system.

Optimization Tips

1Avoid blocking input calls to reduce input lag.

2Use non-blocking or event-driven input handling for smooth command sending.

3Monitor command message frequency to ensure responsive teleoperation.

Performance Quiz - 3 Questions

What is the main performance issue with using Python's blocking input() for keyboard teleoperation?

A It waits for the enter key, causing input lag.

B It consumes too much CPU.

C It sends too many commands too fast.

D It causes network congestion.

DevTools: rosbag / rqt_console

How to check: Record command messages with rosbag while testing keyboard input; use rqt_console to monitor message frequency and delays.

What to look for: Look for consistent, low-latency command message intervals indicating responsive input handling.

Practice

1. What is the main purpose of the teleop_twist_keyboard node in ROS?

easy

A. To control a robot using keyboard keys

B. To visualize robot sensor data

C. To simulate robot movements automatically

D. To compile ROS packages

Solution

1. Step 1: Understand the node's function

   The teleop_twist_keyboard node allows manual control of a robot using keyboard inputs.

2. Step 2: Compare options with the node's purpose

   Only To control a robot using keyboard keys describes controlling a robot with keyboard keys, which matches the node's purpose.

3. Final Answer:

   To control a robot using keyboard keys -> Option A

4. Quick Check:

   Keyboard control = A [OK]

Hint: Remember: teleop means tele-operation via keyboard [OK]

Common Mistakes:

• Confusing teleop with simulation or visualization
• Thinking it compiles code
• Assuming it runs robot automatically

2. Which command correctly runs the teleop_twist_keyboard node in ROS 2?

easy

A. ros run teleop_twist_keyboard teleop_twist_keyboard

B. ros2 launch teleop_twist_keyboard teleop_twist_keyboard.launch

C. ros2 run teleop_twist_keyboard teleop_twist_keyboard

D. ros2 start teleop_twist_keyboard

Solution

1. Step 1: Identify the correct ROS 2 run syntax

   In ROS 2, the command to run a node is ros2 run <package> <executable>.

2. Step 2: Match the command to teleop_twist_keyboard

   ros2 run teleop_twist_keyboard teleop_twist_keyboard uses the correct syntax and package/executable names.

3. Final Answer:

   ros2 run teleop_twist_keyboard teleop_twist_keyboard -> Option C

4. Quick Check:

   ros2 run + package + executable = B [OK]

Hint: Use 'ros2 run' for running nodes in ROS 2 [OK]

Common Mistakes:

• Using 'ros' instead of 'ros2'
• Using 'launch' instead of 'run' for this node
• Typing 'start' which is not a ROS command

3. Given the following keys pressed in teleop_twist_keyboard: i, j, k, what is the expected robot movement sequence?

medium

A. Turn left, move forward, stop

B. Move backward, turn right, stop

C. Stop, move forward, turn right

D. Move forward, turn left, move backward

Solution

1. Step 1: Recall key functions in teleop_twist_keyboard

   Key 'i' moves robot forward, 'j' turns left, 'k' moves backward.

2. Step 2: Match keys to movements in sequence

   Pressing 'i' then 'j' then 'k' results in moving forward, turning left, then moving backward.

3. Final Answer:

   Move forward, turn left, move backward -> Option D

4. Quick Check:

   i = forward, j = left, k = backward [OK]

Hint: Remember i=forward, j=left, k=backward keys [OK]

Common Mistakes:

• Mixing up 'j' and 'l' keys for turning
• Assuming 'k' stops movement
• Confusing forward and backward keys

4. You run ros2 run teleop_twist_keyboard teleop_twist_keyboard but pressing keys does not move the robot. What is the most likely cause?

medium

A. The robot is not connected or not receiving velocity commands

B. The keyboard keys are incorrect; use arrow keys instead

C. The teleop_twist_keyboard node must be launched with a launch file

D. ROS 2 is not installed properly

Solution

1. Step 1: Check common reasons for no robot movement

   If keys are pressed but robot doesn't move, often the robot is not connected or not subscribed to velocity commands.

2. Step 2: Evaluate other options

   Keyboard keys are correct as per documentation; launch file is not required; ROS 2 installation issues would prevent node running.

3. Final Answer:

   The robot is not connected or not receiving velocity commands -> Option A

4. Quick Check:

   No movement = no connection [OK]

Hint: Check robot connection before blaming keys or launch files [OK]

Common Mistakes:

• Assuming arrow keys must be used
• Thinking launch file is mandatory
• Blaming ROS 2 install without checking connection

5. You want to increase the robot's forward speed using teleop_twist_keyboard. Which method correctly achieves this?

hard

A. Press 'i' key twice quickly to double speed

B. Press 'w' key to increase speed while running teleop_twist_keyboard

C. Restart teleop_twist_keyboard with a higher speed parameter

D. Edit the robot's URDF file to increase max speed

Solution

1. Step 1: Understand teleop_twist_keyboard speed control

   The node allows speed adjustment during runtime using 'w' and 'x' keys to increase or decrease linear speed.

2. Step 2: Evaluate other options

   Editing URDF changes robot model, not teleop speed; restarting with parameters is possible but less direct; pressing 'i' twice does not increase speed.

3. Final Answer:

   Press 'w' key to increase speed while running teleop_twist_keyboard -> Option B

4. Quick Check:

   Use 'w' to increase speed live [OK]

Hint: Use 'w' and 'x' keys to adjust speed live [OK]

Common Mistakes:

• Trying to speed up by pressing movement keys repeatedly
• Editing URDF for speed instead of teleop parameters
• Restarting node instead of adjusting speed live