TIODRV – REXYGEN input/output driver with tasks

Block SymbolLicensing group: STANDARD

Function Description
The TIODRV block is used for configuration of special drivers of the REXYGEN system which are able to execute tasks defined by the IOTASK blocks. See the corresponding driver documentation. The prev input of the IOTASK block must be connected with the Tasks output of the TIODRV block. If the driver allows so, the next output of a TIODRV block which is already included in the configuration can be used to add more tasks. The next output of the last task remains unconnected. On the contrary to standard tasks, the number and order of the driver’s tasks are not checked by the REXYGEN Compiler compiler but by the input-output driver itself.

If the driver cannot guarantee periodic execution of some task (e.g. task is triggered by an external event), a corresponding flag is set for the given task. Such a task cannot contain blocks which require constant sampling period (e.g. the majority of controllers). If some of these restricted blocks are used, the executive issues a task execution error, which can be traced using the Diagnostics section of the REXYGEN Studio program. The cpu parameter can be used to specify where the driver thread should run on multi-CPU devices.

This block does not propagate the signal quality. More information can be found in the 1.4 section.

Input

prev	Input for chaining drivers (with tasks)	Long (I32)

Parameter

module	Module name	String
classname	I/O driver class name $⊙$ DrvClass	String
cfgname	Configuration file name $⊙$ iodrv.rio	String
factor	Execution factor $↓$ 1 $⊙$ 10	Long (I32)
stack	Stack size [bytes] $↓$ 1024 $⊙$ 10240	Long (I32)
pri	Driver thread logical priority $↓$ 1 $↑$ 31 $⊙$ 3	Long (I32)
cpu	CPU core assigned to driver thread (-1=default, 0=core 0, 1=core 1, ...) $↓$ -1 $↑$ 127 $⊙$ -1	Long (I32)

Output

next	Output for chaining drivers (with tasks)	Long (I32)
Tasks	Anchor for chain of I/O tasks	Long (I32)

[Previous] [Back to top] [Up] [Next]