Merge pull request #492 in VECTO/vecto-sim from...

Merge pull request #492 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-548-online-user-manual to master

* commit 'b809e697':
  extending release checklist
  update js-function for checking internal links
  corrected dead links
  adding script to check dead internal links

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

@@ -30,7 +30,7 @@ VECTO automatically uses relative paths if the input file (e.g. Vehicle File) is
 :	Enables [Engine Only Mode](#engine-only-mode) (Engineering mode only). The following parameters are needed for this mode:
 
 -   Filepath to the [Engine File (.veng)](#engine-editor)
--   [Driving Cycles](#driving-cycles) including engine torque (or power) and engine speed
+-   [Driving Cycles](#driving-cycles-.vdri) including engine torque (or power) and engine speed
 
 
 Filepath to the Vehicle File (.vveh)
@@ -56,7 +56,7 @@ Auxiliaries
 First, the Auxiliary Type can be selected. If the Bus Auxiliaries are selected a configuration file for the Advanced Auxiliaries has to be specified. When using the Bus Auxiliaries, the standard auxiliaries can  be added as well in the list below to take into account the steering pump, etc.
 The 'Constant Aux Load' can be used to define a constant power demand from the auxiliaries (similar to P_add in the driving cycle, but constant over the whole cycle).
 The following list can be used to define the auxiliary load in more detail via a separate input file. The auxiliaries are configured using the [Auxiliary Dialog](#auxiliary-dialog). 
- For each auxiliary an [Auxiliary Input File (.vaux)](#auxiliary-input-file-.vaux) must be provided and the [driving cycle](#driving-cycles) must include the corresponding supply power.
+ For each auxiliary an [Auxiliary Input File (.vaux)](#auxiliary-input-file-.vaux) must be provided and the [driving cycle](#driving-cycles-.vdri) must include the corresponding supply power.
 **Double-click** entries to edit with the [Auxiliary Dialog](#auxiliary-dialog).
 : ![addaux](pics/plus-circle-icon.png) Add new Auxiliary
 : ![remaux](pics/minus-circle-icon.png) Remove the selected Auxiliary from the list
@@ -65,7 +65,7 @@ The following list can be used to define the auxiliary load in more detail via a
 See [Auxiliaries](#auxiliaries) for details.
 
 Cycles
-:	List of cycles used for calculation. The .vdri format is described [here](#driving-cycles).
+:	List of cycles used for calculation. The .vdri format is described [here](#driving-cycles-.vdri).
 **Double-click** an entry to open the file (see [File Open Command](#settings)).
 **Click** selected items to edit file paths.
 
@@ -80,22 +80,19 @@ Cycles
 
 In this tab the driver assistance functions are enabled and parameterised.
 
-Engine Start/Stop
-:	See [Engine Start/Stop](#engine-startstop) for details.
-
 Overspeed
 :	See [Overspeed](#overspeed) for details.
 
 Look-Ahead Coasting
-:	See [Look-Ahead Coasting](#look-ahead-coasting) for details.
+:	See [Look-Ahead Coasting](#driver-look-ahead-coasting) for details.
 
 Acceleration Limiting
-:	See [Acceleration Limiting](#acceleration-limiting) for details.
+:	See [Acceleration Limiting](#driver-acceleration-limiting) for details.
 
 
 ###Chart Area
 
-If a valid [Vehicle File](#vehicle-editor), [Engine File](#engine-file) and [Gearbox File](#gearbox-file) is loaded into the Editor the main vehicle parameters like HDV class and axle configuration are shown here. The plot shows the full load curve(s) and sampling points of the fuel consumption map. 
+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 class and axle configuration are shown here. The plot shows the full load curve(s) and sampling points of the fuel consumption map. 
 
 ###Controls
 

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

@@ -4,7 +4,7 @@
 
 ###Description
 
-The [Vehicle File (.vveh)](#vehicle-file) defines the main vehicle/chassis parameters like axles including [RRC](#rolling-resistance-coefficient)s, air resistance and weight.
+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 weight.
 
 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.
 
@@ -53,7 +53,7 @@ In Declaration Mode only the vehicle itself needs to be specified. Depending on
 ###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**](#cross-wind-correction).**
+**Note that the Air Drag depends on the chosen [**Cross Wind Correction**](#vehicle-cross-wind-correction).**
 
 <div class="declaration">
 If the vehicle has attached a trailer for simulating certain missions the given **c~d~ x A** value is increased by a fixed amount depending on the trailer used for the given vehicle category.
@@ -69,7 +69,7 @@ For cross wind correction four different options are available:
 In delcaration mode the 'Speed dependent (Declaration Mode)' cross-wind correction is used.
 </div>
 
-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](#cross-wind-correction).
+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
 
@@ -78,7 +78,7 @@ In [Engineering Mode](#engineering-mode) this defines the effective (dynamic) wh
 
 ###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](#rolling-resistance-coefficient).
+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).
 
 <div class="engineering">
 In Engineering mode, the **Wheels Inertia [kgm²]** has to be set per wheel for each axle.
@@ -103,7 +103,7 @@ If a separate retarder is used in the vehicle a **Retarder Torque Loss Map** can
 
 Four options are available:
 : -   No retarder
--	Included in Transmission Loss Maps: Use this if the [Transmission Loss Maps](#transmission-loss-map) already include retarder losses.
+-	Included in Transmission Loss Maps: Use this if the [Transmission Loss Maps](#transmission-loss-map-.vtlm) already include retarder losses.
 -   Primary Retarder (before gearbox): The rpm ratio is relative to the engine speed
 -   Secondary Retarder (after gearbox): The rpm ratio is relative to the cardan shaft speed
 
@@ -117,7 +117,7 @@ If an angledrive is used in the vehicle, it can be defined here.
 Three options are available:
 
 - None (**default**)
-- Separate Angledrive: Use this if the angledrive is measured separately. In this case the ratio must be set and the [Transmission Loss Map](#transmission-loss-map) (or an Efficiency value in Engineering mode) must also be given.
+- Separate Angledrive: Use this if the angledrive is measured separately. In this case the ratio must be set and the [Transmission Loss Map](#transmission-loss-map-.vtlm) (or an Efficiency value in Engineering mode) must also be given.
 - Included in transmission: Use this if the gearbox already includes the transmission losses for the angledrive in the respective transmission loss maps.
 
 

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

@@ -4,7 +4,7 @@
 
 ###Description
 
-The [Engine File (.veng)](#engine-file) defines all engine-related parameters and input files like Fuel Consumption Map and Full Load Curve.
+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
 
@@ -35,14 +35,14 @@ The [Engine's Full Load and Drag Curves (.vfld)](#full-load-and-drag-curves-.vfl
 ###Fuel Consumption Map
 
 
-The [Fuel Consumption Map](#fuel-consumption-map-.vmap) is used to calculate the base FC value. See [Fuel Consumption Calculation](#fuel-consumption-calculation) for details.
+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
 
 <div class="declaration">
-The WHTC Correction Factors are required in [Declaration Mode](#declaration-mode) for the [WHTC FC Correction](#fuel-consumption-calculation).
+The WHTC Correction Factors are required in [Declaration Mode](#declaration-mode) for the [WHTC FC Correction](#engine-fuel-consumption-calculation).
 
 The Cold/Hot Emission Balancing Factor is an additional correction factor that is used to correct the fuel consumption.
 </div>

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

@@ -9,7 +9,7 @@
 
 
 
-The [Gearbox File (.vgbx)](#gearbox-file) defines alls gearbox-related input parameters like gear ratios and transmission loss maps. See [Gear Shift Model](#gear-shift-model) for details.
+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
@@ -35,7 +35,7 @@ Transmission Type
 :	Note: The types AT and Custom are not available in [Declaration Mode](#declaration-mode).
 
 
-For more details on the automatic transmission please see the [AT-Model](#at-gearbox-model)
+For more details on the automatic transmission please see the [AT-Model](#gearbox-at-gearbox-model)
 
 Inertia \[kgm²\]
 :   Rotational inertia of the gearbox (constant for all gears). (Engineering mode only)
@@ -51,9 +51,9 @@ Use the ![add](pics/plus-circle-icon.png) and ![remove](pics/minus-circle-icon.p
 
 -   Gear **"Axle"** defines the ratio of the axle transmission / differential.
 -    **"Ratio"** defines the ratio between the output speed and input speed for the current gear. Must be greater than 0.
--    **"Loss Map or Efficiency"** allows to define either a constant efficiency value or a [loss map (.vtlm)](#transmission-loss-map). <span class="engineering">Note: efficiency values are only allowed in engineering mode</span>
--    **"Shift polygons"** defines the [Shift Polygons InputFile (.vgbs)](#shift-polygons-input-file-.vgbs) for each gear. Not allowed in [Declaration Mode](#declaration-mode). See [GearShift Model](#gear-shift-model) for details.
--	 **"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](#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](#gear-shift-model)!
+-    **"Loss Map or Efficiency"** allows to define either a constant efficiency value or a [loss map (.vtlm)](#transmission-loss-map-.vtlm). <span class="engineering">Note: efficiency values are only allowed in engineering mode</span>
+-    **"Shift polygons"** defines the [Shift Polygons InputFile (.vgbs)](#shift-polygons-input-file-.vgbs) for each gear. Not allowed in [Declaration Mode](#declaration-mode). See [GearShift Model](#gearbox-gear-shift-model) for details.
+-	 **"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
@@ -118,7 +118,7 @@ Max. Speed
 :   Defines the maximum input speed the torque converter can handle.
 
 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](#gear-shift-rules-for-at-gearbox).
+:   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

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

@@ -17,7 +17,7 @@ In this mode the given list of job files is simulated with the respective drivin
 
 
 ###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).
+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)
 :   This option is the a target vehicle speed distance based cycle (like in Declaration Mode). With this option experiments can be made by the manufacturer.

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

@@ -29,7 +29,7 @@ For each auxiliary the power demand is calculated using the following steps:
 | n~Eng~     | Calculated engine speed.                                                                            | \[1/min\]                       |  
 | TransRatio | Speed ratio between auxiliary and engine. [Defined in the Auxiliary File](#auxiliary-input-file-.vaux). | \[-\]                           |  
 | n~aux~     | Auxiliary speed                                                                                     | \[1/min\]                       |  
-| P~supply~  | Effective supply power demand. [Defined in the driving cycle](#driving-cycles).             | \[kW\]                          |  
+| P~supply~  | Effective supply power demand. [Defined in the driving cycle](#driving-cycles-.vdri).             | \[kW\]                          |  
 | EffToSply  | Consumer efficiency. [Defined in the Auxiliary File](#auxiliary-input-file-.vaux).                      | \[-\]                           |  
 | P~auxOut~  | Auxiliary output power                                                                              | \[kW\]                          |  
 | EffMap     | Auxiliary efficiency map. [Defined in the Auxiliary File](#auxiliary-input-file-.vaux).                 | \[kW\] = f( \[1/min\], \[kW\] ) |  
@@ -41,7 +41,7 @@ For each auxiliary the power demand is calculated using the following steps:
 
 
 
-Each auxiliary must be defined in the [Job File](#job-file) and each [driving cycle](#driving-cycles) used with this vehicle/auxiliary must include supply power for each auxiliary. To link the supply power in the driving cycle to the correct auxiliary in the Job File an ID is used. The corresponding supply power is then named *"<Aux\_ID>"*.
+Each auxiliary must be defined in the [Job File](#job-file) and each [driving cycle](#driving-cycles-.vdri) used with this vehicle/auxiliary must include supply power for each auxiliary. To link the supply power in the driving cycle to the correct auxiliary in the Job File an ID is used. The corresponding supply power is then named *"<Aux\_ID>"*.
 
 
 ***Example:*** *The Auxiliary with the ID "ALT" (in the Job File) is linked to the supply power in the column "<Aux\_ALT>" in the driving cylce.*

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

 ##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](#acceleration-limiting).
+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).
 
  ![](pics/LookAheadCoasting.svg)
 
 At the resulting deceleration start point the model calculates the
-coasting trajectory until it meets the brake deceleration trajectory. The resulting deceleration consists of a coasting phase followed by combined mechanical/engine braking. If Look-Ahead Coasting is disabled only the braking phase according to the [deceleration limit](#acceleration-limiting) will be applied.
+coasting trajectory until it meets the brake deceleration trajectory. The resulting deceleration consists of a coasting phase followed by combined mechanical/engine braking. If Look-Ahead Coasting is disabled only the braking phase according to the [deceleration limit](#driver-acceleration-limiting) will be applied.
 
 Since Vecto 3.0.4 the coasting strategy according to the ACEA White Book 2016 is implemented. 
 

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

@@ -13,7 +13,7 @@ The total correction factor CF~total~ depends on the mission profile and is prod
 
 $CF_{total} = CF_{urb} \cdot WF_{urb} + CF_{rur} \cdot WF_{rur} + CF_{mot} \cdot WF_{mot}$
 
-with the correction factor CF~urb~, CF~rur~, CF~mot~ coming from the [Engine](#engine-file), and weighting factors WF~urb~, WF~rur~, WF~mot~ predefined in the declaration data:
+with the correction factor CF~urb~, CF~rur~, CF~mot~ coming from the [Engine](#engine-file-.veng), and weighting factors WF~urb~, WF~rur~, WF~mot~ predefined in the declaration data:
 
 |  Mission profile   | WF~urb~ | WF~rur~ | WF~mot~ |
 |--------------------|---------|---------|---------|

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

@@ -19,9 +19,9 @@ The Gear Shift Model is based on shift curves that define the engine speed for u
 
 
 
-The shift polygons are saved in the [Shift Polygons Input File (.vgbs)](#shift-polygons-input-file-.vgbs) and have to be added to the [Gearbox File](#gearbox-file) when not in [Declaration Mode](#declaration-mode).
+The shift polygons are saved in the [Shift Polygons Input File (.vgbs)](#shift-polygons-input-file-.vgbs) and have to be added to the [Gearbox File](#gearbox-file-.vgbx) when not in [Declaration Mode](#declaration-mode).
 
-In [Declaration Mode](#declaration-mode) the generic shift polygons are computed from the engine's full-load curve. If the maximum torque is limited by the gearbox, the minimum of the current gear and engine maximum torque will be used to compute the [generic shift polygons](#gear-shift-model). Note: the computation of the shift polygons uses characteristic values from the engine such as n~95h~, n~pref~, etc. which are also derived from the full-load curve.
+In [Declaration Mode](#declaration-mode) the generic shift polygons are computed from the engine's full-load curve. If the maximum torque is limited by the gearbox, the minimum of the current gear and engine maximum torque will be used to compute the [generic shift polygons](#gearbox-gear-shift-model). Note: the computation of the shift polygons uses characteristic values from the engine such as n~95h~, n~pref~, etc. which are also derived from the full-load curve.
 
 
 In the Gearbox File two additional parameters are defined:

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

@@ -4,7 +4,7 @@ For verification tasks it is possible to manually input the power at wheels (P~w
 
 ###Requirements
 
-- Driving Cycle must include t, P~wheel~ (Pwheel), Gear (Gear) and Engine Speed (n), see [Driving Cycle (.vdri) format](#driving-cycles).
+- 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.
 
 

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

@@ -50,6 +50,6 @@ In engineering mode the drag points for the torque converter can be specified. I
 If the torque converter characteristics for drag are not specified, the generic points are appended as described above for declaration mode.
 </div>
 
-The torque converter has a separate [Shift Polygon](#shift-polygon-file-.vgbs) which defines the conditions for switching from torque converter gear to locked gear.
+The torque converter has a separate [Shift Polygon](#shift-polygons-input-file-.vgbs) which defines the conditions for switching from torque converter gear to locked gear.
 
 

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

 ##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).
+VECTO offers three different modes to consider cross wind influence on the drag coefficient. It is configured in the [Vehicle File](#vehicle-file-.vveh).
 The aerodymanic force is calculated according to the following equation:
 
 $F_{aero}=1/2 \rho_{air}(C_{d,v}A(v_{veh})) v_{veh}^2$
@@ -55,7 +55,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)
-The base C~d~A value (see [Vehicle File](#vehicle-file)) 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 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:
 
@@ -66,7 +66,7 @@ $C_dA(v_{veh}) = C_dA * F_C_d(v_{veh})$
 
 ###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) must include the air speed relative to the vehicle v~air~ (\<vair\_res\>) and the wind yaw angle (\<vair\_beta\>).
+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\>).
 
 The C~d~A value given in the vehicle configuration is corrected depending on the wind speed and wind angle (given in the driving cycle) using the input file as follows:
 

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

@@ -11,10 +11,10 @@ with:
 |             |        |                                                                                                                  |                            |
 | ----------- | ------ | ---------------------------------------------------------------------------------------------------------------- | -------------------------- |
 | RRC         | [-]    | Total rolling resistance coefficient used for calculation                                                        | [calculated]               |
-| s~(i)~      | [-]    | Relative axle load. Defined in the [Vehicle File](#vehicle-file).                                                | [user input]               |
-| RRC~ISO(i)~ | [-]    | ...Tyre RRC according to ISO 28580. Defined in the [Vehicle File](#vehicle-file).                                | [user input]               |
-| w~(i)~      | [-]    | Number of tyres (4 if Twin Tyres, else 2). Defined in the [Vehicle File](#vehicle-file).                         | [user input]               |
-| F~zISO(i)~  | [N]    | Tyre test load according to ISO 28580 (85% of max. load capacity). Defined in the [Vehicle File](#vehicle-file). | [user input]               |
+| s~(i)~      | [-]    | Relative axle load. Defined in the [Vehicle File](#vehicle-file-.vveh).                                                | [user input]               |
+| RRC~ISO(i)~ | [-]    | ...Tyre RRC according to ISO 28580. Defined in the [Vehicle File](#vehicle-file-.vveh).                                | [user input]               |
+| w~(i)~      | [-]    | Number of tyres (4 if Twin Tyres, else 2). Defined in the [Vehicle File](#vehicle-file-.vveh).                         | [user input]               |
+| F~zISO(i)~  | [N]    | Tyre test load according to ISO 28580 (85% of max. load capacity). Defined in the [Vehicle File](#vehicle-file-.vveh). | [user input]               |
 | m           | [kg]   | Vehicle mass plus loading.                                                                                       | [calculated]               |
 | g           | [m/s²] | Earth gravity acceleration (constant = 9.81, Vecto 3.x: 9.80665)                                                 | [constant model parameter] |
 | β           | [-]    | Constant parameter = 0.9                                                                                         | [constant model parameter] |

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

@@ -8,14 +8,13 @@ In this chapter the used component models for the simulation are described.
 * [ADAS: Overspeed](#driver-overspeed)
 * [Vehicle: Cross Wind Correction](#vehicle-cross-wind-correction)
 * [Vehicle: Rolling Resistance Coefficient](#vehicle-rolling-resistance-coefficient)
-* [Engine Start/Stop](#engine-startstop)
 * [Engine: Fuel Consumption Calculation](#engine-fuel-consumption-calculation)
 * [Engine: Transient Full Load](#engine-transient-full-load)
 * [Engine: WHTC Correction Factors](#engine-correction-factors)
 * [Engine Torque and Engine Speed Limitations](#engine-torque-and-engine-speed-limitations)
 * [Gearbox: Gear Shift Model](#gearbox-gear-shift-model)
-* [Gearbox: MT and AMT Gearshift Rules](#gearbox-mt-and-amt-gear-shift-rules)
-* [Gearbox: AT Gearshift Rules](#gearbox-at-gear-shift-rules)
+* [Gearbox: MT and AMT Gearshift Rules](#gearbox-mt-and-amt-gearshift-rules)
+* [Gearbox: AT Gearshift Rules](#gearbox-at-gearshift-rules)
 * [Torque Converter Model](#torque-converter-model)
 * [Auxiliaries](#auxiliaries)
 * [Engine Only Mode](#engine-only-mode)

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

@@ -30,10 +30,10 @@ Following files use the csv:
 - [Full Load and Drag Curves (.vfld)](#full-load-and-drag-curves-.vfld)
 - [Fuel Consumption Map (.vmap)](#fuel-consumption-map-.vmap)
 - [Shift Polygons Input File (.vgbs)](#shift-polygons-input-file-.vgbs)
-- [Transmission Loss Map (.vtlm)](#transmission-loss-map)
+- [Transmission Loss Map (.vtlm)](#transmission-loss-map-.vtlm)
 - [Torque Converter Characteristics (.vtcc)](#torque-converter-characteristics-.vtcc)
 - [Auxiliary Input File (.vaux)](#auxiliary-input-file-.vaux)
-- [Driving Cycles (.vdri)](#driving-cycles)
+- [Driving Cycles (.vdri)](#driving-cycles-.vdri)
 - [Acceleration Limiting Input File (.vacc)](#acceleration-limiting-input-file-.vacc)
 - [Modal Results (.vmod)](#modal-results-.vmod)
 - [Summary Results (.vsum)](#summary-results-.vsum)

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

@@ -4,6 +4,6 @@ Configuration and component files in Vecto use [JSON](http://en.wikipedia.org/wi
 Following files use JSON:
 
 * [Job](#job-file)
-* [Vehicle](#vehicle-file)
-* [Engine](#engine-file)
-* [Gearbox](#gearbox-file)
+* [Vehicle](#vehicle-file-.vveh)
+* [Engine](#engine-file-.veng)
+* [Gearbox](#gearbox-file-.vgbx)

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

 ##Acceleration Limiting Input File (.vacc)
 
-The file is used for [Acceleration Limiting](#acceleration-limiting). It defines the acceleration and deceleration limits as function of
+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).
 
 - Filetype: .vacc

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

 ##Vair & Beta Cross Wind Correction Input File (.vcdb)
 
-The file is needed for Vair & Beta [Cross Wind Correction](#cross-wind-correction). The file uses the [VECTO CSV format](#csv).
+The file is needed for Vair & Beta [Cross Wind Correction](#vehicle-cross-wind-correction). The file uses the [VECTO CSV format](#csv).
 
 - Filetype: .vcdb
 - Header: **beta [°], delta CdA [m^2]**

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

 ##Speed Dependent Cross Wind Correction Input File (.vcdv)
 
-The file is needed for speed dependent [Cross Wind Correction](#cross-wind-correction). The file uses the [VECTO CSV format](#csv).
+The file is needed for speed dependent [Cross Wind Correction](#vehicle-cross-wind-correction). The file uses the [VECTO CSV format](#csv).
 
 - Filetype: .vcdv
 - Header: **v_veh [km/h], Cd [-]**