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. More...

#include <DisplayTask.hpp>

Inheritance diagram for ucm_schilling::DisplayTask:

Public Member Functions
	DisplayTask (std::string const &name="ucm_schilling::DisplayTask")

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

	~DisplayTask ()

bool	configureHook ()
	The following lines are template definitions for the various state machine. More...

bool	startHook ()

void	updateHook ()

void	errorHook ()

void	stopHook ()

void	cleanupHook ()

void	statusCheck (const UcmStatus &status)

void	processIO ()

void	run ()

void	init_gui_request ()

void	set_calib_values (const ucm_schilling::Config &arg)

Protected Attributes
Driver *	mDriver

Friends
class	DisplayTaskBase

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.

The name of a DisplayTaskContext is primarily defined via:

deployment 'deployment_name'
    task('custom_task_name','ucm_schilling::DisplayTask')
end

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

Constructor & Destructor Documentation

◆ DisplayTask() [1/2]

DisplayTask::DisplayTask ( std::string const & name = "ucm_schilling::DisplayTask" )

DisplayTaskContext constructor for DisplayTask

Parameters

name	Name of the task. This name needs to be unique to make it identifiable via nameservices.
initial_state	The initial DisplayTaskState of the DisplayTaskContext. Default is Stopped state.

◆ DisplayTask() [2/2]

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

DisplayTaskContext constructor for DisplayTask

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.

◆ ~DisplayTask()

DisplayTask::~DisplayTask ( )

Default deconstructor of DisplayTask

Member Function Documentation

◆ cleanupHook()

void DisplayTask::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.

◆ configureHook()

bool DisplayTask::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 "DisplayTaskName" do
  needs_configuration
  ...
end

◆ errorHook()

void DisplayTask::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.

◆ init_gui_request()

void DisplayTask::init_gui_request ( )

◆ processIO()

void DisplayTask::processIO ( )

◆ run()

void DisplayTask::run ( )

◆ set_calib_values()

void DisplayTask::set_calib_values ( const ucm_schilling::Config & arg )

◆ startHook()

bool DisplayTask::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.

◆ statusCheck()

void DisplayTask::statusCheck ( const UcmStatus & status )

◆ stopHook()

void DisplayTask::stopHook ( )

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

◆ updateHook()

void DisplayTask::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

◆ DisplayTaskBase

friend class DisplayTaskBase

friend

Member Data Documentation

◆ mDriver

Driver* ucm_schilling::DisplayTask::mDriver

protected

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

/build/rock-master-18.09-drivers-orogen-ucm-schilling-0.20171014/tasks/DisplayTask.hpp
/build/rock-master-18.09-drivers-orogen-ucm-schilling-0.20171014/tasks/DisplayTask.cpp

Public Member Functions

Protected Attributes

Friends