View source for MotoHawk:Blocks:ADC Angle Vector Stopped Trigger

=ADC Angle Vector Stopped Trigger=

This MotoHawk™ block triggers a Simulink Function-Call subsystem when ADC Angle Vector data acquistion was interrupted because of an error condition. There are a number of error conditions that will result in the execution of this trigger including when an encoder error is detected or because of a data acquisition overrun. The [ADCAngleVectorReadyTrigger.html Ready Trigger] won't execute when there is an error because the entire vector will not have been acquired. This trigger executes instead to provide the model a notification to indicate that pending vectors won't occur. The system will automatically re-synchronize itself and start the data acquisition again, but all partially acquired vectors are discarded.

An encoder error can cause an ADC Angle Vector acquisition error because it is used to trigger the ADC conversion. Some of the triggers may be in error if the encoder has itself encountered a problem.

Data overrun occurs when the data physcially can't be acquired without the loss of some of the data. Three things contribute to overrun. These are the number of samples to be converted on each trigger, the angular spacing between the triggers and the current engine speed that defines the rate at which the triggers are to occur. The ADC takes a finite amount of time to acquire a sample. An overrun will occur if the total time required to acquire the specified number of samples ever exceeds the time available between triggers.

==Block ID==

ADC Angle Vector Stopped Trigger

==Library==

MotoHawk_lib/Analog I/O Blocks

==Description==

[[Image:ADCAngleVectorStoppedTrigger.JPG]]

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==

{| class="TableMHStyle"
| class="TableHeaderTDStyle" style="width: 172px" | Parameter Field
| class="TableHeaderTDStyle" style="width: 158px" | Values
| class="TableHeaderTDStyle" style="width: 299px" | Comments/Description
|- id="nam"
| class="TableTDStyle" style="width: 172px" valign="top" | Name
| class="TableTDStyle" style="width: 158px" valign="top" | 'single-quote' enclosed alpha-numeric text
| class="TableTDStyle" style="width: 299px" valign="top" |
This should be the name of the [ADCAngleVectorDefinition.html ADC Angle Vector Object Definition] that this block is associated with.
|- id="priority_order"
| class="TableTDStyle" style="width: 172px" valign="top" | Priority Order (lower executes first)
| class="TableTDStyle" style="width: 158px" valign="top" | Numeric (Integer)
| class="TableTDStyle" style="width: 299px" valign="top" | Set priority of trigger, lower values execute before higher values.
|- id="trig"
| class="TableTDStyle" style="width: 172px" valign="top" | This trigger is inside another triggered subsystem
| class="TableTDStyle" style="width: 158px" valign="top" | Check Box (enable)
| class="TableTDStyle" style="width: 299px" valign="top" | 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.
|- id="trig_disables"
| class="TableTDStyle" style="width: 172px" valign="top" | Trigger even when containing subsystem is disabled
| class="TableTDStyle" style="width: 158px" valign="top" | Check Box (enable)
| class="TableTDStyle" style="width: 299px" valign="top" | 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.
|}

[[Category:MotoHawk Analog I/O Blocks|ADC Angle Vector Stopped Trigger]]