User Manual

VECTO 2.2

User Interface

When VECTO starts the Main Form is loaded. Closing this form will close VECTO even if other dialogs are still open.

Main Form

Description

The Main Form is loaded when starting VECTO. Closing this form will close VECTO even if other dialogs are still open. In this form all global settings can be controlled and all other application dialogs can be opened.

In order to start a calculation the Calculation Mode must be set and at least one Job File (.vecto) 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:
  • Job Files Tab
  • Driving Cycles Tab (only if Batch Mode is enabled)
  • Options Tab

Job Files Tab

Job Files List

Job files (.vecto) listed here will be used for calculation. Unchecked files will be ignored! Doubleclick entries to edit job files with the VECTO Editor.

cb All
(Un-)Check all files in Job List. Only checked files are calculated when clicking START.

add Add files to Job List

remove Remove selected files from List

updown Move selected files up or down in list

List Options

  • Save/Load List
    • Save or load Job List to text file
  • Load Autosave-List
    • The Autosave-List is saved automatically on application exit and calculation start
  • Clear List
    • Remove all files from Job List
  • Remove Paths
    • Remove paths, i.e. only file names remain using the Working Directory as source path.

START START Button

Start VECTO in the selected mode (see Options).

Driving Cycles Tab

Driving Cycle List
The Driving Cycles List is only used in Batch Mode. The same controls are used as in the Job Files List.

Options Tab

In this tab the global calculation settings can be changed.

Declaration Mode
Enable or disable Declaration Mode
Batch Mode
If Declaration Mode is disabled VECTO can be run in Batch Mode.
cb 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) are always converted to time-based cycles internally)
cb 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).
cb Write modal results
Toggle output of modal results (.vmod files). Summary files (.vsum, .vres) are always created.
cb 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 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.

Controls

new New Job File
Create a new .vecto file using the VECTO Editor
open Open existing Job or Input File
Open an existing input file (Job, Engine, etc.)

tools Tools

info Help

Message List
All messages, warnings and errors are displayed here and written to the log file LOG.txt in the VECTO application folder. Depending on the colour the following message types are displayed:

Note that the message log can be opened in the Tools menu with Open Log.

Statusbar
Displays current status and progress of running calculations. When no calculation is running the current mode is displayed (Standard, Batch or Declaration Mode).

Settings

Description

In the Settings dialog controls general application settings. The settings are saved in the settings.json file.

Interface Settings

Logfile Size Limit [MB]
Whenever the Log File reaches this size it will be restarted. One backup is always stored as LOG_backup.txt.
File Open Command
This command will be used to open CSV Input Files like Driving Cycles (.vdri). See: Run command
Name: Name of the command as it will be shown in the menu when clicking the button.
Command: The actual command.

Example : If the command is excel and the file is C:\VECTO\cycle1.vdri then VECTO will run: excel “C:\VECTO\cycle1.vdri”

Calculation Settings

Air Density [kg/m³]
The Air Density is needed to calculate the air resistance together with the Drag Coefficient and the Cross Sectional Area (see Vehicle Editor).
Fuel Density [kg/l]
The Fuel Density is used to calculate the l/km results.
CO2 -to-Fuel Ratio[-]
Mass ratio (kgCO2 / kgFC) used to calculate CO2 emissions.

Controls

Reset All Settings
All values in the Settings dialog and Options Tab of the Main Form will be restored to default values.

Save and close dialog

Close without saving

Job Editor

Description

The job file (.vecto) 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:

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.

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

General Settings

Engine Only Mode

Enables Engine Only Mode. Only the following parameters are needed for this mode:

Filepath to the Vehicle File (.vveh)
Files can be created and edited using the Vehicle Editor.
Filepath to the Engine File (.veng)
Files can be created and edited using the Engine Editor.
Filepath ot the Gearbox File(.vgbx)
Files can be created and edited using the Gearbox Editor.
Auxiliaries
This list contains all auxiliaries used for calculation. The auxiliaries are configured using the Auxiliary Dialog. For each auxiliary an Auxiliary Input File (.vaux) must be provided and the driving cycle must include the corresponding supply power. Double-click entries to edit with the Auxiliary Dialog.

addaux Add new Auxiliary

remaux Remove the selected Auxiliary from the list

See Auxiliaries for details.

Cycles
List of cycles used for calculation. The .vdri format is described here. Double-click an entry to open the file (see File Open Command). Click selected items to edit file paths.

addcycle Add cycle (.vdri)

remcycle Remove the selected cycle from the list

Driver Assist Tab

In this tab the driver assistance functions are enabled and parameterised.

Engine Start/Stop
See Engine Start/Stop for details.
Overspeed / Eco-Roll
See Overspeed / Eco-Roll for details.
Look-Ahead Coasting
See Look-Ahead Coasting for details.
Acceleration Limiting
See Acceleration Limiting for details.

Chart Area

If a valid Vehicle File, Engine File and 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 the generic shift polygons are shown, not the ones from the Gearbox File.

Controls

new New Job File
Create a new empty .vecto file
open Open existing Job File
Open an existing .vecto file

save Save current Job File

SaveAs Save Job File as…

sendto Send current file to Job List in Main Form
Note: The file will be sent to the Job List automatically when saved.

veh Open Vehicle Editor

eng Open Engine Editor

gbx Open Gearbox Editor

Browse for vehicle/engine/gearbox files

OK Save and close file
File will be added to Job List in the Main Form.

Cancel Cancel without saving

Auxiliary Dialog

Description

The Auxiliary Dialog is used to configure auxiliaries. Auxiliary efficieny is defined using an Auxiliary Input File (.vaux). See Auxiliaries for details on how the power demand for each auxiliary is calculated.

In Declaration Mode only the Technology for each auxiliary has to be selected.

Settings

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 “<AUX_ALT>” in the driving cylce. See Auxiliaries for details.
Input File
Path to the Auxiliary File (.vaux).

Controls

ok Save and close

cancel Close without saving

Vehicle Editor

Description

The Vehicle File (.vveh) defines the main vehicle/chassis parameters like axles including RRCs, air resistance and weight.

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: “Demo1.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.)

General vehicle parameters

Vehicle Category
Needed for Declaration Mode to identify the HDV Class.
Axle Configuration
Needed for Declaration Mode to identify the HDV Class.
Gross Vehicle Mass Rating [t]
Needed for Declaration Mode to identify the HDV Class.
HDV Class
Displays the automatically selected HDV Class depending on the settings above.

Weight/Loading

These fields define the weight and loading of the vehicle. Max. Loading displayes the maximum possible loading for the selected vehicle depending on curb weight and GVW values.

Note: VECTO uses the sum of Curb Weight Vehicle, Curb Weight Extra Trailer/Body and Loading for calculation!

Air Resistance

The product of Drag Coefficient [-] and Cross Sectional Area [m²] (cd x A) and Air Density [kg/m³] (see Settings) together with the vehicle speed defines the Air Resistance. Note that the Drag Coefficient may be altered when using Cross Wind Correction.

Axles/Wheels

For each axle the parameters Relative axle load, RRCISO and FzISO have to be defined in order to calculate the total Rolling Resistance Coefficient. Furthermore the Wheels Inertia [kgm²] has to be set per wheel for each axle. In Declaration Mode the inertia is defined automatically according to the selected tyres. Use the and buttons to add or remove axles form the vehicle. Doubleclick entries to edit existing axle configurations.

Dynamic Tyre Radius [mm]
Effective (dynamic) wheel radius used to calculate engine speed. In Declaration Mode the radius calculated automatically using tyres/rims of the powered axle.
Powered axle tyres/rims
Needed for Declaration Mode to calculate the dynamic tyre radius.

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!

Three options are available:
  • None
  • Primary (before gearbox): The rpm ratio is relative to the engine speed
  • Secondary (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).

Cross Wind Correction

Three different options are available:
  • No Correction
  • Speed dependent (User-defined)
  • Speed dependent (Declaration Mode)
  • Vair & Beta Input

Depending on the chosen mode either a Speed Dependent Cross Wind Correction Input File (.vcdv) or a Vair & Beta Cross Wind Correction Input File (.vcdb) must be defined. For details see Cross Wind Correction.

Controls

New file
Create a new empty .vveh file
Open existing file
Open an existing .vveh file

Save current file

Save file as…

Send current file to the VECTO Editor
Note: If the current file was opened via the VECTO Editor the file will be sent automatically when saved.
Save and close file
If necessary the file path in the VECTO Editor will be updated.

Cancel without saving

Engine Editor

Description

The Engine File (.veng) defines all engine-related parameters and input files like Fuel Consumption Map and Full Load Curves.

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: “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.)

Main Engine Parameters

Make and Model
Free text defining the engine model, type, etc.
Idling Engine Speed [rpm]
Low idle, applied in simulation for vehicle standstill in neutral gear position.
Displacement [ccm]
Used in Declaration Mode to calculate inertia.
Inertia including Flywheel [kgm²]
Inertia for rotating parts including engine flywheel. In Declaration Mode the inertia is calculated automatically.

Full Load and Drag Curves

The Full Load and Drag Curves (.vfld) Note that gear-specific full load curves can be defined in the Gearbox File to limit the maximum gearbox input torque.

The input file (.vfld) file format is described here.

Fuel Consumption Map

The Fuel Consumption Map is used to calculate the base FC value. See Fuel Consumption Calculation for details.

The input file (.vmap) file format is described here.

WHTC Correction Factors

The WHTC Corretion Factors are required in Declaration Mode for the WHTC FC Correction.

Chart Area

The Chart Area shows the fuel consumption map and the selected full load curve.

Controls

newNew file
Create a new empty .veng file
openOpen existing file
Open an existing .veng file

saveSave current file

SaveAsSave file as…

sendtoSend current file to the VECTO Editor
Note: If the current file was opened via the VECTO Editor the file will be sent automatically when saved.

Open file (see File Open Command).

OKSave and close file
If necessary the file path in the VECTO Editor will be updated.

CancelCancel without saving

Gearbox Editor

Description

The Gearbox File (.vgbx) defines alls gearbox-related input parameters like gear ratios and transmission loss maps. See Gear Shift Model for details.

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: “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.)

Main Gearbox Parameters

Make and Model
Free text defining the gearbox model, type, etc.
Transmission Type
Depending on the transmission type some options below are not available.The following types are available:
  • Manual Transmission (MT)
  • Automated Manual Transmission (AMT)
  • Automatic Transmission (AT)
  • Custom
Note: The types AT and Custom are not available in Declaration Mode.
Inertia [kgm²]
Rotational inertia of the gearbox (constant for all gears).
Traction Interruption [s]
Interruption during gear shift event.

Gears

Use the add and remove buttons to add or remove gears form the vehicle. Doubleclick entries to edit existing gears.

Gear shift parameters

Allow shift-up inside polygons
See Gear Shift Model.
Skip Gears
See Gear Shift Model.
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 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.
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) for the selected gear.

Torque Converter

The Torque Converter Model is still in development.

Inertia [kgm²]
Rotational inertia of the engine-side part of the torque converter. (Gearbox-side inertia is not considered in VECTO.)

Controls

New file
Create a new empty .vgbx file
openOpen existing file
Open an existing .vgbx file

save Save current file

SaveAs Save file as…

sendto Send current file to the VECTO Editor
Note: If the current file was opened via the VECTO Editor the file will be sentautomatically when saved.

Open file browser

Open file (see File Open Command).

OK Save and close file
If necessary the file path in the VECTO Editor will be updated.

Cancel Cancel without saving

Graph Window

Description

The Graph Window allows to visualise modal results files (.vmod). Multiple windows can be open at the same time to display different files.

Note that the graph does not update automatically if the results file has changed.

Channels

Use the add and remove buttons to add or remove channels. Doubleclick entries to edit existing channels.

Each channel can be plotted either on the left or on the right Y Axis. Use the checkbox to disable channels in the graph.

X Axis Controls

The X Axis can either show distance or time.

Min, Max
Sets the range for the x axis.
Reset button
Reset the x axis range to display the complete cycle.
+, - buttons
Zoom in/out on the x axis.
<, > buttons
Move the x axis range left/right.

Controls

open Open a .vmod file

Open a new Graph Window

Reload the currently open file

Calculation Modes

The Calculation Mode can be changed in the Options Tab of the Main Form. VECTO is running in Standard Mode when Batch Mode and Declaration Mode is disabled.

Note that Engine Only Mode is not an actual calculation mode and can be set for each Job File individually and used in Standard and Batch Mode.

Standard Mode

This is the default calculation mode in VECTO. It is active when both Batch and Declaration Mode are disabled. In this mode a predefined list of job files (.vecto) is run. Each job file defines a vehicle and a list of driving cycles.

Requirements

Results

Batch Mode

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

Results

Declaration Mode

In Declaration Mode all input parameters that are not user-defined in official certification are locked in the user interface and automatically defined by VECTO during calculation. Calculations will be performed for each mission profile (of the corresponding HDV class) with three different loadings each: Empty, full and with reference loading. 

Declaration Mode can be activated in the Options Tab.

Requirements

Results

Acceleration Limiting

VECTO limits the vehicle acceleration and deceleration according to speed-dependent limits. These limits are defined in the Acceleration Limiting Input File (.vacc). Note that the full load curve also limits acceleration. If the engine cannot provide the required power the vehicle might accelerate below the defined acceleration limit.

This function cannot be disabled. If acceleration and/or deceleration should not be limited during calculation the values in the Acceleration Limiting file (.vacc) have to be changed accordingly.

Parameters in Job File:

The input file format is described here.

Auxiliaries

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.

For each auxiliary the power demand is calculated using the following steps:

  1. Auxiliary speed: naux = nEng * TransRatio

  2. Auxiliary output power: PauxOut = Psupply/EffToSply

  3. Auxiliary input power: PauxIn = EffMap(nAux, PAuxOut)

  4. Auxiliary power consumption: Paux = PauxIn/EffToEng

  5. Paux is added to the engine’s power demand

nEng Calculated engine speed. [1/min]
TransRatio Speed ratio between auxiliary and engine. Defined in the Auxiliary File. [-]
naux Auxiliary speed [1/min]
Psupply Effective supply power demand. Defined in the driving cycle. [kW]
EffToSply Consumer efficiency. Defined in the Auxiliary File. [-]
PauxOut Auxiliary output power [kW]
EffMap Auxiliary efficiency map. Defined in the Auxiliary File. [kW] = f( [1/min], [kW] )
PauxIn Auxiliary input power [kW]
EffToEng Efficiency of auxiliary (belt/gear) drive. Defined in the Auxiliary File. [-]
Paux Mechanical auxiliary power demand at the crank shaft [kW]

Each auxiliary must be defined in the Job File and each driving cycle 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.

Cross Wind Correction

VECTO offers two different modes to consider cross wind influence on the drag coefficient. It is configured in the Vehicle File.

Speed dependent correction (Declaration Mode)

This is the default mode which is used in Declaration Mode. The speed dependent cd x A curve (see below) is calculated based on generic parameters for each vehicle class and the base cd x A value form the Vehicle File.

Speed dependent correction (User-defined)

The base cd x A value (see Vehicle File) is corrected with a user-defined speed dependent scaling function. The input file (.vcdv) format is described here.

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. The driving cycle must include the air speed relative to vehicle (<vair_res>) and the wind yaw angle (<vair_beta>).

Overspeed / Eco-Roll

Both functions control the vehicle’s behaviour on uneven road sections (slope ≠ 0) and can be configured in the Job File’s Driver Assist Tab. Overspeed is designed to model an average driver’s behaviour without the aid of driver assistance systems. Eco-Roll  represents an optional driver assistance feature. For this reason vehicles without Eco-Roll should always have the Overspeed function enabled.

Overspeed

Overspeed activates as soon as the total power demand at the wheels (Pwheel) falls below zero, i.e. the vehicle accelerates on a negative slope. The clutch remains closed, engine in motoring operation, and the vehicle accelerates beyond the cycle’s target speed. When the speed limit (target speed plus Max. Overspeed) is reached the mechanical brakes are engaged to prevent further acceleration.

Example with 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). In this example Overspeed is allowed until the vehicle’s speed exceeds target speed by 5 [km/h].

Parameters in Job File:
  • Minimum speed [km/h]. Below this speed the function is disabled.
  • Max. Overspeed [km/h] (relative to target speed)

Eco-Roll

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.

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:
  • 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)

Engine Only Mode

When this mode is enabled in the Job File then VECTO only calculates the fuel consumption based on a load cycle (engine speed and torque). In the Job File only the following parameters are needed:

The driving cylce (.vdri) must contain:

Note that VECTO adds the engine’s inertia to the given power demand!

Example .vdri cycle:

Engine Start/Stop

If enabled the engine will be turned off after the set Activation Delay [s] if the following conditions apply:

Parameters in 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

The base FC value is interpolated from the stationary FC map. If necessary the base value is corrected to compensate for unconsidered auxiliary energy consumption for vehicles with Start/Stop. In Declaration Mode additionally the WHTC correction is applied, see below.

The CO2 result for the actual mission profile is directly derived from the fuel consumption using a gravimetric CO2/FC factor.

Fuel Map Interpolation

The interpolation is based on 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 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 be aborted.
  3. Calculate the z-value (= fuel) of the given x,y-point in the plane of the triangle

Delaunay Triangulation Example

Auxiliary - Start/Stop Correction

For vehicles with Start/Stop 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

WHTC Correction

The WHTC correction aims to counter the disadvantages of using a stationary FC map. The following steps are applied in VECTO for the WHTC correction method:

  1. VECTO interpolates the fuel consumption for the WHTC load cycle from the engine fuel map based on the target speed and target torque as determined based on the engine full-load curve. The results are FC values for the Urban, Rural and Motorway part.
  2. The correction factor CFWHTC is calculated using the equation below considering the current mission profile’s weighting factors for each part.
  3. The factor is multiplied to the FC values for each time step and the total FC result.

\(CF_{WHTC} = \sum_{i=1}^{3} f_i \cdot \frac{FC_{meas_i}}{FC_{calc_i}}[-]\)

where:

 \(CF_{WHTC}\)    WHTC Correction Factor [-]
 \(i\)       index for each part (Urban, Rural, Motorway) [-]
 \(f_i\)        Weighting factor per part [-]
 \(FC_{meas_i}\)    WHTC measurement result per part (input parameter) [g/kWh]
 \(FC_{calc_i}\)        Calculated FC per part [g/kWh]

Gear Shift Model

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.

Example shift polygons

The shift polygons are saved in the Shift Polygons Input File (.vgbs) and have to be added to the Gearbox File.  

In 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 the Gearbox File two additional parameters are defined:

Gear Skipping

Gear Skipping can be enabled in the 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.

Early Upshift

Early Upshift can be enabled in the 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.

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.

The implemented approach uses a predefined target deceleration (alookahead) to calculate the deceleration time for each particular target speed change.

At the resulting deceleration start point the model calculates the coasting trajectory until it meets the brake deceleration trajectory. The resulting deceleration consists of a coasting phase followed by combined mechanical/engine braking. If Look-Ahead Coasting is disabled only the braking phase according to the deceleration limit will be applied.

Parameters in Job File:
  • Target Retardation = alookahead
  • Minimum speed. Below this speed the function is disabled.

Overspeed / Eco-Roll

Both functions control the vehicle’s behaviour on uneven road sections (slope ≠ 0) and can be configured in the Job File’s Driver Assist Tab. Overspeed is designed to model an average driver’s behaviour without the aid of driver assistance systems. Eco-Roll  represents an optional driver assistance feature. For this reason vehicles without Eco-Roll should always have the Overspeed function enabled.

Overspeed

Overspeed activates as soon as the total power demand at the wheels (Pwheel) falls below zero, i.e. the vehicle accelerates on a negative slope. The clutch remains closed, engine in motoring operation, and the vehicle accelerates beyond the cycle’s target speed. When the speed limit (target speed plus Max. Overspeed) is reached the mechanical brakes are engaged to prevent further acceleration.

Example with 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). In this example Overspeed is allowed until the vehicle’s speed exceeds target speed by 5 [km/h].

Parameters in Job File:
  • Minimum speed [km/h]. Below this speed the function is disabled.
  • Max. Overspeed [km/h] (relative to target speed)

Eco-Roll

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.

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:
  • 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)

Pwheel-Input (SiCo Mode)

For verification tasks it is possible to manually input the power at wheels (Pwheel) 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 Pwheel, Gear and Engine Speed are defined in the driving cycle.

Requirements

Example driving cylce with Pwheel input.

<t> <Pwheel> <Gear> <n>
1 0.0 0 560.0
2 0.0 0 560.0
3 14.0 1 593.2
4 51.9 1 705.5
5 60.0 2 690.0
6 85.6 2 868.4
7 92.0 3 820.0
8 112.3 3 897.6

Rolling Resistance Coefficient

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

\(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}\)

RRC [-] Total rolling resistance coefficient used for calculation
s(i) [-] Relative axle load. Defined in the Vehicle File.
RRCISO(i) [-] …Tyre RRC according to ISO 28580. Defined in the Vehicle File.
m [kg] Vehicle mass plus loading.
g [m/s²] Earth gravity acceleration (constant = 9.81)
w(i) [-] Number of tyres (4 if Twin Tyres, else 2). Defined in the Vehicle File.
FzISO(i) [N] Tyre test load according to ISO 28580 (85% of max. load capacity). Defined in the Vehicle File.
β [-] Constant parameter = 0.9

For each axle the parameters Relative axle load, RRCISO and FzISO have to be defined. Axles with twin tyres have to be marked using the respective checkbox in the Vehicle-Editor.

Torque Converter Model

!!! The Torque Converter Model is still in development !!!

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.

Torque converter characteristics file (.vtcc)

The file is described here.

Setup for Conventional AT gearboxes 

Torque converter file is defined for torque converter only

Setup for Power-distributed AT gearboxes

Torque converter file is defined for the whole gearbox

Transient Full Load

VECTO uses a PT1 function to model transient torque build up using this formula:

\(P_{fld\ dyn_{i}} = \frac{1}{T(n_{i})+1} \cdot [P_{fld\ stat}(n_{i})+T(n_{i}) \cdot P_{act_{i-1}}]\)

where:

ni current engine speed
T(ni) PT1 time constant at engine speed ni (col. 4 in .vfld file)
P_fld_stat(ni) Static full load at engine speed ni (col. 2 in .vfld file)
P_acti-1 Engine power in previous time step

Command Line Arguments

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

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. These files can be changes manually if VECTO is not running.

CSV Format

The following format applies to all CSV (Comma-separated values) Input Files used in VECTO:

List Separator: Comma “,”
Decimal-Mark: Dot “.”
Comments: “#” at the beginning of the comment line. Number and position of comment lines is not limited.
Header: One header line (not a comment line) at the beginning of the file.

Exceptions

Job Editor

Description

The job file (.vecto) 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:

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.

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

General Settings

Engine Only Mode

Enables Engine Only Mode. Only the following parameters are needed for this mode:

Filepath to the Vehicle File (.vveh)
Files can be created and edited using the Vehicle Editor.
Filepath to the Engine File (.veng)
Files can be created and edited using the Engine Editor.
Filepath ot the Gearbox File(.vgbx)
Files can be created and edited using the Gearbox Editor.
Auxiliaries
This list contains all auxiliaries used for calculation. The auxiliaries are configured using the Auxiliary Dialog. For each auxiliary an Auxiliary Input File (.vaux) must be provided and the driving cycle must include the corresponding supply power. Double-click entries to edit with the Auxiliary Dialog.

addaux Add new Auxiliary

remaux Remove the selected Auxiliary from the list

See Auxiliaries for details.

Cycles
List of cycles used for calculation. The .vdri format is described here. Double-click an entry to open the file (see File Open Command). Click selected items to edit file paths.

addcycle Add cycle (.vdri)

remcycle Remove the selected cycle from the list

Driver Assist Tab

In this tab the driver assistance functions are enabled and parameterised.

Engine Start/Stop
See Engine Start/Stop for details.
Overspeed / Eco-Roll
See Overspeed / Eco-Roll for details.
Look-Ahead Coasting
See Look-Ahead Coasting for details.
Acceleration Limiting
See Acceleration Limiting for details.

Chart Area

If a valid Vehicle File, Engine File and 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 the generic shift polygons are shown, not the ones from the Gearbox File.

Controls

new New Job File
Create a new empty .vecto file
open Open existing Job File
Open an existing .vecto file

save Save current Job File

SaveAs Save Job File as…

sendto Send current file to Job List in Main Form
Note: The file will be sent to the Job List automatically when saved.

veh Open Vehicle Editor

eng Open Engine Editor

gbx Open Gearbox Editor

Browse for vehicle/engine/gearbox files

OK Save and close file
File will be added to Job List in the Main Form.

Cancel Cancel without saving

Vehicle Editor

Description

The Vehicle File (.vveh) defines the main vehicle/chassis parameters like axles including RRCs, air resistance and weight.

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: “Demo1.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.)

General vehicle parameters

Vehicle Category
Needed for Declaration Mode to identify the HDV Class.
Axle Configuration
Needed for Declaration Mode to identify the HDV Class.
Gross Vehicle Mass Rating [t]
Needed for Declaration Mode to identify the HDV Class.
HDV Class
Displays the automatically selected HDV Class depending on the settings above.

Weight/Loading

These fields define the weight and loading of the vehicle. Max. Loading displayes the maximum possible loading for the selected vehicle depending on curb weight and GVW values.

Note: VECTO uses the sum of Curb Weight Vehicle, Curb Weight Extra Trailer/Body and Loading for calculation!

Air Resistance

The product of Drag Coefficient [-] and Cross Sectional Area [m²] (cd x A) and Air Density [kg/m³] (see Settings) together with the vehicle speed defines the Air Resistance. Note that the Drag Coefficient may be altered when using Cross Wind Correction.

Axles/Wheels

For each axle the parameters Relative axle load, RRCISO and FzISO have to be defined in order to calculate the total Rolling Resistance Coefficient. Furthermore the Wheels Inertia [kgm²] has to be set per wheel for each axle. In Declaration Mode the inertia is defined automatically according to the selected tyres. Use the and buttons to add or remove axles form the vehicle. Doubleclick entries to edit existing axle configurations.

Dynamic Tyre Radius [mm]
Effective (dynamic) wheel radius used to calculate engine speed. In Declaration Mode the radius calculated automatically using tyres/rims of the powered axle.
Powered axle tyres/rims
Needed for Declaration Mode to calculate the dynamic tyre radius.

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!

Three options are available:
  • None
  • Primary (before gearbox): The rpm ratio is relative to the engine speed
  • Secondary (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).

Cross Wind Correction

Three different options are available:
  • No Correction
  • Speed dependent (User-defined)
  • Speed dependent (Declaration Mode)
  • Vair & Beta Input

Depending on the chosen mode either a Speed Dependent Cross Wind Correction Input File (.vcdv) or a Vair & Beta Cross Wind Correction Input File (.vcdb) must be defined. For details see Cross Wind Correction.

Controls

New file
Create a new empty .vveh file
Open existing file
Open an existing .vveh file

Save current file

Save file as…

Send current file to the VECTO Editor
Note: If the current file was opened via the VECTO Editor the file will be sent automatically when saved.
Save and close file
If necessary the file path in the VECTO Editor will be updated.

Cancel without saving

Speed Dependent Cross Wind Correction Input File (.vcdv)

The file is needed for speed dependent Cross Wind Correction.

File Format

The file uses the VECTO CSV format.

Format:
  • Two columns
  • One header line
  • At least two lines with numeric values (below file header)

Columns:

vehicle speed [km/h] cd Scaling Factor [-]

Vair & Beta Cross Wind Correction Input File (.vcdb)

The file is needed for Vair & Beta Cross Wind Correction.

File Format

The file uses the VECTO CSV format VECTO CSV format.

Format:
  • Two columns
  • One header line
  • At least two lines with numeric values (below file header)

Columns:

Beta [°] cd Scaling Factor [-]

Retarder Loss Torque Input File (.vrlm)

This file is used to define retarder idling losses. It can be used for primary and secondary retarders and must be set in the Vehicle File.

File Format

The file uses the VECTO CSV format.

Format:
  • Two columns
  • One header line
  • At least two lines with numeric values (below file header)

Columns:

Retarder Speed [1/min] Loss Torque [Nm]

Engine Editor

Description

The Engine File (.veng) defines all engine-related parameters and input files like Fuel Consumption Map and Full Load Curves.

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: “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.)

Main Engine Parameters

Make and Model
Free text defining the engine model, type, etc.
Idling Engine Speed [rpm]
Low idle, applied in simulation for vehicle standstill in neutral gear position.
Displacement [ccm]
Used in Declaration Mode to calculate inertia.
Inertia including Flywheel [kgm²]
Inertia for rotating parts including engine flywheel. In Declaration Mode the inertia is calculated automatically.

Full Load and Drag Curves

The Full Load and Drag Curves (.vfld) Note that gear-specific full load curves can be defined in the Gearbox File to limit the maximum gearbox input torque.

The input file (.vfld) file format is described here.

Fuel Consumption Map

The Fuel Consumption Map is used to calculate the base FC value. See Fuel Consumption Calculation for details.

The input file (.vmap) file format is described here.

WHTC Correction Factors

The WHTC Corretion Factors are required in Declaration Mode for the WHTC FC Correction.

Chart Area

The Chart Area shows the fuel consumption map and the selected full load curve.

Controls

newNew file
Create a new empty .veng file
openOpen existing file
Open an existing .veng file

saveSave current file

SaveAsSave file as…

sendtoSend current file to the VECTO Editor
Note: If the current file was opened via the VECTO Editor the file will be sent automatically when saved.

Open file (see File Open Command).

OKSave and close file
If necessary the file path in the VECTO Editor will be updated.

CancelCancel without saving

Full Load and Drag Curves (.vfld)

This file contains the full load and drag curves and the PT1 values for the transient full load calculation.

File Format

The file uses the VECTO CSV format.

Format:
  • Four columns
  • One header line
  • At least two lines with numeric values (below file header)

Columns:

engine speed [1/min] full load torque [Nm] motoring torque [Nm] PT1 time constant [s]

Fuel Consumption Map (.vmap)

The FC map is used to interpolate the base fuel consumption before corrections are applied. For details see Fuel Consumption Calculation.

File Format

The file uses the VECTO CSV format.

Format:
  • Three columns
  • One header line
  • At least four lines with numeric values (below file header)
  • The map must cover the full engine range between full load and motoring curve. Extrapolation is not possible!

Columns:

engine speed [1/min] engine torque [Nm] Fuel Consumption [g/h]

Gearbox Editor

Description

The Gearbox File (.vgbx) defines alls gearbox-related input parameters like gear ratios and transmission loss maps. See Gear Shift Model for details.

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: “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.)

Main Gearbox Parameters

Make and Model
Free text defining the gearbox model, type, etc.
Transmission Type
Depending on the transmission type some options below are not available.The following types are available:
  • Manual Transmission (MT)
  • Automated Manual Transmission (AMT)
  • Automatic Transmission (AT)
  • Custom
Note: The types AT and Custom are not available in Declaration Mode.
Inertia [kgm²]
Rotational inertia of the gearbox (constant for all gears).
Traction Interruption [s]
Interruption during gear shift event.

Gears

Use the add and remove buttons to add or remove gears form the vehicle. Doubleclick entries to edit existing gears.

Gear shift parameters

Allow shift-up inside polygons
See Gear Shift Model.
Skip Gears
See Gear Shift Model.
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 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.
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) for the selected gear.

Torque Converter

The Torque Converter Model is still in development.

Inertia [kgm²]
Rotational inertia of the engine-side part of the torque converter. (Gearbox-side inertia is not considered in VECTO.)

Controls

New file
Create a new empty .vgbx file
openOpen existing file
Open an existing .vgbx file

save Save current file

SaveAs Save file as…

sendto Send current file to the VECTO Editor
Note: If the current file was opened via the VECTO Editor the file will be sentautomatically when saved.

Open file browser

Open file (see File Open Command).

OK Save and close file
If necessary the file path in the VECTO Editor will be updated.

Cancel Cancel without saving

Shift Polygons Input File (.vgbs)

Defines up- and down-shift curves. See Gear Shift Model for details.

File Format

The file uses the VECTO CSV format.

Format:
  • Three columns
  • One header line
  • At least two lines with numeric values (below file header)

Columns:

Engine Torque [Nm] Downshift rpm [1/min] Upshift rpm [1/min]

Transmission Loss Map (.vtlm)

This file defines losses in gearbox and axle transmission and must be provided for each gear in the Gearbox File.

File Format

The file uses the VECTO CSV format.

Format:
  • Three columns
  • One header line
  • At least four lines with numeric values (below file header)

Columns:

Input Speed [1/min] Input Torque [Nm] Torque Loss

Input Speed & Torque always means engine-side.

Sign of torque values:
  • Input Torque > 0 for normal driving operation
  • Input Torque < 0 for motoring operation. The Torque Loss Map must include negative torque values for engine motoring operation!
  • Torque Loss is always positive!
Calculation of Output Torque:
VECTO calculates the output torque using this formula, independent from the current operation mode (driving/braking).

\(Output\ Torque = (Input\ Torque-Torque\ Loss) \times GearRatio\)

Torque Converter Characteristics (.vtcc)

!!! The Torque Converter Model is still in development !!!

This file defines the torque converter characteristics as described in VDI 2153:

The Input Torque at  reference engine speed is needed to calculate the actual engine torque using this formula:

\(T_{in} = T_{ref}(v) \cdot ( \frac{n_{in}}{n_{ref}} )^{2}\)

with:

The torque converter characteristics must also be defined for speed ratios of more than one (ν>1) in order to calculate overrun conditions (torque<0).

File Format

The file uses the VECTO CSV format.

Format:
  • Three columns
  • One header line
  • At least two lines with numeric values (below file header)

Columns:

Speed Ratio ν Torque Ratio μ Input Torque at reference rpm

Auxiliary Input File (.vaux)

This file is used to configure a single auxiliary. Multiple .vaux files can be defined in the Job File via the Auxiliary Dialog.

See Auxiliaries for details on how the power demand for each auxiliary is calculated.

File Format

The file uses the VECTO CSV format with three additional parameters on top of the efficiency map.

Format:
  • Lines 1,3,5 and 7 are reserved for headers. Theses lines are skipped during file read.
  • Line 2: TransRatio = Speed ratio between auxiliary and engine. [-]
  • Line 4: EffToEng = Efficiency of auxiliary (belt/gear) drive [-]
  • Line 6: EffToSply = Consumer efficiency [-]
  • Line 8 and following (at least four): EffMap = Auxiliary efficiency map.

Format:

TransRatio [-] Max. acceleration [m/s2] Max. deceleration [m/s2]
EffToEng [-]
EffToSply [-]
Auxiliary speed [1/min] Mechanical power [kW] Supply power [kW]

Driving Cycle (.vdri)

The Driving Cycle defines vehicle speed, road gradient and other parameters either time- or distance-based. It’s open format requires Idenfiers to define the content of each column.

Important Notes

Supported Identifiers

Identifier Quantity Unit Description
<s> Distance [m] Travelled distance used for distance-based cycles. If <t> is also defined this column will be ignored.
<t> Time [s] Used for time-based cycles. If neither this nor the distance <s> is defined the data will be interpreted as 1Hz.
<v> Vehicle Speed [km/h] Required except for Engine Only Mode and Pwheel-Input calculations.
<grad> Road Gradient [%] Optional.
<stop> Stopping Time [s] Required for distance-based cycles. Not used in time based cycles. <stop> defines the time the vehicle spends in stop phases.
<Aux_xxx> Auxiliary Supply Power [kW] Supply Power input for each auxiliary defined in the .vecto file where xxx matches the ID of the corresponding Auxiliary. ID’s are not case sensitive and must not contain space or special characters.
<n> Engine Speed [rpm] If <n> is defined VECTO uses that instead of the calculated engine speed value.
<gear> Gear [-] Gear input. Overwrites the gear shift model.
<Padd> Additional Aux Power Demand [kW] This power input will be directly added to the engine power in addition to possible other auxiliaries. Also used in Engine Only Mode.
<vair_res> Air speed relative to vehicle [km/h] Only required if Cross Wind Correction is set to Vair & Beta Input.
<vair_beta> Wind Yaw Angle [°] Only required if Cross Wind Correction is set to Vair & Beta Input.
<Pe> Engine power [kW] Effective engine power at clutch. Only required in Engine Only Mode. Alternatively torque can be defined. Use <DRAG> to define motoring operation.
<Me> Engine torque [Nm] Effective engine torque at clutch. Only required in Engine Only Mode. Alternatively power can be defined. Use <DRAG> to define motoring operation.
<Pwheel> Power at wheels [kW] Overwrites power calculation. Requires Gear and Engine Speed input.Cycle must be time based.

Examples

The demo data provided with VECTO contains several .vdri files that may be used as template.

Example 1: Distance-based cycle with Road Gradient and two Auxiliaries

<s> <v> <grad> <stop> <Aux_Alt> <Aux_Demo>
0 60 2.95016969 0 0.5 4.752
1 60 2.95016969 0 0.5 4.752
2 60 2.95016969 0 0.5 4.752
3 60 2.95016969 0 0.5 4.752
4 60 2.95016969 0 0.5 4.752
5 60 2.95016969 0 0.5 4.752
6 60 2.95016969 0 0.5 4.752
7 60 2.95016969 0 0.5 4.752
8 60 2.95016969 0 0.5 4.752
9 60 3.06801369 0 0.5 4.752
10 60 3.06801369 0 0.5 4.752
11 60 3.06801369 0 0.5 4.752
12 60 3.06801369 0 0.5 4.752
13 60 3.06801369 0 0.5 4.752

Example 2: Time-based cycle with Engine Speed, Vair & Beta Input, one Auxiliary and Additional Aux Demand

<t> <v> <grad> <n> <vair_res> <vair_beta> <Aux_Alt> <Padd>
1 0 0 594 0 0 0.532 2.007686806
2 0 0 602.25 0 0 0.588 3.222867975
3 0 0 600 0 0 0.644 3.215345965
4 0 0 598 0 0 0.728 3.208650609
5 0 0 595.25 0 0 0.644 3.199146758
6 0 0 602.5 0 0 0.588 2.050366424
7 0 0 599.25 0 0 0.588 3.212783873
8 0 0 598 0 0 0.644 3.208568475
9 0 0 595.75 0 0 0.504 3.201815003
10 0.3112 0 983.75 0 0 0.476 4.532197507
11 5.2782 -0.041207832 723.75 8.532 0 0.42 2.453370264
12 10.5768 -0.049730127 1223.25 12.024 34 0.476 3.520827362
13 15.66795 -0.05296987 1737.25 14.472 28 0.504 4.880874189
14 20.80995 -0.05715414 2238.25 21.312 21 0.476 6.648425375
15 24.1622 -0.059104326 2428.5 21.42 5 0.476 7.393337294
16 26.56975 -0.057649533 1709.25 22.5 -8 0.476 4.999156225
17 31.6701 -0.056915608 1966.75 32.22 -11 0.504 5.889710204
18 36.98445 -0.06826105 2250 38.232 -5 0.504 6.917938049

Acceleration Limiting Input File (.vacc)

The file is used for Acceleration Limiting. It defines the acceleration and deceleration limits as function of vehicle speed. The filepath has to be defined in the Job File.

File Format

The file uses the VECTO CSV format.

Format:
  • Three columns
  • One header line
  • At least two lines with numeric values (below file header)

Columns:

vehicle speed [km/h] Max. acceleration [m/s2] Max. deceleration [m/s2]

Summary Results (.vsum)

The .vsum file includes total / average results for each calculation run in one execution (ie. click of START Button). The file is located in the directory of the fist run .vecto file.

Quantities:

Name Unit Description
Job [-] Job number. Format is “x-y” with x = file number and y = cycle number
Input File [-] Name of the input file
Cycle [-] Name of the cycle file
time [s] Total simulation time
distance [km] Total travelled distance
speed [km/h] Average vehicle speed
∆altitude [m] Altitude difference between start and end of cycle
Ppos [kW] Average positive engine power
Pneg [kW] Average negative engine power
FC-Final [g/km] & [l/100km] & [l/100tkm] Average fuel consumption. Final value after all corrections.
FC-Map [g/h] & [g/km] Fuel consumption interpolated form Fuel Map.
FC-AUXc [g/km] Fuel consumption after Auxiliary-Start/Stop Correction. (Based on FC.)
FC-WHTCc [g/km] Fuel consumption after WHTC Correction. (Based on FC-AUXc.)
Co2 [g/km] & [g/tkm] Average CO2 emissions.
Pbrake [kW] Average brake power (not including engine drag)
EposICE [kWh] Total positive engine work
EnegICE [kWh] Total negative engine work (engine brake)
Eair [kWh] Total work of air resistance
Eroll [kWh] Total work of rolling resistance
Egrad [kWh] Total work of gradient resistance
Eacc [kWh] Total work from accelerations (<0) / decelerations (>0)
Eaux [kWh] Total energy demand of auxiliaries
Eaux_xxx [kWh] Energy demand of auxiliary with ID xxx. See also Aux Dialog and Driving Cycle.
Ebrake [kWh] Total work dissipated in mechanical braking (sum of service brakes, retader and additional engine exhaust brakes)
Etransm [kWh] Total work of transmission losses
Eretarder [kWh] Total retarder losses
Etorqueconv [kWh] Total torque converter losses
Mass [kg] Vehicle mass (equals Curb Weight Vehicle plus Curb Weight Extra Trailer/Body, see Vehicle Editor)
Loading [kg] Vehicle loading (see Vehicle Editor)
a [m/s2] Average acceleration
a_pos [m/s²] Average acceleration in acceleration phases *
a_neg [m/s²] Average deceleration in deceleration phases *
Acc.Noise [m/s²] Acceleration noise
pAcc [%] Time share of acceleration phases *
pDec [%] Time share of deceleration phases *
pCruise [%] Time share of cruise phases *
pStop [%] Time share of stop phases *

*Driving conditions:

Definition of work (E…):
sign > 0: positive work applied to the vehicle (e.g. from engine, from kinetic energy)
sign < 0: losses
The sum of EposICE, EnegICE, Eair, Eroll, Egrad, Eacc, Eaux, Ebrake, Etransm and Eretarder is zero (besides small rounding error for long driving cycles)

Application Files

VECTO uses a numbers of files to save GUI settings and file lists. All files are text-based and can be changed outside of VECTO if VECTO is not running.

Settings.json

This file is located in VECTO’s config folder. Here all parameters of the Settings Dialog are saved. The file uses the JSON format .

Job / Cycle lists

The job and cycle lists in the Main Form are saved in the joblist.txt / cyclelist.txt files of the config folder.

Both files save the full file paths separated by line breaks. Additionally it is saved whether each file’s checkbox is checked or not. “?1” after a file path means the file is checked (otherwise “?0”). However, this information can be omitted in which case the file will be loaded in checked state.

LOG.txt

The tabulator-separated log file saves all messages of the Main Form’s Message List and is located in VECTO’s program directory. The file is restarted whenever the Logfile Size Limit is reached.One backup is always stored as LOG_backup.txt.

License file

The license file license.dat is located in VECTO’s program directory. Without a valid lisence file VECTO won’t run.

It no valid license file is provided with your VECTO version please contact .

Changelog

VECTO 2.2

VECTO 2.1.4

VECTO 2.1.3

VECTO 2.1.2

VECTO 2.1.1

VECTO 2.1

VECTO 2.0.4-beta4_Test (Test Release)

VECTO 2.0.4-beta3

VECTO 2.0.4-beta2

VECTO 2.0.4-beta1

VECTO 2.0.4-beta

VECTO 2.0.3-beta0

VECTO 2.0.2-beta2

VECTO 2.0.2-beta1

VECTO 2.0.1-beta1-hotfix.VECTO-33

VECTO 2.0.1-beta1

VECTO 2.0.1-beta0

VECTO 2.0

VECTO 1.4.RC8

VECTO 1.4.RC7

VECTO 1.4.RC6

VECTO 1.4.RC5

VECTO 1.4.RC4

VECTO 1.3.1.1

VECTO 1.3.1

VECTO 1.3

VECTO 1.2

VECTO 1.1