Code development platform for open source projects from the European Union institutions

Skip to content
Snippets Groups Projects
Commit 8cb1e630 authored by Markus QUARITSCH's avatar Markus QUARITSCH
Browse files

first round of corrections of usermanual for Vecto 3.1

parent 045eb410
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 151 additions and 268 deletions
Documentation/User Manual/1-user-interface/0_start.md
+ 5
− 5
View file @ 8cb1e630
......@@ -3,7 +3,7 @@ User Manual
====================================
![](pics/VECTOlarge.png)\
\
Version: VECTO 2.2 / VectoCore 3.0.2 / VectoCmd 3.0.2
Version: VECTO 3.1 / VectoCore 3.1.0 / VectoCmd 3.1.0
---
......@@ -13,14 +13,14 @@ VECTO is a tool for the calculation of energy consumption and CO~2~ emissions of
This User Manual consists of 4 Parts:
- [Graphical User Interface](#user-interface):
: Here graphical user interface of VECTO with all windows and configuration possibilities is described.
: Describes the graphical user interface of VECTO with all windows and configuration possibilities.
- [Calculation Modes](#calculation-modes):
: The calculation modes of VECTO are described here (Declaration, Engineering, ...).
: Describes the calculation modes of VECTO (Declaration, Engineering, ...).
- [Simulation Models](#simulation-models):
: This chapter describes the used component models and formulas which are implemented in the software.
- [Input and Output](#input-and-output):
: The input and output file formats are described in this chapter.
: Describes the input and output file formats.
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.
This user manual describes verson 3.1.x of Vecto.
Documentation/User Manual/1-user-interface/B_mainform.md
+ 5
− 32
View file @ 8cb1e630
......@@ -10,12 +10,11 @@
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 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.
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.
The Main Form includes three tabs as described below:
The Main Form includes two tabs as described below:
* Job Files Tab
* Driving Cycles Tab (only if [Batch Mode](#batch-mode-1) is enabled)
* Options Tab
......@@ -56,12 +55,6 @@ Doubleclick entries to edit job files with the [VECTO Editor](#job-editor).
Start VECTO in the selected mode (see [Options](#options-tab)).
###Driving Cycles Tab
Driving Cycle List
: The Driving Cycles List is only used in [Batch Mode](#batch-mode). The same controls are used as in the Job Files List.
###Options Tab
......@@ -74,27 +67,9 @@ In this tab the global calculation settings can be changed.
![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) 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) Modal results in 1Hz
: If selected, the modal results (.vmod file) will be converted into 1Hz after the simulation.
![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
......@@ -143,9 +118,7 @@ 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>
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).
Documentation/User Manual/1-user-interface/D_VECTO-Job-Editor.md
+ 18
− 5
View file @ 8cb1e630
......@@ -13,7 +13,7 @@ The [job file (.vecto)](#job-file) includes all informations to run a VECTO calc
- Filepath ot the [Gearbox File (.vgbx)](#gearbox-editor) which defines gear ratios and transmission losses
- Auxiliaries
- Driver Assist parameters
- Driving Cycles (not used in Batch Mode)
- Driving Cycles (only in Engineering Mode)
###Relative File Paths
......@@ -42,14 +42,27 @@ Filepath to the Engine File (.veng)
Filepath ot the Gearbox File(.vgbx)
: Files can be created and edited using the [Gearbox Editor](#gearbox-editor).
<div class="declaration">
Auxiliaries
: This list contains all auxiliaries used for calculation. The auxiliaries are configured using the [Auxiliary Dialog](#auxiliary-dialog).
In Declaration Mode the set of auxiliaries and their power-demand is pre-defined, depending on the vehicle category and driving cycle.
In Engineering Mode the set of auxiliaries can be freely defined. 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.
: 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).
</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) 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>
: See [Auxiliaries](#auxiliaries) for details.
......@@ -81,7 +94,7 @@ Acceleration Limiting
###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 shift polygons. In [Declaration Mode](#declaration-mode) the **generic** shift polygons are shown, not the ones from the Gearbox File.
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.
###Controls
......
Documentation/User Manual/1-user-interface/E_VECTO-Editor_Aux.md
+ 10
− 2
View file @ 8cb1e630
##Auxiliary Dialog
<div class="declaration">
</div>
<div class="engineering">
![](pics/VECTO-Editor_Aux.png)
</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. 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.
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 (declaration mode)
: 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">
......@@ -28,6 +34,8 @@ Input File
: Path to the [Auxiliary File (.vaux)](#auxiliary-input-file-.vaux).
</div>
###Controls
......
Documentation/User Manual/1-user-interface/F_VEH-Editor.md
+ 40
− 15
View file @ 8cb1e630
......@@ -29,47 +29,71 @@ HDV Class
###Weight/Loading
These fields define the weight and loading of the vehicle. **Max. Loading** displays the maximum possible loading for the selected vehicle depending on curb weight and GVW values.
Curb Weight Vehicle
: Specifies the vehicle's weight without loading
***Note:*** *VECTO uses the sum of* ***Curb Weight Vehicle, Curb Weight Extra Trailer/Body*** *and* ***Loading*** *for calculation!*
<div class="engineering">
Curb Weight Extra Trailer/Body
: Specifies additional weight due to superstructures on the vehicle or an additional trailer
###Air Resistance
Loading
: Speciefies the loading of both, the vehicle and if available the trailer
</div>
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).
**Max. Loading** displays a hint for the maximum possible loading for the selected vehicle depending on curb weight and GVW values (without taking into account the loading capacity of an additional trailer).
***Note:*** *VECTO uses the sum of* ***Curb Weight Vehicle, Curb Weight Extra Trailer/Body*** *and* ***Loading*** *for calculation! The total weight is distributed to all defined axles according to the relative weight share.*
###Dynamic Tyre Radius
<div class="declaration">
In Declaration Mode only the vehicle itself needs to be specified. Depending on the vehicle category and mission the simulation adds a standard trailer for certain missions.
</div>
In [Engineering Mode](#engineering-mode) this defines the effective (dynamic) wheel radius (in [mm]) used to calculate engine speed. In [Declaration Mode](#declaration-mode) the radius calculated automatically using tyres/rims of the powered axle.
###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).**
###Cross Wind Correction Options
<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.
</div>
Four different options are available:
For cross wind correction four different options are available:
: - 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.
<div class="declaration">
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).
###Dynamic Tyre Radius
In [Engineering Mode](#engineering-mode) this defines the effective (dynamic) wheel radius (in [mm]) used to calculate engine speed. In [Declaration Mode](#declaration-mode) the radius calculated automatically using tyres of the powered axle.
###Axles/Wheels
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 class="engineering">
In Engineering mode, the **Wheels Inertia [kgm²]** has to be set per wheel for each axle.
The axles, for both truck and trailer, have to be given.
Use the ![](pics/plus-circle-icon.png) and ![](pics/minus-circle-icon.png) buttons to add or remove axles form the vehicle.
</div>
<div class="engineering">
In [Engineering Mode](#engineering-mode) all axles, for both truck and trailer, have to be given.
<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 weight-shares are added by Vecto automatically.
</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.
Doubleclick entries to edit existing axle configurations.
###Retarder Losses
......@@ -83,6 +107,7 @@ Four options are available:
Both, primary and secondary retarders, require an [Retarder Torque Loss Input File (.vrlm)](#retarder-loss-torque-input-file-.vrlm).
The Retarder Ratio defines the ratio between the engine speed/cardan shaft speed and the retarder.
###Angledrive
......@@ -90,7 +115,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) 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) (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
+ 9
− 2
View file @ 8cb1e630
......@@ -25,7 +25,7 @@ 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 depending on the engine's displacement and also accounts for the clutch's inertia.
: Inertia for rotating parts including engine flywheel. In [Declaration Mode](#declaration-mode) the inertia is calculated depending on the engine's displacement and also accounts for the clutch's inertia.
###Full Load and Drag Curves
......@@ -41,9 +41,16 @@ The input file (.vmap) file format is described [here](#fuel-consumption-map-.vm
###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 Cold/Hot Emission Balancing Factor is an additional correction factor that is used to correct the fuel consumption.
</div>
<div class="engineering">
In engineering a single correction factor for correcting WHTC, Cold/Hot Balancing, ... can be specified.
</div>
###Chart Area
......
Documentation/User Manual/1-user-interface/H_GBX-Editor.md
+ 27
− 31
View file @ 8cb1e630
......@@ -30,11 +30,13 @@ Transmission Type
: Depending on the transmission type some options below are not available. The following types are available:
: - **MT**: Manual Transmission
- **AMT**: Automated Manual Transmission
- **AT**: Automatic Transmission
- **Custom**
- **AT-S**: Automatic Transmission - Serial
- **AT-P** : Automatic Transmission - Power Split
: 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-model)
Inertia \[kgm²\]
: Rotational inertia of the gearbox (constant for all gears). (Engineering mode only)
......@@ -47,65 +49,59 @@ 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.
- **"TC"** (AT only) defines which gears are using the torque converter (lock-up clutch open).
- 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="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)!
- **"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)!
###Gear shift parameters
###Gear shift strategy parameters
![](pics/checkbox.png) Allow shift-up inside polygons
: See [Gear Shift Model](#gear-shift-model).
Since version Vecto 3.0.3 the gearshift polygon calculation according to the ACEA White Book 2016 is implemented and since Vecto 3.0.4 the ACEA White Book 2016 shift strategy for AMT and MT is implemented. For details on this topic please see the ACEA White Book 2016.
![](pics/checkbox.png) Skip Gears
: See [Gear Shift Model](#gear-shift-model).
![](pics/Vecto_ShiftStrategyParameters.png)
<div class="vecto3">
Since version Vecto 3.0.3 the gearshift polygon calculation according to the ACEA White Book 2016 is implemented and since Vecto 3.0.4 the ACEA White Book 2016 shift strategy for AMT and MT is implemented. For details on this topic please see the ACEA White Book 2016.
<div class="engineering">
The user interface contains input fields for the following parameters:
! - **Downshift after upshift delay**: to prevent frequent (oscilating) up-/down shifts this parameter blocks downshifts for a certain period after an upshift
: - **Downshift after upshift delay**: to prevent frequent (oscilating) up-/down shifts this parameter blocks downshifts for a certain period after an upshift
- **Upshift after downshift delay**: to prevent frequent (oscilating) up-/down shifts this parameter blocks upshifts for a certain period after a downshift
- **Min acceleration after upshift**: after an upshift the vehicle must be able to accelerate with at least the given acceleration. The achievable acceleration after an upshift is estimated on the current driving condition and powertrain state.
![](pics/Vecto_ShiftStrategyParameters.png)
</div>
Torque Reserve \[%\]
: This parameter is required for the **Allow shift-up inside polygons** and **Skip Gears** options.
Minimum shift time \[s\]
: 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>
: Limits the time between two gear shifts. This rule will be ignored if rpms are too high or too low.
Start Gear
: In order to calculate an appropriate gear for vehicle start (first gear after vehicle standstill) a fictional load case is calculated using a specified **reference vehicle speed** and **reference acceleration** together with the actual road gradient, transmission losses and auxiliary power demand. This way the start gear is independent from the target speed. VECTO uses the highest possible gear which provides the defined **torque reserve**.
###Chart Area
The Chart Area displays the [Shift Polygons Input File(.vgbs)](#shift-polygons-input-file-.vgbs) for the selected gear.
</div>
###Torque Converter
<div class="vecto2">
Torque converter characteristics file
: Defines the [Torque converter characteristics file](#torque-converter-characteristics-.vtcc) containing the torque ratio and reference torque over the speed ratio.
The [Torque Converter Model](#torque-converter-model) is still in development.
Reference RPM
: Defines the reference speed at which the torque converter characteristics file was measured.
Inertia \[kgm²\]
: Rotational inertia of the engine-side part of the torque converter.
(Gearbox-side inertia is not considered in VECTO.)
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](#at-gear-shift-strategy).
###Chart Area
The Chart Area displays the [Shift Polygons Input File(.vgbs)](#shift-polygons-input-file-.vgbs) as well as the declaration mode shift polygons (dashed lines) for the selected gear.
###Controls
......
Documentation/User Manual/1-user-interface/J_cmd.md deleted 100644 → 0
+ 0
− 41
View file @ 045eb410
##Command Line Arguments
![](pics/cmd.png)
It is possible to control basic functions of VECTO via command line arguments (e.g. to automate calculations and results analysis using scripts).
###General Notes
- The order in which the arguments are provided is free.
- If a file path includes space characters (e.g. "C:\\VECTO Test Files\\Demo.vecto") then double quotes have to be used (as in the picture above).
- If not the complete file path is defined (e.g. "file1.vecto" instead of "c:\\data\\file1.vecto") then VECTO expects the file in the application directory (where VECTO.exe is located).
- In the instructions below square brackets "\[ \]" indicate optional arguments.
###Standard Mode
VECTO.exe -run \[-close\] \[file1.vecto file2.vecto ... fileN.vecto\]
Runs calculation(s) either with the provided .vecto file(s) or (if no file names are defined) with the files already loaded on start up\*. If -**close** is used then VECTO closes after calculations are done.
###Batch Mode
VECTO.exe -run -batch \[-close\] \[file1.vecto file2.vecto ... fileN.vecto\] \[cycle1.vdri cycle2.vdri ... cycleN.vdri\]
Switches to BATCH mode and runs with the provided .vecto and .vdri files. If no files are defined the pre-loaded files\* are used. If -**close** is used then VECTO closes after calculations are done.
###Opening files
VECTO.exe file1.xxx
If the file has one of the following extensions it is opened with the associated editor dialog: .vecto, .vgbx, .veng, .vveh. Note: if more than one .vecto file is provided they will be loaded in the file list (replacing the pre-loaded list\*) instead.
*pre-loaded files: When VECTO starts it loads the file lists (.vecto, .vdri) of the last session, see [Application Files](#application-files). These files can be changes manually if VECTO is not running.
Documentation/User Manual/1-user-interface/K0_VECTO-AdvancedAux.md
+ 1
− 1
View file @ 8cb1e630
......@@ -28,7 +28,7 @@ The Advance Auxiliaries Editor contains four tabs/sub-modules where the differen
###Important notes
Note that the cycle file name used should ideally respect the following syntax to be correctly associated with the pneumatic actuations map (.apac), otherwise the number of actuations will be set at 0 by default:
Note that the cycle file name used should ideally respect the following syntax to be correctly associated with the pneumatic actuations map (.apac), otherwise the number of actuations will be set to 0 by default:
- "AnyOtherText _X_Bus.vdri", with "X" = "Urban", "Heavy urban", “Suburban", or "Interurban"
- "AnyOtherText_Coach.vdri"
......
Documentation/User Manual/2-calculation-modes/batch.md deleted 100644 → 0
+ 0
− 22
View file @ 045eb410
##Batch Mode
<div class="vecto2">
In Batch Mode a list of vehicles is run with a list of driving cycles. Each vehicle defined in the Job List is calculated with each driving cycle defined in the Driving Cycle List. Note that the Driving Cycle List is only visible if Batch Mode is enabled in the Main Form / Options Tab.
###Requirements
- One or more checked job files in the Job List. The job files don't need to include driving cycles. These are ignored in Batch mode.
- One or more checked driving cycles in the Dricing Cycle List
###Results
- Modal results (.vmod) for each job file and driving cycle. One file for each vehicle/cycle combination.
- Average/sum results (.vsum / .vsum.json). One file in total containing results for each vehicle/cycle combination.
</div>
<div class="vecto3">
VECTO V3.x doesn't support Batch mode anymore. The same functionality can be achieved by referencing every needed cycle file in the job files.
</div>
Documentation/User Manual/2-calculation-modes/calculation-modes.md
+ 1
− 12
View file @ 8cb1e630
......@@ -14,15 +14,4 @@ VECTO supports different calculation modes for declaring a vehicle, validation o
In the GUI the Calculation Mode can be changed via the Options Tab of the [Main Form](#main-form).
In the Command Line the Calculation Mode is Declaration by default, but can be changed to Engineering with the "-eng" flag.
<div class="vecto2">
A so called [Batch Mode](#batch-mode) exists in VECTO v2.2, which simulates every given job file with every given cycle file. This has nothing to do with the command line, it is just a convenience function to combine job files and cycle files.
</div>
<div class="vecto3">
VECTO V3.x doesn't support Batch mode anymore. The same functionality can be achieved by referencing every needed cycle file in the job files.
</div>
In the Command Line the default Calculation Mode is Declaration, but can be changed to Engineering with the "-eng" flag.
Documentation/User Manual/2-calculation-modes/engineering.md
+ 3
− 12
View file @ 8cb1e630
##Engineering Mode
The Engineering Mode lets the user define every aspect in the components of the vehicle and the driving cycle. This is for experimenting and validation purposes.
The Engineering Mode lets the user define every aspect in the component models of the vehicle and the driving cycle. This is for experimenting and validation purposes.
In this mode the given list of job files is simulated with the respective driving cycles. Each job file defines a separate vehicle.
<div class="vecto2">
This is the default calculation mode in VECTO V2.
</div>
<div class="vecto3">
In VectoCMD V3.x the default mode is Declaration Mode.
</div>
###Requirements
......@@ -18,7 +12,7 @@ In VectoCMD V3.x the default mode is Declaration Mode.
###Results
- Modal results (.vmod). One file for each vehicle/cycle combination.
- Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
- Sum results (.vsum). One file for each invocation of VECTO.
......@@ -34,7 +28,4 @@ The Driving Cycle determines the simulation method in engineering mode. The opti
* [Pwheel (SiCo) Mode, time-based](#engineering-mode-pwheel-sico-time-based)
: In Pwheel mode the measured power at the wheels is given, and the simulation takes that as input.
**Note:** Time-based driving cycles support arbitrary time steps. However, certain actions are simulated within a single simulation interval (e.g. closing the clutch after a gear switch) and may thus result in artefacts during the simulation due to engine inertia, gearbox inertia, etc. Thus **the suggested minimum time interval for time-based cycles is 0.5s!**
Documentation/User Manual/3-simulation-models/ADAS_EcoRoll.md
+ 1
− 11
View file @ 8cb1e630
......@@ -23,15 +23,5 @@ 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.
Eco-Roll is not implemented in Vecto 3.1.
![](pics/EcoRoll.svg)
*Example of Eco-Roll. Target (purple) and actual speed (orange) on the top left axis, slope (brown) on the top right axis. The bottom graph shows engine power (blue), motoring curve (orange) and mechanical brake power (green). The engine is idling while the vehicle rolls freely and braking when the upper speed limit is reached.*
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
Documentation/User Manual/3-simulation-models/Auxiliaries.md
+ 10
− 5
View file @ 8cb1e630
##Auxiliaries
<div class="declaration">
In Declaration mode the auxiliaries are pre-defined and the power demand is defined based on the vehicle category and mission. For every type of auxiliary (fan, steering pump, HVAC, electrig system, pneumatic system) the user can select a technology from a given list.
</div>
In VECTO a generic map-based approach was implemented to consider all types of auxiliaries. The supply power demand for each single auxiliary is defined in the driving cycle. Hence a time/distance-dependent power demand can be defined. Based on the supply power and a pre-defined efficiency map the auxiliary input power is calculated. A constant efficiency determines the losses between auxiliary and engine.
<div class="engineering">
In Engineering mode VECTO uses a generic map-based approach to consider all types of auxiliaries. The supply power demand for each single auxiliary is defined in the driving cycle. Hence a time/distance-dependent power demand can be defined. Based on the supply power and a pre-defined efficiency map the auxiliary input power is calculated. A constant efficiency determines the losses between auxiliary and engine.
For each auxiliary the power demand is calculated using the following steps:
......@@ -18,7 +21,7 @@ For each auxiliary the power demand is calculated using the following steps:
5. **P~aux~ is added to the engine's power demand**
6. **P~supply~ is defined in the driving cycle
| | | |
......@@ -38,9 +41,11 @@ 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 *"&lt;Aux\_ID&gt;"*.
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 *"&lt;Aux\_ID&gt;"*.
***Example:*** *The Auxiliary with the ID "ALT" (in the Job File) is linked to the supply power in the column "&lt;Aux\_ALT&gt;" in the driving cylce.*
In addition to the generic map-based auxiliaries approach it is also possible to specify a constant load applied to the engine during the whole mission.
***Example:*** *The Auxiliary with the ID "ALT" (in the Job File) is linked to the supply power in the column "&lt;Aux\_ALT&gt;" in the driving cylce.*
</div>
\ No newline at end of file
Documentation/User Manual/3-simulation-models/Engine_DynamicFullLoad.md
+ 2
− 9
View file @ 8cb1e630
##Engine: Transient Full Load
The engine implements a PT1 behaviour to model transient torque build up.
<div class="vecto2">
VECTO 2 uses a PT1 function to model transient torque build up using this formula:
The engine implements a PT1 behaviour to model transient torque build up:
$P_{fld\ dyn_{i}} = \frac{1}{T(n_{i})+1} \cdot \left(P_{fld\ stat}(n_{i})+T(n_{i}) \cdot P_{act_{i-1}}\right)$
......@@ -14,9 +10,8 @@ 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 \left(1 - e^{-\frac{t_i^*}{\mathit{PT1}}}\right)$
......@@ -29,5 +24,3 @@ $t_{i-1}^* = \mathit{PT1} \cdot ln\left(\frac{1}{1 - \frac{P_{eng_{i - 1}}}{P_{f
</div>
Documentation/User Manual/3-simulation-models/Engine_FC.md
+ 0
− 10
View file @ 8cb1e630
......@@ -25,15 +25,5 @@ The interpolation is based on [Delaunay Triangulation ![](pics/external-icon%20
*Delaunay Triangulation Example*
###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).
2. From the difference between the energy consumed by the auxiliaries in the simulation with Start/Stop function and the target value (unit kilowatt-hours), a cycle average change in mechanical power “ΔPe” (unit kilowatt) of the internal combustion engine is calculated (using an average alternator efficiency and the cycle time with running engine).
3. The correction of the fuel consumption is performed for all 1Hz time steps using: ΔFC (unit: grams per hour) = ΔPe \* k where k = gradient in the regression. If the engine is running in motoring conditions ΔFC is set to zero.
![Example of a linear regression between engine power and fuel consumption](pics/StartStopCorrection.svg)
</div>
Documentation/User Manual/3-simulation-models/Engine_StartStop.md
+ 1
− 17
View file @ 8cb1e630
##Engine Start/Stop
<div class="vecto2">
If enabled the engine will be turned off after the set **Activation Delay \[s\] **if the following conditions apply:
- Power demand ≤ 0
- Vehicle speed is below **Max Speed \[km/h\]**
- Engine was running for at least **Min ICE-On Time \[s\]**
**Parameters in [Job File](#job-file):**
- **Max speed \[km/h\]**.
- **Min ICE-On Time \[s\]**
- **Activation Delay \[s\]**
If Start/Stop is enabled the fuel consumption is corrected for not-considered auxiliary energy consumption during engine stop. See [Start/Stop FC Correction](#fuel-consumption-calculation).
</div>
\ No newline at end of file
Eco-Roll is not implemented in Vecto 3.1.
\ No newline at end of file
Documentation/User Manual/3-simulation-models/Engine_WHTC.md
+ 6
− 3
View file @ 8cb1e630
......@@ -26,10 +26,13 @@ with the correction factor CF~urb~, CF~rur~, CF~mot~ coming from the [Engine](#e
| Interurban bus | 45% | 36% | 19% |
| Coach | 0% | 22% | 78% |
The whtc fuel consumption is then calculated with: $FC_{whtc} = FC \cdot CF_{total}$
In order to balance the trade-off between emissions and fuel consumption during cold and hot starting conditions an additional balancing factor $CF_{C/H}$ is determined from the overall specific fuel consumption over the cold start and hot start WHTC test. This value is part of the output from the engine component tool.
The WHTC-corrected fuel consumption is then calculated with: $FC_{whtc} = FC \cdot CF_{total} \cdot CF_{C/H}$
</div>
<div class="engineering">
In engineering mode no WHTC correction is applied by Vecto. For an arbitrary cycle the weighting factors are not known, hence the total correction factor CF~total~ can not be computed.
WHTC correction can be applied manually as a post-processing step.
In engineering mode a single correction is applied by Vecto. The fuel consumption interpolated from the FC map is multiplied by the engineering correction factor.
$FC_{whtc} = FC \cdot CF_{Engineering}$
</div>
\ No newline at end of file
Documentation/User Manual/3-simulation-models/GearShift.md
+ 5
− 6
View file @ 8cb1e630
##Gear Shift Model
##Gear Shift Model (MT, AMT)
The Gear Shift Model is based on shift curves that define the engine speed for up- and down- shifting as a function of engine torque. As soon as the engine operation point passes one of the shift curves a gear change is initiated.
......@@ -34,21 +33,21 @@ In the Gearbox File two additional parameters are defined:
###Gear Skipping
Gear Skipping can be enabled in the [Gearbox File](#gearbox-file). By default it is enabled for AMT and MT. Whenever a gear change is initiated (by crossing the up- or down-shift line) VECTO may skip one or several gears as long as the required torque reserve is provided.
Gear Skipping is active for AMT and MT. Whenever a gear change is initiated (by crossing the up- or down-shift line) VECTO may skip one or several gears as long as the required torque reserve is provided.
![](pics/GBX-Editor-shift3.svg)
###Early Upshift
Early Upshift can be enabled in the [Gearbox File](#gearbox-file) (Allow shift-up inside polygons). By default it is enabled for AMT only. If the next higher gear provides the required torque reserve and it's rpm is still above down-shift-rpm VECTO will shift up.
Early Upshift (allow upshifts inside the shift polygons) is enabled for AMT only. If the next higher gear provides the required torque reserve and it's rpm is still above down-shift-rpm VECTO will shift up.
![](pics/GBX-Editor-shift2.svg)
###Generic shift conditions (extra conditions)
###Generic shift conditions
- Only allow upshifts if the vehicle is not decelerating **and** the calculated (estimated) acceleration in the next gear is higher than a certain value (default: 0.1 m/s²)
- Only allow upshifts if the vehicle is not decelerating **and** the estimated acceleration in the next gear is higher than a certain threshold (default: 0.1 m/s²)
- Do not allow downshifts with less time than a certain amount after an upshift (default 10 s)
- Do not allow upshifts with less time than a certain amount after an downshift (default 10 s)
......
Documentation/User Manual/3-simulation-models/TC.md
+ 7
− 27
View file @ 8cb1e630
##Torque Converter Model
**!!! The Torque Converter Model is still in development and at the moment only available in Vecto 2.2 !!!**
The torque converter is defined as (virtual) separate gear. Independent of the chosen AT gearbox type (serial or power split), Vecto uses a powertrain architecture with a serial torque converter. The mechanical gear ratios and gears with torque converter are created by Vecto depending on the gearbox type and gear configuration.
<div class="vecto2">
The torque converter is defined as (virtual) separate gear. While TC active: Iterative calculation of engine torque and speed based on TC characteristic. Creeping: Engine speed set to idling. Brakes engaged to absorb surplus torque.
While the torque converter is active engine torque and speed are computed based on TC characteristic.
![](pics/GBX-TC.svg)
......@@ -22,36 +21,17 @@ The Input Torque at  reference engine speed is needed to calculate the actual e
$T_{in} = T_{ref}(v) \cdot ( \frac{n_{in}}{n_{ref}} )^{2}$
$μ(ν) = \frac{T_{out}}{T_{in}}$
with:
- T~in~ = engine torque \[Nm\]
- T~ref(ν)~ = reference torque at reference rpm (form .vtcc file) \[Nm\]
- T~ref(ν)~ = reference torque at reference rpm (from .vtcc file) \[Nm\]
- n~in~ = engine speed \[1/min\]
- n~ref~ = reference rpm \[1/min\] (see below)
The torque converter characteristics must also be defined for speed ratios of more than one (ν&gt;1) in order to calculate overrun conditions (torque&lt;0).
###Setup for Conventional AT gearboxes
Torque converter file is defined for **torque converter only**
![](pics/GBX-TC-Setup-1-1.svg)
- Define TC gear with ratio of first (mechanical) gear
- Set transmission losses of first gear (map or constant efficiency)
![](pics/GBX-TC-Setup-1-2.svg)
###Setup for Power-distributed AT gearboxes
Torque converter file is defined for the **whole gearbox**
![](pics/GBX-TC-Setup-2-1.svg)
The torque converter characteristics must also be defined for speed ratios of greater than one (ν&gt;1) in order to calculate overrun conditions or engine drag (torque&lt;0).
- Define TC gear with ratio = 1
- Set transmission efficiency to 1 (= 100%) because losses are covered by the .vtcc file.
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.
![](pics/GBX-TC-Setup-2-2.svg)
</div>
\ No newline at end of file
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

For further information about the platform and support, please see https://code.europa.eu/info/about