Revision history [back]

This is actually not really a ROS concept. At least, in the ROS world, you usually don't talk about "polling". The concept in ROS is actually called (spinning)[http://wiki.ros.org/roscpp/Overview/Callbacks%20and%20Spinning].

In this specific case, this means how often you publish respective messages (sensor and odometry), as written in the docu. The rate parameter specifies, how often the main loop (here)[https://github.com/hbrobotics/ros_arduino_bridge/blob/hydro-devel/ros_arduino_python/nodes/arduino_node.py#L133-L161]. This main loop is polling the sensor and odometry data and publishing it.

This is actually not really a ROS concept. At least, in the ROS world, you usually don't talk about "polling". The concept in ROS is actually called (spinning)[http://wiki.ros.org/roscpp/Overview/Callbacks%20and%20Spinning].spinning.

In this specific case, this means how often you publish respective messages (sensor and odometry), as written in the docu. The rate parameter specifies, how often the main loop (here)[https://github.com/hbrobotics/ros_arduino_bridge/blob/hydro-devel/ros_arduino_python/nodes/arduino_node.py#L133-L161]. here. This main loop is polling the sensor and odometry data and publishing it.

This is actually not really a ROS concept. At least, in the ROS world, you usually don't talk about "polling". The concept in ROS is actually called spinning.

In this specific case, this means how often you publish respective messages (sensor and odometry), as written in the docu. The rate parameter specifies, how often the main loop here. is actually running. This main loop is polling the sensor and odometry data and publishing it.