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.
All
(Un-)Check all files in Job List. Only checked files are calculated when clicking START.
Add files to Job List
Remove selected files from List
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.
If Declaration Mode is disabled VECTO can be run in Batch Mode.
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)
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).
Write modal results
Toggle output of modal results (.vmod files). Summary files (.vsum, .vres) are always created.
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)
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.
Information about the software, license and support contact
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:
Status Messages
Warnings
Errors
Links - click to open file/user manual/etc.
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 isexceland the file isC:\VECTO\cycle1.vdrithen 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:
Filepath to the Vehicle File (.vveh) which defines the not-engine/gearbox-related vehicle parameters
Filepath to the Engine File (.veng) which includes full load curve(s) and the fuel consumption map
Filepath ot the Gearbox File (.vgbx) which defines gear ratios and transmission losses
Auxiliaries
Driver Assist parameters
Driving Cycles (not used in Batch Mode)
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:
Driving Cycles including engine torque (or power) and engine speed
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.
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.
Add cycle (.vdri)
Remove the selected cycle from the list
Driver Assist Tab
In this tab the driver assistance functions are enabled and parameterised.
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.
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.
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.)
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 ofCurb Weight Vehicle, Curb Weight Extra Trailer/BodyandLoadingfor 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
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.
If necessary the file path in the VECTO Editor will be updated.
Cancel 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 and buttons to add or remove gears form the vehicle. Doubleclick entries to edit existing gears.
Gear “A” defines the ratio of the axle transmission / differential.
Column “TC” (AT only) defines which gears are using the torque converter (lock-up clutch open).
Column “Loss Map or Efficiency” allows to define either a constant efficiency value or a loss map (.vtlm).
Column “Full Load Curves” defines the Full Load Curve for (.vfld) each gear. It is used for torque limiting and generic shift polygons in Declaration Mode. If no file is defined the engine full load curve will be used.
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.
If necessary the file path in the VECTO Editor will be updated.
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 and 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 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.
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
One or more checked job files in the Job List
Each job file must include at least one driving cycle
Results
Modal results (.vmod) for each job file and driving cycle. One file for each cycle.
Average/sum results (.vsum / .vsum.json). One file in total containing results for each calculation.
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
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.
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
One or more checked job files in the Job List
The job files don’t need to include driving cycles. These are automatically assigned.
Results
Modal results (.vmod) for each job file and driving cycle. One file for each cycle.
Average/sum results (.vsum / .vsum.json). One file in total containing results for each calculation.
Results overview (.pdf). One file for each job file.
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.
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:
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].
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.
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:
Filepath to the Engine File (.veng)
Driving Cycles including engine torque (or power) and engine speed
Engine torque <Me> or engine power <Pe> at clutch. To explicitly define motoring operation use the <DRAG> keyword,see below. VECTO replaces the keyword with the motoring torque/power from the .vfld file during calculation.
[Optional] Additional power demand (aux) <Padd>
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:
Power demand ≤ 0
Vehicle speed is below Max Speed [km/h]
Engine was running for at least Min ICE-On Time [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.
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.
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.
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:
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).
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).
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:
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.
The correction factor CFWHTC is calculated using the equation below considering the current mission profile’s weighting factors for each part.
The factor is multiplied to the FC values for each time step and the total FC result.
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
Down-shift:
As soon as the current engine speed falls below the down-shift cuve a down-shift is initiated
Up-shift:
MT and AMT transmissions: Up-shift is initiated when the current engine speed is above the up-shift curve
AT transmissions: Up-shift is initiated when the next-gear engine speed is above the up-shift curve
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:
Torque Reserve [%] - Required for the “Early Upshift” and “Skip Gears” options, see below.
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.
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.
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].
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.
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.
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
…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.
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
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.
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.
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 (nota comment line) at the beginning of the file.
The Driving Cycle (.vdri) uses keywords to identify columns and therefore the header line must follow certain specifications.
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:
Filepath to the Vehicle File (.vveh) which defines the not-engine/gearbox-related vehicle parameters
Filepath to the Engine File (.veng) which includes full load curve(s) and the fuel consumption map
Filepath ot the Gearbox File (.vgbx) which defines gear ratios and transmission losses
Auxiliaries
Driver Assist parameters
Driving Cycles (not used in Batch Mode)
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:
Driving Cycles including engine torque (or power) and engine speed
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.
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.
Add cycle (.vdri)
Remove the selected cycle from the list
Driver Assist Tab
In this tab the driver assistance functions are enabled and parameterised.
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.
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.)
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 ofCurb Weight Vehicle, Curb Weight Extra Trailer/BodyandLoadingfor 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
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.
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 and buttons to add or remove gears form the vehicle. Doubleclick entries to edit existing gears.
Gear “A” defines the ratio of the axle transmission / differential.
Column “TC” (AT only) defines which gears are using the torque converter (lock-up clutch open).
Column “Loss Map or Efficiency” allows to define either a constant efficiency value or a loss map (.vtlm).
Column “Full Load Curves” defines the Full Load Curve for (.vfld) each gear. It is used for torque limiting and generic shift polygons in Declaration Mode. If no file is defined the engine full load curve will be used.
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.
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
For distance-based cycles there is a minimum distance-step of 1[m] required. The calculation will abort if larger steps are used.
Time-based cycles can be defined in any given time resolution, including variable time steps. If the time identifier “<t>” is not used the data will be interpreted in 1[s] resolution (1Hz).
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.
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.
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.
At least two lines with numeric values (below file header)
Columns:
vehicle speed [km/h]
Max. acceleration [m/s2]
Max. deceleration [m/s2]
…
…
…
…
…
…
Modal Results (.vmod)
Modal results are only created if enabled in the Options tab. One file is created for each calculation and stored in the same directory as the .vecto file.
Quantities:
Name
Unit
Description
time
[s]
Time step.
dist
[km]
Travelled distance.
v_act
[km/h]
Actual vehicle speed.
v_targ
[km/h]
Target vehicle speed.
acc
[m/s²]
Vehicle acceleration.
grad
[%]
Road gradient.
n
[1/min]
Engine speed.
Tq_eng
[Nm]
Engine torque.
Tq_clutch
[Nm]
Torque at clutch (before clutch, engine-side)
Tq_full
[Nm]
Full load torque
Tq_drag
[Nm]
Motoring torque
Pe_eng
[kW]
Engine power.
Pe_full
[kW]
Engine full load power.
Pe_drag
[kW]
Engine drag power.
Pe_clutch
[kW]
Engine power at clutch (equals Pe minus loss due to rotational inertia Pa Eng).
Gear
[-]
Gear. “0” = clutch opened / neutral.
Ploss GB
[kW]
Gearbox losses.
Ploss Diff
[kW]
Losses in differential / axle transmission.
Ploss Retrader
[kW]
Retarder losses.
Pa Eng
[kW]
Rotational acceleration power: Engine.
Pa GB
[kW]
Rotational acceleration power: Gearbox.
Pa Veh
[kW]
Vehicle acceleration power.
Proll
[kW]
Rolling resistance power demand.
Pair
[kW]
Air resistance power demand.
Pgrad
[kW]
Power demand due to road gradient.
Paux
[kW]
Total auxiliary power demand.
Pwheel
[kW]
Total power demand at wheel = sum of rolling, air, acceleration and road gradient resistance.
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.
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
Bugfix: Error in Declaration Mode Pneumatic System aux power calculation ([kW] were interpreted as [W])
Bugfix: Error in Declaration Mode Electric System aux power calculation
Moved gear-specific Full Load Curves to Gearbox File
Combined Drag Coefficient * Cross Sectional Area in one input parameter
Updated .vgbx file format (Added gear-specific Full Load Curves)
Updated .veng file format (Removed gear-specific Full Load Curves)
Updated .vveh file format (Combined Drag Coefficient * Cross Sectional Area in one parameter)
Updated Generic Vehicles (new file formats)
Removed WHTC Correction Factor Calculation. Now in external tool, VECTO-Engine.
Test Options are now only available in Engineering Mode
Gearbox Editor now shows generic and user-defined shift polygons (if available)
Various small updates in GUI
Added ‘Create JIRA Issue’ dialog
VECTO 2.1.4
Bugfixes in start gear and (A)MT shift model
Updated Coach .vcdv file for higher speeds to avoid extrapolation
Renamed output “FC” to “FC-Map” for better clarification
Same header for g/h and g/km output
Reduced minimum turbine speed for 1C-to-2C AT up-shift condition from 900 to 700rpm.
Updated cross wind correction parameters to current White Book values
VECTO 2.1.3
PwheelPos output in VSUM file.
Implemented new Cd*A(v) method
Bugfix in TC model
Bugfix: Unit error in Cd(v) methods caused incorrect Delta-Cd value being used
VECTO 2.1.2
Improved TC iteration for higher precision
Extended possible TC speed ratio
VECTO 2.1.1
Bugfix: Incorrect torque calculation in AT/TC model caused early up-shifts
Updated C-to-C shift strategy with acc_min rule (see V2.1)
VECTO 2.1
Automatic Transmission / Torque Converter Model
Limit engine rpm in torque converter operation acc. > acc_min
Shift up (C-to-L, L-to-L) if acc. > acc_min and next-gear-rpm > threshold
C-to-C up-shift condition based on N80h engine speed (instead of N95h)
Pwheel-Input (SiCo Mode)
FC [g/h] is always saved in output (in addition to [g/km]), not only
in Engine Only mode
GUI: Corrected air density unit in GUI
Bugfix: Format error in .vmod header
VECTO 2.0.4-beta4_Test (Test Release)
Transmission loss extrapolation Errors are now Warnings in Engineering Mode.
Bugfix: Error in TC Iteration caused crash
Bugfix: Minimizing Graph window caused crash
Fixed error in cycle conversion
Errors if full load curve is too “short”
VECTO 2.0.4-beta3
Bugfix: VECTO didn’t check if the full load curve covers the speed range up to nhi. Now it will abort if the full load curve is “too short”
Update in Torque Convert model: Allowed engine speed range up to n95h (before: Pmax-speed)
Bugfix: Rare crashes caused by gear shift model
Bugfix: Error in engine inertia power calculation
Torque Converter losses in modal results
Implemented speed profile cleaning for very small values. (Caused shifting back to first gear when decelerating.)
DEV Option for advanced CSV format output (units line, additional info)
VECTO 2.0.4-beta2
Bugfix: VECTO freezed if torque converter creeping was not possible due to low full load torque. Now it will abort with error message.
Bugfix: Small fixes in torque converter model
VECTO 2.0.4-beta1
Updated CSV format of some declaration config files
Warning when opening or running files if file was created in different mode (Declaration/Engineering Mode)
VECTO 2.0.3-beta0
Implemented engine-side TC inertia input parameter in GBX file
Updated User Manual for TC inertia
Relabeled “OK” buttons to “Save” in input file editors
VECTO 2.0.2-beta2
AT/TC Update
Various smaller fixes
VECTO 2.0.2-beta1
AT/TC Update
Engine inertia power demand (PaEng) is now always calculated based on the previous engine speed rather than vehicle acceleration.
Various smaller fixes
VECTO 2.0.1-beta1-hotfix.VECTO-33
Fixed VECTO-34
Updated .vsum(.json)
Added l/100km and CO2 results. (Fixed VECTO-33)
Added FC-Final.
Added Loading. (json)
Added missing fuel parameters. (json)
Updated README.md
VECTO 2.0.1-beta1
Updated Segment Table header
Fixed Eco Roll (VECTO-30)
Fixed Cycles in VECTO Editor being overwritten in Engineering Mode (VECTO-31)
VECTO 2.0.1-beta0
Update Notes > Release Notes
Segment Table header
VECTO 2.0
Updated CSV file format. Now only one header with units included.
Changed input file comment symbol form “c” to “#”.
Replaced old Demo/Default Data with “Demo Vehicles”
Updated User Manual
Declaration Mode
Updated GUI including Charts
New internal Graph for VMOD files (replaces GRAPHi)
Shift polygons can be set separately for each gear
Removed rated power (not used anymore)
Removed rated engine speed form engine file. Now calculated form vfld file.
VECTO 1.4.RC8
Bugfix: Eco Roll didn’t go into motoring operation when Overspeed-Limit was reached (could cause higher FC than Overspeed Mode)
Minor update in demo data (12t motoring curve)
VECTO 1.4.RC7
Bugfix: Error in road gradient resulted in altitude error
Speed reduction in smaller steps to get closer to full load curve (before speed was sometimes reduced too much and caused problem with gear shifting)
Updates in demo data
VECTO 1.4.RC6
Bugfix in torque converter calculation
VECTO 1.4.RC5
Bugfix: Gears using torque converter and transmission loss maps may cause invalid “out of engine operation range” errors
Null values for FzISO will abort calculation
Exact road gradient calculation (sin(arctan(grad)*m*g) instead of grad*m*g) and road gradient influence on roll resistance (cos(arctan(grad)*m*g instead of m*g)
Torque converter update: rpms over rated speed are not allowed.
Fixed Wheels inertia in Demo Data
VECTO 1.4.RC4
Bugfix: FC interpolation failed when load points matched map points exactly.
Bugfix: Invalid “FC= -10000!” errors when outside of FC-Map
Bugfix: Vehicle stand-still at end of cycle was ignored (distance-based cycles only)
FC extrapolation will not abort calculation. Invalid FC values are marked in output as “ERROR”.
No abortion if transmission output and input torque have different signs
(In>0, Out<0). (Caused “Transmission Loss Map invalid” error messages)
Eco-Roll revised. New rules:
Engages if Pwheel < 0
Disengages if Underspeed is reached.
Look-Ahead Coasting now uses real coasting also if road gradient > 0 which means the coasting deceleration can be so high that no braking is necessary. In this case the braking phase will be omitted and the total deceleration time can be shorter than expected by the given target coasting deceleration.
“Minimum (actual) speed” instead of “Min. Target Speed” for Eco-Roll,
Overspeed and Look Ahead Coasting
Major update in Gearbox/Toque Converter:
Torque converter can be defined in multiple gears
Same gear numbers in output as in GBX file, i.e. first gear with TC is not “TC” or “0.5” but simply “1”
“Minimum time between two gear shifts” now also limits torque converter shifts
Unlimited number of gears and new gear list in GUI without fixed gear number
Improved gear shift model for torque converter
Driving Cycle Preprocessing and Gear Shift Model now use approximated efficiency values based in the transmission loss maps. Reduces calculation time significantly with little to no impact on fuel consumption.
Full load and drag curves (.vfld) can be defined for each gear separately.
Bugfix: Distance Correction didn’t work right with Look Ahead Coasting. Now distance error is acceptable but at the cost of partly interrupted coasting phases. Should be revised in future updates.
Engine Only Mode: Engine motoring points can be defined explicitly in load cycle with “<DRAG>”
When speed is under 5km/h and engine in motoring operating then gearbox shifts to Neutral
Load-dependent rolling resistance coefficient
Start-Stop activation delay time can be defined in job file
File signing features added:
After each calculation a signature file (.vsig) is created which includes signatures for all input and result files. The file itself is also signed.
Signature files can be verified or manually created under “Tools” > “Sign or Verify Files”
Changes in header and new parameters in modal results (.vmod):
engine speed => n
torque => Tq_eng
Pe => Pe_eng
New: Tq_clutch = torque at clutch (before clutch, engine-side)
New: Tq_full = full load torque
New: Tq_drag = drag torque
Removed: Pe_norm, n_norm -Changes in summary results (.vsum)
Total altitude change instead of average gradient
Auxiliary energy consumption for each auxiliary
Removed: Pe_norm, n_norm
Same job file list for BATCH and STANDARD (Job file list does not change when switching mode)
Updated some error messages (units)
Driving Cycle stop times corrected (No more zero stop times).
VECTO 1.3.1.1
Fixed error in power calculation (rotatory part of acceleration force)
VECTO 1.3.1
Fixed assembly information
VECTO 1.3
Some file-specific error messages link to files
Eco-Roll, Overspeed, Look Ahead Coasting
VECTO 1.2
Engine Start/Stop implemented
Bugfix: Fixed error in FC interpolation (invalid extrapolation errors)
FC Extrapolation will abort the calculation
Transmission Type selection in Gearbox (.vgbx) file.