updating documentation

User Manual/1-user-interface/start.md → User Manual/1-user-interface/0_start.md

@@ -21,6 +21,6 @@ This User Manual consists of 4 Parts:
 - [Input and Output](#input-and-output):
     : The input and output file formats are described in this chapter.
 
-
+This user manual describes both, version 2.2 and verson 3.0.x of Vecto. Vecto 3.x is a complete rewrite of Vecto 2.2 that uses the same models and input data and also produces the same output. However, in some parts version 3.x differs from version 2.2. The according paragraphs are highlighted accordingly.
 
 

User Manual/1-user-interface/mainform.md → User Manual/1-user-interface/B_mainform.md

@@ -10,7 +10,7 @@
 
 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.
 
-In order to start a calculation the [Calculation Mode](#calculation-modes) must be set and at least one [Job File (.vecto)](#job-editor) must added to the Job List. After clicking START all checked files in the Job List will be calculated.
+In order to start a simulation the [Calculation Mode](#calculation-modes) must be set and at least one [Job File (.vecto)](#job-editor) must added to the Job List. After clicking START all checked files in the Job List will be calculated. From the user interface you can either run the simulation using Vecto 2.2 or Vecto 3.x by clicking the according START button on the left side of the window.
 
 The Main Form includes three tabs as described below:
 
@@ -69,38 +69,32 @@ Driving Cycle List
 In this tab the global calculation settings can be changed.
 
 ![](pics/checkbox.png) Declaration Mode
-:   Enable or disable [Declaration Mode](#declaration-mode)
+:   Select either [Declaration Mode](#declaration-mode) or [Engineering Mode](#engineering-mode)
 
+![cb](pics/checkbox.png) Write modal results
+:   Toggle output of modal results (.vmod files). Summary files (.vsum, .vres) are always created.
 
+<div class="vecto2">
 ![](pics/checkbox.png) Batch Mode
 :   If Declaration Mode is disabled VECTO can be run in [Batch Mode](#batch-mode).
 
-
 ![cb](pics/checkbox.png) Cycle Distance Correction
 :   Toggle Cycle Distance Correction. Always ON in Declaration Mode. Cycle Distance Correction monitors the driven distance in each time step and, if necessary, adds or removes time steps in order to keep the original distance given in the driving cycle.
 :   -   If **enabled** the vehicle drives the same **distance** as given in the driving cycle
 -   If ***disabled*** the vehicle travels the same **time** as given in the driving cycle (Note that distance-based cycles (see [here](#driving-cycles)) are always converted to time-based cycles internally)
 
-
 ![cb](pics/checkbox.png) Use gears/rpm's form driving cycle
 :   If activated VECTO will use gear and/or engine speed defintions included in the driving cycle (see [here](#driving-cycles)).
 
-
-![cb](pics/checkbox.png) Write modal results
-:   Toggle output of modal results (.vmod files). Summary files (.vsum, .vres) are always created.
-
-
 ![cb](pics/checkbox.png) Shutdown system after last job
 :   If activated VECTO will shutdown the system after the last job was completed. (Can be aborted during 100 seconds before shutdown.)
 
 Output Path (BATCH Mode only)
 :   Select target directory for result files (.vmod, .vres, .vsum)
 
-
-
 ![cb](pics/checkbox.png) Create Subdirectories for modal results (BATCH Mode only)
 :   If activated a subdirectory for each job file will be created inside **Output Path** for modal output.
-
+</div>
 
 ###Controls
 
@@ -149,5 +143,9 @@ Depending on the colour the following message types are displayed:
 
 Note that the [message log](#application-files) can be opened in the ![](pics/Misc-Tools-icon.png) Tools menu with **Open Log**.
 
+<div class="vecto3">
+In addition to the log messages shown in the message list, Vecto 3 writes more elaborate messages in the subdirectory logs. If multiple simulations are run in parallel (e.g., in declartion mode a vehicle is simulated on different cycles with different loadings) a separate log-file is created for every simulation run.
+</div>
+
 Statusbar
-: Displays current status and progress of running calculations. When no calculation is running the current mode is displayed (Standard, Batch or Declaration Mode).
+: Displays current status and progress of active simulations. When no simulation is executed the current mode is displayed (Standard, Batch or Declaration Mode).

User Manual/1-user-interface/settings.md → User Manual/1-user-interface/C_settings.md

@@ -12,7 +12,7 @@ In the Settings dialog controls general application settings. The settings are s
 
 <div class="vecto22">
 Logfile Size Limit \[MB\]
-:	Whenever the [Log File](#application-files) reaches this size it will be restarted. One backup is always stored as LOG\_backup.txt.
+:	Whenever the [Log File](#application-files) reaches this size it will be restarted. One backup is always stored as LOG\_backup.txt. <span class="vecto3">*Note:* this setting only affects the log-file written by the graphical user interface. The log-files written in the logs subdirectory are not limited by this setting!</span>
 
 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)\

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

@@ -18,16 +18,16 @@ The [job file (.vecto)](#job-file) includes all informations to run a VECTO calc
 
 ###Relative File Paths
 
-It is recommended to define 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.
+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. (The Job File must be saved before browsing for input files.)
+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
 
 ![](pics/checkbox.png) Engine Only Mode
 
-:	Enables [Engine Only Mode](#engine-only-mode). Only the following parameters are needed for this mode:
+:	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

User Manual/1-user-interface/VECTO-Editor_Aux.md → User Manual/1-user-interface/E_VECTO-Editor_Aux.md

@@ -6,24 +6,27 @@
 ###Description
 
 
-The Auxiliary Dialog is used to configure auxiliaries. 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.
-
-In [Declaration Mode](#declaration-mode) only the Technology for each auxiliary has to be selected.
-
+The Auxiliary Dialog is used to configure auxiliaries. In [Declaration Mode](#declaration-mode) the set of auxiliaries and their power demand is pre-defined. The user has to select for every auxiliary 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
 
+<div class="declaration">
+Technology
+:   List of available technology for the auxiliary type (declaration mode)
+</div>
 
+<div class="engineering">
 Type
 :	String defining type of auxiliary. Click the arrow to load from a predefined list, however It is not required to use a type from the list.
 
 ID
-:	The ID string is required to link the auxiliary to the corresponding supply power definition in the driving cycle. The ID must not contain space or special characters text and numbers only). The ID is not case sensitive (e.g. "ALT" will link to "Alt" or "alt", etc.)
-***Example*** *: Auxiliary "ALT" is linked to the column "&lt;AUX\_ALT&gt;" in the driving cylce.*
+:	The ID string is required to link the auxiliary to the corresponding supply power definition in the driving cycle. The ID must contain characters  and numbers only (A-Z, a-z, 0-9). The ID is not case sensitive (e.g. "ALT" will link to "Alt" or "alt", etc.)
+***Example*** *: Auxiliary "ALT" is linked to the column "&lt;Aux\_ALT&gt;" in the driving cylce.*
 See [Auxiliaries](#auxiliaries) for details.
 
 Input File
 :	Path to the [Auxiliary File (.vaux)](#auxiliary-input-file-.vaux).
+</div>
 
 ###Controls
 

User Manual/1-user-interface/VEH-Editor.md → User Manual/1-user-interface/F_VEH-Editor.md

@@ -11,10 +11,10 @@ The [Vehicle File (.vveh)](#vehicle-file) defines the main vehicle/chassis param
 ###Relative File Paths
 
 
-It is recommended to define relative filepaths. This way the Job File and all input files can be moved without having to update the 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. (The Vehicle File must be saved before browsing for input files.)
+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
 
@@ -41,13 +41,22 @@ These fields define the weight and loading of the vehicle. **Max. Loading** disp
 ###Air Resistance
 
 
-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. Note that the Drag Coefficient may be altered when using [**Cross Wind Correction**](#cross-wind-correction).
+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. Note that the Air Drag depends on the chosen [**Cross Wind Correction**](#cross-wind-correction).
 
 ###Axles/Wheels
 
 
-For each axle the parameters **Relative axle load, RRC~ISO~** and **F~zISO~** have to be defined in order to calculate the total [Rolling Resistance Coefficient](#rolling-resistance-coefficient).
-Furthermore the **Wheels Inertia [kgm²]** has to be set per wheel for each axle. In [Declaration Mode](#declaration-mode) the inertia is defined automatically according to the selected tyres.
+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).
+Furthermore the **Wheels Inertia [kgm²]** has to be set per wheel for each axle. In [Declaration Mode](#declaration-mode) the inertia is computed based on the selected tyres and rims. The number of axles specified have to match the vehicle type (e.g., 2 axles for a 4x2 truck). 
+
+<div class="declaration">
+In [Declaration mode](#declaration-mode) only the axles of the truck have to be given. For the trailer predefined wheels and weight-shares are used.
+</div>
+
+<div class="engineering">
+In [Engineering Mode](#engineering-mode) all axles, for both  truck and trailer, have to be given.
+</div>
+
 Use the ![](pics/plus-circle-icon.png) and ![](pics/minus-circle-icon.png) buttons to add or remove axles form the vehicle. Doubleclick entries to edit existing axle configurations.
 
 Dynamic Tyre Radius [mm]
@@ -60,25 +69,27 @@ Powered axle tyres/rims
 ###Retarder Losses
 
 
-If available a **Retarder Torque Loss Map** can be defined here to consider idling losses caused by the retarder.
-***Note: Do not use this function if the retarder's losses are already included in the Transmission Loss Maps!***
+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.
 
 Three options are available:
-: -	Included in Transmission Loss Maps: Use this if the [Transmission Loss Maps](#transmission-loss-map) already include retarder losses.
+: -   No retarder
+-	Included in Transmission Loss Maps: Use this if the [Transmission Loss Maps](#transmission-loss-map) 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
 
-Both, primary and secondary retarders, require an [Retarder Loss Torque Input File (.vrlm)](#retarder-loss-torque-input-file-.vrlm).
+Both, primary and secondary retarders, require an [Retarder Torque Loss Input File (.vrlm)](#retarder-loss-torque-input-file-.vrlm).
 
 
 ###Cross Wind Correction Options
 
 
 Four different options are available:
-: -  No Correction
--  Speed dependent (User-defined)
--  Speed dependent (Declaration Mode)
--  Vair & Beta Input
+: -  No Correction: The specified CdxA value is used to compute the air drag, no cross-wind correction is applied
+-  Speed dependent (User-defined): The specified CdxA value is corrected depending on the vehicle's speed.
+-  Speed dependent (Declaration Mode): A uniformly distributed cross-wind is assumed and used for correcting the air-drag depending on the vehicle's speed
+-  Vair & Beta Input: Correction mode if the actual wind speed and wind angle relative to the vehicle have been measured.
+
+In delcaration mode the 'Speed dependent (Declaration Mode)' cross-wind correction is used.
 
 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).
 

User Manual/1-user-interface/ENG-Editor.md → User Manual/1-user-interface/G_ENG-Editor.md

@@ -8,11 +8,10 @@ The [Engine File (.veng)](#engine-file) defines all engine-related parameters an
 
 ###Relative File Paths
 
-It is recommended to define relative filepaths. This way the Job File and all input files can be moved without having to update the 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. The Engine File must be saved before browsing for input files.)
+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
 
@@ -26,16 +25,12 @@ Displacement \[ccm\]
 :   Used in [Declaration Mode](#declaration-mode) to calculate inertia.
 
 Inertia including Flywheel \[kgm²\]
-:   Inertia for rotating parts including engine flywheel. In [Declaration Mode](#declaration-mode) the inertia is calculated automatically.
+:   Inertia for rotating parts including engine flywheel. In [Declaration Mode](#declaration-mode) the inertia is calculated automatically depending on the engine's displacement and also accounts for the clutch's inertia.
 
 ###Full Load and Drag Curves
 
 
-
-The [Full Load and Drag Curves (.vfld)](#full-load-and-drag-curves-.vfld) Note that gear-specific full load curves can be defined in the [Gearbox File](#gearbox-file) to limit the maximum gearbox input torque.
-
-The input file (.vfld) file format is described
-[here](#full-load-and-drag-curves-.vfld).
+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
 

User Manual/1-user-interface/GBX-Editor.md → User Manual/1-user-interface/H_GBX-Editor.md

@@ -14,7 +14,7 @@ The [Gearbox File (.vgbx)](#gearbox-file) defines alls gearbox-related input par
 
 ###Relative File Paths
 
-It is recommended to define relative filepaths. This way the Job File and all input files can be moved without having to update the 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.
 
 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.)
@@ -36,11 +36,11 @@ Transmission Type
 
 
 Inertia \[kgm²\]
-:   Rotational inertia of the gearbox (constant for all gears).
+:   Rotational inertia of the gearbox (constant for all gears). (Engineering mode only)
 
 
 Traction Interruption \[s\]
-:   Interruption during gear shift event.
+:   Interruption during gear shift event. (Engineering mode only)
 
 
 ###Gears
@@ -48,10 +48,11 @@ Traction Interruption \[s\]
 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.
 
 -   Gear **"A"** defines the ratio of the axle transmission / differential.
--   Column **"TC"** (AT only) defines which gears are using the torque converter (lock-up clutch open).
--   Column **"Loss Map or Efficiency"** allows to define either a constant efficiency value or a [loss map (.vtlm)](#transmission-loss-map).
--   Column **"Shift polygons"** defines the [Shift Polygons InputFile (.vgbs)](#shift-polygons-input-file-.vgbs) for each gear. Not required in [Declaration Mode](#declaration-mode). See [GearShift Model](#gear-shift-model) for details.
--	Column **"Full Load Curves"** defines the [Full Load Curve for (.vfld)](#full-load-and-drag-curves-.vfld) each gear. It is used for torque limiting and [generic shift polygons](#gear-shift-model) in Declaration Mode. If no file is defined the engine full load curve will be used. 
+-    **"TC"** (AT only) defines which gears are using the torque converter (lock-up clutch open).
+-    **"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="vecto3">Note: in Vecto 3 it is mandatory to specify a loss map for every gear!</span>
+-    **"Shift polygons"** defines the [Shift Polygons InputFile (.vgbs)](#shift-polygons-input-file-.vgbs) for each gear. Not required in [Declaration Mode](#declaration-mode). See [GearShift Model](#gear-shift-model) for details.
+-	 **"Full Load Curves"** defines the [Full Load Curve for (.vfld)](#full-load-and-drag-curves-.vfld) each gear. It is used for torque limiting in the current 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)!
 
 
 ###Gear shift parameters
@@ -69,7 +70,8 @@ Torque Reserve \[%\]
 
 
 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.
+:   Limits the time between two gear shifts. This rule will be ignored if rpms are too high or too low. <span class="vecto2">Vecto 2.2 uses fixed time-steps of 1 second, hence only whole seconds can be specified.</span>
+<span class="vecto3">Vecto 3 uses dynamic time-steps, hence any values greater than 0 seconds can be given.</span>
 
 
 Start Gear
@@ -85,7 +87,7 @@ The Chart Area displays the [Shift Polygons Input File(.vgbs)](#shift-polygons-i
 
 ###Torque Converter
 
-
+<div class="vecto2">
 
 The [Torque Converter Model](#torque-converter-model) is still in development.
 
@@ -123,3 +125,4 @@ be updated.
 
 
 ![Cancel](pics/Cancel.png) ***Cancel without saving***
+</div>
\ No newline at end of file

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

@@ -43,4 +43,4 @@ 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 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.*
+***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.*

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

@@ -23,7 +23,7 @@ Parameters in [Job File](#job-file):
 
 ###Eco-Roll
 
-
+<div class="vecto2">
 Instead of using the engine brake (with no fuel consumption) Eco-Roll shifts to Neutral, engine idling, to minimize deceleration and maximize the vehicle's roll out distance. During this phase the engine has to overcome its own idling losses and the power demand from the auxiliaries. The engine is engaged again if the speed exceeds the speed limits defined by Max. Over-/Underspeed.
 
  ![](pics/EcoRoll.svg)
@@ -34,3 +34,4 @@ Parameters in [Job File](#job-file):
 : -   **Minimum speed \[km/h\]** Below this speed the function is disabled.
 -   **Max. Overspeed \[km/h\]** (relative to target speed)
 -   **Max. Underspeed \[km/h\]** (relative to target speed)
+</div>
\ No newline at end of file

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

@@ -13,7 +13,7 @@ The CO~2~ result for the actual mission profile is directly derived from the fue
 The interpolation is based on [Delaunay Triangulation ![](pics/external-icon%2012x12.png)](http://en.wikipedia.org/wiki/Delaunay_triangulation) and works as follows:
 
 1.  Triangulate the given rpm/torque/fuel points (= x,y,z)  to create a
-    network of triangles with each point of the map being part of at
+    grid of triangles with each point of the map being part of at
     least one triangle.
 2.  Find the triangle where the to-be-interpolated load point (x,y)
     is inside. If no triangle meets the criterion the calculation will
@@ -28,6 +28,7 @@ The interpolation is based on [Delaunay Triangulation ![](pics/external-icon%20
 
 ###Auxiliary - Start/Stop Correction
 
+<div class="vecto2">
 For vehicles with [Start/Stop](#engine-startstop) the fuel consumption needs to be corrected to consider the wrong auxiliary energy balance caused by engine stops because VECTO uses a constant power demand for auxiliaries for the whole mission profile. The correction consists of the following steps:
 
 1.  From all 1Hz data points of the VECTO simulation, a linear regression curve (y=k\*x+d) for fuel consumption (unit: grams per hour) over engine power (unit: kilo-watt) is calculated (see figure below).
@@ -37,7 +38,7 @@ For vehicles with [Start/Stop](#engine-startstop) the fuel consumption needs to
 ![](pics/StartStopCorrection.svg)
 
 *Example of a linear regression between engine power and fuel consumption*
-
+</div>
 
 ###WHTC Correction
 

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

 ##Look-Ahead Coasting
 
 
-Like Overspeed, Look-Ahead Coasting is a function that aims on modelling real-life driver behaviour. It is a forward-looking function that detects forthcoming reductions in target speed in the mission profile (e.g. change of road type / speed limit, etc.) and induces an early deceleration using engine braking before applying mechanical brakes according to the [deceleration limit](#acceleration-limiting).
+Like Overspeed, Look-Ahead Coasting is a function that aims on modelling real-life 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).
 
  The implemented approach uses a predefined target deceleration (a~lookahead~) to calculate the deceleration time for each particular target speed change.
 

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

 ##Transient Full Load
 
+<div class="vecto2">
 VECTO uses a PT1 function to model transient torque build up using this formula:
 
 
@@ -11,3 +12,17 @@ with:
 * T(n~i~) ... PT1 time constant at engine speed n~i~ (col. 4 in [.vfld file](#full-load-and-drag-curves-.vfld))
 * P~fld\ stat~(n~i~) ... Static full load at engine speed n~i~ (col. 2 in [.vfld file](#full-load-and-drag-curves-.vfld))
 * P~act\ i-1~ ... Engine power in previous time step
+</div>
+
+<div class="vecto3">
+Vecto 3 uses basically the same PT1 behavior to model transient torque build up. However, due to the dynamic time steps the formula is implemented as follows:
+
+$P_{fld\ dyn_{i}} = P_{fld\ stat}(n_i) \cdot (1 - exp(-\frac{t_i^*}{PT1}))$
+
+where $t^*$ is computed from the dynamic full-load power in the previous simulation interval:
+
+$t_{i-1}^* = PT1 \cdot ln(\frac{1.0}{1 - \frac{P_{eng_{i - 1}}}{P_{fld\ stat}(n_i)}})$
+
+$t_i^* = t_{i-1}^* + dt$
+
+</div>
\ No newline at end of file

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

 ##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 auxiliary power demand. This mode is active as soon as P~wheel~, Gear and Engine Speed are defined in the driving cycle.
+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
 

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

@@ -2,7 +2,7 @@
 
 
 The rolling resistance is calculated using a speed-independent rolling resistance coefficient (RRC).
-In order to consider that the RRC is dependent from the vehicle weight it is modelled as a function of the total vehicle mass. The total RRC is calculated in VECTO using the following formula. The index i refers to each single vehicle axle (truck and trailer).
+In order to consider that the RRC depends on the vehicle weight it is modelled as a function of the total vehicle mass. The total RRC is calculated in VECTO using the following equation (the index i refers to the vehicle's axle (truck and trailer)):
 
 $RRC = \sum_{i=1}^{n} s_{(i)} \cdot RRC_{ISO(i)} \cdot \left( \frac{s_{(i)} \cdot m \cdot g }{w_{(i)} \cdot F_{zISO(i)} } \right)^{\beta-1}$
 
@@ -12,7 +12,7 @@ $RRC = \sum_{i=1}^{n} s_{(i)} \cdot RRC_{ISO(i)} \cdot \left( \frac{s_{(i)} \cdo
 | 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]               |
 | m           | [kg]   | Vehicle mass plus loading.                                                                                         | [calculated]               |
-| g           | [m/s²] | Earth gravity acceleration (constant = 9.81)                                                                       | [constant model parameter] |
+| g           | [m/s²] | Earth gravity acceleration (constant = 9.81, Vecto 3.x: 9.80665)                                                                       | [constant model parameter] |
 | w~(i)~      | [-]    | Number of tyres (4 if Twin Tyres, else 2). Defined in the 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-editor). | [user input]               |
 | β           | [-]    | Constant parameter = 0.9                                                                                           | [constant model parameter] |

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

@@ -22,8 +22,7 @@ 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).
 
-
-In [Declaration Mode](#declaration-mode) the shift polygons are generated automatically based on the full load curve of each gear. If the engine's full load torque is lower than the gear's, then the engine's full load is used to prevent unreasonable shifting with small engines.
+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 the Gearbox File two additional parameters are defined:

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

 ##Cross Wind Correction
 
 
-VECTO offers two 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).
 
 
 ###Speed dependent correction (Declaration Mode)
@@ -14,13 +14,19 @@ This is the default mode which is used in [Declaration Mode](#declaration-mode).
 ###Speed dependent correction (User-defined)
 The base c~d~ x A value (see [Vehicle File](#vehicle-file)) is corrected with a user-defined speed dependent scaling function. The input file (.vcdv) format is described [here](#speed-dependent-cross-wind-correction-input-file-.vcdv).
 
+The CdxA value given in the vehicle configuration is corrected depending on the vehicle's speed and the CD scaling factor from the input file as follows:
+
+C~d~xA~effective~ = CdxA * Cd(v_veh)
 
  ![](pics/VCDV.png)
 
 
 ###Correction using Vair & Beta Input
 
-If available the actual (measured) air speed and direction can be used. The input file (.vcdb) defines the drag coefficient scaling factor. The
-input file (.vcdb) format is described [here](#vair-beta-cross-wind-correction-input-file-.vcdb). 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. The input file (.vcdb) defines delta C~d~xA in square meters depending on the wind speed and wind angle. The input file (.vcdb) format is described [here](#vair-beta-cross-wind-correction-input-file-.vcdb). 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 CdxA 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:
+
+C~d~xA~effective~ = CdxA + delta-Cd(beta)
 
  ![](pics/VCDB.png)