Professional Documents
Culture Documents
Version 03-22-04
(contains instructions for naturally aspirated,
single cylinder, port injection, natural gas
operation)
The links on the next page will bring you directly to instructions for
how to perform WAVE modeling tasks. The links are in
chronological order (building model elements, describing the
element characteristics, viewing results).
Gaseous Fuels
Join the junctions with Ducts. Using the left mouse button, click and drag from the
pink connection point on the leftmost ambient junction, labeled amb1, to the left
connection point on the neighboring orifice junction, labeled orif1. This
draws/creates a duct between the two junctions. The leftmost ambient will be the
intake ambient and the rightmost will be the exhaust ambient. Connect the
remaining junctions following the L to R convention. Note that the orifice icons
disappear, because the default duct diameter is zero.
The recommended convention is to draw all ducts starting from the intake
and drawing towards the exhaust.
In this case there are four ducts. It is assumed that hardware measurements
have been made so that each duct can be defined similar to those
measurements in the above picture.
Click OK to complete the data entry for duct1, then enter data
from the schematic for ducts 2, 3 and 4.
Model Valves
The connections from duct2 and duct3 to
the cyl1 junction are assumed to be valves.
The blue connection from duct2 denotes an
intake valve and the red connection to duct3
denotes an exhaust valve.
If you are not sure which is the correct button, hover the cursor over toolbar icons to
bring up tool tips and find the Run Input Check button.
The Input Check consists of the solver internally assembling the network and
initializing the gas state of every element within the model. If it can successfully
perform these tasks, the model is ready to run a full analysis in the solver.
When the Input Check is successful, the last item printed in the launched shell
window is the simulation title.
Standard output from the input check is printed to the shell but is also printed to a
file having the same prefix as the model file but with a .out extension. This .out file
will be created in the same directory as the .wvm file. If the input check was
unsuccessful, viewing this .out file may help you find problems.
Click on the Simulation pull-down menu and select the Time Plot menu item.
The only plots in the Existing Plots list are the pressure and
temperature plots from duct2. This is because these plots
are allowed at duct3 as well.
Run model in screen mode by clicking the toolbars Run Screen Mode button.
Screen mode runs the model at high priority while sending standard output to the screen.
Batch mode runs the model at reduced priority while sending standard output to the .out file
(batch mode is not discussed here).
WAVE can produce many output files. Click here to find a summary of output file names and
contents.
Open the *.out file with and editor and proceed to the cyclic output section.
Row (1) gives an abbreviation for what each column of data is displaying. This information may be useful
for debugging purposes in simulations that fail during run-time.
Row (2) is a summary for Cylinder #1 during engine cycle 0, the start-up cycle (WAVE simulations, by
default, begin at IVC for cylinder #1 unless otherwise specified in the Simulation -> General Parameters
panel). Only Cylinder #1 will have results for engine cycle 0.
Row (3) is a summary of engine system performance for engine cycle 0.
Rows (4+) will be a summary of every individual cylinder in the system for each engine cycle followed by a
engine system summary for each cycle.
Starting at engine cycle 3, a line denoting auto-convergence conditions is printed to the output. When auto-
convergence conditions are satisfied, if the convergence detection was activated in the Simulation ->
General Parameters panel, WAVE will run two more engine cycles and then finish the case. This happens
regardless of whether or not convergence conditions are satisfied in the following two engine cycles.
The columns titles as labeled in row (1) relate to the lines summarizing individual cylinder
performance. They are, in order -- Cylinder Number, Engine Cycle (cumulative from start of case),
Timestep number (cumulative from start of case), Mass Airflow (kg/hr), Volumetric Efficiency, Exhaust Port
Temperature (K), Equivalence Ratio, IMEP (bar), PMEP (bar), Indicated Horsepower (hp), Indicated
Specific Fuel Consumption (g/kW-hr), Cylinder Pressure at IVC (bar), Cylinder Temperature at IVC (K), and
Trapped Fuel/Air Ratio at IVC. There also is much other data in the *.out file
that the user should become familiar with.
University of Wisconsin Madison
GTI - ERC WAVE Quick Reference
Engine Research Center
Guide, March 2004 pg. 52
.sum File
Return
to link
slide
The .sum file is a simple ASCII text file that can be viewed using any text editor, but it
intended for use by the WavePost post-processor.
The .sum file contains a group of name=value pairs that detail the cycle-averaged results for
each case in the simulation. Cycle-averaged results are single-number values detailing
results that are calculated as an average over the entire last cycle in the
simulation. Examples include Torque, Power, and Fuel-Consumption (a list of what each
name in the .sum file equates to can be found in the REFERENCE LIBRARY, or simply click
here).
The *.wvd file is binary and can not be opened with an editor.
WAVE also will create a .wvd file. The .wvd file is a binary file (not legible in a text-editor)
written in Ricardo SDF (Standard Data File) format and is also intended for use by the
WavePost post-processor. Data for requested time plots and datasets are stored in the .wvd
file. If necessary, this data can be extracted by using either the SDFBrowser or the sdftoascii
command-line program, both installed with WAVE. The .wvd file also stores a copy of the
network layout and other key information for post-processing. This file is vital to running the
WavePost post-processor and should not be tampered with by editing, renaming, etc.
When any time plots are requested in WaveBuild, WAVE will create a .wps file at the end of
the analysis. The .wps file is also an XML format file that can be observed in any web
browser by changing the filename extension to .xml. It is simply a session file (template) for
the WavePost post-processor detailing what information to extract from the .wvd file for
requested time plots that are created during the WAVE simulation.
When WavePost is launched directly from WaveBuild, it will look in the working directory for a
.wps file with the same prefix as the currently loaded .wvm file in WaveBuild. If it exists, the
file is opened in WavePost and the .wvd and .sum files from the same simulation are
assumed to be the results set for analysis.
Right click on the Time Plots folder and select Add Time Plot
Add Data
Time plots can also be added very quickly by right clicking on an element and following the
drop-down menu items till the variable of interest is found.