Wendy.Bolakowski at 17:46, 17 September 2012

2012-09-17T17:46:53Z

Wendy.Bolakowski: Created page with "=Input Capture Trigger= This MotoHawk™ block triggers a Simulink Function-Call subsystem when the input capture triggers. ==Block ID== Input Capture Trigger ==Library== ..."

2012-09-13T18:30:43Z

Created page with "=Input Capture Trigger= This MotoHawk™ block triggers a Simulink Function-Call subsystem when the input capture triggers. ==Block ID== Input Capture Trigger ==Library== ..."

New page

=Input Capture Trigger=

This MotoHawk™ block triggers a Simulink Function-Call subsystem when the input capture triggers.

==Block ID==

Input Capture Trigger

==Library==

MotoHawk_lib/Advanced Digital I/O

==Description==

[[Image:InputCaptureTrigger.png]]

Use this block to trigger a Simulink Function-Call subsystem, when the [InputCaptureDefinition.html Input Capture Definition] block triggers. If the Trigger Mode in the Input Capture Definition block is set to "None," this block will never trigger.

More than one trigger may be placed in a model associated with the same event. In this case, use the 'Priority Order' 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 reason 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. <br /><br /> Do NOT enable 'This trigger is inside another triggered subsystem' on a top-level trigger, 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" | Alpha-numeric text, single-quote enclosed
| class="TableTDStyle" style="width: 299px" valign="top" | Name the input capture resource, must match exactly that in the Input Capture Definition block. No special characters, such as spaces, dashes, commas (underscore allowed).
|- id="priority_order"
| class="TableTDStyle" style="width: 172px" valign="top" | Priority Order
| class="TableTDStyle" style="width: 158px" valign="top" | 0-4
| class="TableTDStyle" style="width: 299px" valign="top" | When more than one trigger is used, set Trigger Priority level, to order priority; lower executes before higher. If the priorities are the same, then the order is implementation dependent.
|- id="run_disabled"
| 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.
|- id="override_app_monitor"
| 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.
|}

</div>

← Older revision		Revision as of 17:46, 17 September 2012
Line 47:		Line 47:
	\|}		\|}

−	</~~div>~~	+	[[Category:MotoHawk_Advanced_Digital_I/O_Blocks\|Input Capture Trigger]]

MotoHawk:Blocks:Input Capture Trigger - Revision history

Wendy.Bolakowski at 17:46, 17 September 2012

Wendy.Bolakowski: Created page with "=Input Capture Trigger= This MotoHawk™ block triggers a Simulink Function-Call subsystem when the input capture triggers. ==Block ID== Input Capture Trigger ==Library== ..."