Documentation/User Manual/3-simulation-models/whr_system.md

+## Engine Waste Heat Recovery Systems
+
+VECTO is able to consider energy recovered from the combustion engine's waste heat either as mechanical power or as electrical power. The following options for waste-heat recovery system are availabel:
+
+  * Mechanical WHR system included in the FC measurements
+  * Mechanical WHR system not connected to the crankshaft
+  * Electrical WHR system
+
+The first type of WHR systems do not require a dedicated simulation as this is already covered in the combustion engine's fuel consumption map. The output power at the crankshaft is usually higher when such a WHR system is active, or for a certain measurement setpoint (torque and engine speed) the fuel consumption is lower compared to an engine without waste-heat recovery system.
+
+For the other two types of WHR systems where the recovered energy is not directly connected to the engine's crankshaft the generated power needs to be provided in the combustion engine's fuel consumption map (see [.vmap file](#fuel-consumption-map-.vmap). The final fuel consumption is corrected for the latter two WHR systems via the [vehicle-line approach](#engine-fuel-consumption-correction), taking into account  the accumulated power generated by the WHR system During the cycle. In case of an electrical WHR system the electric energy is converted to the equivalent mechanical energy that the combustion engine "does not need to provide" considering the alternator's efficiency.
+
+The power generated by a WHR system is interpolated from the engine's WHR map (part of the fuel consumption map) multiplied by a correction factor similar to the WHTC correction for the fuel consumption.

Documentation/User Manual/4-command-line-arguments/cmd.md

-##Command Line Arguments
+## Command Line Arguments
 
 ![](pics/cmd3.png)
 
 The Vecto 3.x commandline tool can be used to start simulations from the command line and  runs without  graphical user interface. If multiple job-files are specified or a job-file contains multiple simulation runs (i.e., multiple cycles and/or loadings) these simulations are executed in parallel.
 
-###General Notes
+### General Notes
 
 -   The order in which the arguments are provided is arbitrary.
 -   If a file path includes space characters (e.g. "C:\\VECTO Test Files\\Demo.vecto") then double quotes have to be used (as in the picture above).
 -   If not the complete file path is defined (e.g. "file1.vecto" instead of "c:\\data\\file1.vecto") then VECTO expects the file in the application directory (where vectocmd.exe is located).
 
-###Basic usage 
+### Basic usage 
 
         vectocmd.exe [-h] [-v] FILE1.(vecto|xml) [FILE2.(vecto|xml) ...]
 
-###List of command line arguments
+### List of command line arguments
 
 - FILE1.vecto [FILE2.vecto ...]: A list of vecto-job files (with the 
        extension: .vecto). At least one file must be given. Delimited by 

Documentation/User Manual/5-input-and-output-files/AALT.md

-##Alternator Input Data (.aalt)
+## Alternator Input Data (.aalt)
 
 ~~~
 [AlternatorName],[RPM],[Amps],[Efficiency],[PulleyRatio]

Documentation/User Manual/5-input-and-output-files/AAUX.md

-##Advanced Auxiliary Input Data (.aaux)
+## Advanced Auxiliary Input Data (.aaux)
 
 **Example: **
 

Documentation/User Manual/5-input-and-output-files/ACMP.md

-##Advanced Compressor Map (.acmp)
+## Advanced Compressor Map (.acmp)
 
 
 This file is used to configure the compressor map for pneumatic auxiliaries, and contains data relating to the compressor performance at various engine speeds. 
 
-###File Format
+### File Format
 
 The file uses the VECTO CSV format, with an example provided below.
 
-###Format
+### Format
 
 Example Configuration for Advanced Compressor Map:
 

Documentation/User Manual/5-input-and-output-files/AENV.md

-##Environmental Conditions Batch Input File (.aenv)
+## Environmental Conditions Batch Input File (.aenv)
  
 This file contains data on number of different environmental/climatic conditions that can be run through the HVAC SSM module when it is in batch-mode to generate a weighted average output for HVAC power and fuelling loads. 
 
 
-###File Format
+### File Format
 
 The file uses the VECTO CSV format, with an example provided below, with the default values based on the methodology agreed with the European Commission and the project Steering Group.
 
-###Format
+### Format
 
 **Default Climatic Conditions input file:**
 

Documentation/User Manual/5-input-and-output-files/APAC.md

-##Pneumatic Actuations Map (.apac)
+## Pneumatic Actuations Map (.apac)
  
 This file contains data on number of different kinds of pneumatic actuations on different duty cycles. 
 
@@ -12,11 +12,11 @@ Some flexibility in syntax is allowable (the model looks for ‘Bus’, ‘Coach
 
 This file contains also the estimated time required for a cycle which is required to estimate the air demand for certain actuations.
 
-###File Format
+### File Format
 
 The file uses the VECTO CSV format, with an example provided below, with the default values based on the methodology agreed with the European Commission and the project Steering Group.
 
-###Format
+### Format
 
 **Default Configuration for Pneumatic Actuations Map:**
 

Documentation/User Manual/5-input-and-output-files/App.md

-##Application Files
+## Application Files
 
 VECTO uses a numbers of files to save GUI settings and file lists. All files are text-based and can be changed outside of VECTO ***if VECTO is not running***.
 
-###Settings.json
+### Settings.json
 This file is located in VECTO's **config** folder. Here all parameters of the [Settings Dialog](#settings) are saved. The file uses the [JSON format](#json).
 
 
-###Job / Cycle lists
+### Job / Cycle lists
 The job and cycle lists in the [Main Form](#main-form) are saved in the **joblist.txt** / **cyclelist.txt** files of the **config** folder.
 
 Both files save the full file paths separated by line breaks. Additionally it is saved whether each file's checkbox is checked or not. "?1" after a file path means the file is checked (otherwise "?0"). However, this information can be omitted in which case the file will be loaded in checked state.
 
-###LOG.txt
+### LOG.txt
 The tabulator-separated log file saves all messages of the [Main Form's Message List](#main-form) and is located in VECTO's program directory. The file is restarted whenever the [Logfile Size Limit](#settings) is reached.One backup is always stored as LOG\_backup.txt.
 
-###License file
+### License file
 The license file license.dat is located in VECTO's program directory. Without a valid lisence file VECTO won't run.
 
 It no valid license file is provided with your VECTO version please contact [vecto@jrc.ec.europa.eu](mailto:vecto@jrc.ec.europa.eu).

Documentation/User Manual/5-input-and-output-files/CSV.md

-##CSV
+## CSV
 Many data files in Vecto use CSV (Comma Separated Values) as common file format. They consist of a header which defines the columns and data entries which are separated by a comma (",").
 
 In Vecto 3 the order of the columns is arbitrary if the column header matches the header definitions described in this user manual. If the column header does not match, a warning is written to the log file and the columns are parsed in the sequence as described in this manual as a fall-back.
 
 
-###Definition###
+### Definition###
 
 
 |                         |                                                                                                                                                                                                                                                                                                                                                                                                    |
@@ -42,8 +42,8 @@ Following files use the csv:
 The [Auxiliary Input File (.vaux)](#auxiliary-input-file-.vaux) uses a modified csv format with some special headers.
 
 
-###Examples###
-####Exampl 1: Acceleration Limiting File####
+### Examples###
+#### Exampl 1: Acceleration Limiting File####
 ~~~
 v [km/h],acc [m/s^2]     ,dec [m/s^2]
 0       ,1.01570922360353,-0.231742702878269
@@ -52,7 +52,7 @@ v [km/h],acc [m/s^2]     ,dec [m/s^2]
 15      ,1.29026714002479,-0.703434814668512
 ~~~
 
-####Example 2: Driving Cycle####
+#### Example 2: Driving Cycle####
 ~~~
 <s>,<v>,<grad>      ,<stop>,<Padd>,<Aux_ALT1>,<Aux_ALT2>,<Aux_ALT3>
 0  ,0  ,-0.020237973,2     ,6.1   ,0.25      ,0.25      ,0.25
@@ -61,7 +61,7 @@ v [km/h],acc [m/s^2]     ,dec [m/s^2]
 3  ,64 ,-0.020237973,0     ,6.1   ,0.25      ,0.25      ,0.25
 ~~~
 
-####Example 3: Transmission Loss Map####
+#### Example 3: Transmission Loss Map####
 ~~~
 Input Speed [rpm],Input Torque [Nm],Torque Loss [Nm]
 0                ,-2500            ,77.5

Documentation/User Manual/5-input-and-output-files/JSON.md

-##JSON
+## JSON
 Configuration and component files in Vecto use [JSON](http://en.wikipedia.org/wiki/JSON) ![](pics/external-icon%2012x12.png) as common file format.
 
 Following files use JSON:

Documentation/User Manual/5-input-and-output-files/VACC.md

-##Acceleration Limiting Input File (.vacc)
+## Acceleration Limiting Input File (.vacc)
 
 The file is used for [Acceleration Limiting](#driver-acceleration-limiting). It defines the acceleration and deceleration limits as function of
 vehicle speed. The filepath has to be defined in the [Job File](#job-file). The file uses the [VECTO CSV format](#csv).

Documentation/User Manual/5-input-and-output-files/VAUX.md

-##Auxiliary Input File (.vaux)
+## Auxiliary Input File (.vaux)
 This file is used to configure a single auxiliary. Multiple .vaux files can be defined in the [Job File](#job-file) via the [Auxiliary Dialog](#auxiliary-dialog). The file uses the [VECTO CSV format](#csv) with three additional parameters on top of the efficiency map.
 
 See [Auxiliaries](#auxiliaries) for details on how the power demand for each auxiliary is calculated.

Documentation/User Manual/5-input-and-output-files/VCDB.md

-##Vair & Beta Cross Wind Correction Input File (.vcdb)
+## Vair & Beta Cross Wind Correction Input File (.vcdb)
 
 The file is needed for Vair & Beta [Cross Wind Correction](#vehicle-cross-wind-correction). The file uses the [VECTO CSV format](#csv).
 

Documentation/User Manual/5-input-and-output-files/VCDV.md

-##Speed Dependent Cross Wind Correction Input File (.vcdv)
+## Speed Dependent Cross Wind Correction Input File (.vcdv)
 
 The file is needed for speed dependent [Cross Wind Correction](#vehicle-cross-wind-correction). The file uses the [VECTO CSV format](#csv).
 

Documentation/User Manual/5-input-and-output-files/VDRI.md

-##Driving Cycles (.vdri)
+## Driving Cycles (.vdri)
 
 A Driving Cycle defines the parameters of a simulated route in Vecto. It is either time-based or distance-based and has different fields depending on the driving cycle type.
 The basic file format is [Vecto-CSV](#csv) and the file type ending is ".vdri". A Job must have at least one driving cycle (except in Declaration mode, where the driving cycles are predefined).
 
-###Driving Cycle Types
+### Driving Cycle Types
 - **Declaration Mode**: [Target speed, distance-based](#declaration-mode-cycles)
 - **Verification Test Mode**: [Measured driving cycle, time-based](#verification-test-cycle)
 - **Engineering Mode**:
@@ -17,7 +17,7 @@ The basic file format is [Vecto-CSV](#csv) and the file type ending is ".vdri".
 - Distance-based cycles can be defined in any distance resolution, including variable distance steps.
 - Time-based cycles can be defined in any time resolution, including variable time steps.
 
-###Declaration Mode Cycles
+### Declaration Mode Cycles
 In Declaration Mode driving cycles are automatically chosen depending on vehicle category and cannot be changed by the user. These predefined cycles are of type target-speed, distance-based.
 
 - Coach: 275km
@@ -31,7 +31,7 @@ In Declaration Mode driving cycles are automatically chosen depending on vehicle
 - Urban: 40km
 - Urban Delivery: 28km
 
-###Verification Test Cycle
+### Verification Test Cycle
 This kind of cycle is used for simulating vehicles defined in declaration mode (xml) on a real driving cycle.
 
 Header: **\<t>, \<v>, \<n\_eng>,\<n\_fan>, \<tq\_left>, \<tq\_right>, \<n\_wh\_left>, \<n\_wh\_right>***, \<fc>, \<gear>*
@@ -70,7 +70,7 @@ Units are optional and are enclosed in [square-brackets] after the header-column
 
 
 
-###Engineering Mode: Target-Speed, Distance-Based Cycle
+### Engineering Mode: Target-Speed, Distance-Based Cycle
 This driving cycle defines the target speed over distance. Vecto tries to achieve and maintain this target speed.
 
 Header: **\<s>, \<v>, \<stop>***\[, \<Padd>]\[, \<grad>]\[, \<PTO>]\[, \<vair\_res>, \<vair\_beta>]\[, \<Aux\_ID>]*
@@ -103,7 +103,7 @@ Units are optional and are enclosed in [square-brackets] after the header-column
 |        2 |          35 |           0 |        3.03 |          1.3 |
 |        3 |          50 |           0 |        2.99 |          1.3 |
 
-###Engineering Mode: Measured-Speed, Time-Based Cycle
+### Engineering Mode: Measured-Speed, Time-Based Cycle
 This driving cycle defines the actual measured speed over time. Vecto tries to simulate the vehicle model using this speed as the actual vehicle speed.
 Due to differences in the real and simulated shift strategies a small difference in speed can occur, but Vecto immediately tries to catch up after the gear is engaged again.
 
@@ -132,7 +132,7 @@ Units are optional and are enclosed in [square-brackets] after the header-column
 |        3 |         2.4 |        2.99 |          1.3 |
 
 
-###Engineering Mode: Measured-Speed With Gear, Time-Based Cycle
+### Engineering Mode: Measured-Speed With Gear, Time-Based Cycle
 
 This driving cycle defines the actual measured speed of the vehicle, the gear, and the engine speed over time.
 It overrides the shift strategy of Vecto and also directly sets the engine speed.
@@ -164,7 +164,7 @@ Units are optional and are enclosed in [square-brackets] after the header-column
 |        2 |         1.2 |           3 |        3.03 |          1.3 |
 |        3 |         2.4 |           3 |        2.99 |          1.3 |
 
-###Engineering Mode: Pwheel (SiCo), Time-Based
+### Engineering Mode: Pwheel (SiCo), Time-Based
 This driving cycle defines the power measured at the wheels over time. Vecto tries to simulate the vehicle with this power requirement.
 
 Header: **\<t>, \<Pwheel>, \<gear>, \<n>***\[, \<Padd>]*
@@ -190,7 +190,7 @@ Units are optional and are enclosed in [square-brackets] after the header-column
 |        3 |          50.56 |           3 |       1400 |          1.3 |
 
 
-###Engine Only Mode: Engine Only Driving Cycle
+### Engine Only Mode: Engine Only Driving Cycle
 
 This driving cycle directly defines the engine's power or torque at the output shaft over time. Vecto adds the engine's inertia to the given power demand and simulates the engine.
 

Documentation/User Manual/5-input-and-output-files/VFLD.md

-##Full Load and Drag Curves (.vfld)
+## Full Load and Drag Curves (.vfld)
 
 This file contains the full load and drag curves and the PT1 values for the [transient full load calculation](#engine-transient-full-load). The file uses the [VECTO CSV format](#csv).
 

Documentation/User Manual/5-input-and-output-files/VGBS.md

-##Shift Polygons Input File (.vgbs)
+## Shift Polygons Input File (.vgbs)
 
 Defines up- and down-shift curves. See [Gear Shift Model](#gearbox-gear-shift-model) for details. The file uses the [VECTO CSV format](#csv).
 

Documentation/User Manual/5-input-and-output-files/VGBX.md

-##Gearbox File (.vgbx)
+## Gearbox File (.vgbx)
 
 File for the definition of a gearbox in Vecto. Can be created with the [Gearbox Editor](#gearbox-editor).
 

Documentation/User Manual/5-input-and-output-files/VMAP.md

-##Fuel Consumption Map (.vmap)
+## Fuel Consumption Map (.vmap)
 The FC map is used to interpolate the base fuel consumption before corrections are applied. For details see [Fuel Consumption Calculation](#engine-fuel-consumption-calculation). The file uses the [VECTO CSV format](#csv).
 
 

Documentation/User Manual/5-input-and-output-files/VMOD.md

-##Modal Results (.vmod)
+## Modal Results (.vmod)
 
 Modal results are only created if enabled in the [Options](#main-form) tab. One file is created for each calculation and stored in the same directory as the .vecto file.