update markown files to have space after the headings-marker

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.
 

Documentation/User Manual/1-user-interface/B_mainform.md

-##Main Form
+## Main Form
 
 
 
 ![](pics/mainform.svg)
 
 
-###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).
 
 ![up](pics/Actions-arrow-up-icon.png)![down](pics/Actions-arrow-down-icon.png) ***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](pics/Play-icon.png) ***START Button***
+#### ![START](pics/Play-icon.png) ***START Button***
 
 Start VECTO in the selected mode (see [Options](#options-tab)).
 
 
 
-###Options Tab
+### Options Tab
 
 ![](pics/VECTO_OptionsTab.png)
 
@@ -89,7 +89,7 @@ Output values in vmod at beginning and end of simulation iterval
 ![](pics/VECTO_vmod_vgl.png)
 
 
-###Controls
+### Controls
 
 ![new](pics/blue-document-icon.png) New Job File
 : Create a new .vecto file using the [VECTO Editor](#job-editor)

Documentation/User Manual/1-user-interface/C_settings.md

-##Settings
+## Settings
 
 
 ![](pics/Settings.PNG)
 
 
-###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![](pics/external-icon%2012x12.png)](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

Documentation/User Manual/1-user-interface/D1_VECTO-Job-Editor.md

-##Job Editor
+## Job Editor
 
 
 ![](pics/VECTO-Editor.png)
 
 
-###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
 
 ![](pics/checkbox.png) Engine Only Mode
 
@@ -73,7 +73,7 @@ Cycles
 : ![remcycle](pics/minus-circle-icon.png) Remove the selected cycle from the list
 
 
-###Driver Assist Tab
+### Driver Assist Tab
 
 ![](pics/VECTO-Editor-DriverAssist.png)
 
@@ -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](pics/blue-document-icon.png) New Job File
 :	Create a new empty .vecto file

Documentation/User Manual/1-user-interface/D2_VTP-Job-Editor.md

-##VTP-Job Editor
+## VTP-Job Editor
 
 
 ![](pics/VTP-Job.png)
 
 
-###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](pics/blue-document-icon.png) New Job File
 :	Create a new empty .vecto file

Documentation/User Manual/1-user-interface/E_VECTO-Editor_Aux.md

-##Auxiliary Dialog
+## Auxiliary Dialog
 
 
 
@@ -12,12 +12,12 @@
 ![Auxiliary Dialog (Engineering Mode)](pics/VECTO-Editor_Aux_ENG.jpg)
 </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
 
 
 ![ok](pics/OK.png) ***Save and close***

Documentation/User Manual/1-user-interface/F_VEH-Editor.md

-##Vehicle Editor
+## Vehicle Editor
 
 ![](pics/VEH-Editor.PNG)
 
-###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
 
 
 ![](pics/blue-document-icon.png) New file

Documentation/User Manual/1-user-interface/G_ENG-Editor.md

-##Engine Editor
+## Engine Editor
 
 ![](pics/ENG-Editor.PNG)
 
-###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](pics/blue-document-icon.png)New file

Documentation/User Manual/1-user-interface/H_GBX-Editor.md

-##Gearbox Editor
+## Gearbox Editor
 
 
 
 ![](pics/GBX-Editor.PNG)
 
 
-###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 ![add](pics/plus-circle-icon.png) and ![remove](pics/minus-circle-icon.png) buttons to add or remove gears from the vehicle. Doubleclick entries to edit existing gears.
 
@@ -56,7 +56,7 @@ Use the ![add](pics/plus-circle-icon.png) 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
 
 
 

Documentation/User Manual/1-user-interface/I_Graph.md

-##Graph Window
+## Graph Window
 
 
 ![](pics/Graph.svg)
 
 
-###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 ![add](pics/plus-circle-icon.png) and ![remove](pics/minus-circle-icon.png) buttons to add or remove channels. Doubleclick entries to edit existing channels.
@@ -20,7 +20,7 @@ Use the ![add](pics/plus-circle-icon.png) and ![remove](pics/minus-circle-icon.p
 Each channel can be plotted either on the left or on the right Y Axis. Use the checkbox to disable channels in the graph.
 
 
-###X Axis Controls
+### X Axis Controls
 
 
 The X Axis can either show distance or time.
@@ -38,7 +38,7 @@ Reset button
 :   Move the x axis range left/right.
 
 
-###Controls
+### Controls
 
 ![open](pics/Open-icon.png) ***Open a .vmod file***
 

Documentation/User Manual/1-user-interface/K0_VECTO-AdvancedAux.md

-##Advanced Auxiliary Dialog
+## Advanced Auxiliary Dialog
 
 <div class="engineering">
 
 
 ![](pics/VECTO-Editor_AAUX.png)
 
-###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.
 

Documentation/User Manual/1-user-interface/K1_VECTO-AdvancedAux_EL.md

-##Electrical Auxiliaries Editor
+## Electrical Auxiliaries Editor
  
 ![](pics/AA_Electrics.jpg)
  
-###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.
 

Documentation/User Manual/1-user-interface/K2_VECTO-AdvancedAux_EL-ALT.md

-##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
 ![](pics/CombAltSchem.png)
 
 
-###File Format
+### File Format
 
 The file uses the VECTO CSV format.
 

Documentation/User Manual/1-user-interface/K3_VECTO-AdvancedAux_PNEU.md

-##Pneumatic Auxiliaries Editor
+## Pneumatic Auxiliaries Editor
  
 
 ![](pics/AA_Pneumatics.jpg)
  
-###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.
 

Documentation/User Manual/1-user-interface/K4_VECTO-AdvancedAux_HVAC.md

-##HVAC Auxiliaries Editor
+## HVAC Auxiliaries Editor
  
 ![](pics/AA_HVAC.jpg)
 
-###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
 
 ![](pics/HVAC_BusParameters.jpg)
 
@@ -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
 
 ![](pics/HVAC_BoundaryConditions.jpg)
 
 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
 
 ![](pics/HVAC_Other.jpg)
 
@@ -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
 
 ![](pics/HVAC_TechList.jpg)
 
@@ -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.
 

Documentation/User Manual/2-calculation-modes/calculation-modes.md

-#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.
 

Documentation/User Manual/2-calculation-modes/declaration.md

-##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.

Documentation/User Manual/2-calculation-modes/engine-only.md

-##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:
 

Documentation/User Manual/2-calculation-modes/engineering.md

-##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)

Documentation/User Manual/2-calculation-modes/verification-test.md

-##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