auv_control::PIDController Class Reference

The task context provides and requires services. It uses an ExecutionEngine to perform its functions. Essential interfaces are operations, data flow ports and properties. These interfaces have been defined using the oroGen specification. In order to modify the interfaces you should (re)use oroGen and rely on the associated workflow. Controller that takes either positions or velocities, expressed in either the world or aligned frames, and outputs "whatever" in the same frame. More...

#include <PIDController.hpp>

Inheritance diagram for auv_control::PIDController:

Public Member Functions
	PIDController (std::string const &name="auv_control::PIDController")
	PIDController (std::string const &name, RTT::ExecutionEngine *engine)
	~PIDController ()
bool	configureHook ()
	The following lines are template definitions for the various state machine. More...
bool	startHook ()
void	updateHook ()
void	errorHook ()
void	stopHook ()
void	cleanupHook ()

Protected Member Functions
bool	isPoseSampleValid ()

Protected Attributes
bool	on_init
base::Timeout	new_pose_samples_timeout

Friends
class	PIDControllerBase

Detailed Description

The task context provides and requires services. It uses an ExecutionEngine to perform its functions. Essential interfaces are operations, data flow ports and properties. These interfaces have been defined using the oroGen specification. In order to modify the interfaces you should (re)use oroGen and rely on the associated workflow. Controller that takes either positions or velocities, expressed in either the world or aligned frames, and outputs "whatever" in the same frame.

The name of a TaskContext is primarily defined via:

     deployment 'deployment_name'
         task('custom_task_name','auv_control::PIDController')
     end

It can be dynamically adapted when the deployment is called with a prefix argument.

Constructor & Destructor Documentation

PIDController::PIDController

(

std::string const &

name = "auv_control::PIDController"

)

TaskContext constructor for PIDController

Parameters

name	Name of the task. This name needs to be unique to make it identifiable via nameservices.

PIDController::PIDController	(	std::string const &	name,
		RTT::ExecutionEngine *	engine
	)

TaskContext constructor for PIDController

Parameters

name	Name of the task. This name needs to be unique to make it identifiable for nameservices.
engine	The RTT Execution engine to be used for this task, which serialises the execution of all commands, programs, state machines and incoming events for a task.
initial_state	The initial TaskState of the TaskContext. Default is Stopped state.

PIDController::~PIDController

(

)

Default deconstructor of PIDController

Member Function Documentation

void PIDController::cleanupHook

(

)

This hook is called by Orocos when the state machine transitions from Stopped to PreOperational, requiring the call to configureHook() before calling start() again.

bool PIDController::configureHook

(

)

The following lines are template definitions for the various state machine.

This hook is called by Orocos when the state machine transitions from PreOperational to Stopped. If it returns false, then the component will stay in PreOperational. Otherwise, it goes into Stopped.

It is meaningful only if the #needs_configuration has been specified in the task context definition with (for example):

task_context "TaskName" do
  needs_configuration
  ...
end

void PIDController::errorHook

(

)

This hook is called by Orocos when the component is in the RunTimeError state, at each activity step. See the discussion in updateHook() about triggering options.

Call recover() to go back in the Runtime state.

bool PIDController::isPoseSampleValid ( )

protected

bool PIDController::startHook

(

)

This hook is called by Orocos when the state machine transitions from Stopped to Running. If it returns false, then the component will stay in Stopped. Otherwise, it goes into Running and updateHook() will be called.

void PIDController::stopHook

(

)

This hook is called by Orocos when the state machine transitions from Running to Stopped after stop() has been called.

void PIDController::updateHook

(

)

This hook is called by Orocos when the component is in the Running state, at each activity step. Here, the activity gives the "ticks" when the hook should be called.

The error(), exception() and fatal() calls, when called in this hook, allow to get into the associated RunTimeError, Exception and FatalError states.

In the first case, updateHook() is still called, and recover() allows you to go back into the Running state. In the second case, the errorHook() will be called instead of updateHook(). In Exception, the component is stopped and recover() needs to be called before starting it again. Finally, FatalError cannot be recovered.

Friends And Related Function Documentation

friend class PIDControllerBase

friend

Member Data Documentation

base::Timeout auv_control::PIDController::new_pose_samples_timeout

protected

bool auv_control::PIDController::on_init

protected

---

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

• /build/rock-master-18.09-control-orogen-auv-control-0.20180621/tasks/PIDController.hpp
• /build/rock-master-18.09-control-orogen-auv-control-0.20180621/tasks/PIDController.cpp