Difference between revisions of "MotoHawk:Blocks: PSP Oneshot Unsync"
(Created page with "=Unsynchronized PSP Output Pulse= The MotoHawk™ Unsynchronized PSP pulse blocks allows PSP like behaviors ([InjectorSequence.html Injector Sequence], [DualPSP.html Dual PSP...") |
(→Operation Principles) |
||
| Line 20: | Line 20: | ||
===Operation Principles=== | ===Operation Principles=== | ||
| − | Often systems have a need to generate a pulse(s) on outputs that have been configured for Periodic Synchronized Pulse (PSP) operation when an encoder signal is not present. A common situation is to execute a prime pulse before encoder synchronization has been achieved. The MotoHawk™ Unsynchronized PSP Oneshot blocks allows PSP like behaviors ([InjectorSequence.html Injector Sequence], [DualPSP.html Dual PSP], [MultiplePSP.html Multiple PSP] etc) to generate pulses without encoder speed. | + | Often systems have a need to generate a pulse(s) on outputs that have been configured for Periodic Synchronized Pulse (PSP) operation when an encoder signal is not present. A common situation is to execute a prime pulse before encoder synchronization has been achieved. The MotoHawk™ Unsynchronized PSP Oneshot blocks allows PSP like behaviors ([http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/InjectorSequence.html Injector Sequence], [http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/DualPSP.html Dual PSP], [http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/MultiplePSP.html Multiple PSP] etc) to generate pulses without encoder speed. |
| − | This block is used in conjunction with the [PSPOneshotUnsyncTrigger.html PSP Oneshot Unsynce Trigger] block to generate pulse(s). This block identifies the resource that is to support this behavior. The operation will only function if a PSP behavior exists in the model that is utilizing this selected resource. | + | This block is used in conjunction with the [http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/PSPOneshotUnsyncTrigger.html PSP Oneshot Unsynce Trigger] block to generate pulse(s). This block identifies the resource that is to support this behavior. The operation will only function if a PSP behavior exists in the model that is utilizing this selected resource. |
| − | Triggering execution of the [PSPOneshotUnsyncTrigger.html PSP Oneshot Unsync Trigger] block will start a single pulse on the resource referenced by this block provided the encoder has not achieved synchronization. Attempts to trigger the generation of a pulse once the encoder has synchronized are ignored. An encoder that has synchronized, but then loses synchronization because of an error is still considered synchronized so far as this behavior is concerned. In general pulses are only possible while the encoder system is observing zero speed and also while the encoder is attempting initial synchronization. | + | Triggering execution of the [http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/PSPOneshotUnsyncTrigger.html PSP Oneshot Unsync Trigger] block will start a single pulse on the resource referenced by this block provided the encoder has not achieved synchronization. Attempts to trigger the generation of a pulse once the encoder has synchronized are ignored. An encoder that has synchronized, but then loses synchronization because of an error is still considered synchronized so far as this behavior is concerned. In general pulses are only possible while the encoder system is observing zero speed and also while the encoder is attempting initial synchronization. |
The condition of the pulses of the parent PSP behavior have no effect on the ability to schedule unsynchronized oneshot pulses. Thus disabling the pulses on the PSP parent won't prevent an unsynchronized oneshot pulse from being scheduled by this behavior. | The condition of the pulses of the parent PSP behavior have no effect on the ability to schedule unsynchronized oneshot pulses. Thus disabling the pulses on the PSP parent won't prevent an unsynchronized oneshot pulse from being scheduled by this behavior. | ||
| Line 30: | Line 30: | ||
Repeated triggers that occur while the pulse is already asserted are ignored. | Repeated triggers that occur while the pulse is already asserted are ignored. | ||
| − | The [PSPOneshotUnsyncTrigger.html PSP Oneshot Unsync Trigger] block supports a signal that allows the duration of the triggered pulse to be controlled. | + | The [http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/PSPOneshotUnsyncTrigger.html PSP Oneshot Unsync Trigger] block supports a signal that allows the duration of the triggered pulse to be controlled. |
==Block Parameters== | ==Block Parameters== | ||
Revision as of 19:54, 13 September 2012
Contents
Unsynchronized PSP Output Pulse
The MotoHawk™ Unsynchronized PSP pulse blocks allows PSP like behaviors ([InjectorSequence.html Injector Sequence], [DualPSP.html Dual PSP], [MultiplePSP.html Multiple PSP] etc) to generate a oneshot like pulse without encoder speed.
Block ID
PSP Oneshot Unsync
Library
MotoHawk_lib/Advanced Digital I/O
Description
- [#PSPOneshotUnsync_BlockParameters Block Mask Parameter Descriptions]
- [#principles Operation Principles]
Operation Principles
Often systems have a need to generate a pulse(s) on outputs that have been configured for Periodic Synchronized Pulse (PSP) operation when an encoder signal is not present. A common situation is to execute a prime pulse before encoder synchronization has been achieved. The MotoHawk™ Unsynchronized PSP Oneshot blocks allows PSP like behaviors (Injector Sequence, Dual PSP, Multiple PSP etc) to generate pulses without encoder speed.
This block is used in conjunction with the PSP Oneshot Unsynce Trigger block to generate pulse(s). This block identifies the resource that is to support this behavior. The operation will only function if a PSP behavior exists in the model that is utilizing this selected resource.
Triggering execution of the PSP Oneshot Unsync Trigger block will start a single pulse on the resource referenced by this block provided the encoder has not achieved synchronization. Attempts to trigger the generation of a pulse once the encoder has synchronized are ignored. An encoder that has synchronized, but then loses synchronization because of an error is still considered synchronized so far as this behavior is concerned. In general pulses are only possible while the encoder system is observing zero speed and also while the encoder is attempting initial synchronization.
The condition of the pulses of the parent PSP behavior have no effect on the ability to schedule unsynchronized oneshot pulses. Thus disabling the pulses on the PSP parent won't prevent an unsynchronized oneshot pulse from being scheduled by this behavior.
Repeated triggers that occur while the pulse is already asserted are ignored.
The PSP Oneshot Unsync Trigger block supports a signal that allows the duration of the triggered pulse to be controlled.
Block Parameters
| Parameter Field | Values | Comments/Description |
| Name | Alpha-numeric text, single-quote enclosed |
Unique C-legal name that will be used to identify this instance of the block. This name will be used by other PSP Oneshot Unsync blocks like the [PSPOneshotUnsyncTrigger.html PSP Oneshot Unsync Trigger] block to reference this definition block. |
| Resource | Drop-down list | Module resource (target module dependent) that is to support unsynchronized oneshot pulses. |
