volef

Compute volumetric efficiency for a single engine manifold on a continuous basis.

Enter:

volef <priority> <interval> <filename> [+c]

Where:

priority	Specify the system task priority.
interval	Specify the process interval. Specify FAS, MED, or SLO or in milliseconds.
filename	Specify the specification file path.
+c	Optional. Specify this flag to identify this task as critical to the watchdog.

Example:

volef 8 SLO specs/volef_specs.315 +c &
The above command spawns ‘volef’ in the background at a priority of 8. The computations are performed once every second using the specifications given in the file /asset/specs/volef_specs.315. The task is also assigned to be a critical task. As a result, if the task ever stops responding to the watchdog, any test that is running will be aborted.

The volef task will register its name with the filename (not the full pathame), in this case “volef_specs.315”.  This name can be used by the ‘re-read’ command to request that it update the specifications by reading the specification file again.  This feature allows the specifications to be changed “on-the-fly” without slaying and restarting the app. 

Notes:

This task is normally started in the go script that starts CyFlex and assumes a 4-cycle engine.

See Also:

         The volef2 application can be used to compute volumetric efficiency for 2-cycle engines.

Computing Volumetric Efficiency, also see /cyflex/specs.def/volef.def for example spec