diff --git a/Documentation/User Manual/1-user-interface/0_start.md b/Documentation/User Manual/1-user-interface/0_start.md
index 444871c401fcb0bc1a99a6844a667d216e5950a8..b48cbd407a88c7c9e7a16abbf13357fb68ad3c01 100644
--- a/Documentation/User Manual/1-user-interface/0_start.md
+++ b/Documentation/User Manual/1-user-interface/0_start.md
@@ -10,7 +10,7 @@ Software Requirements
+ Microsoft .NET Framework 4.5
-##Installation Options
+## Installation Options
VECTO is distributed as a portable application. This means you can simply unzip the archive and directly execute it. This, however, requires write and execute permissions for the VECTO application directory.
diff --git a/Documentation/User Manual/1-user-interface/B_mainform.md b/Documentation/User Manual/1-user-interface/B_mainform.md
index c9fd73c69b92d0d2081f399911dc28950e9d9f15..478d4943544580fdd05c942ddff4b4e7ff0ca7f0 100644
--- a/Documentation/User Manual/1-user-interface/B_mainform.md
+++ b/Documentation/User Manual/1-user-interface/B_mainform.md
@@ -1,11 +1,11 @@
-##Main Form
+## Main Form
-###Description
+### Description
The Main Form is loaded when starting VECTO. Closing this form will close VECTO even if other dialogs are still open. In this form all global settings can be controlled and all other application dialogs can be opened.
@@ -18,10 +18,10 @@ The Main Form includes two tabs as described below:
* Options Tab
-###Job Files Tab
+### Job Files Tab
-####Job Files List#
+#### Job Files List#
Job files (.vecto) listed here will be used for calculation. Unchecked files will be ignored!
Doubleclick entries to edit job files with the [VECTO Editor](#job-editor).
@@ -35,7 +35,7 @@ Doubleclick entries to edit job files with the [VECTO Editor](#job-editor).
 ***Move selected files up or down in list***
-#####List Options#
+##### List Options#
- **Save/Load List**
- Save or load Job List to text file
@@ -50,13 +50,13 @@ Doubleclick entries to edit job files with the [VECTO Editor](#job-editor).
-#### ***START Button***
+####  ***START Button***
Start VECTO in the selected mode (see [Options](#options-tab)).
-###Options Tab
+### Options Tab
@@ -89,7 +89,7 @@ Output values in vmod at beginning and end of simulation iterval
-###Controls
+### Controls
 New Job File
: Create a new .vecto file using the [VECTO Editor](#job-editor)
diff --git a/Documentation/User Manual/1-user-interface/C_settings.md b/Documentation/User Manual/1-user-interface/C_settings.md
index eadfe36f33140ada3958f95e5774f52f4805e9ff..ef4e0b62fa0fc79b27fa2a65bcee6a528ecd8e74 100644
--- a/Documentation/User Manual/1-user-interface/C_settings.md
+++ b/Documentation/User Manual/1-user-interface/C_settings.md
@@ -1,14 +1,14 @@
-##Settings
+## Settings
-###Description
+### Description
In the Settings dialog controls general application settings. The settings are saved in the [settings.json](#application-files) file.
-###Interface Settings
+### Interface Settings
File Open Command
: This command will be used to open CSV Input Files like Driving Cycles (.vdri). See: [Run command](http://en.wikipedia.org/wiki/Run_command)\
@@ -18,7 +18,7 @@ File Open Command
: ***Example*** *: If the command is* ***excel*** *and the file is* ***C:\\VECTO\\cycle1.vdri*** *then VECTO will run:* ***excel "C:\\VECTO\\cycle1.vdri"***
-###Calculation Settings
+### Calculation Settings
<div class="engineering">
Air Density \[kg/m³\]
@@ -27,7 +27,7 @@ Air Density \[kg/m³\]
This setting is only used in Engineering mode. In Declaration mode the default value of 1.188 \[kg/m³\] is used.
</div>
-###Controls
+### Controls
Reset All Settings
diff --git a/Documentation/User Manual/1-user-interface/D1_VECTO-Job-Editor.md b/Documentation/User Manual/1-user-interface/D1_VECTO-Job-Editor.md
index c3e32012c2084985ad0efc3c7636c1f1c4ecb69c..68fa3f58da6317f7ee66cf091c343b9a8754a885 100644
--- a/Documentation/User Manual/1-user-interface/D1_VECTO-Job-Editor.md
+++ b/Documentation/User Manual/1-user-interface/D1_VECTO-Job-Editor.md
@@ -1,10 +1,10 @@
-##Job Editor
+## Job Editor
-###Description
+### Description
The [job file (.vecto)](#job-file) includes all informations to run a VECTO calculation. It defines the vehicle and the driving cycle(s) to be used for calculation. In summary it defines:
@@ -16,14 +16,14 @@ The [job file (.vecto)](#job-file) includes all informations to run a VECTO calc
- Driving Cycles (only in Engineering Mode)
-###Relative File Paths
+### Relative File Paths
It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. Example: "Vehicles\\Vehicle1.vveh" points to the "Vehicles" subdirectory of the Job File's directoy.
VECTO automatically uses relative paths if the input file (e.g. Vehicle File) is in the same directory as the Job File. (*Note:* The Job File must be saved before browsing for input files.)
-###General Settings
+### General Settings
 Engine Only Mode
@@ -73,7 +73,7 @@ Cycles
:  Remove the selected cycle from the list
-###Driver Assist Tab
+### Driver Assist Tab
@@ -90,11 +90,11 @@ Acceleration Limiting
: See [Acceleration Limiting](#driver-acceleration-limiting) for details.
-###Chart Area
+### Chart Area
If a valid [Vehicle File](#vehicle-editor), [Engine File](#engine-file-.veng) and [Gearbox File](#gearbox-file-.vgbx) is loaded into the Editor the main vehicle parameters like HDV group and axle configuration are shown here. The plot shows the full load curve(s) and sampling points of the fuel consumption map.
-###Controls
+### Controls
 New Job File
: Create a new empty .vecto file
diff --git a/Documentation/User Manual/1-user-interface/D2_VTP-Job-Editor.md b/Documentation/User Manual/1-user-interface/D2_VTP-Job-Editor.md
index f691f1c1fea3d763bc017b4c08ba6184f53e6689..4027ac7662bb733888c0c7e0023b5b437f78cddf 100644
--- a/Documentation/User Manual/1-user-interface/D2_VTP-Job-Editor.md
+++ b/Documentation/User Manual/1-user-interface/D2_VTP-Job-Editor.md
@@ -1,10 +1,10 @@
-##VTP-Job Editor
+## VTP-Job Editor
-###Description
+### Description
A VTP-Job is intended to verify the declared data of a vehicle through an on-road test. VTP-Jobs can be either simulated in engineering mode or declaration mode. For a VTP simulation the measured driving cycle along with the VECTO job-file is required. The driving cycle has to contain the vehicle's velocity, rotational speed of the driven wheels, torque of the driven wheels, and fuel consumption in a temporal resolution of 2Hz.
VECTO computes the best matching gear based on the vehicle parameters, the actual vehicle speed and the engine speed.
@@ -25,7 +25,7 @@ In declaration mode only the first given driving cycle is simulated as the resul
In declaration mode the manufacturer's record file needs to be provided. Furthermore, declaration mode simulations consider correction factors for the net calorific value of the used fuel and the vehicle's mileage. In engineering mode the according input fields are not shown.
</div>
-###Relative File Paths
+### Relative File Paths
It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. Example: "Vehicles\\Vehicle1.xml" points to the "Vehicles" subdirectory of the Job File's directoy.
@@ -43,11 +43,11 @@ Cycles
-###Chart Area
+### Chart Area
If a valid Vehicle File is loaded into the Editor the main vehicle parameters like HDV group and axle configuration are shown here. The plot shows the full load curve(s) and sampling points of the fuel consumption map.
-###Controls
+### Controls
 New Job File
: Create a new empty .vecto file
diff --git a/Documentation/User Manual/1-user-interface/E_VECTO-Editor_Aux.md b/Documentation/User Manual/1-user-interface/E_VECTO-Editor_Aux.md
index 17af1ed23b1199120f1983d4182775a8fbeee53f..3e131ced8a7b0782deab4f56df824a5be67cf815 100644
--- a/Documentation/User Manual/1-user-interface/E_VECTO-Editor_Aux.md
+++ b/Documentation/User Manual/1-user-interface/E_VECTO-Editor_Aux.md
@@ -1,4 +1,4 @@
-##Auxiliary Dialog
+## Auxiliary Dialog
@@ -12,12 +12,12 @@
</div>
-###Description
+### Description
The Auxiliary Dialog is used to configure auxiliaries. In [Declaration Mode](#declaration-mode) the set of auxiliaries and their power demand is pre-defined. For every auxiliary the user has to select the technology from a given list. In [Engineering Mode](#engineering-mode) the set of auxiliaries can be specified by the user. Auxiliary efficieny is defined using an [Auxiliary Input File (.vaux)](#auxiliary-input-file-.vaux). See [Auxiliaries](#auxiliaries) for details on how the power demand for each auxiliary is calculated.
-###Settings
+### Settings
<div class="declaration">
Technology
@@ -40,7 +40,7 @@ Input File
-###Controls
+### Controls
 ***Save and close***
diff --git a/Documentation/User Manual/1-user-interface/F_VEH-Editor.md b/Documentation/User Manual/1-user-interface/F_VEH-Editor.md
index 664035c06588fc605e1441eb12ec225b19318505..9cd0e8fb370054971dab0ca99f13d988323a9f4e 100644
--- a/Documentation/User Manual/1-user-interface/F_VEH-Editor.md
+++ b/Documentation/User Manual/1-user-interface/F_VEH-Editor.md
@@ -1,21 +1,21 @@
-##Vehicle Editor
+## Vehicle Editor
-###Description
+### Description
The [Vehicle File (.vveh)](#vehicle-file-.vveh) defines the main vehicle/chassis parameters like axles including [RRC](#vehicle-rolling-resistance-coefficient)s, air resistance and masses.
The Vehicle Editor contains 3 tabs to edit all vehicle-related parameters. The 'General' tab allows to input mass, loading, air resistance, vehicle axles, etc. The 'Powertrain' allows to define the retarder, an optional angle drive, or PTO consumer. In the third tab the engine torque can be limited to a maximum for individual gears.
-###Relative File Paths
+### Relative File Paths
It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths.
Example: "Demo\\RT1.vrlm" points to the "Demo" subdirectory of the Vehicle File's directoy.
VECTO automatically uses relative paths if the input file (e.g. Retarder Losses File) is in the same directory as the Vehicle File. (*Note:* The Vehicle File must be saved before browsing for input files.)
-###General vehicle parameters
+### General vehicle parameters
Vehicle Category
: Needed for [Declaration Mode](#declaration-mode) to identify the HDV Group.
@@ -29,7 +29,7 @@ Technically Permissible Maximum Laden Mass [t]
HDV Group
: Displays the automatically selected HDV Group depending on the settings above.
-###Masses/Loading
+### Masses/Loading
Corrected Actual Curb Mass Vehicle
: Specifies the vehicle's mass without loading
@@ -50,7 +50,7 @@ Loading
In Declaration Mode only the vehicle itself needs to be specified. Depending on the vehicle category and mission the simulation adds a standard trailer for certain missions.
</div>
-###Air Resistance and Corss Wind Correction Options
+### Air Resistance and Corss Wind Correction Options
The product of Drag Coefficient [-] and Cross Sectional Area [m²] (**c~d~ x A**) and **Air Density** [kg/m³] (see [Settings](#settings)) together with the vehicle speed defines the Air Resistance. Vecto uses the combined value **c~d x A** as input.
**Note that the Air Drag depends on the chosen [**Cross Wind Correction**](#vehicle-cross-wind-correction).**
@@ -71,12 +71,12 @@ In delcaration mode the 'Speed dependent (Declaration Mode)' cross-wind correcti
Depending on the chosen mode either a [Speed Dependent Cross Wind Correction Input File (.vcdv)](#speed-dependent-cross-wind-correction-input-file-.vcdv) or a [Vair & Beta Cross Wind Correction Input File (.vcdb)](#speed-dependent-cross-wind-correction-input-file-.vcdv) must be defined. For details see [Cross Wind Correction](#vehicle-cross-wind-correction).
-###Dynamic Tyre Radius
+### Dynamic Tyre Radius
In [Engineering Mode](#engineering-mode) this defines the effective (dynamic) wheel radius (in [mm]) used to calculate engine speed. In [Declaration Mode](#declaration-mode) the radius calculated automatically using tyres of the powered axle.
-###Axles/Wheels
+### Axles/Wheels
For each axle the parameters **Relative axle load, RRC~ISO~** and **F~zISO~** have to be given in order to calculate the total [Rolling Resistance Coefficient](#vehicle-rolling-resistance-coefficient).
@@ -97,7 +97,7 @@ For missions with a trailer predefined wheels and load-shares are added by Vecto
Doubleclick entries to edit existing axle configurations.
-###Retarder Losses
+### Retarder Losses
If a separate retarder is used in the vehicle a **Retarder Torque Loss Map** can be defined here to consider idling losses caused by the retarder.
@@ -111,7 +111,7 @@ Both, primary and secondary retarders, require an [Retarder Torque Loss Input Fi
The Retarder Ratio defines the ratio between the engine speed/cardan shaft speed and the retarder.
-###Angledrive
+### Angledrive
If an angledrive is used in the vehicle, it can be defined here.
Three options are available:
@@ -121,7 +121,7 @@ Three options are available:
- Included in transmission: Use this if the gearbox already includes the transmission losses for the angledrive in the respective transmission loss maps.
-###PTO Transmission
+### PTO Transmission
If the vehicle has an PTO consumer, a pto transmission and consumer can be defined here. (Only in [Engineering Mode](#engineering-mode))
@@ -133,13 +133,13 @@ Three settings can be set:
<div class="declaration">
-###ADAS
+### ADAS
On the ADAS tab, the options for advanced driver assistant systems can be selected. This is only supported in declaration mode. Depending on the mission cycle, vehicle group, and payload a certain benefit is applied to the calcualated fuel consumption. See [ADAS: Overspeed](#driver-overspeed) and [ADAS Technologies](#vehicle-adas-technologies)
</div>
-###Controls
+### Controls
 New file
diff --git a/Documentation/User Manual/1-user-interface/G_ENG-Editor.md b/Documentation/User Manual/1-user-interface/G_ENG-Editor.md
index 5c3f9ed554be5c0747e394248d56492b2a6586a1..e9800be6f72c56cd93cbae519ed6da5ebd48b504 100644
--- a/Documentation/User Manual/1-user-interface/G_ENG-Editor.md
+++ b/Documentation/User Manual/1-user-interface/G_ENG-Editor.md
@@ -1,19 +1,19 @@
-##Engine Editor
+## Engine Editor
-###Description
+### Description
The [Engine File (.veng)](#engine-file-.veng) defines all engine-related parameters and input files like Fuel Consumption Map and Full Load Curve.
-###Relative File Paths
+### Relative File Paths
It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths.
Example: "Demo\\FLD1.vfld" points to the "Demo" subdirectory of the Engine File's directory.
VECTO automatically uses relative paths if the input file (e.g. FC Map) is in the same directory as the Engine File. *Note:* The Engine File must be saved before browsing for input files.)
-###Main Engine Parameters
+### Main Engine Parameters
Make and Model \[text]\
: Free text defining the engine model, type, etc.
@@ -30,19 +30,19 @@ Fuel Type
Inertia including Flywheel \[kgm²\]
: Inertia for rotating parts including engine flywheel. In [Declaration Mode](#declaration-mode) the inertia is calculated depending on the engine's displacement and also accounts for the clutch's inertia.
-###Full Load and Drag Curves
+### Full Load and Drag Curves
The [Engine's Full Load and Drag Curves (.vfld)](#full-load-and-drag-curves-.vfld) limits the engine's maximum torque and drag torque respectively The full-load curve must at least cover the engine-speed range from idling speed up to the speed where the power goes down to 70% of the maximum power. The input file (.vfld) file format is described [here](#full-load-and-drag-curves-.vfld).
-###Fuel Consumption Map
+### Fuel Consumption Map
The [Fuel Consumption Map](#fuel-consumption-map-.vmap) is used to calculate the base FC value. See [Fuel Consumption Calculation](#engine-fuel-consumption-calculation) for details.
The input file (.vmap) file format is described [here](#fuel-consumption-map-.vmap).
-###WHTC Correction Factors
+### WHTC Correction Factors
<div class="declaration">
The WHTC Correction Factors are required in [Declaration Mode](#declaration-mode) for the [WHTC FC Correction](#engine-fuel-consumption-calculation).
@@ -55,12 +55,12 @@ In engineering a single correction factor for correcting WHTC, Cold/Hot Balancin
</div>
-###Chart Area
+### Chart Area
The Chart Area shows the fuel consumption map and the selected full load curve.
-###Controls
+### Controls
New file
diff --git a/Documentation/User Manual/1-user-interface/H_GBX-Editor.md b/Documentation/User Manual/1-user-interface/H_GBX-Editor.md
index ec8f6fc997735f4fa10489f0a60b5c98c71275b2..0d259fc3cf87765ef4358d39418f1c39465a6c37 100644
--- a/Documentation/User Manual/1-user-interface/H_GBX-Editor.md
+++ b/Documentation/User Manual/1-user-interface/H_GBX-Editor.md
@@ -1,18 +1,18 @@
-##Gearbox Editor
+## Gearbox Editor
-###Description
+### Description
The [Gearbox File (.vgbx)](#gearbox-file-.vgbx) defines alls gearbox-related input parameters like gear ratios and transmission loss maps. See [Gear Shift Model](#gearbox-gear-shift-model) for details.
-###Relative File Paths
+### Relative File Paths
It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. \
Example: "Gears\\Gear1.vtlm" points to the "Gears" subdirectory of the Gearbox File's directoy.
@@ -20,7 +20,7 @@ Example: "Gears\\Gear1.vtlm" points to the "Gears" subdirectory of the Gearbox F
VECTO automatically uses relative paths if the input file (e.g. Shift Polygons File) is in the same directory as the Gearbox File. (The Gearbox File must be saved before browsing for input files.)
-###Main Gearbox Parameters
+### Main Gearbox Parameters
Make and Model
: Free text defining the gearbox model, type, etc.
@@ -45,7 +45,7 @@ Traction Interruption \[s\]
: Interruption during gear shift event. (Engineering mode only)
-###Gears
+### Gears
Use the  and  buttons to add or remove gears from the vehicle. Doubleclick entries to edit existing gears.
@@ -56,7 +56,7 @@ Use the  and ![remove](pics/minus-circle-icon.p
- **"Max Torque"** defines the maximum allowed torque (if applicable) for ah gear. It is used for limiting the engine's torque in certain gear. Note: in Declaration mode the [generic shift polygons](#gearbox-gear-shift-model) are computed from the engine's full-load curve. If the maximum torque is limited by the gearbox, the minimum of the gearbox and engine maximum torque will be used to compute the [generic shift polygons](#gearbox-gear-shift-model)!
-###Gear shift strategy parameters
+### Gear shift strategy parameters
Since version Vecto 3.0.3 the gearshift polygon calculation according to the ACEA White Book 2016 is implemented and since Vecto 3.0.4 the ACEA White Book 2016 shift strategy for AMT and MT is implemented. The AT-S and AT-P strategies are implemented since Version 3.1.0. For details on this topic please see the ACEA White Book 2016.
@@ -76,7 +76,7 @@ Minimum shift time \[s\]
: Limits the time between two gear shifts. This rule will be ignored if rpms are too high or too low.
-###Shift Strategy Parameters
+### Shift Strategy Parameters
Downshift after upshift delay \[s\]
: Minimal duration between an upshift and a consecutive downshift.
@@ -87,7 +87,7 @@ Upshift after downshift delay \[s\]
Min. acceleration after upshift \[m/s²\]
: Limit for the minimal achievable acceleration to test if an upshift is reasonable.
-###Start Gear
+### Start Gear
In order to calculate an appropriate gear for vehicle start (first gear after vehicle standstill) a fictional load case is calculated using a specified **reference vehicle speed** and **reference acceleration** together with the actual road gradient, transmission losses and auxiliary power demand. This way the start gear is independent from the target speed. VECTO uses the highest possible gear which provides the defined **torque reserve**.
@@ -102,7 +102,7 @@ Reference acceleration at clutch-in
</div>
-###Torque Converter
+### Torque Converter
Torque converter characteristics file
: Defines the [Torque converter characteristics file](#torque-converter-characteristics-.vtcc) containing the torque ratio and reference torque over the speed ratio.
@@ -121,7 +121,7 @@ Torque converter shift polygon
: Defines the [Shift Polygons InputFile (.vgbs)](#shift-polygons-input-file-.vgbs) separately for the torque converter. For details on shifting from/to the torque converter gear please see [AT Gear Shift Strategy](#gearbox-at-gearshift-rules).
-###Torque Converter: Minimal acceleration after upshift
+### Torque Converter: Minimal acceleration after upshift
Here the minimal achievable accelerations before upshifts can be defined.
@@ -132,7 +132,7 @@ Acc. for C->C \[m/s²\]
: The minimal achievable acceleration for shifts from first torque converter gear to second torque converter gear (1C->2C)
-###Power shift losses
+### Power shift losses
Shift time \[s\]
: The shift time for powershift losses.
@@ -141,12 +141,12 @@ Inertia factor \[-\]
: The inertia factor for powershift losses.
-###Chart Area
+### Chart Area
The Chart Area displays the [Shift Polygons Input File(.vgbs)](#shift-polygons-input-file-.vgbs) as well as the declaration mode shift polygons (dashed lines) for the selected gear.
-###Controls
+### Controls
diff --git a/Documentation/User Manual/1-user-interface/I_Graph.md b/Documentation/User Manual/1-user-interface/I_Graph.md
index 7082b9563747b359b52281563befd7c5886afbb7..c5421ed552cb94350488409785edbbc5af95034f 100644
--- a/Documentation/User Manual/1-user-interface/I_Graph.md
+++ b/Documentation/User Manual/1-user-interface/I_Graph.md
@@ -1,10 +1,10 @@
-##Graph Window
+## Graph Window
-###Description
+### Description
The Graph Window allows to visualise [modal results files (.vmod)](#modal-results-.vmod). Multiple windows can be open at the same time to display different files.
@@ -12,7 +12,7 @@ The Graph Window allows to visualise [modal results files (.vmod)](#modal-result
Note that the graph does **not** update automatically if the results file has changed.
-###Channels
+### Channels
Use the  and  buttons to add or remove channels. Doubleclick entries to edit existing channels.
@@ -20,7 +20,7 @@ Use the  and  ***Open a .vmod file***
diff --git a/Documentation/User Manual/1-user-interface/K0_VECTO-AdvancedAux.md b/Documentation/User Manual/1-user-interface/K0_VECTO-AdvancedAux.md
index b3f70bda7bab575a21868ecccf9524277e643c7b..0968cb81f56e8c2ef3281c8cafbf5b0f00ba9740 100644
--- a/Documentation/User Manual/1-user-interface/K0_VECTO-AdvancedAux.md
+++ b/Documentation/User Manual/1-user-interface/K0_VECTO-AdvancedAux.md
@@ -1,11 +1,11 @@
-##Advanced Auxiliary Dialog
+## Advanced Auxiliary Dialog
<div class="engineering">
-###Description
+### Description
In the VECTO Job Editor dialog you need to select "BusAuxiliaries" in the drop down list on the left to configure the advanced auxiliaries.
@@ -26,7 +26,7 @@ The Advance Auxiliaries Editor contains four tabs/sub-modules where the differen
: The "HVAC" tab defines the steady state output values, which can also be loaded via the Steady State Model File (.AHSM)
-###Important notes
+### Important notes
Note that the cycle file name used should ideally respect the following syntax to be correctly associated with the pneumatic actuations map (.apac), otherwise the number of actuations will be set to 0 by default:
@@ -35,7 +35,7 @@ Note that the cycle file name used should ideally respect the following syntax t
Some flexibility in syntax is allowable (the model looks for 'Bus', 'Coach', 'Urban', etc. in the file name), meaning that the standard default cycles are fully/correctly supported. However, for newly created cycles (i.e. for use in Engineering Mode) it is recommended to follow the above convention to guarantee correct functionality.
-###File Format
+### File Format
The file uses the VECTO JSON format.
diff --git a/Documentation/User Manual/1-user-interface/K1_VECTO-AdvancedAux_EL.md b/Documentation/User Manual/1-user-interface/K1_VECTO-AdvancedAux_EL.md
index 7d3db62212f8f7efc75be269185a0b8b47c9c1c7..d14c3c38f93acb73873e14f199433c211d02a458 100644
--- a/Documentation/User Manual/1-user-interface/K1_VECTO-AdvancedAux_EL.md
+++ b/Documentation/User Manual/1-user-interface/K1_VECTO-AdvancedAux_EL.md
@@ -1,8 +1,8 @@
-##Electrical Auxiliaries Editor
+## Electrical Auxiliaries Editor
-###Description
+### Description
The "Electrics" tab defines various parameters for electric auxiliaries used on the vehicle:
@@ -19,7 +19,7 @@ The "Electrics" tab defines various parameters for electric auxiliaries used on
* Note: for certain fields the allowable values are also controlled/prescribed according to the requirements of the project steering group.
-###Results Cards
+### Results Cards
Upon activation of Smart Electrics using the check box, the user may enter Result Card values according to the methodology proposed by the steering group. Until the certification procedure to determine the correct values is agreed, it is recommended to use the following default values:
@@ -57,7 +57,7 @@ Example Default Results Card values
: Result Card: Overrun
-###Default Values
+### Default Values
The following table provides a summary of the default values that are populated whenever a new advanced auxiliaries (.AAUX) file is created from scratch (nominal consumption and % active are always fixed defaults, so are not shown). The table also indicates the editable/default status of the relevant parameters in the VECTO UI in Engineering mode, and the recommended status in Declaration mode (not currently implemented). The default values / parameter status has been agreed with the project steering group.
diff --git a/Documentation/User Manual/1-user-interface/K2_VECTO-AdvancedAux_EL-ALT.md b/Documentation/User Manual/1-user-interface/K2_VECTO-AdvancedAux_EL-ALT.md
index 513fd53838e5d42549a7dd5197e11442013dc808..43ce207f7afc58b62809ddff23b123bc3877e35f 100644
--- a/Documentation/User Manual/1-user-interface/K2_VECTO-AdvancedAux_EL-ALT.md
+++ b/Documentation/User Manual/1-user-interface/K2_VECTO-AdvancedAux_EL-ALT.md
@@ -1,4 +1,4 @@
-##Combined Alternator Map File (.aalt)
+## Combined Alternator Map File (.aalt)
The Combined Alternator Map (.AALT) file contains data relating to the efficiency of the alternator at various engine speeds and current demand. The .AALT file is a CSV file containing three fields: “Amp”, “RPM” (engine speed), and “Efficiency”. It can be created via the select file button, or an existing map directly imported into VECTO via the File Browser.
@@ -20,7 +20,7 @@ The methodology for calculating the combined efficiency map is summarised below
-###File Format
+### File Format
The file uses the VECTO CSV format.
diff --git a/Documentation/User Manual/1-user-interface/K3_VECTO-AdvancedAux_PNEU.md b/Documentation/User Manual/1-user-interface/K3_VECTO-AdvancedAux_PNEU.md
index fc56a7b2c9b3e6d2af93028df203c4cc0c08d234..e52d878181a676e00b134f1ee4e2ae0d167fe690 100644
--- a/Documentation/User Manual/1-user-interface/K3_VECTO-AdvancedAux_PNEU.md
+++ b/Documentation/User Manual/1-user-interface/K3_VECTO-AdvancedAux_PNEU.md
@@ -1,9 +1,9 @@
-##Pneumatic Auxiliaries Editor
+## Pneumatic Auxiliaries Editor
-###Description
+### Description
The "Pneumatics" tab defines various parameters for pneumatic auxiliaries used on the vehicle:
@@ -16,7 +16,7 @@ The "Pneumatics" tab defines various parameters for pneumatic auxiliaries used o
- The “Retarder Brake”, “Smart Pneumatics” and “Smart Regeneration” and enable via check boxes.
-###Default Values
+### Default Values
The following table provides a summary of the default values that are populated whenever a new advanced auxiliaries (.AAUX) file is created from scratch. The table also indicates the editable/default status of the relevant parameters in the VECTO UI in Engineering mode, and the recommended status in Declaration mode (not currently implemented). The default values / parameter status has been agreed with the project steering group.
diff --git a/Documentation/User Manual/1-user-interface/K4_VECTO-AdvancedAux_HVAC.md b/Documentation/User Manual/1-user-interface/K4_VECTO-AdvancedAux_HVAC.md
index e9e3bc74fda1b4d4fb3cc7875541e6d6ef7981cf..238d6961d949515f74eecd125e1a5413b76fc3d9 100644
--- a/Documentation/User Manual/1-user-interface/K4_VECTO-AdvancedAux_HVAC.md
+++ b/Documentation/User Manual/1-user-interface/K4_VECTO-AdvancedAux_HVAC.md
@@ -1,8 +1,8 @@
-##HVAC Auxiliaries Editor
+## HVAC Auxiliaries Editor
-###Description
+### Description
The "HVAC" tab defines various parameters for heating, ventilation and air conditioning (HVAC) auxiliaries used on the vehicle, calculated from the HVAC Steady State Model (HVAC SSM):
- Disable HVAC Module [tickbox]
@@ -17,7 +17,7 @@ Outputs from the HVAC SSM include:
- Fuelling Litres Per Hour
-###HVAC Steady-State Model Editor
+### HVAC Steady-State Model Editor
The HVAC Steady-State Model (HVAC SSM) Editor defines various data and parameters for calculation of HVAC auxiliary demands (electrical, mechanical and fuelling) from the vehicle, replicating the key inputs/functionality from the HVAC CO2SIM model developed for ACEA:
@@ -32,7 +32,7 @@ At the top of the window, two sets of outputs are presented for electrical, mech
- 'Base' values: These are the calculated resulting demands from the inputs on the 'Bus Parameters', 'Boundary Conditions' and 'Other' tabs.
- 'Adjusted' values: these are the final values output from the model, which additionally factor in the HVAC technologies included in the 'Tech List Input' tab.
-###Bus Parameters
+### Bus Parameters
@@ -49,13 +49,13 @@ Input bus parameters can be edited directly or imported/calculated from the Bus
- Other fields, that are greyed out, are locked and not editable, containing fixed default values or calculations.
-###Boundary Conditions
+### Boundary Conditions
On this tab the various boundary conditions for the HVAC SSM calculations can be set. Certain fields (greyed out) are locked and not editable, containing fixed default values or calculations.
-###Other
+### Other
@@ -65,7 +65,7 @@ On this tab a number of other parameters for the HVAC SSM calculations can be se
- Ventilation settings
- Auxiliary Heater parameters: the power of the fuel fired heater may be included, other fields are provided for information only and are locked. The 'Engine Waste Heat' values are calculated during the actual model runs, which are determined via a pre-run of the model over the selected drive-cycle.
-###TechList Input
+### TechList Input
@@ -76,7 +76,7 @@ To determine energy consumption of a certain bus-HVAC system combination, a cust
The final 'Diagnostics' tab provides a summary of the resulting outputs from the HVAC Tech List tab.
-###Default Values
+### Default Values
The following table provides a summary of the default values that are populated whenever a new advanced auxiliaries (.AAUX) file is created from scratch. The table also indicates the editable/default status of the relevant parameters in the VECTO UI in Engineering mode, and the recommended status in Declaration mode (not currently implemented). The default values / parameter status has been agreed with the project steering group.
@@ -231,7 +231,7 @@ Definition of bins for transmission rates according to ACEA TF5 recommendation:
| **Ventilation** | High (20x internal volume / h) | Low (7x internal volume / h) |
| **Heating** | High (10x internal volume / h) | Low (7x internal volume / h)
-###File Format
+### File Format
The HVAC SSM (.ahsm) and Bus Parameter Database (.abdb) files use the VECTO CSV format.
diff --git a/Documentation/User Manual/2-calculation-modes/calculation-modes.md b/Documentation/User Manual/2-calculation-modes/calculation-modes.md
index 942b7f3d890f85d89cc248c78a4b90fda1c772ce..7e190642f81c55c67474ccfa3964446d82221c87 100644
--- a/Documentation/User Manual/2-calculation-modes/calculation-modes.md
+++ b/Documentation/User Manual/2-calculation-modes/calculation-modes.md
@@ -1,4 +1,4 @@
-#Calculation Modes
+# Calculation Modes
VECTO supports different calculation modes for declaring a vehicle, validation of test-results, or experimenting with different parameters and components. These modes are described here.
diff --git a/Documentation/User Manual/2-calculation-modes/declaration.md b/Documentation/User Manual/2-calculation-modes/declaration.md
index 2d02411ff4f2661984bca26417f312617d6f81e1..b7a26931df0ab6c561612ba86999a71b46ee5f3b 100644
--- a/Documentation/User Manual/2-calculation-modes/declaration.md
+++ b/Documentation/User Manual/2-calculation-modes/declaration.md
@@ -1,16 +1,16 @@
-##Declaration Mode
+## Declaration Mode
In Declaration Mode many input parameters are predefined for the official certification. They are locked in the user interface and will automatically be set by VECTO during calculation. Calculations will be performed for each mission profile (of the corresponding HDV class) with two different loadings: low loading and reference loading.
Declaration Mode can be activated in the [Options Tab](#main-form).
-###Requirements
+### Requirements
- One or more checked job files in the Job List
- The job files don't need to include driving cycles. These are automatically assigned.
-###Results
+### Results
- Modal results (.vmod). One file for each vehicle/cycle/loading combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
- Sum results (.vsum). One file for each invocation of VECTO.
diff --git a/Documentation/User Manual/2-calculation-modes/engine-only.md b/Documentation/User Manual/2-calculation-modes/engine-only.md
index 8e4d08df3e787e26a3e935c4e2ee9f7ef479d51d..ef18bcc634031b7269075f3de7dcbb978fd5a455 100644
--- a/Documentation/User Manual/2-calculation-modes/engine-only.md
+++ b/Documentation/User Manual/2-calculation-modes/engine-only.md
@@ -1,4 +1,4 @@
-##Engine-Only Mode
+## Engine-Only Mode
When this mode is enabled in the Job File then VECTO only calculates the fuel consumption based on a load cycle (engine speed and torque). In the [Job File](#job-file) only the following parameters are needed:
diff --git a/Documentation/User Manual/2-calculation-modes/engineering.md b/Documentation/User Manual/2-calculation-modes/engineering.md
index 54039a99e4bdabcfaf81cf07d5f7cea2b01421bb..13d88e33966c3b7d25345c94e05fdc39ea03145f 100644
--- a/Documentation/User Manual/2-calculation-modes/engineering.md
+++ b/Documentation/User Manual/2-calculation-modes/engineering.md
@@ -1,22 +1,22 @@
-##Engineering Mode
+## Engineering Mode
The Engineering Mode lets the user define every aspect in the component models of the vehicle and the driving cycle. This is for experimenting and validation purposes.
In this mode the given list of job files is simulated with the respective driving cycles. Each job file defines a separate vehicle.
-###Requirements
+### Requirements
- One or more checked job files in the Job List
- Each job file must include at least one driving cycle
-###Results
+### Results
- Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
- Sum results (.vsum). One file for each invocation of VECTO.
-###Options
+### Options
The Driving Cycle determines the simulation method in engineering mode. The option depends directly on the driving cycle input and cannot be set explicitely. For more information about the formats see [Driving Cycles](#driving-cycles-.vdri).
* [Target speed, distance-based](#engineering-mode-target-speed-distance-based-cycle)
diff --git a/Documentation/User Manual/2-calculation-modes/verification-test.md b/Documentation/User Manual/2-calculation-modes/verification-test.md
index a1beecf8775824d92e6bc2aecf0759a5b5c2f5ff..83ea7b632c301ea85f8a498db5a78f03b35e2f28 100644
--- a/Documentation/User Manual/2-calculation-modes/verification-test.md
+++ b/Documentation/User Manual/2-calculation-modes/verification-test.md
@@ -1,15 +1,15 @@
-##Verification Test Mode
+## Verification Test Mode
The purpose of the verification test is to simulate a vehicle defined in declaration mode on a measured real-driving cycle. This simulation mode uses its own [cyle format](#verification-test-cycle), requiring mainly vehicle speed, wheel speed, wheel torque, engine-fan speed, and engine speed. VECTO then calculates the appropriate gear and simulates the cycle. Auxiliary power is according to the technologies defined in the vehicle. However, the engine fan auxiliary is ignored and the power demand for the engine fan is calcuated based on the engine-fan speed. The power demand for the other auxiliaries depends on the vehicle's actual speed. The fuel consumption is calculated using the engine speed from the driving cycle and the torque demand as given in the cycle, adding the losses of all powertrain components.
<div class="engineering">
-###Requirements
+### Requirements
- One or more checked job files in the Job List
- Each job must include a vehicle in declaration mode (XML)
- Each job file must include at least one driving cycle
-###Results
+### Results
- Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
- Sum results (.vsum). One file for each invocation of VECTO.
@@ -17,21 +17,21 @@ The purpose of the verification test is to simulate a vehicle defined in declara
<div class="declaration">
-###Requirements
+### Requirements
- One or more checked job files in the Job List
- Each job must include a vehicle in declaration mode (XML)
- Each job must include the manufacturer report (XML) of the vehicle as generated for the vehicle delcaration
- Each job file must include exactly one driving cycle (in case multiple driving cycles are provided, only the first cycle is simulated!)
-###Results
+### Results
- VTP Report (.xml). Contains a description of the vehicle and its components, the verification test analysis according to the draft legislation, and a validation of the input data digest values
- Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
- Sum results (.vsum). One file for each invocation of VECTO.
-###Validations
+### Validations
- Before the simulation of the measured VTP cycle starts, the provided cycle data is passed through some sanity checks:
* The cycle is provided in 2Hz
diff --git a/Documentation/User Manual/3-simulation-models/ADAS_EcoRoll.md b/Documentation/User Manual/3-simulation-models/ADAS_EcoRoll.md
index 5d9c01c0ebaefd3a3eb41bb06e4dbeb5f44ffee3..15f8076dcb601f48779fdf28ff7eb6da197725cc 100644
--- a/Documentation/User Manual/3-simulation-models/ADAS_EcoRoll.md
+++ b/Documentation/User Manual/3-simulation-models/ADAS_EcoRoll.md
@@ -1,10 +1,10 @@
-##Driver: Overspeed
+## Driver: Overspeed
Both functions control the vehicle's behaviour on uneven road sections (slope ≠ 0) and can be configured in the [Job File](#job-file)'s Driver Assist Tab. Overspeed is designed to model an average driver's behaviour without the aid of driver assistance systems. Eco-Roll represents an optional driver assistance feature. For this reason vehicles without Eco-Roll should always have the Overspeed function enabled.
-###Overspeed
+### Overspeed
Overspeed activates as soon as the total power demand at the wheels (Pwheel) falls below zero, i.e. the vehicle accelerates on a negative slope. The clutch remains closed, engine in motoring operation, and the vehicle accelerates beyond the cycle's target speed. When the speed limit (target speed plus **Max. Overspeed**) is reached the mechanical brakes are engaged to prevent further acceleration.
@@ -20,13 +20,13 @@ Parameters in [Job File](#job-file):
- **Max. Overspeed \[km/h\]** (relative to target speed)
-##Advanced Driver Assistant Systems: Engine Stop/Start
+## Advanced Driver Assistant Systems: Engine Stop/Start
-###Description
+### Description
If engine stop/start is enabled in the Vehicle, the engine is turned off during vehicle stops to reduce the fuel consumption. During vehicle stops the energy demand for certain auxiliaires and for starting the engine is accumulated. In a post-processing step the final [fuel consumption is corrected](#engine-fuel-consumption-correction) to consider the energy demand for the auxiliaries and engine start.
-###Model Parameters
+### Model Parameters
- **Delay engine-off:** if the vehicle stops, the engine is switched off after this timespan
- **Max engine-off timespan:** if the enine is switched off at a vehicle stand, the engine is turned on again after this timespan. This basically limits the max. time the engine is switched off at a single engine-off event.
@@ -38,7 +38,7 @@ If engine stop/start is enabled in the Vehicle, the engine is turned off during
- Engine stop/start utility factor: 0.8
</div>
-###Engine Start-Up Energy Demand
+### Engine Start-Up Energy Demand
The energy demand to ramp-up the engine depends on the engine's inertia and the engine's drag torque and is computed according to the following equation:
@@ -49,7 +49,7 @@ $E_{ICE,start} = E_{ICE,rampUp} / \eta_{alternator}^2$
$E_{ICE,start}$ is the amount of energy the combustion engine needs to provide to compensate the start up is the ramp-up energy multiplied by the efficiency of the alternator. $t_{ICE,start}$ is assumed to be 1 second and $\eta_{alternator}$ is 0.7.
-###Auxiliaries and Utility Factor
+### Auxiliaries and Utility Factor
During ICE-off phases the ICE is fully shut of in the simulation (.vmod data). However, in reality the ICE is not always switched off due to certain
boundary conditions (e.g. power demand from an auxiliary, temperature, etc.). This is considered in the [post-processing](#engine-fuel-consumption-correction).
@@ -75,9 +75,9 @@ In Engineering Mode the energy demand of the auxiliaries can be specified for th
</div>
-##Advanced Driver Assistant Systems: Eco-Roll
+## Advanced Driver Assistant Systems: Eco-Roll
-###Description
+### Description
Eco-roll is a driver assistant system that automatically decouples the internal combustion engine from the power train during specific downhill driving conditions with low negative slopes. The aim is to save fuel during such phases. VECTO supports eco-roll without engine stop/start and eco-roll with engine stop/start. In the former case, the combustion engine is idling during eco-roll phases while in the latter case the combustion engine is turned off during eco-roll events. For vehicles having eco-roll with engine stop/start the fuel consumption is corrected for the engine stop/start events and the auxiliary power demand during engine-off phases.
@@ -96,7 +96,7 @@ In Engineering Mode the energy demand of all auxiliaries is assumed to be drawn
</div>
-###Model Parameters
+### Model Parameters
- **Minimum speed:** minimum vehicle speed to allow eco-roll to be activated
- **Activation delay:** delay between the point in time when all conditions for an eco-roll event are fulfilled until eco-roll is activated
@@ -109,7 +109,7 @@ In Engineering Mode the energy demand of all auxiliaries is assumed to be drawn
- Underspeed threshold: 0 km/h
</div>
-###Eco-Roll Model
+### Eco-Roll Model
**Calulations during simulation**
@@ -121,9 +121,9 @@ The following state diagram depicts when eco-roll is activated during the simula
-##Advanced Driver Assistant Systems: Predictive Cruise Control
+## Advanced Driver Assistant Systems: Predictive Cruise Control
-###Description
+### Description
Predictive cruise control (PCC): systems which optimise the usage of potential energy during a driving cycle based on an available preview of road gradient data and the use of a GPS system. A PCC system declared in the input to the simulation tool shall have a gradient preview distance longer than 1000 meters and cover all following use cases:
@@ -147,7 +147,7 @@ Predictive cruise control is only considered on highway sections of the simulate
In declaration mode, the whole long-haul cycle is considered as highway. Moreover, the section from 29760m to 96753m of the regional delivery cycle is considered as highway.
</div>
-###Model Parameters
+### Model Parameters
- **Allowed underspeed:** Threshold below the target speed the vehicle's velocity may be reduced to during a PCC event (use-case 1 & 2, $v_{neg}$)
- **Allowed overspeed:** Threshold above the target speed the vehicle's velocity may reach during a PCC event (use-cae 3)
@@ -165,7 +165,7 @@ In declaration mode, the whole long-haul cycle is considered as highway. Moreove
- Preview distance use case 2: 1000 m
</div>
-###Predictive Cruise Control Model Use-cases 1 and 2
+### Predictive Cruise Control Model Use-cases 1 and 2
**Pre-Processing**
@@ -203,7 +203,7 @@ The following state diagram depicts when a PCC event is activated during the sim
The fuel consumption of vehicles equipped with PCC option 1 & 2 and eco-roll with engine stop/start will be corrected for engine stop/start as described in [engine stop/start correction](#engine-fuel-consumption-correction).
-###Predictive Cruise Control Model Use-case 3
+### Predictive Cruise Control Model Use-case 3
To consider predictive cruise control use-case 3, the driver model's allowed overspeed is set to the model parameter *allowed overspeed* in highway sections if the vehicle supports PCC use-case 3.
diff --git a/Documentation/User Manual/3-simulation-models/Auxiliaries.md b/Documentation/User Manual/3-simulation-models/Auxiliaries.md
index 8f06505a0e052474bdfdc4e9a95cb2dbadf3e920..82ea11928382ee452f155d838d3e1d2342cc1801 100644
--- a/Documentation/User Manual/3-simulation-models/Auxiliaries.md
+++ b/Documentation/User Manual/3-simulation-models/Auxiliaries.md
@@ -1,4 +1,4 @@
-##Auxiliaries
+## Auxiliaries
<div class="declaration">
In Declaration mode the auxiliaries are pre-defined and the power demand is defined based on the vehicle category and mission. For every type of auxiliary (fan, steering pump, HVAC, electrig system, pneumatic system) the user can select a technology from a given list.
diff --git a/Documentation/User Manual/3-simulation-models/Driver_AccLimit.md b/Documentation/User Manual/3-simulation-models/Driver_AccLimit.md
index c8b482e50081743184a72d11969d2dda7cc01343..7ef435ae62e87c2de700d93587bbd309f1e5baca 100644
--- a/Documentation/User Manual/3-simulation-models/Driver_AccLimit.md
+++ b/Documentation/User Manual/3-simulation-models/Driver_AccLimit.md
@@ -1,4 +1,4 @@
-##Driver: Acceleration Limiting
+## Driver: Acceleration Limiting
VECTO limits the vehicle acceleration and deceleration depending on current vehicle speed, to model a realistic driver behavior. These limits are defined in the [Acceleration Limiting Input File (.vacc)](#acceleration-limiting-input-file-.vacc), which can be set in the [Job File](#job-file). In Declaration mode this is already predefined.
diff --git a/Documentation/User Manual/3-simulation-models/Driver_LAC.md b/Documentation/User Manual/3-simulation-models/Driver_LAC.md
index 668a5637530d60c511b18fe8e412d0c08b3097b6..e6a65b14c58c6d471d0c0c5e29d70d44fdaf4c5e 100644
--- a/Documentation/User Manual/3-simulation-models/Driver_LAC.md
+++ b/Documentation/User Manual/3-simulation-models/Driver_LAC.md
@@ -1,4 +1,4 @@
-##Driver: Look-Ahead Coasting
+## Driver: Look-Ahead Coasting
Look-Ahead Coasting is a function that aims on modelling real driver behaviour. It is a forward-looking function that detects forthcoming reductions in target speed in the mission profile (e.g. speed limit, etc.) and induces an early deceleration using engine braking before applying mechanical brakes according to the [deceleration limit](#driver-acceleration-limiting).
@@ -36,7 +36,7 @@ In engineering mode the parameters can be freely chosen while in declaration mod
-####Decision Factor for target velocity lookup (DF~vel~)
+#### Decision Factor for target velocity lookup (DF~vel~)
@@ -50,7 +50,7 @@ v_target [km/h], decision_factor [-]
100 , 1
~~~
-####Decision Factor for velocity drop lookup (DF~vdrop~)
+#### Decision Factor for velocity drop lookup (DF~vdrop~)
Example (default values):
diff --git a/Documentation/User Manual/3-simulation-models/Engine_DualFuel.md b/Documentation/User Manual/3-simulation-models/Engine_DualFuel.md
index 674e5769ba0988ddd5ee717ecbef2bdb3cf8daa0..ed4759a4fb3db5dfc5e1a5ca5f7b04bb872a13ad 100644
--- a/Documentation/User Manual/3-simulation-models/Engine_DualFuel.md
+++ b/Documentation/User Manual/3-simulation-models/Engine_DualFuel.md
@@ -1,4 +1,4 @@
-##Dual Fuel Engine
+## Dual Fuel Engine
<div class="engineering">
VECTO supports to simulate vehicles equipped with dual-fuel engines, i.e. two different fuels are used simulateously. Therefore, the engine model contains a second fuel comsumption map and VECTO interpolates the fuel consumtion from both consumption maps. In the .vmod and .vsum files the consumption of every fuel is reported. The CO2 emissions are te sum of CO2 emissions from both fuels.
diff --git a/Documentation/User Manual/3-simulation-models/Engine_DynamicFullLoad.md b/Documentation/User Manual/3-simulation-models/Engine_DynamicFullLoad.md
index 8b724d5432b03faafe964c9d1d2c8cf763a89c28..9b9a10d9f2400df67556e60eace2d9ef796bec11 100644
--- a/Documentation/User Manual/3-simulation-models/Engine_DynamicFullLoad.md
+++ b/Documentation/User Manual/3-simulation-models/Engine_DynamicFullLoad.md
@@ -1,4 +1,4 @@
-##Engine: Transient Full Load
+## Engine: Transient Full Load
The engine implements a PT1 behaviour to model transient torque build up:
diff --git a/Documentation/User Manual/3-simulation-models/Engine_FC.md b/Documentation/User Manual/3-simulation-models/Engine_FC.md
index d87ae049395323ce5c908d8624de78e1e43c979f..0bf9fada2adc34eb59ba231a2e5d9872e9635355 100644
--- a/Documentation/User Manual/3-simulation-models/Engine_FC.md
+++ b/Documentation/User Manual/3-simulation-models/Engine_FC.md
@@ -1,4 +1,4 @@
-##Engine: Fuel Consumption Calculation
+## Engine: Fuel Consumption Calculation
The base FC value is interpolated from the stationary [FC map](#fuel-consumption-map-.vmap). If necessary the base value is corrected to compensate for unconsidered auxiliary energy consumption for vehicles with Start/Stop. In Declaration Mode [additional correction factors are applied](#engine-correction-factors).
@@ -6,7 +6,7 @@ The base FC value is interpolated from the stationary [FC map](#fuel-consumption
The CO~2~ result for the actual mission profile is directly derived from the fuel consumption using a gravimetric [CO~2~/FC factor](#settings).
-###Fuel Map Interpolation
+### Fuel Map Interpolation
The interpolation is based on [Delaunay Triangulation ](http://en.wikipedia.org/wiki/Delaunay_triangulation) and works as follows:
diff --git a/Documentation/User Manual/3-simulation-models/Engine_FC_Correction.md b/Documentation/User Manual/3-simulation-models/Engine_FC_Correction.md
index 4d4fc91e1b901f920c1a810d20ccb0662b4e9ccd..9dc11afe98fe303a1bb5abcdf7ad58395300bacc 100644
--- a/Documentation/User Manual/3-simulation-models/Engine_FC_Correction.md
+++ b/Documentation/User Manual/3-simulation-models/Engine_FC_Correction.md
@@ -1,8 +1,8 @@
-##Engine Fuel Consumption Correction
+## Engine Fuel Consumption Correction
The final fuel consumption is corrected in a post-processing to reflect systems not directly modeled in VECTO (e.g. electric waste heat recovery sysmtes) or to account for systems not active all the time for different reasons (e.g., engine stop-start).
-###Engine Stop/Start Correction
+### Engine Stop/Start Correction
As the energy demand of auxiliaries is modeled as an average power demand over the whole simulated cycle, the demand of certain auxiliaries during engine-off periods needs to be compensated during engine-on periods. This is done using the [Engine-Line approach](#engine-line-approach).
@@ -14,13 +14,13 @@ A utility factor (UF) considers that the ICE is not off in all cases. Therefore
For the post-processing two different utility factors are considered. One for ICE-off phases during vehicle standstill and one for ICE-off phases during driving.
-####ICE Start
+#### ICE Start
$\textrm{E\_ICE\_start} = \sum{\textrm{P\_ICE\_start} \cdot dt}$
$\textrm{FC\_ICE\_start} = \textrm{E\_ICE\_start} \cdot k_\textrm{engline}$
-####Mechanical Auxiliaries
+#### Mechanical Auxiliaries
$\textrm{E\_aux\_ESS\_mech\_ICEoff\_standstill} = \sum_{\forall \textrm{v\_act}_i = 0}{\textrm{P\_aux\_ESS\_mech\_ICE\_off} \cdot dt}$
@@ -40,11 +40,10 @@ $$
& \textrm{E\_aux\_ESS\_mech\_ICEoff\_driving} \cdot k_\textrm{engline} \cdot \textrm{UF}_\textrm{driving} + \\
& (\textrm{E\_aux\_ESS\_mech\_ICEon\_driving} \cdot k_\textrm{engline} + \textrm{FC}(n_\textrm{idle}, 0) \cdot \textrm{t\_ICEoff\_driving}) \cdot (1 - \textrm{UF}_\textrm{driving})
\end{align*}
-
$$
-####Bus Auxiliaries Correction -- Electric System
+#### Bus Auxiliaries Correction -- Electric System
The bus auxiliaries electric system correction is used for conventional vehicles with ESS and buses with smart electric system in the same way.
@@ -56,7 +55,7 @@ $\Delta\textrm{E\_BusAux\_ES\_mech} = (\textrm{E\_BusAux\_ES\_consumed} - \textr
$\textbf{\textrm{FC\_BusAux\_ES}} = \textrm{E\_BusAux\_ES} \cdot k_\textrm{engline}$
-####Bus Auxiliaries Correction -- Electric System Supply from REESS
+#### Bus Auxiliaries Correction -- Electric System Supply from REESS
$\textrm{E\_DCDC\_missing} = \textrm{P\_DCDC\_missing} \cdot dt$
@@ -65,7 +64,7 @@ $\textrm{E\_DCDC\_missing\_mech} = \textrm{E\_DCDC\_missing} / \textrm{DCDC\_Con
$\textbf{\textrm{FC\_DCDCMissing}} = \textrm{E\_DCDC\_missing\_mech} \cdot k_\textrm{engline}$
-####Bus Auxiliaries Correction -- Pneumatic System
+#### Bus Auxiliaries Correction -- Pneumatic System
For the pneumatic system the goal of the post-processing correction is that the correct amount of compressed air is generated, even when the ICE is off. As the average
air demand is calculated with an estimated cycle driving time, the first step is to correct the air demand using the actual cycle driving time.
@@ -106,11 +105,10 @@ $$
& \textrm{FC\_BusAux\_PS\_Drag\_ICEoff\_driving} + \\
& \textrm{FC\_busAux\_PS\_Drag\_ICEoff\_standstill}
\end{align*}
-
$$
-####Bus Auxiliaries Correction -- Aux Heater
+#### Bus Auxiliaries Correction -- Aux Heater
The power demand for an additional fuel-fired heater is calculated in the post-processing. The HVAC steaty state model calculates the heating demand (weighted sum of different climatic conditions) and based on the engine's average waste heat over the cycle the power demand for the aux heater is calculated. The fuel consumption for the aux heater is only added for the main fuel:
@@ -123,7 +121,7 @@ $\textrm{E\_auxHeater} = \textrm{HVACSSM}_\textrm{AuxHtr}(\overline{P}_\textrm{i
$\textbf{\textrm{FC\_BusAux\_AuxHeater}} = \textrm{E\_auxHeater} \cdot \textrm{NCV}_\textrm{main fuel}$
-####Waste Heat Recovery Systems
+#### Waste Heat Recovery Systems
$\textrm{E\_WHR\_mech} = \sum{\textrm{P\_WHR\_mech} \cdot dt}$
@@ -140,7 +138,7 @@ $$
$\textbf{\textrm{FC\_WHR}} = - (\textrm{E\_WHR\_mech} + \textrm{E\_WHR\_el\_mech}) \cdot k_\textrm{engline}$
-####Hybrid Vehicles: REESS SoC Correction
+#### Hybrid Vehicles: REESS SoC Correction
If the REESS Soc at the end of the simulation is higher than the initial SoC the correction is done according to:
@@ -161,7 +159,7 @@ $\eta_{\textrm{REESS}_\textrm{chg}} = \frac{\textrm{E\_REESS\_INT\_CHG}}{\textrm
$\eta_{\textrm{REESS}_\textrm{dischg}} = \frac{\textrm{E\_REESS\_INT\_DISCHG}}{\textrm{E\_REEES\_T\_DISCHG}}$
-###Corrected Total Fuel Consumption
+### Corrected Total Fuel Consumption
The final fuel consumption after all corrections are applied is calcualted as follows:
@@ -176,11 +174,10 @@ $$
& \textrm{FC\_BusAux\_AuxHeater} \;+ \\
& \textrm{FC\_SoC}
\end{align*}
-
$$
-###Engine-Line Approach
+### Engine-Line Approach
The total fuel consumption is corrected in a post-processing step according to the *engine-line* approach. Therefore, for every engine operating point where the engine is on and has a positive fuel consumption the fuel consumption is plotted over the engine power. The slope (k) of the linear regression of the fuel consumption is used to compute the additional fuel that is needed for the energy demand during engine-off periods and engine starts.
diff --git a/Documentation/User Manual/3-simulation-models/Engine_Speed_Torque_limitations.md b/Documentation/User Manual/3-simulation-models/Engine_Speed_Torque_limitations.md
index 74f03f51517b3d260734f60996ff69a47508923e..b64dfce41f0291502e27fc71234a91f936dae83e 100644
--- a/Documentation/User Manual/3-simulation-models/Engine_Speed_Torque_limitations.md
+++ b/Documentation/User Manual/3-simulation-models/Engine_Speed_Torque_limitations.md
@@ -1,5 +1,5 @@
-##Engine Torque and Engine Speed Limitations
+## Engine Torque and Engine Speed Limitations
The engine's maximum speed and maximum torque may be limited by either the gearbox (due to mechanical constraints) or the vehicle control.
Engine torque limitations are modeled by limiting the engine full-load curve to the defined maximum torque, i.e., the original engine full-load curve is cropped at the defined maximum torque for a certain gear. Limits regarding the gearbox' maximum input speed are modeled by intersecting (and limiting) the upshift line with the max. input speed. In the last gear, where no upshifts are possible, the engine speed is limited to the gearbox' maximum input speed.
@@ -14,11 +14,11 @@ In Engineering Mode, speed and torque limits can be defined and will be effectiv
<div class="declaration">
In Declaration Mode, the following rules restrict the limitations of engine torque:
-###Transmission Input-Speed Limitations
+### Transmission Input-Speed Limitations
* Applicable for every gear
-###Transmission Torque Limitations
+### Transmission Torque Limitations
* For higher 50% of gears (i.e., gears 7 to 12 for a 12-gear transmission):
- Transmissions max torque > 90% of engine max torque: max. torque limitation *not* applicable (VECTO extrapolates loss-maps)
@@ -26,7 +26,7 @@ In Declaration Mode, the following rules restrict the limitations of engine torq
* For lower 50% of gears (i.e., gears 1 to 6 for a 12-gear transmission):
- Transmission torque limit is always applicable
-###Vehicle defined Torque Limitations
+### Vehicle defined Torque Limitations
* For higher 50% of gears (i.e., gears 7 to 12 for a 12-gear transmission):
- Torque limit > 95% of engine max torque: max. torque limitation *not* applicable (VECTO extrapolates loss-maps)
diff --git a/Documentation/User Manual/3-simulation-models/Engine_WHTC.md b/Documentation/User Manual/3-simulation-models/Engine_WHTC.md
index c2a0fd53c18cfcb76158b488ed750b41c358e59b..0d3114e9a3f853a067e9184531f0ec6a93a3d672 100644
--- a/Documentation/User Manual/3-simulation-models/Engine_WHTC.md
+++ b/Documentation/User Manual/3-simulation-models/Engine_WHTC.md
@@ -1,4 +1,4 @@
-##Engine: Correction Factors
+## Engine: Correction Factors
<div class="declaration">
In declaration mode the fuel consumption is corrected as follows:
diff --git a/Documentation/User Manual/3-simulation-models/FuelProperties.md b/Documentation/User Manual/3-simulation-models/FuelProperties.md
index 6254e2ebbd97c942a0e194c5fbcc8ca40e3d3a4a..35efb4705efcfe5fcde99d823827148dda190826 100644
--- a/Documentation/User Manual/3-simulation-models/FuelProperties.md
+++ b/Documentation/User Manual/3-simulation-models/FuelProperties.md
@@ -1,4 +1,4 @@
-##Fuel Properties
+## Fuel Properties
| FuelType | Tanksystem | FuelDensity [kg/m3] | CO2 per FuelWeight [kgCo2/kgFuel] | NCV_stdEngine [kJ/kg] | NCV_stdVecto [kJ/kg] | Note |
| ------------ | ------------ | --------------------- | ----------------------------------- | ----------------------- | ---------------------- | ------- |
@@ -13,6 +13,6 @@
Specifications are based on a recent analysis (2018) performed by CONCAWE/EUCAR and shall reflect typical fuel on the European market. The data is scheduled to be published in March 2019 in the context of the study:
Well-To-Wheels Analysis Of Future Automotive Fuels And Powertrains in the European Context – Heavy Duty vehicles
-###VECTO Input for CNG/LNG Vehicles
+### VECTO Input for CNG/LNG Vehicles
Currently only the fuel type 'NG PI' for the engine certification is allowed according to Regulation (EU) 2017/2400. For LNG vehicles, therefore, the engine fuel type has to be set to 'NG PI' and at the vehicle level NgTankSystem has to be set to 'liquefied'. For CNG vehicles the same engine fuel type is provided but NgTankSystem has to be set to 'compressed'.
diff --git a/Documentation/User Manual/3-simulation-models/GearShift.md b/Documentation/User Manual/3-simulation-models/GearShift.md
index 89fedc63fec5dfc7685a4c7da9cb30650075c40d..eb0016fb7a11120230457fbca64dec29d8eec782 100644
--- a/Documentation/User Manual/3-simulation-models/GearShift.md
+++ b/Documentation/User Manual/3-simulation-models/GearShift.md
@@ -1,4 +1,4 @@
-##Gearbox: Gear Shift Model
+## Gearbox: Gear Shift Model
The Gear Shift Model is based on shift curves that define the engine speed for up- and down- shifting as a function of engine torque. As soon as the engine operation point passes one of the shift curves a gear change is initiated.
@@ -30,7 +30,7 @@ In the Gearbox File two additional parameters are defined:
- **Minimum shift time** \[s\] - Limits the time between two gear shifts in whole seconds. This rule will be ignored if rpms are too high or too low. Note that high values may cause high rpms during acceleration.
-###Gear Skipping
+### Gear Skipping
Gear Skipping is active for AMT and MT. Whenever a gear change is initiated (by crossing the up- or down-shift line) VECTO may skip one or several gears as long as the required torque reserve is provided.
@@ -38,7 +38,7 @@ Gear Skipping is active for AMT and MT. Whenever a gear change is initiated (by
-###Early Upshift
+### Early Upshift
Early Upshift (allow upshifts inside the shift polygons) is enabled for AMT only. If the next higher gear provides the required torque reserve and it's rpm is still above down-shift-rpm VECTO will shift up.
diff --git a/Documentation/User Manual/3-simulation-models/GearShift_AMT.md b/Documentation/User Manual/3-simulation-models/GearShift_AMT.md
index 2d05d61addedbadd590423e6341dfa57044a3529..21534afd0ec0ec28c4e16bbf4e081932ad773210 100644
--- a/Documentation/User Manual/3-simulation-models/GearShift_AMT.md
+++ b/Documentation/User Manual/3-simulation-models/GearShift_AMT.md
@@ -1,4 +1,4 @@
-##Shift Strategy: AMT Gearshift Rules
+## Shift Strategy: AMT Gearshift Rules
This section describes the gearshift rules for automatic manual transmission models. When a gearshift is triggered, gears may be skipped.
@@ -35,7 +35,7 @@ The general shift conditions are checked first in the shift algorithm. The follo
| Rating current gear | 0.97 |
| $T_{reserve}$ | 0 |
-###Emergency shifts
+### Emergency shifts
Emergency shifts depend on the current gear and the engine speed. The shifting rules for emergency shifts have been adopted from the "Classic" gearshift strategy in VECTO. In case of application of emergency rule no skipping of gears is applied.
@@ -54,7 +54,7 @@ Upshift conditions:
* Current gear < highest gear
* $n_{eng} < n_{95h}$
-###Polygon shifts
+### Polygon shifts
The second level of the gearshift algorithm is the polygon shift rule. If the current operating point is outside of the shift polygons, the polygon shift rule applies:
@@ -68,7 +68,7 @@ Upshift behaviour:
It should be noted, that there is no skip gears at downshifting in the polygon shift mode.
-###Efficiency shifts
+### Efficiency shifts
The efficiency shift rule is added on top of the polygon shift rule. The EffShift strategy allows gear shifts if the current engine operating point is inbetween the gearshift lines and a certain threshold above the engine's drag curve and the combined fuel efficiency considering engine and gearbox characteristics in the candidate gear is better than in the current gear. Therefore the fuel consumption of the current gear and the gears within an allowed gear shift range (parameter allowed +/- gears) is calculated. For AMT transmissions, the current operating point is used for this efficiency evaluation. Since, the velocity drop due to traction interruption is not relevant for this evaluation as this operating point only occurs for a short period of time. Efficiency shifts are only allowed below a certain gear ratio (gearbox + axle) to prevent frequent gear changes in the very lowest gears.
diff --git a/Documentation/User Manual/3-simulation-models/GearShift_AT.md b/Documentation/User Manual/3-simulation-models/GearShift_AT.md
index 2e46e9a4b7933a3b4ed49344cd6ce0406253b70f..d7496188051624fe5dd80904ca1a841d7aaff84a 100644
--- a/Documentation/User Manual/3-simulation-models/GearShift_AT.md
+++ b/Documentation/User Manual/3-simulation-models/GearShift_AT.md
@@ -1,11 +1,11 @@
-##Gearbox: AT Gearshift Rules
+## Gearbox: AT Gearshift Rules
For AT gearboxes neither Skip Gears nor Early upshift (see [Gearbox: Gear Shift Model](#gearbox-gear-shift-model)) are enabled. Moreover, the gears are shifted strictly sequentially:
- 1C -> 1L -> 2L -> ... (torque converter only in 1st gear)
- 1C -> 2C -> 2L -> ... (torque converter in 1st and 2nd gear)
-###Shift Polygons in Declaration Mode
+### Shift Polygons in Declaration Mode
The shift lines in Declaration Mode only apply for trucks and gearboxes with serial torque converter (AT-S).
@@ -14,14 +14,14 @@ The shift lines in Declaration Mode only apply for trucks and gearboxes with ser
-###Upshift rules
+### Upshift rules
+ If engine speed and engine torque in the *next gear* (see shift sequence) is above the upshift line AND
+ the acceleration in the next gear is above a certain threshold if the driver is accelerating, i.e., acceleration_nextGear > min(Min. acceleration threshold, Driver acceleration)
The user interface allows to enter two acceleration thresholds, one for locked gear to locked gear shifts and another vor converter to locked gear shifts. For converter to converter shifts the latter threshold applies.
-###Downshift
+### Downshift
* If the engine speed falls below the downshift curve
@@ -30,7 +30,7 @@ The user interface allows to enter two acceleration thresholds, one for locked g
- OR during deceleration phase when the torque converter is active and the engine speed would fall below idle speed
-###Shift parameters
+### Shift parameters
- Min. time between two consecutive gearshifts.
- Min. acceleration after gearshift for L to L gear shifts
diff --git a/Documentation/User Manual/3-simulation-models/GearShift_MT.md b/Documentation/User Manual/3-simulation-models/GearShift_MT.md
index 6701c43dd8adf74b24ea22bccf288b260cebe8a8..31c0ebb04443545f8709f0c27c78647c99b56a2e 100644
--- a/Documentation/User Manual/3-simulation-models/GearShift_MT.md
+++ b/Documentation/User Manual/3-simulation-models/GearShift_MT.md
@@ -1,30 +1,30 @@
-##Gearbox: MT and AMT Gearshift Rules
+## Gearbox: MT and AMT Gearshift Rules
This section describes the gearshift rules for manual and automatic manual transmission models. When a gearshift is triggered, gears may be skipped for both MT and AMT gearboxes (see [Gearbox: Gear Shift Model](#gearbox-gear-shift-model)). Early Upshift (see [Gearbox: Gear Shift Model](#gearbox-gear-shift-model)) is only enabled for AMT gearboxes.
-###Shift Polygons in Declaration Mode (According to ACEA Whitebook 2016)
+### Shift Polygons in Declaration Mode (According to ACEA Whitebook 2016)
-####1. Computation of Characteristic Points
+#### 1. Computation of Characteristic Points
-####2. Definition of Shift Lines
+#### 2. Definition of Shift Lines
-####3. Exception 1: Margin to Max-Torque line (Downshift)
+#### 3. Exception 1: Margin to Max-Torque line (Downshift)
Note: Line L1 is shiftet parallel so that it satisfies the max-torque margin condition, not intersected.
-####4. Exception 2: Minimal Distance between Downshift and Upshift Lines
+#### 4. Exception 2: Minimal Distance between Downshift and Upshift Lines
-####5. Final Gearshift Lines (Example)
+#### 5. Final Gearshift Lines (Example)
If the gearbox defines a maximum input speed for certain gears the upshift line may further be intersected
and limited to the gear's maximum input speed.
-###Upshift rules
+### Upshift rules
* If the engine speed is higher than the gearbox maximum input speed or engine n_{95h} speed (whichever is lower)
* If all of the following conditions are met:
@@ -34,7 +34,7 @@ and limited to the gear's maximum input speed.
- The last gearshift was longer than a certain threshold (Declaration Mode: 2s) ago AND
- The last downshift was longer than a certain threshold (Declaration Mode: 10s) ago
-###Upshift rules for Early Upshift (AMT only)
+### Upshift rules for Early Upshift (AMT only)
* If the engine speed is higher than the gearbox maximum input speed or engine n_{95h} speed (whichever is lower)
* If all of the following conditions are met:
@@ -45,7 +45,7 @@ and limited to the gear's maximum input speed.
- The last downshift was longer than a certain threshold (Declaration Mode: 10s) ago
-###Downshift
+### Downshift
* If the engine speed is lower than the engine's idle speed
* If all of the following conditions are met:
@@ -54,7 +54,7 @@ and limited to the gear's maximum input speed.
- The last upshift was longer than a certain threshold (Declaration Mode: 10s) ago
-###Shift parameters
+### Shift parameters
- Gearshift lines
- Engine idle speed
diff --git a/Documentation/User Manual/3-simulation-models/Gearbox_AT.md b/Documentation/User Manual/3-simulation-models/Gearbox_AT.md
index 0f3ee4f3f9033d76586301f752205b77040c00ff..a993ef11a3ef1a5759158fc3274ac13e4fc13392 100644
--- a/Documentation/User Manual/3-simulation-models/Gearbox_AT.md
+++ b/Documentation/User Manual/3-simulation-models/Gearbox_AT.md
@@ -1,4 +1,4 @@
-##Gearbox: AT Gearbox Model
+## Gearbox: AT Gearbox Model
Vecto supports both, AT gearboxes with serial torque converter and AT gearboxes with power split. Internally, both gearbox types are simulated using a power train architecture with the torque converter in series.
@@ -14,18 +14,18 @@ For AT gearboxes using power split the torque converter characteristics already
The .vmod file for vehicles with AT gearboxes contains an additional column that indicates if the torque converter is locked or not.
-###Gearshift losses for AT Gearboxes
+### Gearshift losses for AT Gearboxes
For AT gearboxes the losses during a power-shift are modeled according to the following equations
-####Basic assumptions
+#### Basic assumptions
+ Only power-shifts with positive power at gearbox output side are considered.
+ Both upshifts and downshifts with positive power at gearbox output side have to be considered.
+ The power at gearbox output side is assumed to be constant during a power-shift
-####Power-shift loss computation
+#### Power-shift loss computation
Model parameters: shift time ($t_s$), inertia factor ($f_I$)
diff --git a/Documentation/User Manual/3-simulation-models/PTO.md b/Documentation/User Manual/3-simulation-models/PTO.md
index 0214d0ab4c222c1c1fc282c2c1558130248e5bf2..327912c0de7df330bf4a173ba8cbcb8c9e8ea837 100644
--- a/Documentation/User Manual/3-simulation-models/PTO.md
+++ b/Documentation/User Manual/3-simulation-models/PTO.md
@@ -1,4 +1,4 @@
-##PTO
+## PTO
VECTO supports the simulation of PTO related components and losses in the powertrain. Structurally this consists of 2 components (PTO transmission, PTO consumer) and 3 different kind of losses (transmission, idling, cycle).
@@ -53,7 +53,7 @@ The following image shows the behavior of running PTO cycles during a normal dri
<div class="engineering">
-###Additional PTO activations in Engineering mode
+### Additional PTO activations in Engineering mode
In engineering mode additonal PTO activations are available to simulate different types of municipal vehicles. It is possible to add a certain PTO load during driving while the engine speed and gear is fixed (to simulate for example roadsweepers), or to add PTO activation while driving (to simulate side loader refuse trucks for example). In both cases the PTO activation is indicated in the driving cycle.
diff --git a/Documentation/User Manual/3-simulation-models/PwheelInput.md b/Documentation/User Manual/3-simulation-models/PwheelInput.md
index fc5fbc4f1e39299c2c53bfef453dcd9d5d5759b7..6271354e3ea912dbbab32c3e7ed313e0b75a928a 100644
--- a/Documentation/User Manual/3-simulation-models/PwheelInput.md
+++ b/Documentation/User Manual/3-simulation-models/PwheelInput.md
@@ -1,8 +1,8 @@
-##P~wheel~-Input (SiCo Mode)
+## P~wheel~-Input (SiCo Mode)
For verification tasks it is possible to manually input the power at wheels (P~wheel~) which is normally calculated via longitudinal dynamics. In this case VECTO only calculates the losses between wheels and engine and adds auxiliary power demand. This mode is active as soon as P~wheel~, Gear and Engine Speed are defined in the driving cycle.
-###Requirements
+### Requirements
- Driving Cycle must include t, P~wheel~ (Pwheel), Gear (Gear) and Engine Speed (n), see [Driving Cycle (.vdri) format](#driving-cycles-.vdri).
- The driving cycle must be time-based.
diff --git a/Documentation/User Manual/3-simulation-models/TC.md b/Documentation/User Manual/3-simulation-models/TC.md
index 0aee618f9d01398938c766e08013e929740cf958..328b714f08d2bc258b3fba21d137781b6cf32ced 100644
--- a/Documentation/User Manual/3-simulation-models/TC.md
+++ b/Documentation/User Manual/3-simulation-models/TC.md
@@ -1,4 +1,4 @@
-##Torque Converter Model
+## Torque Converter Model
The torque converter is defined as (virtual) separate gear. Independent of the chosen AT gearbox type (serial or power split), Vecto uses a powertrain architecture with a serial torque converter. The mechanical gear ratios and gears with torque converter are created by Vecto depending on the gearbox type and gear configuration.
@@ -7,7 +7,7 @@ While the torque converter is active engine torque and speed are computed based
-###Torque converter characteristics file (.vtcc)
+### Torque converter characteristics file (.vtcc)
The file is described [here](#torque-converter-characteristics-.vtcc).
diff --git a/Documentation/User Manual/3-simulation-models/Transmission_Losses.md b/Documentation/User Manual/3-simulation-models/Transmission_Losses.md
index 105f3f8247eaf7351a8b5a5c92559486f2c0ebb4..8e433f66f31c5e4c2a8d8f70c6eb17c722b618c4 100644
--- a/Documentation/User Manual/3-simulation-models/Transmission_Losses.md
+++ b/Documentation/User Manual/3-simulation-models/Transmission_Losses.md
@@ -1,4 +1,4 @@
-##Transmission Losses
+## Transmission Losses
Every transmission component (gearbox, angledrive, axlegear, ...) uses the following formula for calculating the torques at input and output side of the component:
diff --git a/Documentation/User Manual/3-simulation-models/Vehicle_ADAS_technologies.md b/Documentation/User Manual/3-simulation-models/Vehicle_ADAS_technologies.md
index 2ff439c5012a55062d7f382f6f7df7ecd0dd143a..fc871ab55500842efa748d78279e37e0c608428a 100644
--- a/Documentation/User Manual/3-simulation-models/Vehicle_ADAS_technologies.md
+++ b/Documentation/User Manual/3-simulation-models/Vehicle_ADAS_technologies.md
@@ -1,4 +1,4 @@
-##Vehicle: ADAS Technologies
+## Vehicle: ADAS Technologies
<div class="declaration">
Advanced Driver Assistant Systems are considered in Declaration Mode via a technology dependent and vehicle group specific bonus on the fuel cosumption as described in the followin.
@@ -44,93 +44,3 @@ The following table maps the valid combinations of ADAS systems to a so-called "
| true | false | true | Option 1 & 2 | 11/1 |
| true | false | true | Option 1 & 2 & 3 | 11/2 |
-
-For the vehicle groups 4, 5, 9, and 10 the following reduction in fuel consumption is applied for the different cycle and payload combinations and ADAS Combination. The first value is applied for low-loading and the second value is applied for reference load.
-
-### Vehicle Group 4
-
-| ADAS Combination | LongHaul | LongHaul EMS | Regional Delivery | Regional Delivery EMS | Urban Delivery |
-| ------------------ | ------------- | -------------- | ------------------- | ----------------------- | ---------------- |
-| 1 | -0.1% / 0.0% | | -0.5% / -0.5% | | -1.5% / -1.2% |
-| 2 | 0.0% / 0.0% | | -0.1% / -0.1% | | 0.0% / 0.0% |
-| 3 | 0.0% / -0.1% | | -0.1% / -0.2% | | 0.0% / 0.0% |
-| 4/1 | -0.1% / -0.4% | | 0.0% / -0.1% | | 0.0% / 0.0% |
-| 4/2 | -0.1% / -0.5% | | -0.1% / -0.2% | | 0.0% / 0.0% |
-| 5 | -0.1% / -0.1% | | -0.6% / -0.6% | | -1.5% / -1.2% |
-| 6 | -0.1% / -0.1% | | -0.6% / -0.7% | | -1.5% / -1.2% |
-| 7/1 | -0.1% / -0.4% | | -0.5% / -0.6% | | -1.5% / -1.2% |
-| 7/2 | -0.1% / -0.6% | | -0.6% / -0.7% | | -1.5% / -1.2% |
-| 8/1 | -0.1% / -0.4% | | -0.1% / -0.2% | | 0.0% / 0.0% |
-| 8/2 | -0.1% / -0.5% | | -0.1% / -0.3% | | 0.0% / 0.0% |
-| 9/1 | -0.1% / -0.4% | | -0.2% / -0.3% | | 0.0% / 0.0% |
-| 9/2 | -0.1% / -0.5% | | -0.2% / -0.4% | | 0.0% / 0.0% |
-| 10/1 | -0.2% / -0.4% | | -0.6% / -0.7% | | -1.5% / -1.2% |
-| 10/2 | -0.2% / -0.6% | | -0.6% / -0.7% | | -1.5% / -1.2% |
-| 11/1 | -0.2% / -0.4% | | -0.7% / -0.8% | | -1.5% / -1.2% |
-| 11/2 | -0.2% / -0.6% | | -0.7% / -0.8% | | -1.5% / -1.2% |
-
-### Vehicle Group 5
-
-| ADAS Combination | LongHaul | LongHaul EMS | Regional Delivery | Regional Delivery EMS | Urban Delivery |
-| ------------------ | ------------- | -------------- | ------------------- | ----------------------- | ---------------- |
-| 1 | -0.1% / 0.0% | 0.0% / 0.0% | -0.4% / -0.3% | -0.3% / -0.2% | -1.8% / -1.3% |
-| 2 | 0.0% / -0.1% | 0.0% / -0.1% | -0.1% / -0.1% | -0.2% / 0.0% | 0.0% / 0.0% |
-| 3 | -0.1% / -0.2% | 0.0% / -0.1% | -0.2% / -0.2% | -0.3% / -0.1% | 0.0% / 0.0% |
-| 4/1 | -0.2% / -0.5% | -0.2% / -0.1% | -0.2% / -0.6% | -0.3% / -0.5% | 0.0% / 0.0% |
-| 4/2 | -0.2% / -0.7% | -0.3% / -0.3% | -0.4% / -0.9% | -0.5% / -0.8% | 0.0% / 0.0% |
-| 5 | -0.1% / -0.1% | 0.0% / -0.1% | -0.5% / -0.4% | -0.5% / -0.3% | -1.8% / -1.3% |
-| 6 | -0.1% / -0.2% | -0.1% / -0.2% | -0.6% / -0.5% | -0.6% / -0.4% | -1.8% / -1.3% |
-| 7/1 | -0.2% / -0.5% | -0.3% / -0.1% | -0.6% / -0.9% | -0.7% / -0.8% | -1.8% / -1.3% |
-| 7/2 | -0.3% / -0.7% | -0.3% / -0.4% | -0.8% / -1.3% | -0.8% / -1.1% | -1.8% / -1.3% |
-| 8/1 | -0.2% / -0.6% | -0.2% / -0.1% | -0.3% / -0.7% | -0.5% / -0.5% | 0.0% / 0.0% |
-| 8/2 | -0.2% / -0.7% | -0.3% / -0.4% | -0.4% / -1.0% | -0.7% / -0.8% | 0.0% / 0.0% |
-| 9/1 | -0.2% / -0.6% | -0.3% / -0.2% | -0.4% / -0.8% | -0.6% / -0.6% | 0.0% / 0.0% |
-| 9/2 | -0.2% / -0.8% | -0.3% / -0.4% | -0.5% / -1.1% | -0.7% / -0.9% | 0.0% / 0.0% |
-| 10/1 | -0.2% / -0.6% | -0.3% / -0.2% | -0.7% / -1.0% | -0.8% / -0.8% | -1.8% / -1.3% |
-| 10/2 | -0.3% / -0.8% | -0.3% / -0.4% | -0.8% / -1.3% | -1.0% / -1.1% | -1.8% / -1.3% |
-| 11/1 | -0.3% / -0.7% | -0.3% / -0.2% | -0.8% / -1.1% | -0.9% / -0.9% | -1.8% / -1.3% |
-| 11/2 | -0.3% / -0.8% | -0.4% / -0.5% | -0.9% / -1.4% | -1.0% / -1.2% | -1.8% / -1.3% |
-
-### Vehicle Group 9
-
-| ADAS Combination | LongHaul | LongHaul EMS | Regional Delivery | Regional Delivery EMS | Urban Delivery |
-| ------------------ | ------------- | -------------- | ------------------- | ----------------------- | ---------------- |
-| 1 | -0.1% / 0.0% | 0.0% / 0.0% | -0.5% / -0.4% | -0.3% / -0.2% | |
-| 2 | 0.0% / -0.1% | 0.0% / 0.0% | -0.1% / -0.1% | 0.0% / 0.0% | |
-| 3 | 0.0% / -0.2% | 0.0% / -0.1% | -0.2% / -0.2% | -0.2% / -0.2% | |
-| 4/1 | -0.1% / -0.4% | -0.2% / -0.1% | -0.1% / -0.3% | -0.3% / -0.6% | |
-| 4/2 | -0.1% / -0.6% | -0.3% / -0.3% | -0.2% / -0.5% | -0.5% / -0.9% | |
-| 5 | -0.1% / -0.1% | -0.1% / -0.1% | -0.6% / -0.5% | -0.3% / -0.3% | |
-| 6 | -0.1% / -0.2% | -0.1% / -0.2% | -0.7% / -0.6% | -0.5% / -0.4% | |
-| 7/1 | -0.2% / -0.5% | -0.3% / -0.1% | -0.6% / -0.7% | -0.6% / -0.8% | |
-| 7/2 | -0.2% / -0.6% | -0.3% / -0.4% | -0.7% / -0.9% | -0.8% / -1.1% | |
-| 8/1 | -0.1% / -0.5% | -0.2% / -0.1% | -0.2% / -0.4% | -0.3% / -0.6% | |
-| 8/2 | -0.1% / -0.7% | -0.3% / -0.4% | -0.2% / -0.5% | -0.5% / -0.9% | |
-| 9/1 | -0.1% / -0.6% | -0.3% / -0.2% | -0.3% / -0.5% | -0.4% / -0.7% | |
-| 9/2 | -0.2% / -0.7% | -0.3% / -0.4% | -0.3% / -0.6% | -0.6% / -1.0% | |
-| 10/1 | -0.2% / -0.5% | -0.3% / -0.2% | -0.6% / -0.8% | -0.6% / -0.8% | |
-| 10/2 | -0.2% / -0.7% | -0.3% / -0.4% | -0.7% / -0.9% | -0.8% / -1.1% | |
-| 11/1 | -0.2% / -0.6% | -0.3% / -0.2% | -0.7% / -0.9% | -0.7% / -0.9% | |
-| 11/2 | -0.2% / -0.8% | -0.3% / -0.4% | -0.8% / -1.0% | -0.9% / -1.2% | |
-
-### Vehicle Group 10
-
-| ADAS Combination | LongHaul | LongHaul EMS | Regional Delivery | Regional Delivery EMS | Urban Delivery |
-| ------------------ | ------------- | -------------- | ------------------- | ----------------------- | ---------------- |
-| 1 | -0.1% / 0.0% | 0.0% / 0.0% | -0.4% / -0.3% | -0.3% / -0.2% | |
-| 2 | 0.0% / -0.1% | 0.0% / 0.0% | -0.1% / -0.1% | 0.0% / 0.0% | |
-| 3 | -0.1% / -0.2% | 0.0% / -0.1% | -0.2% / -0.2% | -0.2% / -0.1% | |
-| 4/1 | -0.2% / -0.5% | -0.2% / -0.1% | -0.3% / -0.6% | -0.4% / -0.6% | |
-| 4/2 | -0.2% / -0.7% | -0.3% / -0.4% | -0.4% / -0.9% | -0.6% / -0.9% | |
-| 5 | -0.1% / -0.1% | 0.0% / -0.1% | -0.5% / -0.4% | -0.4% / -0.2% | |
-| 6 | -0.1% / -0.2% | -0.1% / -0.2% | -0.6% / -0.5% | -0.5% / -0.3% | |
-| 7/1 | -0.2% / -0.5% | -0.3% / -0.1% | -0.6% / -1.0% | -0.7% / -0.8% | |
-| 7/2 | -0.3% / -0.7% | -0.4% / -0.4% | -0.8% / -1.3% | -0.9% / -1.1% | |
-| 8/1 | -0.2% / -0.5% | -0.2% / -0.1% | -0.3% / -0.7% | -0.4% / -0.6% | |
-| 8/2 | -0.2% / -0.7% | -0.3% / -0.4% | -0.4% / -1.0% | -0.6% / -0.9% | |
-| 9/1 | -0.2% / -0.6% | -0.3% / -0.2% | -0.4% / -0.8% | -0.5% / -0.7% | |
-| 9/2 | -0.3% / -0.8% | -0.3% / -0.4% | -0.5% / -1.1% | -0.7% / -1.0% | |
-| 10/1 | -0.3% / -0.6% | -0.3% / -0.2% | -0.7% / -1.0% | -0.7% / -0.8% | |
-| 10/2 | -0.3% / -0.8% | -0.4% / -0.4% | -0.8% / -1.3% | -0.9% / -1.1% | |
-| 11/1 | -0.3% / -0.6% | -0.3% / -0.2% | -0.8% / -1.1% | -0.8% / -0.9% | |
-| 11/2 | -0.3% / -0.8% | -0.4% / -0.5% | -0.9% / -1.4% | -1.0% / -1.2% | |
\ No newline at end of file
diff --git a/Documentation/User Manual/3-simulation-models/Vehicle_CrossWindCorrection.md b/Documentation/User Manual/3-simulation-models/Vehicle_CrossWindCorrection.md
index ca6a803661b439ca646ffba4f1e28ca5e15fc630..f5b593c51adb24d97ac0b21e8bc82e4b450613f4 100644
--- a/Documentation/User Manual/3-simulation-models/Vehicle_CrossWindCorrection.md
+++ b/Documentation/User Manual/3-simulation-models/Vehicle_CrossWindCorrection.md
@@ -1,4 +1,4 @@
-##Vehicle: Cross Wind Correction
+## Vehicle: Cross Wind Correction
VECTO offers three different modes to consider cross wind influence on the drag coefficient. It is configured in the [Vehicle File](#vehicle-file-.vveh).
@@ -8,7 +8,7 @@ $F_{aero}=1/2 \rho_{air}(C_{d,v}A(v_{veh})) v_{veh}^2$
The speed dependecy of the $C_dA$ value allows for consideration of average cross widn conditions.
-###Speed dependent correction (Declaration Mode)
+### Speed dependent correction (Declaration Mode)
This is the mode which is used in [Declaration Mode](#declaration-mode).
@@ -54,7 +54,7 @@ $v_{wind} \ldots \text{velocity of ambient wind}$
The generation of the $C_{d,v}A(v_{veh})$ curve is demonstrated in [this Excel sheet](Cdv_Generator_VECTO3.2.xlsx)
-###Speed dependent correction (User-defined)
+### Speed dependent correction (User-defined)
The base C~d~A value (see [Vehicle File](#vehicle-file-.vveh)) is corrected with a user-defined speed dependent scaling function. A [vcdv-File](#speed-dependent-cross-wind-correction-input-file-.vcdv) is needed for this calculation.
The C~d~A value given in the vehicle configuration is corrected depending on the vehicle's speed and the C~d~ scaling factor from the input file as follows:
@@ -64,7 +64,7 @@ $C_dA(v_{veh}) = C_dA * F_Cd(v_{veh})$
-###Correction using Vair & Beta Input
+### Correction using Vair & Beta Input
The actual (measured) air speed and direction can be used to correct cross-wid influence if available. A [vcdb-File](#vair-beta-cross-wind-correction-input-file-.vcdb) is needed for this calculation. This file defines a ΔC~d~A value in \[m²\] depending on the wind angle. The [driving cycle](#driving-cycles-.vdri) must include the air speed relative to the vehicle v~air~ (\<vair\_res\>) and the wind yaw angle (\<vair\_beta\>).
diff --git a/Documentation/User Manual/3-simulation-models/Vehicle_RRC.md b/Documentation/User Manual/3-simulation-models/Vehicle_RRC.md
index 3d02e10bd4466d1988c3558d74dee57186b73e76..6f25a965333aa4bcc8fe2afa415b37d5b4aacc01 100644
--- a/Documentation/User Manual/3-simulation-models/Vehicle_RRC.md
+++ b/Documentation/User Manual/3-simulation-models/Vehicle_RRC.md
@@ -1,4 +1,4 @@
-##Vehicle: Rolling Resistance Coefficient
+## Vehicle: Rolling Resistance Coefficient
The rolling resistance is calculated using a speed-independent rolling resistance coefficient (RRC).
diff --git a/Documentation/User Manual/3-simulation-models/simulation-models.md b/Documentation/User Manual/3-simulation-models/simulation-models.md
index 6e60b45f0686174fb4ffccceb5572202e9ee02db..f878719b92b872a616e83ef0e3557001c718e3c9 100644
--- a/Documentation/User Manual/3-simulation-models/simulation-models.md
+++ b/Documentation/User Manual/3-simulation-models/simulation-models.md
@@ -1,4 +1,4 @@
-#Simulation Models
+# Simulation Models
In this chapter the used component models for the simulation are described.
diff --git a/Documentation/User Manual/3-simulation-models/whr_system.md b/Documentation/User Manual/3-simulation-models/whr_system.md
index 6eb9a6c8065922a5d62266df83f6d6cf7908306b..eae9977ddc8e3d6ea2100de365e5d8aeb359beaf 100644
--- a/Documentation/User Manual/3-simulation-models/whr_system.md
+++ b/Documentation/User Manual/3-simulation-models/whr_system.md
@@ -1,4 +1,4 @@
-##Engine Waste Heat Recovery Systems
+## 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:
diff --git a/Documentation/User Manual/4-command-line-arguments/cmd.md b/Documentation/User Manual/4-command-line-arguments/cmd.md
index ba7aa6de5b2faae6c9fddf115708b02060d7d1d7..92c92e7ad37b26d0efadeea467ee07f861bec1e8 100644
--- a/Documentation/User Manual/4-command-line-arguments/cmd.md
+++ b/Documentation/User Manual/4-command-line-arguments/cmd.md
@@ -1,20 +1,20 @@
-##Command Line Arguments
+## Command Line Arguments
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
diff --git a/Documentation/User Manual/5-input-and-output-files/AALT.md b/Documentation/User Manual/5-input-and-output-files/AALT.md
index f01d550b3d2af8d46d86e19412b32d7259d42cec..64df7c73a40e06d45a3935a564819c15af6500f6 100644
--- a/Documentation/User Manual/5-input-and-output-files/AALT.md
+++ b/Documentation/User Manual/5-input-and-output-files/AALT.md
@@ -1,4 +1,4 @@
-##Alternator Input Data (.aalt)
+## Alternator Input Data (.aalt)
~~~
[AlternatorName],[RPM],[Amps],[Efficiency],[PulleyRatio]
diff --git a/Documentation/User Manual/5-input-and-output-files/AAUX.md b/Documentation/User Manual/5-input-and-output-files/AAUX.md
index 057db8953fa59e27dc21536c62f47d3583c01a4e..d3e84e7735f043ea72fcb91d55e829dbe66c5788 100644
--- a/Documentation/User Manual/5-input-and-output-files/AAUX.md
+++ b/Documentation/User Manual/5-input-and-output-files/AAUX.md
@@ -1,4 +1,4 @@
-##Advanced Auxiliary Input Data (.aaux)
+## Advanced Auxiliary Input Data (.aaux)
**Example: **
diff --git a/Documentation/User Manual/5-input-and-output-files/ACMP.md b/Documentation/User Manual/5-input-and-output-files/ACMP.md
index a5b422cb8f40f7deb050d6165c7cf5217236e56d..e13dfa4ae1ca1a87feedfd6ed358b49277f03819 100644
--- a/Documentation/User Manual/5-input-and-output-files/ACMP.md
+++ b/Documentation/User Manual/5-input-and-output-files/ACMP.md
@@ -1,13 +1,13 @@
-##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:
diff --git a/Documentation/User Manual/5-input-and-output-files/AENV.md b/Documentation/User Manual/5-input-and-output-files/AENV.md
index 914a31ef1ae2b7142df3f857a3a39481023b4a2c..9653a00a55fb5f057f91a3928bff98983dcae204 100644
--- a/Documentation/User Manual/5-input-and-output-files/AENV.md
+++ b/Documentation/User Manual/5-input-and-output-files/AENV.md
@@ -1,13 +1,13 @@
-##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:**
diff --git a/Documentation/User Manual/5-input-and-output-files/APAC.md b/Documentation/User Manual/5-input-and-output-files/APAC.md
index 0486babe70f2e360f6885cca7af7b94895168b0f..061f57a040daabba26f6915db7e77feff9322045 100644
--- a/Documentation/User Manual/5-input-and-output-files/APAC.md
+++ b/Documentation/User Manual/5-input-and-output-files/APAC.md
@@ -1,4 +1,4 @@
-##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:**
diff --git a/Documentation/User Manual/5-input-and-output-files/App.md b/Documentation/User Manual/5-input-and-output-files/App.md
index 7fae53fbacbe777e3394cdd61d65d1d2e6125292..2e87725faee8f60b765dabc5e833b5960954ab09 100644
--- a/Documentation/User Manual/5-input-and-output-files/App.md
+++ b/Documentation/User Manual/5-input-and-output-files/App.md
@@ -1,20 +1,20 @@
-##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).
diff --git a/Documentation/User Manual/5-input-and-output-files/CSV.md b/Documentation/User Manual/5-input-and-output-files/CSV.md
index 144ab62c00907488d87d089e77bc0531d43eeada..c6be2442b7de7223ac1234eba91ab5e559206408 100644
--- a/Documentation/User Manual/5-input-and-output-files/CSV.md
+++ b/Documentation/User Manual/5-input-and-output-files/CSV.md
@@ -1,10 +1,10 @@
-##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
diff --git a/Documentation/User Manual/5-input-and-output-files/JSON.md b/Documentation/User Manual/5-input-and-output-files/JSON.md
index 6bd64523570813c29e008ff689fb90886ea343ff..9c423b290a9abc93687d0888f7226845f7b46fa0 100644
--- a/Documentation/User Manual/5-input-and-output-files/JSON.md
+++ b/Documentation/User Manual/5-input-and-output-files/JSON.md
@@ -1,4 +1,4 @@
-##JSON
+## JSON
Configuration and component files in Vecto use [JSON](http://en.wikipedia.org/wiki/JSON)  as common file format.
Following files use JSON:
diff --git a/Documentation/User Manual/5-input-and-output-files/VACC.md b/Documentation/User Manual/5-input-and-output-files/VACC.md
index 1d527e506ea5a95357ff95a3ac778dd4a76e705b..3524373ef25dd649b2b5dbed9704a5d25a10fded 100644
--- a/Documentation/User Manual/5-input-and-output-files/VACC.md
+++ b/Documentation/User Manual/5-input-and-output-files/VACC.md
@@ -1,4 +1,4 @@
-##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).
diff --git a/Documentation/User Manual/5-input-and-output-files/VAUX.md b/Documentation/User Manual/5-input-and-output-files/VAUX.md
index 23b3f50b6f5275f264f46387ba019ed3390b6049..35ef13fe056197ad0d38ba837a786c3a61891251 100644
--- a/Documentation/User Manual/5-input-and-output-files/VAUX.md
+++ b/Documentation/User Manual/5-input-and-output-files/VAUX.md
@@ -1,4 +1,4 @@
-##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.
diff --git a/Documentation/User Manual/5-input-and-output-files/VCDB.md b/Documentation/User Manual/5-input-and-output-files/VCDB.md
index 7d6303b090ce46fc0d1102095c9b802a22b2bcf6..5c1fbbb334cd5cb8779851715c5f59cd44937c8e 100644
--- a/Documentation/User Manual/5-input-and-output-files/VCDB.md
+++ b/Documentation/User Manual/5-input-and-output-files/VCDB.md
@@ -1,4 +1,4 @@
-##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).
diff --git a/Documentation/User Manual/5-input-and-output-files/VCDV.md b/Documentation/User Manual/5-input-and-output-files/VCDV.md
index b2d03b19637dedfdf2c1ea631f6cb79d97bf407d..22fc03089d761b5c954853c8d2d99897603adf80 100644
--- a/Documentation/User Manual/5-input-and-output-files/VCDV.md
+++ b/Documentation/User Manual/5-input-and-output-files/VCDV.md
@@ -1,4 +1,4 @@
-##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).
diff --git a/Documentation/User Manual/5-input-and-output-files/VDRI.md b/Documentation/User Manual/5-input-and-output-files/VDRI.md
index 6750a7ed54924f87570511e49360037b992b148e..5a8e6e7bfb16924cc0dc6125d6f8d091212e1a25 100644
--- a/Documentation/User Manual/5-input-and-output-files/VDRI.md
+++ b/Documentation/User Manual/5-input-and-output-files/VDRI.md
@@ -1,9 +1,9 @@
-##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.
diff --git a/Documentation/User Manual/5-input-and-output-files/VFLD.md b/Documentation/User Manual/5-input-and-output-files/VFLD.md
index 9e0b18f8d80a5b76c0cbe59491ebb17a3b1f43e6..5a13ea2105583bd7ea903855f31aab87c9d62bd3 100644
--- a/Documentation/User Manual/5-input-and-output-files/VFLD.md
+++ b/Documentation/User Manual/5-input-and-output-files/VFLD.md
@@ -1,4 +1,4 @@
-##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).
diff --git a/Documentation/User Manual/5-input-and-output-files/VGBS.md b/Documentation/User Manual/5-input-and-output-files/VGBS.md
index 75fdb12f8263c28e04a9978b98427e896fd085c8..8874fff9bd0a4dc8d7864ef2a5c974acea22af70 100644
--- a/Documentation/User Manual/5-input-and-output-files/VGBS.md
+++ b/Documentation/User Manual/5-input-and-output-files/VGBS.md
@@ -1,4 +1,4 @@
-##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).
diff --git a/Documentation/User Manual/5-input-and-output-files/VGBX.md b/Documentation/User Manual/5-input-and-output-files/VGBX.md
index a763a13634fc5748ea26c52f611ca2a1901ac414..81368e1cc54fcb5aea65ec063001cb8e3da136d9 100644
--- a/Documentation/User Manual/5-input-and-output-files/VGBX.md
+++ b/Documentation/User Manual/5-input-and-output-files/VGBX.md
@@ -1,4 +1,4 @@
-##Gearbox File (.vgbx)
+## Gearbox File (.vgbx)
File for the definition of a gearbox in Vecto. Can be created with the [Gearbox Editor](#gearbox-editor).
diff --git a/Documentation/User Manual/5-input-and-output-files/VMAP.md b/Documentation/User Manual/5-input-and-output-files/VMAP.md
index 832db75b0e1474768c85893736d585346cda14da..b909804c32d41235fda6bb7a7a2a66fb38014932 100644
--- a/Documentation/User Manual/5-input-and-output-files/VMAP.md
+++ b/Documentation/User Manual/5-input-and-output-files/VMAP.md
@@ -1,4 +1,4 @@
-##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).
diff --git a/Documentation/User Manual/5-input-and-output-files/VMOD.md b/Documentation/User Manual/5-input-and-output-files/VMOD.md
index cc9d25962de4f17c26768371abffc4e2332ed70e..86d28c9775fa2a1f177688d4553f0e439d3372fe 100644
--- a/Documentation/User Manual/5-input-and-output-files/VMOD.md
+++ b/Documentation/User Manual/5-input-and-output-files/VMOD.md
@@ -1,4 +1,4 @@
-##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.
diff --git a/Documentation/User Manual/5-input-and-output-files/VPTOC.md b/Documentation/User Manual/5-input-and-output-files/VPTOC.md
index e089faa0d6d6a35f28f280ff5b6e651572484c5b..8e142a2fc9b675fa914b24225e40daed77ea9022 100644
--- a/Documentation/User Manual/5-input-and-output-files/VPTOC.md
+++ b/Documentation/User Manual/5-input-and-output-files/VPTOC.md
@@ -1,4 +1,4 @@
-##PTO Cycle (.vptoc)
+## PTO Cycle (.vptoc)
The PTO cycle defines the power demands during standing still and doing a pto operation. This can only be used in [Engineering Mode](#engineering-mode) when a pto transmission is defined. It can be set in the [Vehicle-Editor](#vehicle-editor). The basic file format is [Vecto-CSV](#csv) and the file type ending is ".vptoc". A PTO cycle is time-based and may have variable time steps, but it is recommended to use a resolution between 1[Hz] and 2[Hz]. Regardless of starting time, VECTO shifts it to always begin at 0[s].
diff --git a/Documentation/User Manual/5-input-and-output-files/VPTOI.md b/Documentation/User Manual/5-input-and-output-files/VPTOI.md
index 2dab33ed21c98d4ed3ce74303c490cb4c920c3ed..2c6a15b97d29f28e191372f1957d9040c64328ab 100644
--- a/Documentation/User Manual/5-input-and-output-files/VPTOI.md
+++ b/Documentation/User Manual/5-input-and-output-files/VPTOI.md
@@ -1,4 +1,4 @@
-##PTO Idle Consumption Map (.vptoi)
+## PTO Idle Consumption Map (.vptoi)
The pto idle consumption map defines the speed-dependent power demand when the pto cycle is not active. This is only be used in [Engineering Mode](#engineering-mode) when a pto transmission is defined.
The exact demand is interpolated based on the engine speed. PTO consumer idling losses are added to engine loads during any parts of the vehicle operation except the "PTO cycle". It can be defined in the [Vehicle-File](#vehicle-file-.vveh) and set via the [Vehicle-Editor](#vehicle-editor).
diff --git a/Documentation/User Manual/5-input-and-output-files/VPTOR.md b/Documentation/User Manual/5-input-and-output-files/VPTOR.md
index f25f147b93dc4fb229357ddd812af3fa07da6343..2573daf2153b161432d1627a36e404ab6a842737 100644
--- a/Documentation/User Manual/5-input-and-output-files/VPTOR.md
+++ b/Documentation/User Manual/5-input-and-output-files/VPTOR.md
@@ -1,4 +1,4 @@
-##PTO power demand during drive (.vptor)
+## PTO power demand during drive (.vptor)
**Example:**
diff --git a/Documentation/User Manual/5-input-and-output-files/VRLM.md b/Documentation/User Manual/5-input-and-output-files/VRLM.md
index 3e8767f03ddc748ad46557a7a07b743358daf658..be7e1a1df57fc0ccc4763cb53fb9b6aa32310bc7 100644
--- a/Documentation/User Manual/5-input-and-output-files/VRLM.md
+++ b/Documentation/User Manual/5-input-and-output-files/VRLM.md
@@ -1,4 +1,4 @@
-##Retarder Loss Torque Input File (.vrlm)
+## Retarder Loss Torque Input File (.vrlm)
This file is used to define retarder idling losses. It can be used for primary and secondary retarders and must be set in the [Vehicle File](#vehicle-editor). The file uses the [VECTO CSV format](#csv).
- Filetype: .vrlm
diff --git a/Documentation/User Manual/5-input-and-output-files/VSUM.md b/Documentation/User Manual/5-input-and-output-files/VSUM.md
index 4a64d633d27d8acf5d071b4ba0db3bdc6e065d4a..cb561f21b051991614e4c6e2b32e83403b0d3c1f 100644
--- a/Documentation/User Manual/5-input-and-output-files/VSUM.md
+++ b/Documentation/User Manual/5-input-and-output-files/VSUM.md
@@ -1,4 +1,4 @@
-##Summary Results (.vsum)
+## Summary Results (.vsum)
The .vsum file includes total / average results for each calculation run in one execution (ie. click of [START Button](#main-form)). The file is located in the directory of the fist run .vecto file.
***Quantities:***
diff --git a/Documentation/User Manual/5-input-and-output-files/VTCC.md b/Documentation/User Manual/5-input-and-output-files/VTCC.md
index b2c685c1d2aceb69b77f04ed0f0dac118e44c298..3ef3793a952e18006d4873d2f9b9f7b677412880 100644
--- a/Documentation/User Manual/5-input-and-output-files/VTCC.md
+++ b/Documentation/User Manual/5-input-and-output-files/VTCC.md
@@ -1,4 +1,4 @@
-##Torque Converter Characteristics (.vtcc)
+## Torque Converter Characteristics (.vtcc)
The file uses the [VECTO CSV format](#csv).
diff --git a/Documentation/User Manual/5-input-and-output-files/VTLM.md b/Documentation/User Manual/5-input-and-output-files/VTLM.md
index 6c3993889e30ad4bca8c3a55f7b0fe4771a4f0cc..cc7632cf659b44078eadfe5703af25b83e6292fb 100644
--- a/Documentation/User Manual/5-input-and-output-files/VTLM.md
+++ b/Documentation/User Manual/5-input-and-output-files/VTLM.md
@@ -1,4 +1,4 @@
-##Transmission Loss Map (.vtlm)
+## Transmission Loss Map (.vtlm)
This file defines losses in transmission components, i.e. every gear, axlegear, angledrive. See [Transmission Losses] (#transmission-losses) for the formula how the losses are accounted in the components. The file uses the [VECTO CSV format](#csv).
@@ -21,7 +21,7 @@ Input Speed [rpm],Input Torque [Nm],Torque Loss [Nm]
~~~
-####Sign of torque values
+#### Sign of torque values
* Input Torque >0 means normal driving operation.
* Input Torque \<0 means motoring operation. **The Torque Loss Map must include negative torque values for engine motoring operation!**
diff --git a/Documentation/User Manual/5-input-and-output-files/VVEH.md b/Documentation/User Manual/5-input-and-output-files/VVEH.md
index 081da56023e22a7dbba17647e4dcb16138f62df2..b9a73a0d6b3398921dac1cca2687cc6423c38c8e 100644
--- a/Documentation/User Manual/5-input-and-output-files/VVEH.md
+++ b/Documentation/User Manual/5-input-and-output-files/VVEH.md
@@ -1,4 +1,4 @@
-##Vehicle File (.vveh)
+## Vehicle File (.vveh)
File for the definition of a vehicle in vecto. Can be created with the [Vehicle Editor](#vehicle-editor).
diff --git a/Documentation/User Manual/5-input-and-output-files/XML_DeclarationReport.md b/Documentation/User Manual/5-input-and-output-files/XML_DeclarationReport.md
index 103166703c8f627031273853eaf276534a747c13..8f0e18722c8d9152739b26d128f3d98c3e49efca 100644
--- a/Documentation/User Manual/5-input-and-output-files/XML_DeclarationReport.md
+++ b/Documentation/User Manual/5-input-and-output-files/XML_DeclarationReport.md
@@ -1,4 +1,4 @@
-##XML Declaration Report
+## XML Declaration Report
<div class="declaration">
In Declaration Mode VECTO generates two reports according to the Technical Annex for vehicle certification:
diff --git a/Documentation/User Manual/5-input-and-output-files/XML_Job-File_DeclarationMode.md b/Documentation/User Manual/5-input-and-output-files/XML_Job-File_DeclarationMode.md
index c468c83d977ed520f64dabe35d7e48ec0dc88779..5c74fea8dfb03cca06a751d96a26378bac597bd1 100644
--- a/Documentation/User Manual/5-input-and-output-files/XML_Job-File_DeclarationMode.md
+++ b/Documentation/User Manual/5-input-and-output-files/XML_Job-File_DeclarationMode.md
@@ -1,4 +1,4 @@
-##XML Job-File (Declaration Mode)
+## XML Job-File (Declaration Mode)
<div class="declaration">
For vehicle certification the input data (vehicle data) has to be provided in XML format. Please see the following resources for more information:
diff --git a/Documentation/User Manual/5-input-and-output-files/input-output.md b/Documentation/User Manual/5-input-and-output-files/input-output.md
index c4593e1c933cae9c5699520cd60dc4aeb9fafc3a..8cc55af44a5c7de8810dc8f60699e1636dcf665c 100644
--- a/Documentation/User Manual/5-input-and-output-files/input-output.md
+++ b/Documentation/User Manual/5-input-and-output-files/input-output.md
@@ -1,4 +1,4 @@
-#Input and Output
+# Input and Output
Vecto uses data files for input and output of data. These are stored in different formats which are listed here.
diff --git a/Documentation/User Manual/6-changelog/changelog.md b/Documentation/User Manual/6-changelog/changelog.md
index ed1d6e99c917b32b07e066706b8cbf7ae015df8a..f1ff844d92f572b4e262e4b2627802f3d851ee8c 100644
--- a/Documentation/User Manual/6-changelog/changelog.md
+++ b/Documentation/User Manual/6-changelog/changelog.md
@@ -1,4 +1,4 @@
-#Changelog
+# Changelog
**VECTO-3.3.11**