Public Member Functions | Protected Attributes
ros_control_boilerplate::GenericHWControlLoop Class Reference

The control loop - repeatidly calls read() and write() to the hardware interface at a specified frequency We use MONOTONIC time to ensure robustness in the event of system time updates/change. See http://stackoverflow.com/questions/3523442/difference-between-clock-realtime-and-clock-monotonic. More...

#include <generic_hw_control_loop.h>

List of all members.

Public Member Functions

 GenericHWControlLoop (ros::NodeHandle &nh, boost::shared_ptr< ros_control_boilerplate::GenericHWInterface > hardware_interface)
 Constructor.
void update (const ros::TimerEvent &e)
 Timer event Note: we do not use the TimerEvent time difference because it does NOT guarantee that the time source is strictly linearly increasing.

Protected Attributes

boost::shared_ptr
< controller_manager::ControllerManager
controller_manager_
 ROS Controller Manager and Runner.
struct timespec current_time_
double cycle_time_error_threshold_
ros::Duration desired_update_freq_
ros::Duration elapsed_time_
boost::shared_ptr
< ros_control_boilerplate::GenericHWInterface
hardware_interface_
 Abstract Hardware Interface for your robot.
struct timespec last_time_
double loop_hz_
std::string name_ = "generic_hw_control_loop"
ros::NodeHandle nh_
ros::Timer non_realtime_loop_

Detailed Description

The control loop - repeatidly calls read() and write() to the hardware interface at a specified frequency We use MONOTONIC time to ensure robustness in the event of system time updates/change. See http://stackoverflow.com/questions/3523442/difference-between-clock-realtime-and-clock-monotonic.

Definition at line 55 of file generic_hw_control_loop.h.


Constructor & Destructor Documentation

Constructor.

Parameters:
NodeHandle
hardware_interface- the robot-specific hardware interface to be use with your robot

Definition at line 47 of file generic_hw_control_loop.cpp.


Member Function Documentation

Timer event Note: we do not use the TimerEvent time difference because it does NOT guarantee that the time source is strictly linearly increasing.

Definition at line 69 of file generic_hw_control_loop.cpp.


Member Data Documentation

ROS Controller Manager and Runner.

This class advertises a ROS interface for loading, unloading, starting, and stopping ros_control-based controllers. It also serializes execution of all running controllers in update.

Definition at line 98 of file generic_hw_control_loop.h.

Definition at line 90 of file generic_hw_control_loop.h.

Definition at line 83 of file generic_hw_control_loop.h.

Definition at line 82 of file generic_hw_control_loop.h.

Definition at line 87 of file generic_hw_control_loop.h.

Abstract Hardware Interface for your robot.

Definition at line 101 of file generic_hw_control_loop.h.

Definition at line 89 of file generic_hw_control_loop.h.

Definition at line 88 of file generic_hw_control_loop.h.

std::string ros_control_boilerplate::GenericHWControlLoop::name_ = "generic_hw_control_loop" [protected]

Definition at line 79 of file generic_hw_control_loop.h.

Definition at line 76 of file generic_hw_control_loop.h.

Definition at line 86 of file generic_hw_control_loop.h.


The documentation for this class was generated from the following files:


ros_control_boilerplate
Author(s): Dave Coleman
autogenerated on Thu Jun 6 2019 20:37:19