Why teleoperation enables manual robot control in ROS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize the ROS node for teleoperation.

ROS

ros::init(argc, argv, [1]);

Drag options to blanks, or click blank then click option'

A"teleop_node"

B"robot_control"

C"manual_drive"

D"auto_nav"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a node name unrelated to teleoperation.

Forgetting to put the node name in quotes.

The ROS node must be initialized with the name "teleop_node" to identify the teleoperation control node.

2fill in blank

medium

Complete the code to create a ROS publisher for velocity commands.

ROS

ros::Publisher vel_pub = nh.advertise<geometry_msgs::Twist>([1], 10);

Drag options to blanks, or click blank then click option'

A"/robot_speed"

B"/cmd_vel"

C"/velocity_cmd"

D"/move_robot"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-standard topic name that the robot does not subscribe to.

Omitting the leading slash in the topic name.

The standard topic for velocity commands in ROS teleoperation is "/cmd_vel".

3fill in blank

hard

Fix the error in the teleoperation loop to publish velocity commands correctly.

ROS

while (ros::ok()) {
  geometry_msgs::Twist vel_msg;
  vel_msg.linear.x = [1];
  vel_pub.publish(vel_msg);
  ros::spinOnce();
  loop_rate.sleep();
}

Drag options to blanks, or click blank then click option'

Aspeed

Bvelocity

Clinear_speed

Dcmd_vel

Attempts:

3 left

💡 Hint

Common Mistakes

Using the topic name or message type as a variable.

Using undefined variable names.

The variable 'speed' holds the linear velocity value to assign to vel_msg.linear.x.

4fill in blank

hard

Fill both blanks to subscribe to joystick input and update velocity commands.

ROS

ros::Subscriber joy_sub = nh.subscribe([1], 10, [2]);

Drag options to blanks, or click blank then click option'

A"/joy"

B"/joystick"

CjoyCallback

DvelocityCallback

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect topic names that do not publish joystick data.

Using callback functions unrelated to joystick input.

The joystick input topic is "/joy" and the callback function handling input is 'joyCallback'.

5fill in blank

hard

Fill all three blanks to create a dictionary mapping joystick axes to velocity commands.

ROS

std::map<std::string, double> axis_map = {{
  {"linear_x", [1],
  {"angular_z", [2],
  {"linear_y", [3]
}};

Drag options to blanks, or click blank then click option'

Ajoy->axes[1]

Bjoy->axes[0]

Cjoy->axes[3]

Djoy->axes[2]

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up axis indices for linear and angular movements.

Using axes indices that do not exist or are incorrect.

Axis 1 controls linear_x, axis 0 controls angular_z, and axis 3 controls linear_y in joystick mapping.

Practice

1. Why does teleoperation enable manual control of a robot in ROS?

easy

A. Because it only records robot movements for later playback

B. Because it automatically programs the robot without human input

C. Because it allows a human to send commands remotely to the robot

D. Because it disables all robot sensors during operation

Solution

1. Step 1: Understand teleoperation purpose

   Teleoperation means controlling a robot from a distance by sending commands manually.

2. Step 2: Connect teleoperation to manual control

   Since a human sends commands directly, the robot moves as the human wants, enabling manual control.

3. Final Answer:

   Because it allows a human to send commands remotely to the robot -> Option C

4. Quick Check:

   Teleoperation = Remote manual control [OK]

Hint: Teleoperation means remote human control [OK]

Common Mistakes:

• Thinking teleoperation programs the robot automatically
• Confusing teleoperation with recording playback
• Assuming sensors are disabled during teleoperation

2. Which ROS package is commonly used for teleoperation via keyboard input?

easy

A. roslaunch

B. teleop_twist_keyboard

C. rviz

D. rosbag

Solution

1. Step 1: Identify teleoperation packages in ROS

   ROS provides a package named teleop_twist_keyboard to control robots using keyboard commands.

2. Step 2: Compare options

   roslaunch starts nodes, rviz visualizes data, and rosbag records data, but none provide keyboard teleoperation.

3. Final Answer:

   teleop_twist_keyboard -> Option B

4. Quick Check:

   Keyboard teleoperation = teleop_twist_keyboard [OK]

Hint: Keyboard teleoperation uses teleop_twist_keyboard [OK]

Common Mistakes:

• Confusing roslaunch as teleoperation tool
• Thinking rviz controls the robot manually
• Assuming rosbag sends commands

3. Given this ROS command: rosrun teleop_twist_keyboard teleop_twist_keyboard.py, what happens when you press the 'i' key?

medium

A. The robot moves backward

B. The robot stops immediately

C. The robot turns left

D. The robot moves forward

Solution

1. Step 1: Understand teleop_twist_keyboard controls

   In this package, pressing 'i' sends a forward velocity command to the robot.

2. Step 2: Match key to robot action

   Pressing 'i' moves the robot forward; other keys control turning or stopping.

3. Final Answer:

   The robot moves forward -> Option D

4. Quick Check:

   'i' key = move forward [OK]

Hint: 'i' key moves robot forward in teleop_twist_keyboard [OK]

Common Mistakes:

• Thinking 'i' stops the robot
• Confusing 'i' with turning keys
• Assuming 'i' moves robot backward

4. You tried to run teleoperation with rosrun teleop_twist_keyboard teleop_twist_keyboard.py but get a 'Permission denied' error. What is the likely fix?

medium

A. Make the script executable with chmod +x teleop_twist_keyboard.py

B. Reinstall ROS completely

C. Change the robot's battery

D. Run roscore twice

Solution

1. Step 1: Identify cause of 'Permission denied'

   This error usually means the script file lacks execute permission.

2. Step 2: Fix permission issue

   Running chmod +x teleop_twist_keyboard.py grants execute rights, allowing the script to run.

3. Final Answer:

   Make the script executable with chmod +x teleop_twist_keyboard.py -> Option A

4. Quick Check:

   Permission denied = add execute permission [OK]

Hint: Add execute permission to script with chmod +x [OK]

Common Mistakes:

• Reinstalling ROS unnecessarily
• Thinking hardware issues cause permission errors
• Running roscore multiple times won't fix permissions

5. You want to manually guide a robot arm using teleoperation but also record the commands for replay later. Which ROS tools would you combine?

hard

A. teleop_twist_keyboard and rosbag

B. rviz and roslaunch

C. roscore and rosparam

D. rosnode and rosservice

Solution

1. Step 1: Identify teleoperation tool

   teleop_twist_keyboard lets you manually control the robot arm by sending commands.

2. Step 2: Identify recording tool

   rosbag records ROS messages, so it can save the teleoperation commands for replay.

3. Step 3: Combine tools for manual control and recording

   Using both together lets you control manually and save the commands for later use.

4. Final Answer:

   teleop_twist_keyboard and rosbag -> Option A

5. Quick Check:

   Manual control + record = teleop_twist_keyboard + rosbag [OK]

Hint: Use teleop_twist_keyboard to control and rosbag to record [OK]

Common Mistakes:

• Confusing rviz as a recording tool
• Thinking roscore records commands
• Using rosnode or rosservice for control and recording