updating documentation - work on the first sections done.

Documentation/User Manual/1-user-interface/0_start.md

@@ -12,7 +12,7 @@ Software Requirements
 
 ##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.
+VECTO is distributed as a portable application. This means you can simply unzip the archive and directly start VECTO.exe. This, however, requires write and execute permissions for the VECTO application directory.
 
 In case you do not have execute permissions, please ask your system administrator to install VECTO into an appropriate directory (e.g. under `C:\Program Files`). Installing VECTO requires the following two steps:
 
@@ -21,7 +21,7 @@ In case you do not have execute permissions, please ask your system administrato
 
 If the ExecutionMode is set to `install` (this is also possible when running VECTO from an arbitrary directory), VECTO does not write its configuration files and log files to the application directory but to the directories `%APPDATA%` and `%LOCALAPPDATA%` (usually `C:\Users\<username>\AppData\Roaming` and `C:\Users\<username>\AppData\Local`).
 
-**Important:** If the ExecutionMode is set to `install` it is necessary that you copy the generic VECTO models distributed with VECTO to a location where you have write permissions as VECTO writes the results to the same directory as the job file.
+**Important:** If VECO is run from a directory without write permissions it is necessary that you copy the generic VECTO models distributed with VECTO to a location where you have write permissions or set the output path to a directory with write permissions (see the [Options in the main window](#main-form)).
 
 
 User Manual

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

@@ -81,12 +81,12 @@ In this tab the global calculation settings can be changed.
 **MISC**
 
 Validate Data
-:    Enables or disables internal checks if the model parameters are within a reasonable range. When simulating a new vehicle model it is good to have this option enabled. If the model parameters are from certified components or the model data has been modified slightly this check may be disabled. The VECTO simulation will abort anyways if there is an error in the model parameters. Enabling this option increases the simulation time by a few seconds.
+:    Enables or disables internal checks if the model parameters are within a reasonable range. When simulating a new vehicle model it is good to have this option enabled. If the model parameters are from certified components or the model data has only been modified slightly this check may be disabled. The VECTO simulation will abort anyways if there is an error in the model parameters. Enabling this option increases the simulation time by a few seconds.
 
 Output values in vmod at beginning and end of simulation iterval
 :    By defaul VECTO writes the simulation results at the middle of every simulation interval. If this option is enabled, the .vmod file will contain two entries for every simulation interval, one at the beginning and one at the end of the simulation interval. Enabling this option may be helpful for analysing the trace of certain signals but can not be used for quantitative analyses of the fuel consumption, average power losses, etc. The generated modal result file has the suffix '_sim'. The picture below shows the difference in the output (top: conventional, bottom: if this option is checked)
 
-![](pics/VECTO_vmod_vgl.png)
+![Regular VECTO .vmod output (top) vs. beginning and end of simulation interval (bottom)](pics/VECTO_vmod_vgl.png)
 
 
 ###Controls
@@ -139,4 +139,4 @@ Note that the [message log](#application-files) can be opened in the ![](pics/Mi
 In addition to the log messages shown in the message list, Vecto 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.
 
 Statusbar
-: Displays current status and progress of active simulations. When no simulation is executed 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 (Engineering or Declaration Mode).

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

@@ -11,7 +11,7 @@ The [job file (.vecto)](#job-file) includes all informations to run a VECTO calc
 -   Filepath to the [Vehicle File (.vveh)](#vehicle-editor) which defines the not-engine/gearbox-related vehicle parameters
 -   Filepath to the [Engine File (.veng)](#engine-editor) which includes full load curve(s) and the fuel consumption map
 -   Filepath to the [Gearbox File (.vgbx)](#gearbox-editor) which defines gear ratios and transmission losses
--   Filepath to the [Gearshift Parameters File (.vtcu)](#gearshift-parameters-file) which allows to override parameters of the [Effshift Gearshift Strategy](#gear-shift-model). The gearshift parameters cannot be edited via the graphical user interface. In case the default parameters shall be used either an empty .vtcu file ([see .vtcy](#gearshift-parameters-file)) or the gearbox file (.vgbx) can be provided. An example .vtcu file is provided [here](#gearshift-parameters-file)
+-   Filepath to the [Gearshift Parameters File (.vtcu)](#gearshift-parameters-file) which allows to override parameters of the [Effshift Gearshift Strategy](#gear-shift-model). The gearshift parameters cannot be edited via the graphical user interface. In case the default parameters shall be used either an empty .vtcu file ([see .vtcu](#gearshift-parameters-file)) or the gearbox file (.vgbx) can be provided. An example .vtcu file is provided [here](#gearshift-parameters-file)
 -   Auxiliaries
 -   Driver Assist parameters
 -   Driving Cycles (only in Engineering Mode)
@@ -55,29 +55,24 @@ Filepath ot the Hybrid Strategy Parameters File(.vhctl)
 
 <div class="declaration">
 Auxiliaries
-:	This group contains input elements to define the vehicle's load from the auxiliaries.
-In Declaration Mode only the pre-defined auxiliaries are available and their power-demand is also pre-defined, depending on the vehicle category and driving cycle. This means the Auxiliary Type is set to 'Classic: Vecto Auxiliary' and no 'Constant Aux Load' can be specified.
-The following list contains the pre-defined auxiliaries where the concrete technology for each auxiliary can be configured using the [Auxiliary Dialog](#auxiliary-dialog). 
-**Double-click** entries to edit with the [Auxiliary Dialog](#auxiliary-dialog).
+:	This group contains input elements to define the engine's load from the auxiliaries.
+In Declaration Mode only the pre-defined auxiliaries are available and their power-demand is also pre-defined, depending on the vehicle category and driving cycle. 
+The list contains the pre-defined auxiliaries where the concrete technology for each auxiliary can be configured using the [Auxiliary Dialog](#auxiliary-dialog). 
+**Double-click** entries to edit with the [Auxiliary Dialog](#auxiliary-dialog). No other types of auxiliaries can be used in declaration mode.
 </div>
 
 <div class="engineering">
 Auxiliaries
-:	In Engineering Mode the set of auxiliaries can be freely defined.
-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-.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
-</div>
+:	In Engineerin Mode the auxiliary power demand can be defined in three ways. 
 
-<div class="engineering">
-Electric Auxiliaries
-:   In Engineering mode it is possible to add electric auxiliaires. These auxiliaries are connected to the high-voltage battery.
+The first option is to define the power demand directly in the driving cycle in the column "Padd" (see (Driving Cycles)[#driving-cycles-.vdri]. This allows to vary the auxiliary load over distance (or time, for time-based driving cycles).
+
+The second option is to define a constant power demand over the whole cycle. The auxiliary power demand can be specified depending on whether the combustion engine is on or off and the vehicle is driving. The auxiliary power demand during engine-off phase is corrected in the (post-processing)[#engine-fuel-consumption-correction].
+
+The third option is to use the bus-auxiliaries model. For details see the (Bus Auxiliaries model)[#bus-auxiliaries].
 </div>
 
+
 See [Auxiliaries](#auxiliaries) for details.
 
 
@@ -87,6 +82,15 @@ See [Auxiliaries](#auxiliaries) for details.
 
 Cycles
 :	List of cycles used for calculation. The .vdri format is described [here](#driving-cycles-.vdri).
+
+<div class="declaration">
+	In Declaration Mode, the cycles to be simulated depend on the vehicle group. The cycles are listed in this window for reference.
+</div>
+
+<div class="engineering">
+	In Engineering Mode the cycles can be freely selected. All declaration cycles are provided in the Folder "Mission Profiles" and can be used or a custom cycle can be created and used.
+</div>
+
 **Double-click** an entry to open the file (see [File Open Command](#settings)).
 **Click** selected items to edit file paths.
 
@@ -99,7 +103,7 @@ Cycles
 ![](pics/JobForm_DriverModel.png)
 
 
-In this tab the driver assistance functions are enabled and parameterised.
+In this tab the driver assistance functions are enabled and parameterised. The parameters for overspeed, look-ahead coasting and driver acceleration can only be modified in Engineering Mode.
 
 Overspeed
 :	See [Overspeed](#overspeed) for details.
@@ -117,9 +121,11 @@ Acceleration Limiting
 
 In this tab certain general parameters for the advanced driver assistant system model can be set. Which ADAS feature is available can be selected in the vehicle itself, in Engineering Mode parameters like minimum activation speed, activation delay, or allowed overspeed can be adjusted. In Declaration Mode all parameters are fixed.
 
+For details on the individual parameters see the corresponding section [Engine Stop/Start](#advanced-driver-assistant-systems-engine-stopstart), [Eco-Roll](#advanced-driver-assistant-systems-eco-roll), [Predictive Cruise Control](#advanced-driver-assistant-systems-predictive-cruise-control)
+
 ###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. 
+The chart area on the right shows the main vehicle parameters like HDV group and axle configuration if a valid [Vehicle File](#vehicle-editor), [Engine File](#engine-file-.veng) and [Gearbox File](#gearbox-file-.vgbx) is loaded into the Editor. The plot shows the full load curve(s) and sampling points of the fuel consumption map. 
 
 ###Controls
 

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

@@ -7,20 +7,22 @@
 ###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.
 Next, VECTO re-computes the fuel consumption based for the given driving cycle. For a VTP-test the re-computed fuel consumption has to be within certain limits of the real fuel consumption.
 
 The [VTP job file (.vecto)](#vtp-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:
 
--   Filepath to the Vehicle File (.xml)](#vehicle-editor which defines all relevant parameters, including all components
+-   Filepath to the Vehicle File ([.xml](#xml-job-file-declaration-mode)) which defines all relevant parameters, including all components
 -   Driving Cycles
 
 
 <div class="engineering">
-	In engineering mode multiple driving cycles can be specified
+In engineering mode multiple driving cycles can be specified
 </div>
+
 <div class="declaration">
-In declaration mode only the first given driving cycle is simulated as the results are further compared with the re-simulated Long-Haul results.
+In declaration mode only the first given driving cycle is simulated as the results are further compared with the re-simulated results of the reference cycle. The reference cycle is the first driving cycle applicable for the actual vehicle group as listed in the Job Window and provided in the reports (i.e., LongHaul for most heavy lorries).
 
 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>
@@ -45,7 +47,7 @@ Cycles
 
 ###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. 
+The chart area on the right shows the main vehicle parameters like HDV group and axle configuration if a valid Vehicle File is loaded into the Editor. The plot shows the full load curve(s) and sampling points of the fuel consumption map. 
 
 ###Controls
 

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

 ##Auxiliary Dialog
 
 
-
 <div class="declaration">
 ![Auxiliary Dialog (Declaration Mode)](pics/VECTO-Editor_Aux_DECL.jpg)
-</div>
-
-
-
-<div class="engineering">
-![Auxiliary Dialog (Engineering Mode)](pics/VECTO-Editor_Aux_ENG.jpg)
-</div>
 
 ###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.
+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
 
-<div class="declaration">
 Technology
 :   List of available technology for the auxiliary type
 For the  steering pump multiple technologies can be defined, one for each steered axle.
-</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 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.
+###Controls
 
-Input File
-:	Path to the [Auxiliary File (.vaux)](#auxiliary-input-file-.vaux).
-</div>
+![ok](pics/OK.png) ***Save and close***
 
+![cancel](pics/Cancel.png) ***Close without saving***
 
+</div>
 
-###Controls
+<div class="engineering">
+In Engineering Mode the auxiliary power demand can either be specified in the driving cycle over distance (or time), specified as constant load, or via the bus auxiliaires. For more details see [the Auxiliaries tab in the Job editor](#job-editor).
+</div>
 
 
-![ok](pics/OK.png) ***Save and close***
 
-![cancel](pics/Cancel.png) ***Close without saving***

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

-##Vehicle Editor
+##Vehicle Editor -- General Tab
 
 ![](pics/VEH-Editor.PNG)
 
@@ -6,7 +6,7 @@
 
 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.
+The Vehicle Editor contains up to 6 tabs, depending on the powertrain architecture and simulation mode, to edit all vehicle-related parameters. The 'General' tab allows to input mass, loading, air resistance, vehicle axles, etc. The 'Powertrain' tab allows to define the retarder, an optional angle drive. The third tab is dedicated to all electric components in case of hybrid electric and battery electric vehicles. In the fourth tab the torque limitations for the combustion engine, the electric motor and the whole vehicle can be specified. The fifth tab allows to enable or disable certain advanced driver assistant systems to be considered in the vehicle. The last tab is dedicated to PTOs, either as a basic component or to simulate municipal vehicles such as refuse trucks or road speepers with dedicated PTO activation either during driving or during standstill. 
 
 ###Relative File Paths
 
@@ -23,7 +23,7 @@ Vehicle Category
 Axle Configuration
 : Needed for [Declaration Mode](#declaration-mode) to identify the HDV Group.
 
-Technically Permissible Maximum Laden Mass [t]
+Technically Permissible Maximum Laden Mass [t] (TPMLM)
 : Needed for [Declaration Mode](#declaration-mode) to identify the HDV Group.
 
 HDV Group
@@ -59,9 +59,9 @@ The product of Drag Coefficient [-] and Cross Sectional Area [m²] (**c~d~ x A**
 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.
 </div>
 
-For cross wind correction four different options are available:
+For cross wind correction four different options are available (see [Cross Wind Correction](#vehicle-cross-wind-correction) for details):
 : -  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 (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.
 
@@ -91,15 +91,44 @@ Use the ![](pics/plus-circle-icon.png) and ![](pics/minus-circle-icon.png) butto
 <div class="declaration">
 In [Declaration mode](#declaration-mode) only the axles of the truck have to be given (e.g., 2 axles for a 4x2 truck). 
 The dynamic tyre radius is derived from the second axle as it is assumed this is the driven axle.
-For missions with a trailer predefined wheels and load-shares are added by Vecto automatically.
+For missions with a trailer, predefined wheels and load-shares are added by Vecto automatically.
 </div>
 
 Doubleclick entries to edit existing axle configurations.
 
-###Powertrain Tab
+
+
+###Controls
+
+
+![](pics/blue-document-icon.png) New file
+: Create a new empty .vveh file
+
+![](pics/Open-icon.png) Open existing file
+: Open an existing .vveh file
+
+![](pics/Actions-document-save-icon.png) ***Save current file***
+
+![](pics/Actions-document-save-as-icon.png) ***Save file as...***
+
+![](pics/export-icon.png) Send current file to the [VECTO Editor](#job-editor)
+: **Note:** If the current file was opened via the [VECTO Editor](#job-editor) the file will be sent automatically when saved.
+
+![](pics/OK.png) Save and close file
+: If necessary the file path in the [VECTO Editor](#job-editor) will be updated.
+
+![](pics/Cancel.png) ***Cancel without saving***
+
+
+
+##Vehicle Editor -- Powertrain Tab
 
 ![](pics/VehicleForm_Powertrain.png)
 
+###Vehicle Idling Speed
+
+The idling speed of the combustion engine can be increased in the vehicle settings. This may be necessary due to certain auxiliaries or for other technical reasons. This value is only considered if it is higher than the idling speed defined in the combustion engine.
+
 ###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.
@@ -124,17 +153,8 @@ 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
-
-If the vehicle has an PTO consumer, a pto transmission and consumer can be defined here. (Only in [Engineering Mode](#engineering-mode))
-
-Three settings can be set:
-
-- PTO Transmission: Here a transmission type can be chosen (adds constant load at all times).
-- PTO Consumer Loss Map (.vptol): Here the [PTO Idle Loss Map](#pto-idle-consumption-map-.vptoi) of the pto consumer can be defined (adds power demand when the pto cycle is not active).
-- PTO Cycle (.vptoc): Defines the [PTO Cycle](#pto-cycle-.vptoc) which is used when the pto-cycle is activated (when the PTO-Flag in the driving cycle is set).
 
-###Electric Components
+##Vehicle Editor -- Electric Components Tab
 
 ![](pics/VECTO_VehicleEditor_ParHyb_El.png)
 
@@ -143,41 +163,69 @@ For hybrid vehicles and battery electric vehicles the input elements on the *ele
 The position where the electric machine is positioned in the powertrain can be selected. It is possible that the electric machine is connected to the powertrain via a fixed gear ratio.
 At the moment electric machines are supported to be present at a single position only. It is not possible to have an electric motor at position P2 and another at position P4!
 However, it is possible that more than one electric machine is used at a certain position. 
-The *Efficiency EM to Drivetrain* can be used to consider the efficiency of a transmission step between drivetrain and electric machine or to consider losses of a summation gear.
 
-For the electric energy storage multiple battery packs can be configured and the initial state of charge can be defined.
+The *Loss map EM ADC* can be used to consider the losses of a transmission step between drivetrain and electric machine or to consider losses of a summation gear. The loss map has the same format as for all other transmission components (see [Transmission Loss Map (.vtlm)](#transmission-loss-map-.vtlm)). For simplicity or if no such transmission step is used it is possible to enter the efficiency directly (i.e., "1" if no transmission step is used).
 
-The maximum power of a hybrid drivetrain can be limited to a certain power. This limit has to be at least the maximum power of the combustion engine.
+In case of a P2.5 configuration (the electric motor is connected to an internal shaft of the tranmission) the transmission ratio for every single gear of the transmission has to be specified in the list to the right of the electric motor parameters.
 
-###Torque Limits
+For the electric energy storage multiple battery packs can be configured either in series or in parallel and the initial state of charge of the whole battery system can be defined.  For every entry of a battery pack the number of packs (count) in series and a string identifier need to be specified. Battery packs on the same string are connected in series (e.g., two different battery packs on string nuber 1 are in series) while all strings are then connected in parallel (see [Battery Model](#foo) for details). This is only supported for batteries and **not** for SuperCaps.
+
+**Double-click** an entry to edit.
+**Click** selected item.
+: ![addcycle](pics/plus-circle-icon.png) Add REESS (.vbat)
+: ![remcycle](pics/minus-circle-icon.png) Remove the selected REESS from the list
+
+In the REESS Dialog the battery file itself and how it is connected to the electric system (i.e, the string identifier and number of packs used) can be modified.
+
+![](pics/BatteryPackDialog.png)
+
+
+##Vehicle Editor -- Torque Limits Tab
 
 ![](pics/VehicleForm_TorqueLimits.png)
 
-In case that the gearbox' maximum torque is lower than the engine's maximum torque or to model certain features like Top-Torque (where in the highest gear more torque is available) it is possible to limit the engine's maximum torque depending on the engaged gear. This can be entered in the torque limits tab.
+On this tab different torque limits can be applied at the vehicle level. 
 
-###ADAS
+First, the maximum torque of the ICE may be limited for certain gears (see [Engine Torque Limitations](#engine-torque-and-engine-speed-limitations)).
+In case that the gearbox' maximum torque is lower than the engine's maximum torque or to model certain features like Top-Torque (where in the highest gear more torque is available) it is possible to limit the engine's maximum torque depending on the engaged gear. 
 
-![](pics/VehicleForm_ADAS.png))
+Next, the maximum available torque for the electric machine can be reduced at the vehicle level, both for propulsion and recuperation. The input file is the same as the maximum drive and maximum recuperation curve (see [Electric Motor Max Torque File](#electric-motor-max-torque-file-.vemp))
 
-On the ADAS tab, the options for advanced driver assistant systems can be selected.  See [ADAS: Overspeed](#driver-overspeed) and [ADAS Technologies](#vehicle-adas-technologies)
+Last, the overall propulsion of the vehicle (i.e., electric motor plus combusion engine) can be limited. The "Propulsion Torque Limit" curve limits the maximum effective torque at the gearbox input shaft over the input speed. This curve is added to the combustion engine's maximum torque curve (only positive values are allowed!). For details on the file format see [Propulsion Torque Limit File](#propulsion-torque-limit-file-.vtqp). The propulsion torque limit has to be provided from 0 rpm to the maximum speed of the combustion engine. In case of P3 or P4 configuration, the torque at the gearbox input shaft is calculated assuming that the electric motor does not contribute to propelling the vehicle, considering the increased losses in the transmission components inbetween. For P2.5 powertrain configurations no special calculations are necessary as this architecture is internally anyhow modelled as P2 architecture.
 
-###Controls
+##Vehicle Editor -- ADAS Tab
 
+![](pics/VehicleForm_ADAS.png)
 
-![](pics/blue-document-icon.png) New file
-: Create a new empty .vveh file
+On the ADAS tab, the advanced driver assistant systems present in the vehicle can be selected.  See [ADAS - Engine Stop/Start](#advanced-driver-assistant-systems-engine-stopstart), [ADAS - EcoRoll](#advanced-driver-assistant-systems-eco-roll), and [ADAS - Predictive Cruise Control](#advanced-driver-assistant-systems-predictive-cruise-control)
 
-![](pics/Open-icon.png) Open existing file
-: Open an existing .vveh file
 
-![](pics/Actions-document-save-icon.png) ***Save current file***
+##Vehicle Editor -- PTO Tab
 
-![](pics/Actions-document-save-as-icon.png) ***Save file as...***
+![](pics/Vehicleform_PTO.png)
 
-![](pics/export-icon.png) Send current file to the [VECTO Editor](#job-editor)
-: **Note:** If the current file was opened via the [VECTO Editor](#job-editor) the file will be sent automatically when saved.
+###PTO Transmission
 
-![](pics/OK.png) Save and close file
-: If necessary the file path in the [VECTO Editor](#job-editor) will be updated.
+If the vehicle has an PTO consumer, a pto transmission and consumer can be defined here. (Only in [Engineering Mode](#engineering-mode))
+
+Three settings can be set:
+
+- PTO Transmission: Here a transmission type can be chosen (adds constant load at all times).
+- PTO Consumer Loss Map (.vptol): Here the [PTO Idle Loss Map](#pto-idle-consumption-map-.vptoi) of the pto consumer can be defined (adds power demand when the pto cycle is not active).
+- PTO Cycle (.vptoc): Defines the [PTO Cycle](#pto-cycle-.vptoc) which is used when the pto-cycle is activated (when the PTO-Flag in the driving cycle is set).
+
+<div class="engineering">
+In engineering mode additional PTO activations are available to simulate different types of municipal vehicles. It is possible to add a certain PTO load during driving while the engine speed and gear is fixed (to simulate for example roadsweepers), or to add PTO activation while driving (to simulate side loader refuse trucks for example). In both cases the PTO activation is indicated in the [driving cycle](#driving-cycles-.vdri) (column "PTO").
+
+
+###Roadsweeper operation
+
+PTO activation mode 2 simulates PTO activation while driving at a fixed engine speed and gear. The minimum engine speed and working gear is entered in the PTO tab. For details see [PTO](#pto).
+
+
+###Sideloader operation
+
+PTO activation mode 3 simulates a time-based PTO activation while driving. Therefore, a separate PTO cycle ([.vptor]()) containing the PTO power over time has to be provided. The start of PTO activation is indicated with a '3' in the 'PTO' column of the [driving cycle](#driving-cycles-.vdri). For details see [PTO](#pto).
+
+</div>
 
-![](pics/Cancel.png) ***Cancel without saving***