MotoHawk:Blocks:Dual PSP - Revision history

Wendy.Bolakowski: /* Pulse Scheduling */

2013-04-03T15:22:08Z

‎Pulse Scheduling

Wendy.Bolakowski: /* Pulse Scheduling */

2013-04-03T15:19:14Z

‎Pulse Scheduling

Wendy.Bolakowski: /* Block Parameters */

2013-04-03T15:15:30Z

‎Block Parameters

Wendy.Bolakowski at 17:36, 17 September 2012

2012-09-17T17:36:19Z

Ron.Lewis at 17:19, 17 September 2012

2012-09-17T17:19:42Z

Wendy.Bolakowski at 17:14, 17 September 2012

2012-09-17T17:14:45Z

Wendy.Bolakowski at 17:10, 17 September 2012

2012-09-17T17:10:51Z

Wendy.Bolakowski at 17:04, 17 September 2012

2012-09-17T17:04:24Z

Wendy.Bolakowski at 17:03, 17 September 2012

2012-09-17T17:03:12Z

Wendy.Bolakowski at 17:02, 17 September 2012

2012-09-17T17:02:05Z

@@ Line 103: / Line 103: @@
 [[Category:MotoHawk_Advanced_Digital_I/O_Blocks|Dual PSP]]
-== Pulse Scheduling ==
+== Block Inputs ==
 === How are the block inputs such as Start Angle applied? ===

← Older revision		Revision as of 15:19, 3 April 2013
Line 104:		Line 104:

	== Pulse Scheduling ==		== Pulse Scheduling ==
		+
		+	=== How are the block inputs such as Start Angle applied? ===
		+
		+	The start angle is applied at the rate that the block executes. This is true for all PSP like behaviors. The start may not be applied directly to the TPU then.
		+
		+	=== If there is a step change to the block inputs, are missing or double pulses possible? ===
		+
		+	Double pulses are not inherently protected for and so they can occur if you step change the pulse’s start time toward TDC. This is because the PSP is always trying to schedule the pulse and it doesn’t know that the last occurrence of the pulse was not that long ago. It does not know the context of the pulse. This is only a problem for single pulse systems. A system with more than one pulse won’t have this problem because the system goes from scheduling one pulse to scheduling the other and thus won’t experience the step change double pulse. This can actually be used to protect for it.
		+
		+	The figure illustrates.
		+
		+	[[image:pulse_scheduling.png]]

← Older revision		Revision as of 15:15, 3 April 2013
Line 102:		Line 102:

	[[Category:MotoHawk_Advanced_Digital_I/O_Blocks\|Dual PSP]]		[[Category:MotoHawk_Advanced_Digital_I/O_Blocks\|Dual PSP]]
		+
		+	== Pulse Scheduling ==

← Older revision		Revision as of 17:36, 17 September 2012
Line 101:		Line 101:
	\|}		\|}

−	[[Category:MotoHawk_Advanced_Digital_I/O_Blocks]]	+	[[Category:MotoHawk_Advanced_Digital_I/O_Blocks\|Dual PSP]]

← Older revision		Revision as of 17:19, 17 September 2012
Line 1:		Line 1:
−	==Dual PSP==	+	=Dual PSP=

	The MotoHawk™ Dual PSP block provides an interface to ControlCore's PSP (Periodic Synchronous Pulse) behavior. ControlCore can loosely be thought of as the module's operating system. Such pulses are periodic because they are synchronised to the Encoder within the system. This block allows one or two pulses to be created and managed by ControlCore. This block is a powerful and very flexible block in that it allows for very precise control of pulse generation through its dual termination capability. It is somewhat different to other pulse generation blocks like the MotoHawk™ Injector Sequence Block in that it does not create outputs that span multiple resources. The power of this block would allow the functionality of the MotoHawk™ Injector Sequence Block to be implemented via first principles, but multiple Dual PSP Blocks would be needed.		The MotoHawk™ Dual PSP block provides an interface to ControlCore's PSP (Periodic Synchronous Pulse) behavior. ControlCore can loosely be thought of as the module's operating system. Such pulses are periodic because they are synchronised to the Encoder within the system. This block allows one or two pulses to be created and managed by ControlCore. This block is a powerful and very flexible block in that it allows for very precise control of pulse generation through its dual termination capability. It is somewhat different to other pulse generation blocks like the MotoHawk™ Injector Sequence Block in that it does not create outputs that span multiple resources. The power of this block would allow the functionality of the MotoHawk™ Injector Sequence Block to be implemented via first principles, but multiple Dual PSP Blocks would be needed.

← Older revision		Revision as of 17:14, 17 September 2012
Line 101:		Line 101:
	\|}		\|}

−	[[Category:~~MotoHawk Blocks:Advanced Digital I~~/~~O Blocks~~]]	+	[[Category:MotoHawk_Advanced_Digital_I/O_Blocks]]

← Older revision		Revision as of 17:10, 17 September 2012
Line 101:		Line 101:
	\|}		\|}

−	[[Category:Advanced Digital I/O Blocks]]	+	[[Category:MotoHawk Blocks:Advanced Digital I/O Blocks]]

← Older revision		Revision as of 17:04, 17 September 2012
Line 101:		Line 101:
	\|}		\|}

−	[[Category:Advanced Digital I/O Blocks~~\|Dual PSP~~]]	+	[[Category:Advanced Digital I/O Blocks]]

← Older revision		Revision as of 17:03, 17 September 2012
Line 101:		Line 101:
	\|}		\|}

−	[[Category:Advanced Digital I/O]]	+	[[Category:Advanced Digital I/O Blocks\|Dual PSP]]

← Older revision		Revision as of 17:02, 17 September 2012
Line 101:		Line 101:
	\|}		\|}

−	[[Category:~~MotoHawk Library Categories\|~~Advanced Digital I/O]]	+	[[Category:Advanced Digital I/O]]