Flexible Encoder - Revision history

Wayne.Hawken: /* Interpolative Triggers */

2018-07-05T13:03:38Z

‎Interpolative Triggers

Michael.Vogeli: fixed breaks

2015-10-01T15:09:35Z

fixed breaks

Michael.Vogeli: fixed breaks

2015-10-01T15:07:12Z

fixed breaks

Michael.Vogeli: fixed breaks

2015-10-01T15:05:38Z

fixed breaks

Michael.Vogeli: fixed breaks

2015-10-01T15:04:59Z

fixed breaks

Michael.Vogeli: fixed breaks

2015-10-01T15:03:48Z

fixed breaks

Michael.Vogeli: fixed breaks

2015-10-01T15:03:01Z

fixed breaks

Michael.Vogeli: fixed breaks

2015-10-01T15:02:20Z

fixed breaks

Michael.Vogeli: fixed breaks

2015-10-01T15:01:37Z

fixed breaks

Michael.Vogeli: fixed breaks

2015-10-01T14:57:50Z

fixed breaks

@@ Line 101: / Line 101: @@
 In classic encoder, the TDC would be reported on the next physical tooth.  Resolution is one tooth.
 Flexible Encoder provides for an interpolation between teeth.
 In legacy encoder you need to schedule based on where you see the physical teeth.  This can particularly be a problem if there is a low number of teeth.   But, with flexible encoder the trigger is interpolative.
@@ Line 117: / Line 110: @@
 [[Image:interpolative_triggers1.jpg|750px]]
 =Average and Cycle RPM=

@@ Line 790: / Line 790: @@
 No, the TPU on the 5xx modules (48, 80, 128-pin) aren’t capable of supporting as complex and flexible as the Flexible Encoder (5xxx modules have an eTPU, or enhanced TPU).
-<br\>
+<br/>
 .  <big>'''How do I define my sensor type (Vr or Hall Effect)?'''</big>
 There is now a new block, Interface (VR/DG) under Module Configuration Blocks library of MotoHawk.  If you don't put a signal interface block in your model, you will get a build warning.
-<br\>
+<br/>
 .  <big>'''Can I use an old version of MotoHawk?'''</big>
 No, 2012a or higher is required for Flexible Encoder.
-<br\>
+<br/>
 . <big>'''Does Flexible Encoder support Variable CAM?'''</big>
@@ Line 806: / Line 806: @@
 Yes, there is a Phase Reporting dropdown option on the Absolute or Companion Source selection.  Then, the Variable CAM is implemented on Flex Encoder, through: Source Phase
 Trigger, Setting the "Phase Reporting" attribute on the source to a suitable value, Get Last Source Phase block.
-<br\>
+<br/>
 .  <big>'''For a CAM-only pattern, such as 6-Plus-1, should it still be defined as if it were 360-degrees?'''</big>
 Yes, the xml pattern defines a WHEEL, so it must be 360-degrees.
-<br\>
+<br/>
 . <big>'''Are there any example xml files?'''</big>
 There are some xml patterns included with MotoHawk as examples in the MotoHawk installation.   /Motocoder/Encoders (ex. C:\Program Files (x86)\Woodward\MCS\MotoHawk\2012b_beta4.298\MotoCoder\Encoders).
-<br\>
+<br/>
 .  <big>'''When defining a CAM pattern, should I start with tooth 0 at angle 0, or should this contemplate the phase difference between the two wheels?'''</big>
@@ Line 823: / Line 823: @@
 An example could be the same pattern definition can be used twice yet have different phasing. E.g. single 60M2 wheel with two sensors
-<br\>
+<br/>
 .  <big>'''Can you confirm that both the 60-Minus-2 and 6-Plus-1 patterns would be considered standard unique and that rather than a Sync Companion, the 6-Plus-1 should be setup as a Half-Cycle Companion?'''</big>
@@ Line 834: / Line 834: @@
 Even if you have a Standard Unique pattern, you would need another (companion) source to determine half cycle information.  A companion source can give half cycle information (ex. CAM).  A different absolute source can be used as a companion also, and this could provide redundancy.   So, a 60-1 and a 24-1 would both be defined as Standard Unique sources, and in one application the 24-1 could be a companion to the 60-1 and provide redundancy in the event that the 60-1 is lost.  In another application the 24-1 could be the absolute source with a different (maybe single tooth) wheel as a companion.
-<br\>
+<br/>

@@ Line 716: / Line 716: @@
 '''Half Cycle 0'''
-<br\>
+<br/>
-<br\>
+<br/>
 ====SetHalfCycleTooth====

@@ Line 578: / Line 578: @@
 ====Standard Unique Keys====
-'''Standard''':  Provide Sync <br\>
+'''Standard''':  Provide Sync <br/>
-'''Unique''' - Stands Alone <br\>
+'''Unique''' - Stands Alone <br/>
 The 18M1, 60M2, 36P1 would all be examples of Standard Unique Keys.

@@ Line 502: / Line 502: @@
 == Key Construction ==
-<br\>
+<br/>
 <big>'''Keys Describe how to synchronize a pattern and are identified by the application developer.'''
-<br\>
+<br/>
-<br\>
+<br/>
 A key is a pattern that is used by the flexible encoder system to facilitate pattern synchronization. Pattern synchronization needs to occur before the encoder system can associate each observed tooth to a specific angle on the encoder wheel. The flexible encoder observes the input signal(s) and searches that signal for a key(s). There can sometimes be more than one.

@@ Line 481: / Line 481: @@
 [[Image:FlexiEnc_ToothCamWheel.png]]
-<br\>
+<br/>
-<br\>
+<br/>

@@ Line 352: / Line 352: @@
 There should be no faults on the source that is switched to.
-<br\>
+<br/>
-<br\>
+<br/>
 = Diagnostics =

@@ Line 325: / Line 325: @@
 [[Image:FlexiEnc_FailOverSwitch.png]]
-<br\>
+<br/>
-<br\>
+<br/>
-<br\>
+<br/>
 ===Time Delay Before Attempting Sync===

@@ Line 159: / Line 159: @@
 '''Does Pseudo Encoder support RPM Triggers?'''  No
-<br\> <br\><br\>
+<br/> <br/><br/>
 = Absolute and Companion Sources=

@@ Line 94: / Line 94: @@
 .  If you need to design a variable cam system, there is a Phase Reporting dropdown option on the Absolute or Companion Source selection.  Then, the Variable CAM is implemented on Flex Encoder, through the use of the Flexible Encoder Source Phase Trigger and Get Last Source Phase blocks.
-<br\>
+<br/>
-<br\>
+<br/>
 =Interpolative Triggers=