developer, maintenancecenter, writer
57
edits
Difference between revisions of "NVGate Tachometer"
Jump to navigation
Jump to search
no edit summary
| Line 715: | Line 715: | ||
===Extract tach from FFT waterfall and edit tachometer=== | ===Extract tach from FFT waterfall and edit tachometer=== | ||
[[External_Tools:_TachTool|Read this page]] | [[External_Tools:_TachTool|Read this page]] | ||
*'''Tachometer centered on FFT/SOA blocks''' | |||
This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section. | |||
'''With classical tach:''' | |||
The RPM is collected at the end of the analysis block | |||
[[File:RPM1.png|thumb]] | |||
This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a | |||
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones. | |||
'''With centered tach:''' | |||
The RPM is calculated as the average speed during the block duration to be synchronized with the | |||
analyzed data. | |||
[[File:RPM2.png|thumb]] | |||
With the centered tachometer, the orders calculations match more accurately the actual orders in | |||
waterfall. | |||
The computation of the angular speed takes in account the averaging, triggering and overlap used | |||
in the plug-in. | |||
The centered speed is calculated as: | |||
[[File:CT1.png|thumb]] | |||