MotoHawk:Blocks:ADC Angle Vector Ready Trigger

ADC Angle Vector Ready Trigger

This MotoHawk™ block triggers a Simulink Function-Call subsystem when an ADC Angle Vector has been captured by the system.

Block ID

ADC Angle Vector Ready Trigger

Library

MotoHawk_lib/Analog I/O Blocks

Description

More than one trigger may be placed in a model basing off of the same event. In this case, the 'Priority Order' can be used to order these independent triggers. If the priorities are the same, then the order is determined by Simulink. Checking 'This trigger is inside another triggered subsystem' will attempt to simulate the block inside of another triggered rate, when the rate is periodic. The most common way to check this is to place a background periodic task inside of a foreground periodic task, or vice versa.

The trigger from this block may occur in bursts, synchronized to the outer rate, while simulating, but will perform as expected on the target. Note that 'This trigger is inside another triggered subsystem' should not be checked on top-level triggers, otherwise the block will not simulate at all. If this trigger is used inside of a containing subsystem, normally the triggered subsystem will pause and resume based on the enable/disable status of the containing subsystem. Checking 'Trigger even when containing subsystem is disabled' will cause triggers to occur even while the parent is disabled.

Note that this feature will not simulate, but will execute correctly on the target.

Block Parameters

Parameter Field	Values	Comments/Description
Name	'single-quote' enclosed alpha-numeric text	This should be the name of the [ADCAngleVectorDefinition.html ADC Angle Vector Object Definition] that this block is associated with.
Priority Order (lower executes first)	Numeric (Integer)	Set priority of trigger, lower values execute before higher values.
This trigger is inside another triggered subsystem	Check Box (enable)	Enable if trigger is inside another triggered subsystem. Trigger attempts to simulate the block inside of another triggered rate, when the rate is periodic. The most common reason to enable is to place a background periodic task inside of a foreground periodic task, or vice versa. The trigger from this block may occur in bursts, synchronized to the outer rate, while simulating, but will perform as expected on the target. Do not enable on top-level triggers, otherwise the block will not simulate at all.
Trigger even when containing subsystem is disabled	Check Box (enable)	If this trigger is used inside of a containing subsystem, normally the triggered subsystem will pause and resume based on the enable/disable status of the containing subsystem. Checking this causes triggers to occur even while the parent is disabled. Note that this feature will not simulate, but will execute correctly on the target.