Platform Requirements

Hardware Requirements

Software Requirements

User Manual



Version: VECTO 3.3 / VectoCore 3.3.0 / VectoCmd 3.3.0


VECTO is a tool for the calculation of energy consumption and CO2 emissions of vehicles. It models the components of a heavy-duty vehicle and simulates a virtual drive on a route. The goal is to provide a standardized way of calculating the energy consumption (fuel consumption) and corresponding CO2 emissions.

This User Manual consists of 4 Parts:

This user manual describes verson 3.3.x of Vecto.

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 simulation 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 two tabs as described below:

  • Job Files Tab
  • 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).

Options Tab

In this tab the global calculation settings can be changed.

Declaration Mode
Select either Declaration Mode or Engineering Mode
cb Write modal results
Toggle output of modal results (.vmod files). Summary files (.vsum, .vres) are always created.
cb Modal results in 1Hz
If selected, the modal results (.vmod file) will be converted into 1Hz after the simulation.

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

  • User Manual
    • Opens this User Manual
  • Release Notes
    • Open the Release Notes (pdf)
  • Report Bug via CITnet / JIRA
    • Open the CITnet/JIRA website for reporting bug
  • Create Activation File
    • Create an Activation File used for Licensing
  • About VECTO
    • 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.

In addition to the log messages shown in the message list, Vecto writes more elaborate messages in the subdirectory logs. If multiple simulations are run in parallel (e.g., in declartion mode a vehicle is simulated on different cycles with different loadings) a separate log-file is created for every simulation run.

Statusbar
Displays current status and progress of active simulations. When no simulation is executed the current mode is displayed (Standard, Batch or Declaration Mode).

Settings

Description

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

Interface Settings

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

This setting is only used in Engineering mode. In Declaration mode the default value of 1.188 [kg/m³] is used.

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 (only in Engineering Mode)

Relative File Paths

It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. Example: “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. (Note: The Job File must be saved before browsing for input files.)

General Settings

Engine Only Mode

Enables Engine Only Mode (Engineering 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 group contains input elements to define the vehicle’s load from the auxiliaries. In Declaration Mode only the pre-defined auxiliaries are available and their power-demand is also pre-defined, depending on the vehicle category and driving cycle. This means the Auxiliary Type is set to ‘Classic: Vecto Auxiliary’ and no ‘Constant Aux Load’ can be specified. The following list contains the pre-defined auxiliaries where the concrete technology for each auxiliary can be configured using the Auxiliary Dialog. Double-click entries to edit with the Auxiliary Dialog.
Auxiliaries
In Engineering Mode the set of auxiliaries can be freely defined. First, the Auxiliary Type can be selected. If the Bus Auxiliaries are selected a configuration file for the Advanced Auxiliaries has to be specified. When using the Bus Auxiliaries, the standard auxiliaries can be added as well in the list below to take into account the steering pump, etc. The ‘Constant Aux Load’ can be used to define a constant power demand from the auxiliaries (similar to P_add in the driving cycle, but constant over the whole cycle). The following list can be used to define the auxiliary load in more detail via a separate input file. The auxiliaries are configured using the Auxiliary Dialog. 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.

Overspeed
See Overspeed 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 sampling points of the fuel consumption map.

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

VTP-Job Editor

Description

The VTP 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 (.xml)](#vehicle-editor which defines all relevant parameters, including all components
  • Driving Cycles

Relative File Paths

It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. Example: “Vehicles\Vehicle1.xml” 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. (Note: The Job File must be saved before browsing for input files.)

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

Chart Area

If a valid Vehicle File is loaded into the Editor the main vehicle parameters like HDV class and axle configuration are shown here. The plot shows the full load curve(s) and sampling points of the fuel consumption map.

Controls

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.

Browse for vehicle file

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

Cancel Cancel without saving

Auxiliary Dialog

Auxiliary Dialog (Declaration Mode)

Auxiliary Dialog (Declaration Mode)

Auxiliary Dialog (Engineering Mode)

Auxiliary Dialog (Engineering Mode)

Description

The Auxiliary Dialog is used to configure auxiliaries. In Declaration Mode the set of auxiliaries and their power demand is pre-defined. For every auxiliary the user has to select the technology from a given list. In Engineering Mode the set of auxiliaries can be specified by the user. Auxiliary efficieny is defined using an Auxiliary Input File (.vaux). See Auxiliaries for details on how the power demand for each auxiliary is calculated.

Settings

Technology
List of available technology for the auxiliary type For the steering pump multiple technologies can be defined, one for each steered axle.
Type
String defining type of auxiliary. Click the arrow to load from a predefined list, however It is not required to use a type from the list.
ID
The ID string is required to link the auxiliary to the corresponding supply power definition in the driving cycle. The ID must contain characters and numbers only (A-Z, a-z, 0-9). The ID is not case sensitive (e.g. “ALT” will link to “Alt” or “alt”, etc.) Example : Auxiliary “ALT” is linked to the column “<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

Advanced Auxiliary Dialog

Description

In the VECTO Job Editor dialog you need to select “BusAuxiliaries” in the drop down list on the left to configure the advanced auxiliaries.

The Advance Auxiliaries Editor File (.aaux) defines all the auxiliary related parameters and input files like Alternator and Compressor Maps and HVAC steady state model outputs.

The Advance Auxiliaries Editor contains four tabs/sub-modules where the different advanced auxiliary types can be configured:

  • General
    Currently empty – reserved for potential future expansion.
  • Electrics
    The “Electrics” tab defines various parameters for electric auxiliaries used on the vehicle.
  • Pneumatics
    The “Pneumatic” tab defines various pneumatic auxiliaries data and pneumatic variables
  • HVAC
    The “HVAC” tab defines the steady state output values, which can also be loaded via the Steady State Model File (.AHSM)

Important notes

Note that the cycle file name used should ideally respect the following syntax to be correctly associated with the pneumatic actuations map (.apac), otherwise the number of actuations will be set to 0 by default:

  • “AnyOtherText _X_Bus.vdri“, with”X" = “Urban”, “Heavy urban”, “Suburban”, or “Interurban”
  • “AnyOtherText_Coach.vdri”

Some flexibility in syntax is allowable (the model looks for ‘Bus’, ‘Coach’, ‘Urban’, etc. in the file name), meaning that the standard default cycles are fully/correctly supported. However, for newly created cycles (i.e. for use in Engineering Mode) it is recommended to follow the above convention to guarantee correct functionality.

File Format

The file uses the VECTO JSON format.

The new file types have also defined to support the new Advanced Auxiliaries module in VECTO include:

File EXT NAME Storage Type Description
.AAUX JSON Overall configuration information for Electrical, Pneumatic and HVAC. Top of the tree for Advanced Auxiliaries
.AALT CSV Advanced Combined Alternators: Contains combined map plus source maps.
.ACMP CSV Advanced Compressor Map.
.APAC CSV Pneumatic Actuations Map: Stores number of actuations per cycle
.AHSM JSON Stores Steady State Model results, and also the configuration which resulted in the final result. UI to calculate various heat/cool/ventilate properties resulting in Electrical and Mechanical Power as well as cooling based on environmental conditions.
.ABDB CSV Bus Parameter Database: Contains a list of the default parameters for different buses.
.AENV CSV Stores a number of environmental conditions to be used by HVAC model when in batch-mode.

Electrical Auxiliaries Editor

Description

The “Electrics” tab defines various parameters for electric auxiliaries used on the vehicle:

  • Powernet Voltage [locked field/fixed value]
  • Alternator Map, including filepath to the new Combined Alternator Map (.AALT) file
    Files can be imported (blank field)/the Combined Alternator Map editor opened (file present) by clicking on the ‘browse’ button adjacent to the “Alternator Map” text box.
  • Alternator Pulley Efficiency [locked field/fixed value]
  • Door Actuation Time(S) [locked field/fixed value]
  • Stored Energy Efficiency [locked field/fixed value]
  • Smart Electrics [On/Off]
    Smart electrics are enabled by checking the “Smart Electrics” box
  • Electrical Consumables
    The “Electrical Consumables” table contains a list electrical equipment that place demand on the engine. Check boxes enable the user to select whether the energy demanded by each consumable is included in the calculation of the base vehicle. The user can modify only the number of consumables of each type installed on the vehicle*. The Nominal Consumption (amps) for each consumer, and the percentage of time each consumer is active during the cycle are locked default values as agreed with the project steering group.
  • Note: for certain fields the allowable values are also controlled/prescribed according to the requirements of the project steering group.

Results Cards

Upon activation of Smart Electrics using the check box, the user may enter Result Card values according to the methodology proposed by the steering group. Until the certification procedure to determine the correct values is agreed, it is recommended to use the following default values:

Example Default Results Card values

Result Card: Idle
Amps SmartAmps
40 0
50 0
60 54
70 64
80 30
Result Card: TractionON
Amps SmartAmps
40 0
50 0
60 83
70 94
80 45
Result Card: Overrun
Amps SmartAmps
40 0
50 0
60 172
70 182
80 90

Default Values

The following table provides a summary of the default values that are populated whenever a new advanced auxiliaries (.AAUX) file is created from scratch (nominal consumption and % active are always fixed defaults, so are not shown). The table also indicates the editable/default status of the relevant parameters in the VECTO UI in Engineering mode, and the recommended status in Declaration mode (not currently implemented). The default values / parameter status has been agreed with the project steering group.

Default parameter values and editable status for the Electrical module

General Inputs

Category Name Default value Engineering Declaration
Powernet Voltage Powernet Voltage 28.3 Locked default Locked default
Alternator Map Alternator Map blank Open/editable Open/OEM data
Alternator Pulley Efficiency Alternator Pulley Efficiency 0.92 Locked default Locked default
Door Actuation Time (s) Door Actuation Time (s) 4.0 Locked default Locked default
Smart Electrics Smart Electrics No (/Yes) Open/editable Open/OEM data

List of Electrical Consumables

Category Name No. in Vehicle, Default Value Engineering Declaration
Doors Doors per vehicle 3 Open/editable Open/OEM data
Veh Electronics &Engine Controllers, Valves, etc 1 Locked default Locked default
Vehicle basic equipment Radio City 1 Open/editable Open/OEM data
Vehicle basic equipment Radio Intercity 0 Open/editable Open/OEM data
Vehicle basic equipment Radio/Audio Tourism 0 Open/editable Open/OEM data
Vehicle basic equipment Fridge 0 Open/editable Open/OEM data
Vehicle basic equipment Kitchen Standard 0 Open/editable Open/OEM data
Vehicle basic equipment Interior lights City/ Intercity + Doorlights [1/m] 12 Open/editable Locked default
Vehicle basic equipment LED Interior lights ceiling city/ontercity + door [1/m] 0 Open/editable Locked default
Vehicle basic equipment Interior lights Tourism + reading [1/m] 0 Open/editable Locked default
Vehicle basic equipment LED Interior lights ceiling Tourism + LED reading [1/m] 0 Open/editable Locked default
Customer Specific Equipment External Displays Font/Side/Rear 4 Open/editable Open/OEM data
Customer Specific Equipment Internal display per unit ( front side rear) 1 Open/editable Open/OEM data
Customer Specific Equipment CityBus Ref EBSF Table4 Devices ITS No Displays 1 Open/editable Open/OEM data
Lights Exterior Lights BULB 1 Locked default Locked default
Lights Day running lights LED bonus 1 Open/editable Open/OEM data
Lights Antifog rear lights LED bonus 1 Open/editable Open/OEM data
Lights Position lights LED bonus 1 Open/editable Open/OEM data
Lights Direction lights LED bonus 1 Open/editable Open/OEM data
Lights Brake Lights LED bonus 1 Open/editable Open/OEM data

Combined Alternator Map File (.aalt)

The Combined Alternator Map (.AALT) file contains data relating to the efficiency of the alternator at various engine speeds and current demand. The .AALT file is a CSV file containing three fields: “Amp”, “RPM” (engine speed), and “Efficiency”. It can be created via the select file button, or an existing map directly imported into VECTO via the File Browser.

A new combined alternator map can be created or an existing one edited using the Combined Alternators editor module (see below). This module enables the creation of a combined average alternator efficiency map by the advanced auxiliaries module, using input data for one or more alternators (Pully Ratio, Efficiency at different RPM/AMP combinations):

Alternators may be added/deleted from the list. Data for existing alternators can be loaded into the form by double-clicking on the relevant alternator, and the data may then be updated and saved back down.

The ‘Diagnostics’ tab provides a summary of the input data that is fed into combined alternator map calculations:

The methodology for calculating the combined efficiency map is summarised below (and also included in the full schematics file included with the User Manual). Note: A simplified calculation is performed using the average of the user input efficiency values in the model pre-run only, to keep total run-time to a minimum (with negligible impact on the final result). :

File Format

The file uses the VECTO CSV format.

Several example default alternator maps are provided for use until a finalised certification procedure is in place for OEM-specific data.

Example Default Alternator Configuration for Advanced Alternator Map

Pulley Ratio: 3.6
RPM 2000 2000 4000 4000 6000 6000
Amps Efficiency Amps Efficiency Amps Efficiency
10.00 62.00 10.00 64.00 10.00 53.00
I_max/2 27.00 70.00 63.00 74.00 68.00 70.00
I_max 53.00 30.00 125.00 68.00 136.00 62.00

Notes: Bold values are locked/fixed values; I_max = the maximum current in Amps.

Pneumatic Auxiliaries Editor

Description

The “Pneumatics” tab defines various parameters for pneumatic auxiliaries used on the vehicle:

  • Pneumatic Auxiliaries Data/Variables
    Data for various pneumatic auxiliaries and the relevant pneumatic variables can be edited in the adjacent text boxes.
  • Filepath to the Compressor Map (.ACMP) file
    Files can be imported by clicking the browse button adjacent to the “Compressor Map” text box.
  • Filepath to the Actuations Map (.APAC) file
    Files can be imported by clicking the browse button adjacent to the “Actuations Map” text box.
  • The “Retarder Brake”, “Smart Pneumatics” and “Smart Regeneration” and enable via check boxes.

Default Values

The following table provides a summary of the default values that are populated whenever a new advanced auxiliaries (.AAUX) file is created from scratch. The table also indicates the editable/default status of the relevant parameters in the VECTO UI in Engineering mode, and the recommended status in Declaration mode (not currently implemented). The default values / parameter status has been agreed with the project steering group.

Default parameter values and editable status for the Pneumatic module

Pneumatic Auxiliaries Data

Category Default value Engineering Declaration Comments
AdBlue NI per minute 21.25 Open/editable Locked default Only relevant for Pneumatic AdBlue Dosing, also needs drive cycle duration
Air Controlled Suspension NI/Minute 15 Open/editable Locked default Only relevant for Pneumatic Air Suspension Control, also needs drive cycle duration
Breaking No Retarder NI/KG 0.00081 Open/editable Locked default also needs vehicle weight
Braking with Retarder NI/KG 0.0006 Open/editable Locked default Also needs vehicle weight
Air demand per Kneeling NI/Kg mm 0.000066 Open/editable Locked default Also needs vehicle weight and kneeling height
Dead Vol Blowouts/L/Hour 24 Open/editable Locked default
Dead Volume Litres 30 Open/editable Locked default
Non Smart Regen Fraction Total Air Demand 0.26 Open/editable Locked default
Overrun Utilisation for Compression Fraction 0.97 Open/editable Locked default Taken directly from White Book
Per Door Opening NI 12.7 Open/editable Locked default Only relevant for Pneumatic Door Operation, also needs number of door openings
Per Stop Brake Actuation NI/KG 0.00064 Open/editable Locked default Also needs vehicle weight
Smart Regen Fraction Total Air Demand 0.12 Open/editable Locked default

Pneumatic Variables

Category Default value Engineering Declaration Comments
Compressor Map Open/editable Locked default A number of pre-set defaults will be provided; later value from test procedure.
Compressor Gear Ratio 1.00 Open/editable Open/OEM data Related compressor shaft speed to engine shaft speed
Compressor Gear Efficiency 0.97 Open/editable Locked default
AdBlue Dosing Pneumatic Open/editable Open/OEM data Pneumatic (/Electric)
Air Suspension Control Mechanically Open/editable Open/OEM data Mechanically (/Electrically)
Door Operation Pneumatic Open/editable Open/OEM data Pneumatic (/Electric)
Kneeling height millimeters 70 Open/editable Open/OEM data Used with air demand per kneeling
Actuations Map testPneumatic ActuationsMap Open/editable Locked default
Retarder brake Yes Open/editable Open/OEM data Yes (/No)
Smart Pneumatics No Open/editable Open/OEM data No (/Yes)
Smart Regeneration No Open/editable Open/OEM data No (/Yes)

HVAC Auxiliaries Editor

Description

The “HVAC” tab defines various parameters for heating, ventilation and air conditioning (HVAC) auxiliaries used on the vehicle, calculated from the HVAC Steady State Model (HVAC SSM): - Disable HVAC Module [tickbox] - Filepath to the Steady State Model File (.AHSM) : Files can be imported by clicking the browse button adjacent to the HVAC “Steady State Model File (.AHSM)” text box. - Filepath to the Bus Parameter Database (.ABDB) " Files can be imported by clicking the browse button adjacent to the HVAC SSM bus parameters database file (.ABDB) text box. The bus parameter database contains a list of default parameters for a number of pre-existing/defined buses that can be quickly switched between within the HVAC SSM Editor module.

Outputs from the HVAC SSM include: - Electrical Load Power Watts - Mechanical Load Power Watts - Fuelling Litres Per Hour

HVAC Steady-State Model Editor

The HVAC Steady-State Model (HVAC SSM) Editor defines various data and parameters for calculation of HVAC auxiliary demands (electrical, mechanical and fuelling) from the vehicle, replicating the key inputs/functionality from the HVAC CO2SIM model developed for ACEA:

  • Bus Parameters
  • Boundary Conditions
  • Other
  • Tech List Input
  • Diagnostics

At the top of the window, two sets of outputs are presented for electrical, mechanical and fuelling demand:

  • ‘Base’ values: These are the calculated resulting demands from the inputs on the ‘Bus Parameters’, ‘Boundary Conditions’ and ‘Other’ tabs.
  • ‘Adjusted’ values: these are the final values output from the model, which additionally factor in the HVAC technologies included in the ‘Tech List Input’ tab.

Bus Parameters

Input bus parameters can be edited directly or imported/calculated from the Bus Parameter Database (.abdb) file via the ‘<Select>’ drop-down box at the top of the page. Parameters in the accompanying database file (.abdb) include:

  • Bus Model Name (free text)
  • Registered passengers
  • Type (i.e. ‘raised floor’ = Class III, ‘semi low floor’ = Class II, or ‘low floor’ = Class I)
  • Is Double Decker [tick box]
  • Length in m,
  • Wide in m,
  • Height in m,
  • [Engine Type (only ‘diesel’ is currently supported), only when creating a ‘New’ entry]
  • Other fields, that are greyed out, are locked and not editable, containing fixed default values or calculations.

Boundary Conditions

On this tab the various boundary conditions for the HVAC SSM calculations can be set. Certain fields (greyed out) are locked and not editable, containing fixed default values or calculations.

Other

On this tab a number of other parameters for the HVAC SSM calculations can be set: - Environmental conditions: when in ‘Batch Mode’ a climatic conditions dataset (.aenv) file must be used containing a series of environmental conditions. Otherwise single values for temperature and solar load may be input (these fields are locked/not used when in batch mode). - AC System specifications/type: the AC-Compressor Type selection determines the COP value used, according to the specification of the project steering group. - Ventilation settings - Auxiliary Heater parameters: the power of the fuel fired heater may be included, other fields are provided for information only and are locked. The ‘Engine Waste Heat’ values are calculated during the actual model runs, which are determined via a pre-run of the model over the selected drive-cycle.

TechList Input

To determine energy consumption of a certain bus-HVAC system combination, a customisable list of technologies may be added/edited on this tab to allow to take special features into account which have a reducing or increasing influence. Because several technologies are only available for certain bus types, the list has to be bus type-specific. The technologies list and the default values has been populated according to the steering group recommendations, however these may be deleted, edited or added to as required on this tab in Engineering mode.

Diagnostics

The final ‘Diagnostics’ tab provides a summary of the resulting outputs from the HVAC Tech List tab.

Default Values

The following table provides a summary of the default values that are populated whenever a new advanced auxiliaries (.AAUX) file is created from scratch. The table also indicates the editable/default status of the relevant parameters in the VECTO UI in Engineering mode, and the recommended status in Declaration mode (not currently implemented). The default values / parameter status has been agreed with the project steering group.

Default parameter values and editable status for the HVAC module

INP - BusParameters tab

Bus Parameterisation

Category/Input Default value Engineering Declaration
Select <Select>
Bus Model Open/editable Locked default
Number of Passengers <ABDB or input> Open/editable Locked default
Bus Type Open/editable Locked default
Double Decker? No Open/editable Open/OEM data
Bus Length (m) <ABDB or input> Open/editable Locked default
Bus Width (m) <ABDB or input> Open/editable Locked default
Bus Height (m) <ABDB or input> Open/editable Locked Calc
Bus Floor Surface Area (m^2) Calculation Locked Calc Locked Calc
Bus Window Surface (m^2) Calculation Locked Calc Locked Calc
Bus Surface Area (m^2) Calculation Locked Calc Locked Calc
Bus Volume (m^3) Calculation Locked Calc Locked Calc

INP - Boundary Conditions tab

Boundary Conditions

Category/Input Default value Engineering Declaration
G-Factor ** 0.95 Open/editable Open/editable
Solar Clouding 0.8 Locked Calc Locked Calc
Heat per Passenger into Cabin (W) 80 Locked Calc Locked Calc
Passenger Boundary Temperature (oC) 12 Open/editable Locked default
Passenger Density: Low Floor (Pass/m^2) 3 Locked Calc Locked default
Passenger Density: Semi Low Floor (Pass/m^2) 2.2 Locked Calc Locked default
Passenger Density: Raised Floor (Pass/m^2) 1.4 Locked Calc Locked default
Calculated Passenger Number Calculation Locked Calc Locked Calc
U-Values W/(K*m^3) Calculation Locked Calc Locked Calc
Heating Boundary Temperature (oC) 18 Open/editable Locked default
Cooling Boundary Temperature (oC) 23 Open/editable Locked default
Temperature at which cooling turns OFF 17 Locked default
High Ventilation (l/h) 20 Open/editable Locked default
How Ventilation (l/h) 7 Open/editable Locked default
High (m^3/h) Calculation Locked Calc Locked Calc
low (m^3/h) Calculation Locked Calc Locked Calc
High Vent Power (W) Calculation Locked Calc Locked Calc
Low Vent Power (W) Calculation Locked Calc Locked Calc
Specific Ventilation Power (Wh/m3) 0.56 Open/editable Locked default
Aux. Heater Efficiency 0.84 Open/editable Locked default
GCV (Diesel / Heating oil) (kwh/kg) 11.8 Open/editable Locked default
Window Area per Unit Bus Length (m^2/m) Calculation Locked Calc Locked Calc
Front + Rear Window Area (m^2) Calculation Locked Calc Locked Calc
Max Temperature Delta for low Floor Busses (K) 3 Open/editable Locked default
Max Possible Benefit from Technology List (Fraction) 0.5 Open/editable Locked default

INP - Other

Enviromental Conditions

Category/Input Default value Engineering Declaration
Enviromental Temperature (oC) 25 Open/editable Locked default
Solar (W/m²) 400 Open/editable Locked default
Batch-mode ON Open/editable Locked default
Environmental Conditions Database TBC Default Open/editable Locked default

AC-system

Category/Input Default value Engineering Declaration
AC-compressor type 2-stage (0/100) Open/editable Open/OEM data
AC-compressor type (Mechanical / Electrical) Calculation Locked Calc Locked Calc
AC-compressor capacity (kW) 18 Open/editable Locked default
COPCool 3.50 Locked Calc Locked Calc

Ventilation

Category/Input Default value Engineering Declaration
Ventilation during heating Yes Open/editable Locked default
Ventilation when both Heating and AC are inactive Yes Open/editable Locked default
Ventilation during AC Yes Open/editable Locked default
Ventilation flow setting when both Heating and AC are inactive High Open/editable Locked default***
Ventilation during Heating High Open/editable Locked default***
Ventilation during Cooling High Open/editable Locked default***

Aux. Heater

Category/Input Default value Engineering Declaration
Fuel Fired Heater (kW) 30 Open/editable Open/OEM data

*TechList Input**

Insulation

Category/Input Default value Engineering Declaration
Double-glazing TF5 table* Open/editable Tick box only
Tinted windows TF5 table* Open/editable Tick box only

Ventilation

Category/Input Default value Engineering Declaration
Fan controll strategy TF5 table* Open/editable Tick box only

Heating

Category/Input Default value Engineering Declaration
Heat pump systems TF5 table* Open/editable Tick box only
Adjustable coolant thermostat TF5 table* Open/editable Tick box only
Adjustable auxiliary heater TF5 table* Open/editable Tick box only
Engine waste-gas heat exchanger TF5 table* Open/editable Tick box only

Cooling

Category/Input Default value Engineering Declaration
Separate air distribution ducts TF5 table* Open/editable Tick box only

Notes:

* Default parameter values for Technology List from ACEA TF5 proposal

** Tinted Window: G-Factor/g-value (= “solar factor” = “total solar energy transmittance”) according ISO 9050. ISO 9050 defines wind speed at the outside surface of 14 km/h.

Definition of bins for transmission rates according to ACEA TF5 recommendation:

g-value bonus
< 0,1 To be simulated with g = 0,05
0,11 – 0,20 To be simulated with g = 0,15
0,21 – 0,30 To be simulated with g = 0,25
0,31 – 0,40 To be simulated with g = 0,35
0,41 – 0,50 To be simulated with g = 0,45
0,51 – 0,60 To be simulated with g = 0,55
0,61 – 0,70 To be simulated with g = 0,65
0,71 – 0,80 To be simulated with g = 0,75
0,81 – 0,90 To be simulated with g = 0,85
0,91 - 1 To be simulated with g = 0,95

*** Air Flow Rate: recommended for future implementation in Declaration mode by ACEA TF5:

Phase With thermal comfort roof mounted system Without thermal comfort roof mounted system
Cooling High (20x internal volume / h) Low (7x internal volume / h)
Ventilation High (20x internal volume / h) Low (7x internal volume / h)
Heating High (10x internal volume / h) Low (7x internal volume / h)

File Format

The HVAC SSM (.ahsm) and Bus Parameter Database (.abdb) files use the VECTO CSV format.

Vehicle Editor

Description

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

The Vehicle Editor contains 3 tabs to edit all vehicle-related parameters. The ‘General’ tab allows to input mass, loading, air resistance, vehicle axles, etc. The ‘Powertrain’ allows to define the retarder, an optional angle drive, or PTO consumer. In the third tab the engine torque can be limited to a maximum for individual gears.

Relative File Paths

It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. Example: “Demo\RT1.vrlm” points to the “Demo” subdirectory of the Vehicle File’s directoy.

VECTO automatically uses relative paths if the input file (e.g. Retarder Losses File) is in the same directory as the Vehicle File. (Note: 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

Curb Weight Vehicle
Specifies the vehicle’s weight without loading
Curb Weight Extra Trailer/Body
Specifies additional weight due to superstructures on the vehicle or an additional trailer
Loading
Speciefies the loading of both, the vehicle and if available the trailer

Max. Loading displays a hint for the maximum possible loading for the selected vehicle depending on curb weight and GVW values (without taking into account the loading capacity of an additional trailer).

Note: VECTO uses the sum of Curb Weight Vehicle, Curb Weight Extra Trailer/Body and Loading for calculation! The total weight is distributed to all defined axles according to the relative weight share.

In Declaration Mode only the vehicle itself needs to be specified. Depending on the vehicle category and mission the simulation adds a standard trailer for certain missions.

Air Resistance and Corss Wind Correction Options

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. Vecto uses the combined value c~d x A as input. Note that the Air Drag depends on the chosen Cross Wind Correction.

If the vehicle has attached a trailer for simulating certain missions the given cd x A value is increased by a fixed amount depending on the trailer used for the given vehicle category.

For cross wind correction four different options are available:
  • No Correction: The specified CdxA value is used to compute the air drag, no cross-wind correction is applied
  • Speed dependent (User-defined): The specified CdxA value is corrected depending on the vehicle’s speed.
  • Speed dependent (Declaration Mode): A uniformly distributed cross-wind is assumed and used for correcting the air-drag depending on the vehicle’s speed
  • Vair & Beta Input: Correction mode if the actual wind speed and wind angle relative to the vehicle have been measured.

In delcaration mode the ‘Speed dependent (Declaration Mode)’ cross-wind correction is used.

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

Dynamic Tyre Radius

In Engineering Mode this defines the effective (dynamic) wheel radius (in [mm]) used to calculate engine speed. In Declaration Mode the radius calculated automatically using tyres of the powered axle.

Axles/Wheels

For each axle the parameters Relative axle load, RRCISO and FzISO have to be given in order to calculate the total Rolling Resistance Coefficient.

In Engineering mode, the Wheels Inertia [kgm²] has to be set per wheel for each axle. The axles, for both truck and trailer, have to be given.

Use the and buttons to add or remove axles form the vehicle.

In Declaration mode only the axles of the truck have to be given (e.g., 2 axles for a 4x2 truck). The dynamic tyre radius is derived from the second axle as it is assumed this is the driven axle. For missions with a trailer predefined wheels and weight-shares are added by Vecto automatically.

Doubleclick entries to edit existing axle configurations.

Retarder Losses

If a separate retarder is used in the vehicle a Retarder Torque Loss Map can be defined here to consider idling losses caused by the retarder.

Four options are available:
  • No retarder
  • Included in Transmission Loss Maps: Use this if the Transmission Loss Maps already include retarder losses.
  • Primary Retarder (before gearbox): The rpm ratio is relative to the engine speed
  • Secondary Retarder (after gearbox): The rpm ratio is relative to the cardan shaft speed

Both, primary and secondary retarders, require an Retarder Torque Loss Input File (.vrlm).

The Retarder Ratio defines the ratio between the engine speed/cardan shaft speed and the retarder.

Angledrive

If an angledrive is used in the vehicle, it can be defined here. Three options are available:

  • None (default)
  • Separate Angledrive: Use this if the angledrive is measured separately. In this case the ratio must be set and the Transmission Loss Map (or an Efficiency value in Engineering mode) must also be given.
  • Included in transmission: Use this if the gearbox already includes the transmission losses for the angledrive in the respective transmission loss maps.

PTO Transmission

If the vehicle has an PTO consumer, a pto transmission and consumer can be defined here. (Only in Engineering Mode)

Three settings can be set:

  • PTO Transmission: Here a transmission type can be chosen (adds constant load at all times).
  • PTO Consumer Loss Map (.vptol): Here the PTO Idle Loss Map of the pto consumer can be defined (adds power demand when the pto cycle is not active).
  • PTO Cycle (.vptoc): Defines the PTO Cycle which is used when the pto-cycle is activated (when the PTO-Flag in the driving cycle is set).

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

Relative File Paths

It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. Example: “Demo\FLD1.vfld” points to the “Demo” subdirectory of the Engine File’s directory.

VECTO automatically uses relative paths if the input file (e.g. FC Map) is in the same directory as the Engine File. Note: The Engine File must be saved before browsing for input files.)

Main Engine Parameters

Make and Model [text]
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.
Fuel Type
Used to compute derived results such as fuel consumption in liters and CO2 values. This parameter influences the CO2-to-fuel ratio and fuel density. The actual values can be looked up in FuelTypes.csv.
Inertia including Flywheel [kgm²]
Inertia for rotating parts including engine flywheel. In Declaration Mode the inertia is calculated depending on the engine’s displacement and also accounts for the clutch’s inertia.

Full Load and Drag Curves

The Engine’s Full Load and Drag Curves (.vfld) limits the engine’s maximum torque and drag torque respectively The full-load curve must at least cover the engine-speed range from idling speed up to the speed where the power goes down to 70% of the maximum power. The input file (.vfld) file format is described here.

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 Correction Factors are required in Declaration Mode for the WHTC FC Correction.

The Cold/Hot Emission Balancing Factor is an additional correction factor that is used to correct the fuel consumption.

In engineering a single correction factor for correcting WHTC, Cold/Hot Balancing, … can be specified.

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

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 use relative filepaths. This way the Job File and all input files can be moved without having to update the paths.
Example: “Gears\Gear1.vtlm” points to the “Gears” subdirectory of the Gearbox File’s directoy.

VECTO automatically uses relative paths if the input file (e.g. Shift Polygons File) is in the same directory as the Gearbox File. (The Gearbox File must be saved before browsing for input files.)

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:
  • MT: Manual Transmission
  • AMT: Automated Manual Transmission
  • AT-S: Automatic Transmission - Serial
  • AT-P : Automatic Transmission - Power Split
Note: The types AT and Custom are not available in Declaration Mode.

For more details on the automatic transmission please see the AT-Model

Inertia [kgm²]
Rotational inertia of the gearbox (constant for all gears). (Engineering mode only)
Traction Interruption [s]
Interruption during gear shift event. (Engineering mode only)

Gears

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

  • Gear “Axle” defines the ratio of the axle transmission / differential.
  • “Ratio” defines the ratio between the output speed and input speed for the current gear. Must be greater than 0.
  • “Loss Map or Efficiency” allows to define either a constant efficiency value or a loss map (.vtlm). Note: efficiency values are only allowed in engineering mode
  • “Shift polygons” defines the Shift Polygons InputFile (.vgbs) for each gear. Not allowed in Declaration Mode. See GearShift Model for details.
  • “Max Torque” defines the maximum allowed torque (if applicable) for ah gear. It is used for limiting the engine’s torque in certain gear. Note: in Declaration mode the generic shift polygons are computed from the engine’s full-load curve. If the maximum torque is limited by the gearbox, the minimum of the gearbox and engine maximum torque will be used to compute the generic shift polygons!

Gear shift strategy parameters

Since version Vecto 3.0.3 the gearshift polygon calculation according to the ACEA White Book 2016 is implemented and since Vecto 3.0.4 the ACEA White Book 2016 shift strategy for AMT and MT is implemented. The AT-S and AT-P strategies are implemented since Version 3.1.0. For details on this topic please see the ACEA White Book 2016.

The user interface contains input fields for the following parameters:
  • Downshift after upshift delay: to prevent frequent (oscilating) up-/down shifts this parameter blocks downshifts for a certain period after an upshift
  • Upshift after downshift delay: to prevent frequent (oscilating) up-/down shifts this parameter blocks upshifts for a certain period after a downshift
  • Min acceleration after upshift: after an upshift the vehicle must be able to accelerate with at least the given acceleration. The achievable acceleration after an upshift is estimated on the current driving condition and powertrain state.
Torque Reserve [%]
This parameter is required for the Allow shift-up inside polygons and Skip Gears options.
Minimum shift time [s]
Limits the time between two gear shifts. This rule will be ignored if rpms are too high or too low.

Shift Strategy Parameters

Downshift after upshift delay [s]
Minimal duration between an upshift and a consecutive downshift.
Upshift after downshift delay [s]
Minimal duration between an downshift and a consecutive upshift.
Min. acceleration after upshift [m/s²]
Limit for the minimal achievable acceleration to test if an upshift is reasonable.

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.

Torque reserve
The minimal torque reserve which has to be provided.
Reference vehicle speed at clutch-in
The reference vehicle speed
Reference acceleration at clutch-in
The reference acceleration

Torque Converter

Torque converter characteristics file
Defines the Torque converter characteristics file containing the torque ratio and reference torque over the speed ratio.
Inertia [kgm²]
Rotational inertia of the engine-side part of the torque converter. (Gearbox-side inertia is not considered in VECTO.)
Reference RPM
Defines the reference speed at which the torque converter characteristics file was measured.
Max. Speed
Defines the maximum input speed the torque converter can handle.
Torque converter shift polygon
Defines the Shift Polygons InputFile (.vgbs) separately for the torque converter. For details on shifting from/to the torque converter gear please see AT Gear Shift Strategy.

Torque Converter: Minimal acceleration after upshift

Here the minimal achievable accelerations before upshifts can be defined.

Acc. for C->L [m/s²]
The minimal achievable acceleration for shifts from torque converter gear to locked gear.
Acc. for C->C [m/s²]
The minimal achievable acceleration for shifts from first torque converter gear to second torque converter gear (1C->2C)

Power shift losses

Shift time [s]
The shift time for powershift losses.
Inertia factor [-]
The inertia factor for powershift losses.

Chart Area

The Chart Area displays the Shift Polygons Input File(.vgbs) as well as the declaration mode shift polygons (dashed lines) for the selected gear.

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 sent automatically 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

Command Line Arguments

The Vecto 3.x commandline tool can be used to start simulations from the command line and runs without graphical user interface. If multiple job-files are specified or a job-file contains multiple simulation runs (i.e., multiple cycles and/or loadings) these simulations are executed in parallel.

General Notes

  • The order in which the arguments are provided is arbitrary.
  • 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 vectocmd.exe is located).

Basic usage

    vectocmd.exe [-h] [-v] FILE1.(vecto|xml) [FILE2.(vecto|xml) ...]

List of command line arguments

  • FILE1.vecto [FILE2.vecto …]: A list of vecto-job files (with the extension: .vecto). At least one file must be given. Delimited by whitespace.
  • -t: output information about execution times
  • -mod: write mod-data in addition to sum-data
  • -eng: switch to engineering mode (implies -mod)
  • -v: Shows verbose information (errors and warnings will be displayed)
  • -vv: Shows more verbose information (infos will be displayed)
  • -vvv: Shows debug messages (slow!)
  • -vvvv: Shows all verbose information (everything, slow!)
  • -V: show version information
  • -h: Displays this help.

Calculation Modes

VECTO supports different calculation modes for declaring a vehicle, validation of test-results, or experimenting with different parameters and components. These modes are described here.

In the GUI the Calculation Mode can be changed via the Options Tab of the Main Form.

In the Command Line the default Calculation Mode is Declaration, but can be changed to Engineering with the “-eng” flag.

Engineering Mode

The Engineering Mode lets the user define every aspect in the component models of the vehicle and the driving cycle. This is for experimenting and validation purposes.

In this mode the given list of job files is simulated with the respective driving cycles. Each job file defines a separate vehicle.

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). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the ‘Options’ tab on the Main Window
  • Sum results (.vsum). One file for each invocation of VECTO.

Options

The Driving Cycle determines the simulation method in engineering mode. The option depends directly on the driving cycle input and cannot be set explicitely. For more information about the formats see Driving Cycles.

Note: Time-based driving cycles support arbitrary time steps. However, certain actions are simulated within a single simulation interval (e.g. closing the clutch after a gear switch) and may thus result in artefacts during the simulation due to engine inertia, gearbox inertia, etc. Thus the suggested minimum time interval for time-based cycles is 0.5s!

Declaration Mode

In Declaration Mode many input parameters are predefined for the official certification. They are locked in the user interface and will automatically be set 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 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). One file for each vehicle/cycle/loading combination. Modal results are only written if the modal output is enabled in the ‘Options’ tab on the Main Window
  • Sum results (.vsum). One file for each invocation of VECTO.
  • Results (.xml). One file for each job.

Verification Test Mode

The purpose of the verification test is to simulate a vehicle defined in declaration mode on a measured real-driving cycle. This simulation mode uses its own cyle format, requiring mainly vehicle speed, wheel speed, wheel torque, engine-fan speed, and engine speed. VECTO then calculates the appropriate gear and simulates the cycle. Auxiliary power is according to the technologies defined in the vehicle. However, the engine fan auxiliary is ignored and the power demand for the engine fan is calcuated based on the engine-fan speed. The power demand for the other auxiliaries depends on the vehicle’s actual speed. The fuel consumption is calculated using the engine speed from the driving cycle and the torque demand as given in the cycle, adding the losses of all powertrain components.

Requirements

  • One or more checked job files in the Job List
  • Each job must include a vehicle in declaration mode (XML)
  • Each job file must include at least one driving cycle

Results

  • Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the ‘Options’ tab on the Main Window
  • Sum results (.vsum). One file for each invocation of VECTO.

Requirements

  • One or more checked job files in the Job List
  • Each job must include a vehicle in declaration mode (XML)
  • Each job must include the manufacturer report (XML) of the vehicle as generated for the vehicle delcaration
  • Each job file must include exactly one driving cycle (in case multiple driving cycles are provided, only the first cycle is simulated!)

Results

  • VTP Report (.xml). Contains a description of the vehicle and its components, the verification test analysis according to the draft legislation, and a validation of the input data digest values
  • Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the ‘Options’ tab on the Main Window
  • Sum results (.vsum). One file for each invocation of VECTO.

Validations

  • Before the simulation of the measured VTP cycle starts, the provided cycle data is passed through some sanity checks:
  • The cycle is provided in 2Hz
  • The ratio of wheel speeds (left/right) should be lower than 1.4 for wheel speeds above 0.1rpm
  • The absolute difference of wheel speeds (left/right) should be lower than 1rpm for wheel speeds below 0.1rpm
  • The torque ratio (left/right) should be lower than 3 and the absoulte difference should be lower than 200Nm.
  • The fan speed shall be between 20 and 4000rpm, unless the vehicle is equipped with an electric fan
  • The fuel consumption within a window off 10min should be between 180 and 600 g/kWh_(PWheel_pos)

In case the provided cycle exceeds these limits an according warning message is shown in the user interface and written to the report.

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 cycle also has to be in a special format which is described here: Engine Only Driving Cycle.

Simulation Models

In this chapter the used component models for the simulation are described.

Powertrain and Components Structure

The powertrain in Vecto V3 consists of the following components which are generally connected in this order:

The engine tries to supply the requested power demand (including all power losses happening in the powertrain and auxiliaries). If the engine can’t supply the given power demand, the driver reduces the accelerating.

Powertrain Values

The powertrain can be configured to represent different situations depending on the used retarder and gearbox configuration. The output values in the Modfile depict different points in the powertrain depending on the current configuration. Here are some schematic overviews which show the values and the position in the powertrain they represent:

AMT Transmission Input Retarder

AMT Transmission Output Retarder

AT Transmission Input Retarder

AT Transmission Output Retarder

Axle

Driver: Acceleration Limiting

VECTO limits the vehicle acceleration and deceleration depending on current vehicle speed, to model a realistic driver behavior. These limits are defined in the Acceleration Limiting Input File (.vacc), which can be set in the Job File. In Declaration mode this is already predefined.

The graph shows the acceleration and deceleration limits depending on the current vehicle speed.

The graph shows the acceleration and deceleration limits depending on the current vehicle speed.

Driver: Look-Ahead Coasting

Look-Ahead Coasting is a function that aims on modelling real driver behaviour. It is a forward-looking function that detects forthcoming reductions in target speed in the mission profile (e.g. speed limit, etc.) and induces an early deceleration using engine braking before applying mechanical brakes according to the deceleration limit.

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.

Since Vecto 3.0.4 the coasting strategy according to the ACEA White Book 2016 is implemented.

The look ahead coasting functionality represents the driver behavior prior to a deceleration event. Due to information of the route ahead the driver is able to anticipate on the deceleration event by releasing the accelerator pedal.

This pedal release decision is based on an estimation of kinetical and potential (height) energy gain versus the expected dissipated energy tue to vehicle resistances during the route section ahead.

For an upcoming target speed change the energy level after the speed change is compared to the vehicle’s current energy level (kinetic and potential energy). The difference of those energy levels is used to estimate the average deceleration force to reach the next target speed. Coasting starts if the vehicle’s (estimated) average resistance force during coasting multiplied by a speed dependent ‘Decision Factor’ becomes smaller than the average deceleration force. (For details on the equations please see the ACEA White Book 2016, Section 8)

The Decision Factor (DF) depends on the next target speed and the speed change:

DF_{Coasting} = 2.5 - 1.5 * DF_{vel} * DF_{vdrop}

whereas DF_{vel} and DF_{vdrop} are speed dependent and speed change dependent lookup curves, giving a value from 0 and 1.

For the look ahead coasting target speed changes within the preview distance are considered.

preview distance [m] = 10 * vehicle speed [km/h]

Parameters in Job File:
  • PreviewDistanceFactor
  • DF_offset: offset in the equation for DFcoasting (default 2.5)
  • DF_scaling: factor in the equation for DFcoasting (default 1.5)
  • DF_targetSpeedLookup: csv file for DFvel lookup (see below)
  • Df_velocityDropLookup: csv file for DFvdrop lookup (see below)

In engineering mode the parameters can be freely chosen while in declaration mode the default values are used.

Decision Factor for target velocity lookup (DFvel)

Example (default values):

v_target [km/h], decision_factor [-]
0              , 0
48             , 0
52             , 1
100            , 1

Decision Factor for velocity drop lookup (DFvdrop)

Example (default values):

v_drop [km/h], decision_factor [-]
-100          , 1
9             , 1
11            , 0
100           , 0

Driver: Overspeed

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

Eco-Roll is not implemented in Vecto 3.1.

Vehicle: Cross Wind Correction

VECTO offers three different modes to consider cross wind influence on the drag coefficient. It is configured in the Vehicle File. The aerodymanic force is calculated according to the following equation:

F_{aero}=1/2 \rho_{air}(C_{d,v}A(v_{veh})) v_{veh}^2

The speed dependecy of the C_dA value allows for consideration of average cross widn conditions.

Speed dependent correction (Declaration Mode)

This is the mode which is used in Declaration Mode.

The crossind correction is based on the following boundary conditions:

1 Average wind conditions: The typical conditions are defined with 3m/s of wind at a height of 4m above ground level, blowin uniformly distributed from all directions. 2 Dependency of C_dA value on yaw angle: The dependency of the CdA value on yaw angle is described by generic 3^{rd} order polynomial functions of the form:

C_dA(\beta) - C_dA(0) = a_1\beta + a_2\beta^2 + a_3\beta^3

The following table gives the coefficients per vehicle type:

a1 a2 a3
rigid solo 0.013526 0.017746 -0.000666
rigid trailer, EMS 0.017125 0.072275 -0.004148
tractor semitrailer 0.030042 0.040817 -0.002130
bus, coach -0.000794 0.021090 -0.001090

In a pre-processing step VECTO calculates the function for C_dA value as a function of vehicle speed. This is done by integration of all possible directions of the ambient wind from ground level to maximum vehicle height considering the boundary layer effect based on the following formulas:

C_{d,v}A(v_{veh}) = \frac{1}{2 \pi v_{veh}^2 h_{veh}}\int_{\alpha = 0°}^{\alpha = 360°}{\int_{h=0}^{h=h_{veh}}{C_dA(\beta)\cdot v_{air}(h, \alpha)^2} \text{d}h\ \text{d}\alpha}

v_{air}(h) = \sqrt{(v_{wind}(h)\cdot\cos\alpha + v_{veh})^2 + (v_{wind}(h)\cdot\sin\alpha)^2}

v_{wind}(h) = v_{wind}(h_{ref})\cdot \left(\frac{h}{h_{ref}}\right)^{0.2}

with

\alpha \ldots \text{direction of ambient wind relative to the vehicle x-axis}

h \ldots \text{height above ground}

h_{ref} \ldots \text{reference heigth, 4m, for 3m/s average ambient wind}

v_{air} \ldots \text{resulting air flow velocity from vehicle speed and ambient wind}

v_{veh} \ldots \text{vehicle speed}

v_{wind} \ldots \text{velocity of ambient wind}

The generation of the C_{d,v}A(v_{veh}) curve is demonstrated in this Excel sheet

Speed dependent correction (User-defined)

The base CdA value (see Vehicle File) is corrected with a user-defined speed dependent scaling function. A vcdv-File is needed for this calculation.

The CdA value given in the vehicle configuration is corrected depending on the vehicle’s speed and the Cd scaling factor from the input file as follows:

C_dA(v_{veh}) = C_dA * F_C_d(v_{veh})

Correction using Vair & Beta Input

The actual (measured) air speed and direction can be used to correct cross-wid influence if available. A vcdb-File is needed for this calculation. This file defines a ΔCdA value in [m²] depending on the wind angle. The driving cycle must include the air speed relative to the vehicle vair (<vair_res>) and the wind yaw angle (<vair_beta>).

The CdA value given in the vehicle configuration is corrected depending on the wind speed and wind angle (given in the driving cycle) using the input file as follows:

C_dA(v_veh) = C_dA + {\Delta}C_d(\beta)

Vehicle: Rolling Resistance Coefficient

The rolling resistance is calculated using a speed-independent rolling resistance coefficient (RRC). In order to consider that the RRC depends on the vehicle weight it is modelled as a function of the total vehicle mass. The total RRC is calculated in VECTO using the following equation (the index i refers to the vehicle’s axle (truck and trailer)):

RRC = \sum_{i=1}^{n} s_{(i)} \cdot RRC_{ISO(i)} \cdot \left( \frac{s_{(i)} \cdot m \cdot g }{w_{(i)} \cdot F_{zISO(i)} } \right)^{\beta-1}

with:

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

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.

Engine: 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 additional correction factors are applied.

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 grid of triangles with each point of the map being part of at least one triangle.
  2. Find the triangle where the to-be-interpolated load point (x,y) is inside. If no triangle meets the criterion the calculation will be aborted.
  3. Calculate the z-value (= fuel) of the given x,y-point in the plane of the triangle

Delaunay Triangulation Example

Engine: Transient Full Load

The engine implements a PT1 behaviour to model transient torque build up:

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

with:

Vecto 3.x uses basically the same PT1 behavior to model transient torque build up. However, due to the dynamic time steps the formula is implemented as follows:

P_{fld\ dyn_{i}} = P_{fld\ stat}(n_i) \cdot \left(1 - e^{-\frac{t_i^*}{\mathit{PT1}}}\right)

where t* is computed from the dynamic full-load power in the previous simulation interval:

t_i^* = t_{i-1}^* + dt

t_{i-1}^* = \mathit{PT1} \cdot ln\left(\frac{1}{1 - \frac{P_{eng_{i - 1}}}{P_{fld\ stat}(n_i)}}\right)

Engine: Correction Factors

In declaration mode the fuel consumption is corrected as follows:

To prevent inconsistencies of regulated emissions and fuel consumption between the WHTC (hot part) test and the steady state fuel map as well as considering effects of transient engine behaviour a “WHTC correction factor” is used.

Based on the target engine operation points of the particular engine in WHTC the fuel consumption is interpolated from the steady state fuel map (“backward calculation”) in each of the three parts of the WHTC separately. The measured specific fuel consumption per WHTC part in [g/kWh] is then divided by the interpolated specific fuel consumption to obtain the “WHTC correction factors” CFurb (Urban), CFrur (Rural), CFmot (Motorway). For the interpolation the same method as for interpolation in VECTO is applied (Delauney triangulation).

All calculations regarding the brake specific fuel consumption from the interpolation as well as from the measurement and the three correction factors CFurb, CFrur, CFmot are fully implemented in the VECTO-Engine evaluation tool.

The total correction factor CFtotal depends on the mission profile and is produced in VECTO by mission profile specific weighting factors listed in the table below.

CF_{total} = CF_{urb} \cdot WF_{urb} + CF_{rur} \cdot WF_{rur} + CF_{mot} \cdot WF_{mot}

with the correction factor CFurb, CFrur, CFmot coming from the Engine, and weighting factors WFurb, WFrur, WFmot predefined in the declaration data:

Mission profile WFurb WFrur WFmot
Long haul 11% 0% 89%
Regional delivery 17% 30% 53%
Urban delivery 69% 27% 4%
Municipial utility 98% 0% 2%
Construction 62% 32% 6%
Citybus 100% 0% 0%
Interurban bus 45% 36% 19%
Coach 0% 22% 78%

In order to balance the trade-off between emissions and fuel consumption during cold and hot starting conditions an additional balancing factor CF_{C/H} is determined from the overall specific fuel consumption over the cold start and hot start WHTC test. Additional correction factors considered are regarding the net calorific value of the fuel (CF_{NCV}) and exhaust after-treatment systems (CF_{RegPer}). This values are part of the output from the engine component tool.

The WHTC-corrected fuel consumption is then calculated with: FC_{final} = FC \cdot CF_{total} \cdot CF_{C/H} \cdot CF_{RegPer}

In engineering mode a single correction is applied by Vecto. The fuel consumption interpolated from the FC map is multiplied by the engineering correction factor.

FC_{final} = FC \cdot CF_{Engineering}

Engine Torque and Engine Speed Limitations

The engine’s maximum speed and maximum torque may be limited by either the gearbox (due to mechanical constraints) or the vehicle control. Engine torque limitations are modeled by limiting the engine full-load curve to the defined maximum torque, i.e., the original engine full-load curve is cropped at the defined maximum torque for a certain gear. Limits regarding the gearbox’ maximum input speed are modeled by intersecting (and limiting) the upshift line with the max. input speed. In the last gear, where no upshifts are possible, the engine speed is limited to the gearbox’ maximum input speed.

Gear shift polygons are calculated by VECTO based on the overall (i.e. from gearbox and vehicle control) cropped engine fullload curve.

In Engineering Mode, speed and torque limits can be defined and will be effective for every gear.

In Declaration Mode, the following rules restrict the limitations of engine torque:

Transmission Input-Speed Limitations

  • Applicable for every gear

Transmission Torque Limitations

  • For higher 50% of gears (i.e., gears 7 to 12 for a 12-gear transmission):
    • Transmissions max torque > 90% of engine max torque: max. torque limitation not applicable (VECTO extrapolates loss-maps)
    • Transmissions max torque <= 90% of engine max torque: max. torque limitation applicable
  • For lower 50% of gears (i.e., gears 1 to 6 for a 12-gear transmission):
    • Transmission torque limit is always applicable

Vehicle defined Torque Limitations

  • For higher 50% of gears (i.e., gears 7 to 12 for a 12-gear transmission):
    • Torque limit > 95% of engine max torque: max. torque limitation not applicable (VECTO extrapolates loss-maps)
    • Torque limit <= 90% of engine max torque: max. torque limitation applicable
  • For lower 50% of gears (i.e., gears 1 to 6 for a 12-gear transmission):
    • Torque limit is not applicable

Transmission Losses

Every transmission component (gearbox, angledrive, axlegear, …) uses the following formula for calculating the torques at input and output side of the component:

T_{output} = (T_{input} - T_{loss}) * r_{gear}

with:

The following components are accounted as transmission components (see Powertrain and Components Structure for a complete overview over all components in the powertrain):

Gearbox: AT Gearbox Model

Vecto supports both, AT gearboxes with serial torque converter and AT gearboxes with power split. Internally, both gearbox types are simulated using a power train architecture with the torque converter in series.

Automatic transmission with torque converter in series

Automatic transmission with torque converter in series

Automatic transmission with parallel torque converter

Automatic transmission with parallel torque converter

In the input data Gearbox File only the mechanical gears need to be specified. Depending on the gearbox type (AT-S or AT-P) Vecto adds the correct virtual ‘torque converter gear’.

For AT gearbox with serial torque converter, the torque converter uses the same ratio and mechanical losses as the first gear (and second, depending on the gear ratios), and adds the torque converter.

For AT gearboxes using power split the torque converter characteristics already takes the transmission ratio and mechanical losses into account. Hence, Vecto sets the ratio for the mechanical gear to 1 without additional losses.

The .vmod file for vehicles with AT gearboxes contains an additional column that indicates if the torque converter is locked or not.

Gearshift losses for AT Gearboxes

For AT gearboxes the losses during a power-shift are modeled according to the following equations

Basic assumptions

  • Only power-shifts with positive power at gearbox output side are considered.
  • Both upshifts and downshifts with positive power at gearbox output side have to be considered.
  • The power at gearbox output side is assumed to be constant during a power-shift

Power-shift loss computation

Model parameters: shift time (t_s), inertia factor (f_I)

Engine speed, clutch speed during power-shift

Engine speed, clutch speed during power-shift

T_{PS,loss} = |T_{GBX,in} * \Delta\omega_F| * t_s / dt

\Delta\omega_I = \omega_{engine,1} - \omega_{engine,2}

\Delta\omega_F = (\omega_{engine,1} - \omega_{engine,1^*}) / 2

Gearbox: 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 when not in Declaration Mode.

In Declaration Mode the generic shift polygons are computed from the engine’s full-load curve. If the maximum torque is limited by the gearbox, the minimum of the current gear and engine maximum torque will be used to compute the generic shift polygons. Note: the computation of the shift polygons uses characteristic values from the engine such as n95h, npref, etc. which are also derived from the full-load curve.

In the Gearbox File two additional parameters are defined:

Gear Skipping

Gear Skipping is active for AMT and MT. Whenever a gear change is initiated (by crossing the up- or down-shift line) VECTO may skip one or several gears as long as the required torque reserve is provided.

Early Upshift

Early Upshift (allow upshifts inside the shift polygons) is enabled for AMT only. If the next higher gear provides the required torque reserve and it’s rpm is still above down-shift-rpm VECTO will shift up.

Gearbox: MT and AMT Gearshift Rules

This section describes the gearshift rules for manual and automatic manual transmission models. When a gearshift is triggered, gears may be skipped for both MT and AMT gearboxes (see Gearbox: Gear Shift Model). Early Upshift (see Gearbox: Gear Shift Model) is only enabled for AMT gearboxes.

Shift Polygons in Declaration Mode (According to ACEA Whitebook 2016)

1. Computation of Characteristic Points

2. Definition of Shift Lines

3. Exception 1: Margin to Max-Torque line (Downshift)

Note: Line L1 is shiftet parallel so that it satisfies the max-torque margin condition, not intersected.

4. Exception 2: Minimal Distance between Downshift and Upshift Lines

5. Final Gearshift Lines (Example)

If the gearbox defines a maximum input speed for certain gears the upshift line may further be intersected and limited to the gear’s maximum input speed.

Upshift rules

  • If the engine speed is higher than the gearbox maximum input speed or engine n_{95h} speed (whichever is lower)
  • If all of the following conditions are met:
    • The vehicle is not decelerating AND
    • Engine operation point (speed and torque) is above (right of) the upshift line AND
    • The acceleration in the next gear is above a certain threshold if the driver is accelerating, i.e., acceleration_nextGear > min(Min. acceleration threshold, Driver acceleration) AND
    • The last gearshift was longer than a certain threshold (Declaration Mode: 2s) ago AND
    • The last downshift was longer than a certain threshold (Declaration Mode: 10s) ago

Upshift rules for Early Upshift (AMT only)

  • If the engine speed is higher than the gearbox maximum input speed or engine n_{95h} speed (whichever is lower)
  • If all of the following conditions are met:
    • The vehicle is not decelerating AND
    • The engine’s operating point (speed and torque) is above the downshift line with a certain margin to the max. torque (torque reserve) AND
    • The acceleration in the next gear is above a certain threshold if the driver is accelerating, i.e., acceleration_nextGear > min(Min. acceleration threshold, Driver acceleration) AND
    • The last gearshift was longer than a certain threshold (Declaration Mode: 2s) ago AND
    • The last downshift was longer than a certain threshold (Declaration Mode: 10s) ago

Downshift

  • If the engine speed is lower than the engine’s idle speed
  • If all of the following conditions are met:
    • Engine operation point (speed and torque) is below (left of) the downshift line AND
    • The last gearshift was longer than a certain threshold (Declaration Mode: 2s) ago AND
    • The last upshift was longer than a certain threshold (Declaration Mode: 10s) ago

Shift parameters

  • Gearshift lines
  • Engine idle speed
  • Gearbox max. input speed
  • Engien n_{95h} speed
  • Min. time between two consecutive gearshifts.
  • Min. time for upshift after a downshift
  • Min. time for downshift after an upshift
  • Min. acceleration in next gear

For Skip Gears and Early Upshift the following additional parameters are required:

  • Torque reserve

Gearbox: AT Gearshift Rules

For AT gearboxes neither Skip Gears nor Early upshift (see Gearbox: Gear Shift Model) are enabled. Moreover, the gears are shifted strictly sequentially:

Shift Polygons in Declaration Mode

The shift lines in Declaration Mode only apply for trucks and gearboxes with serial torque converter (AT-S).

  • Downshift line: 700 rpm (torque independent, vertical line)
  • Upshift line: 900 rpm for torque <= 0; 1150 rpm @ Engine’s maximum torque

Upshift rules

  • If engine speed and engine torque in the next gear (see shift sequence) is above the upshift line AND
  • the acceleration in the next gear is above a certain threshold if the driver is accelerating, i.e., acceleration_nextGear > min(Min. acceleration threshold, Driver acceleration)

The user interface allows to enter two acceleration thresholds, one for locked gear to locked gear shifts and another vor converter to locked gear shifts. For converter to converter shifts the latter threshold applies.

Downshift

  • If the engine speed falls below the downshift curve

  • Drivetrain in “Neutral” when either
    • velocity < 5 km/h
    • OR during deceleration phase when the torque converter is active and the engine speed would fall below idle speed

Shift parameters

  • Min. time between two consecutive gearshifts.
  • Min. acceleration after gearshift for L to L gear shifts
  • Min. acceleration after gearhsift for C to L gear shifts
  • Min. acceleration after gearshift for C to C geear shifts

Torque Converter Model

The torque converter is defined as (virtual) separate gear. Independent of the chosen AT gearbox type (serial or power split), Vecto uses a powertrain architecture with a serial torque converter. The mechanical gear ratios and gears with torque converter are created by Vecto depending on the gearbox type and gear configuration.

While the torque converter is active engine torque and speed are computed based on TC characteristic.

Torque converter characteristics file (.vtcc)

The file is described here.

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

  • Speed Ratio (ν) = Output Speed / Input Speed
  • Torque Ratio (μ) = Output Torque / Input Torque
  • Input Torque (Tref(ν)) is the input torque (over ν) for a specific reference engine speed (see below).

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}

\mu(\nu) = \frac{T_{out}}{T_{in}}

with:

  • Tin = engine torque [Nm]
  • Tref(ν) = reference torque at reference rpm (from .vtcc file) [Nm]
  • nin = engine speed [1/min]
  • nref = reference rpm [1/min] (see below)

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

Note: The torque converter characteristics must not contain parts where either the torque ratio or the input torque are constant!

In declaration mode, the torque converter for drag points is automatically appended by VECTO. Input data with a speed ratio ≥ 1 are skipped.

For Power Split transmissions, where the torque converter characteristics already contains the gearbox losses and transmission ratio, the generic drag points are adapted according to the following equations:

\nu_{PS} = \nu / ratio_i

\mu_{PS} = \mu \cdot ratio_i

In engineering mode the drag points for the torque converter can be specified. If so, the input data has to cover at least the speed ratio up to 2.2.

If the torque converter characteristics for drag are not specified, the generic points are appended as described above for declaration mode.

The torque converter has a separate Shift Polygon which defines the conditions for switching from torque converter gear to locked gear.

Auxiliaries

In Declaration mode the auxiliaries are pre-defined and the power demand is defined based on the vehicle category and mission. For every type of auxiliary (fan, steering pump, HVAC, electrig system, pneumatic system) the user can select a technology from a given list.

In Engineering mode VECTO uses a generic map-based approach to consider all types of auxiliaries. The supply power demand for each single auxiliary is defined in the driving cycle. Hence a time/distance-dependent power demand can be defined. Based on the supply power and a pre-defined efficiency map the auxiliary input power is calculated. A constant efficiency determines the losses between auxiliary and engine.

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

  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

  6. **Psupply is defined in the driving cycle

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/auxiliary must include supply power for each auxiliary. To link the supply power in the driving cycle to the correct auxiliary in the Job File an ID is used. The corresponding supply power is then named “<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.

In addition to the generic map-based auxiliaries approach it is also possible to specify a constant load applied to the engine during the whole mission.

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

Requirements

  • Driving Cycle must include t, Pwheel (Pwheel), Gear (Gear) and Engine Speed (n), see Driving Cycle (.vdri) format.
  • The driving cycle must be time-based.

Example driving cycle 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

PTO

VECTO supports the simulation of PTO related components and losses in the powertrain. Structurally this consists of 2 components (PTO transmission, PTO consumer) and 3 different kind of losses (transmission, idling, cycle).

Structural Overview of PTO Components

Losses in the PTO “Transmission” part (blue)

This is considered by constant power consumption as a function of the PTO type. The power consumption is added in all vehicle operation conditions, due to VECTO not differentiating between clutch open/closed and gear engaged/disengaged. The PTO type is configurable in the Vehicle Editor. The exact values are shown in the following table:

Technology Power Loss [W]
None 0
only the drive shaft of the PTO - shift claw, synchronizer, sliding gearwheel 50
only the drive shaft of the PTO - multi-disc clutch 1000
only the drive shaft of the PTO - multi-disc clutch, oil pump 2000
drive shaft and/or up to 2 gear wheels - shift claw, synchronizer, sliding gearwheel 300
drive shaft and/or up to 2 gear wheels - multi-disc clutch 1500
drive shaft and/or up to 2 gear wheels - multi-disc clutch, oil pump 3000
drive shaft and/or more than 2 gear wheels - shift claw, synchronizer, sliding gearwheel 600
drive shaft and/or more than 2 gear wheels - multi-disc clutch 2000
drive shaft and/or more than 2 gear wheels - multi-disc clutch, oil pump 4000

Idling losses of the PTO “Consumer” (red)

The idling losses are a function of speed as determined by the DIN 30752-1 procedure. If the PTO transmission includes a shifting element (i.e. declutching of consumer part possible) the torque losses of the consumer in VECTO input shall be defined with zero. This is only used outside of PTO cycles, since the PTO cycles already include these losses. The idling losses are defined as a lossmap dependend on speed which is configurable in the Vehicle Editor. The file format is described in PTO Idle Consumption Map.

Cycle losses during the PTO cycle of the PTO “Consumer” (red)

A specific PTO cycle (time-based, engine speed and torque from PTO consumer as determined by the DIN 30752-1 procedure) is simulated during vehicle stops labelled as “with PTO activation”. The execution of the driving cycle stops during this time and the pto cycle is executed. Afterwards the normal driving cycle continues.

Power consumption in the PTO transmission part added to power demand from the PTO cycle. The cycle is configurable in the Vehicle Editor and follows the file format described in PTO-Cycle. The timings in the PTO cycle get shifted to start at 0.

Behavior During PTO Driving Cycles

A PTO cycle can only be activated during a stop phase in the driving cycle. When the PTO cycle is activated VECTO exhibits the following behavior: Half of the stop time is added before the pto cycle, and the other half is added afterwards. If the halved stop times are still longer than 3 seconds, they get divided even further to 3 intervals in order to achieve a more appealing visualization in the output (falling down, low baseline, rising again). It is recommended to have a stop time of at least 2 seconds.

The following image shows the behavior of running PTO cycles during a normal driving cycle:

  1. Normal driving behavior.
  2. The first half of the stop phase begins, the vehicle stops and the engine speed goes down to idle speed (if there is enough time).
  3. The PTO cycle continues from the last engine speed in stop phase and sets it to the engine speed of the first entry in the PTO cycle.
  4. After the PTO cycle ends, the second half of the stop phase begins and the engine speed again goes to idle speed (if enough time passes).
  5. After the stop phase the normal driving behavior starts again - the vehicle drives off.

Input and Output

Vecto uses data files for input and output of data. These are stored in different formats which are listed here.

Input:

Output:

XML Job-File (Declaration Mode)

For vehicle certification the input data (vehicle data) has to be provided in XML format. Please see the following resources for more information:

XML Declaration Report

In Declaration Mode VECTO generates two reports according to the Technical Annex for vehicle certification:

  • Manufacturer Report
  • Customer Information Report

Both reports are in XML format and contain a description of the simulated vehicle and the simulation results. The format is described in the following resources:

Sample reports are distributed with the generic vehicles.

Note: For better readability and improved presentation, the XML has attached a stylesheet that allows nice rendering in web-browsers. If you open an XML report in your browser, you may be asked the credentials for the CITnet SVN server (same credentials as you need for downloading VECTO) as the CSS is hosted on CITnet.

CSV

Many data files in Vecto use CSV (Comma Separated Values) as common file format. They consist of a header which defines the columns and data entries which are separated by a comma (“,”).

In Vecto 3 the order of the columns is arbitrary if the column header matches the header definitions described in this user manual. If the column header does not match, a warning is written to the log file and the columns are parsed in the sequence as described in this manual as a fall-back.

Definition

Header: Vecto CSV needs exactly one header line with the definition of the columns at the beginning of the file.
Columns can be surrounded with “<” and “>” to mark them as identifiers (which makes them position independent). In Vecto 3.x every column is seen as identifier, regardless of “<>”.
Columns may be succeded with unit information (enclosed in “[" and “]”) for documentation purposes.
Column Separator: , (Comma. Separates the columns of a data line.)
Decimal-Mark: . (Dot. Splits numbers into integer part and decimal part.)
Thousand-Separator: Vecto CSV does not allow a thousand-separator.
Comments: # (Number sign. Declares text coming afterwards in the current line as comment.)
Whitespace: Whitespaces between columns will be stripped away. Therefore it is possible to align the columns for better readability, if desired.

Note: All column headers are case insensitive.

Note: Unit information in the column header (enclosed in “[" and “]”) are only information for the user. Vecto does not read the unit string nor convert between units. The values are expected to be in the units as specified in the user manual.

Following files use the csv:

Notes: The Auxiliary Input File (.vaux) uses a modified csv format with some special headers.

Examples

Exampl 1: Acceleration Limiting File

v [km/h],acc [m/s^2]     ,dec [m/s^2]
0       ,1.01570922360353,-0.231742702878269
5       ,1.38546581120225,-0.45346198022574
10      ,1.34993329755465,-0.565404125020508
15      ,1.29026714002479,-0.703434814668512

Example 2: Driving Cycle

<s>,<v>,<grad>      ,<stop>,<Padd>,<Aux_ALT1>,<Aux_ALT2>,<Aux_ALT3>
0  ,0  ,-0.020237973,2     ,6.1   ,0.25      ,0.25      ,0.25
1  ,64 ,-0.020237973,0     ,6.1   ,0.25      ,0.25      ,0.25
2  ,64 ,-0.020237973,0     ,6.1   ,0.25      ,0.25      ,0.25
3  ,64 ,-0.020237973,0     ,6.1   ,0.25      ,0.25      ,0.25

Example 3: Transmission Loss Map

Input Speed [rpm],Input Torque [Nm],Torque Loss [Nm]
0                ,-2500            ,77.5
0                ,-1500            ,62.5
0                ,-500             ,47.5
0                ,500              ,47.5

JSON

Configuration and component files in Vecto use JSON as common file format.

Following files use JSON:

Job File

File for the definition of an job in vecto. A job contains everything what is needed to run a simulation. Can be created with the Job Editor.

Refers to other files:

Example:

{
  "Header": {
    "CreatedBy": "Michael Krisper (Graz University of Technology)",
    "Date": "2016-03-18T14:37:05+01:00",
    "AppVersion": "3.0.2",
    "FileVersion": 2
  },
  "Body": {
    "SavedInDeclMode": false,
    "VehicleFile": "Vehicle.vveh",
    "EngineFile": "Engine.veng",
    "GearboxFile": "Gearbox.vgbx",
    "Cycles": [
      "DrivingCycle_Rural.vdri",
      "DrivingCycle_Urban.vdri"
    ],
    "Aux": [
      {
        "ID": "ALT",
        "Type": "Alternator",
        "Path": "Alternator.vaux",
        "Technology": ""
      },
      {
        "ID": "PN",
        "Type": "PneumaticSystem",
        "Path": "Pneumatic System.vaux",
        "Technology": ""
      },
      {
        "ID": "HVAC",
        "Type": "HVAC",
        "Path": "AirCondition.vaux",
        "Technology": ""
      }
    ],
    "VACC": "Driver.vacc",
    "EngineOnlyMode": true,
    "StartStop": {
      "Enabled": false,
      "MaxSpeed": 5.0,
      "MinTime": 0.0,
      "Delay": 0
    },
    "LAC": {
      "Enabled": true,
      "Dec": -0.5,
      "MinSpeed": 50.0
    },
    "OverSpeedEcoRoll": {
      "Mode": "OverSpeed",
      "MinSpeed": 70.0,
      "OverSpeed": 5.0,
      "UnderSpeed": 5.0
    }
  }
}

VTP-Job File

File for the definition of a verification test job in vecto. A job contains everything what is needed to run a simulation. Can be created with the Verifcation Test Job Editor.

Refers to other files:

Example:

{
  "Header": {
    "CreatedBy": "VECTO 3.2",
    "Date": "2017-11-14T13:16:31.7337506Z",
    "AppVersion": "3",
    "FileVersion": 4
  },
  "Body": {
    "SavedInDeclMode": false,
    "DeclarationVehicle": "SampleVehicle.xml",
    "FanPowerCoefficients": [
      0.00000055,
      14.62,
      108.5
    ],
    "FanDiameter": 0.225,
    "Cycles": [
      "VTP-cycle.vdri"
    ]
  }
}

Vehicle File (.vveh)

File for the definition of a vehicle in vecto. Can be created with the Vehicle Editor.

Refers to other files:

Example:

{
  "Header": {
    "CreatedBy": "Michael Krisper (Graz University of Technology)",
    "Date": "2016-03-18T14:42:45+01:00",
    "AppVersion": "3.0.2",
    "FileVersion": 7
  },
  "Body": {
    "SavedInDeclMode": false,
    "VehCat": "RigidTruck",
    "CurbWeight": 6000.0,
    "CurbWeightExtra": 0.0,
    "Loading": 0.0,
    "MassMax": 11.9,
    "CdA": 4.5,
    "rdyn": 450,
    "Rim": "15° DC Rims",
    "CdCorrMode": "CdOfVeng",
    "CdCorrFile": "CrossWindCorrection.vcdv",
    "Retarder": {
      "Type": "Secondary",
      "Ratio": 1.0,
      "File": "Retarder.vrlm"
    },
    "AngularGear": {
      "Type" : "SeparateAngularGear",
      "Ratio": 1.0,
      "LossMap": "AngularGear.vtlm"
    },
    "AxleConfig": {
      "Type": "4x2",
      "Axles": [
        {
          "Inertia": 6.0,
          "Wheels": "245/70 R19.5",
          "AxleWeightShare": 0.0,
          "TwinTyres": false,
          "RRCISO": 0.008343465,
          "FzISO": 20800.0
        },
        {
          "Inertia": 6.0,
          "Wheels": "245/70 R19.5",
          "AxleWeightShare": 0.0,
          "TwinTyres": true,
          "RRCISO": 0.00943769,
          "FzISO": 20800.0
        }
      ]
    }
  }
}

Speed Dependent Cross Wind Correction Input File (.vcdv)

The file is needed for speed dependent Cross Wind Correction. The file uses the VECTO CSV format.

Example:

v_veh [km/h],Cd [-]
0           ,1.173
5           ,1.173
10          ,1.173
15          ,1.173
20          ,1.173
25          ,1.173
30          ,1.173
35          ,1.173
40          ,1.173
45          ,1.173
50          ,1.173
55          ,1.173
60          ,1.173
65          ,1.153
70          ,1.136
75          ,1.121
80          ,1.109
85          ,1.099
90          ,1.090
95          ,1.082
100         ,1.07

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

The file is needed for Vair & Beta Cross Wind Correction. The file uses the VECTO CSV format.

Example:

beta [°],delta CdA [m^2]
0       ,0.00
1       ,0.07
2       ,0.21
3       ,0.40
4       ,0.64
5       ,0.90
6       ,1.19
7       ,1.48
8       ,1.76
9       ,2.02
10      ,2.25
20      ,3.14
40      ,3.24
60      ,-0.76
80      ,-4.76
100     ,-9.01
120     ,-15.01
140     ,-21.01
160     ,-20.86
180     ,-16.15

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. The file uses the VECTO CSV format.

Example:

Retarder Speed [1/min],Torque Loss [Nm]
0                     ,10
100                   ,10.02
200                   ,10.08
300                   ,10.18
...

Engine File (.veng)

File for the definition of an engine in Vecto. Can be created with the Engine Editor.

Refers to other files:

Example:

{
  "Header": {
    "CreatedBy": "Michael Krisper (Graz University of Technology",
    "Date": "2016-10-03T15:25:00+01:00",
    "AppVersion": "3.1.0",
    "FileVersion": 3
  },
  "Body": {
    "SavedInDeclMode": false,
    "ModelName": "Engine",
    "Displacement": 7700.0,
    "IdlingSpeed": 600.0,
    "Inertia": 3.789,
    "FullLoadCurve": "EngineFullLoadCurve.vfld",
    "FuelMap": "FuelConsumptionMap.vmap",
    "WHTC-Engineering": 1.03
  }
}

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. The file uses the VECTO CSV format.

Note: The PT1 column is not required in Declaration Mode! Pre-defined values are used.

Example:

engine speed [1/min],full load torque [Nm],motoring torque [Nm],PT1 [s]
560                 ,1180                 ,-149                ,0.6
600                 ,1282                 ,-148                ,0.6
800                 ,1791                 ,-149                ,0.6
...

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. The file uses the VECTO CSV format.

Extrapolation of fuel consumption map is possible in Engineering Mode (with warnings!). In Declaration Mode it is not allowed.

Example:

engine speed [rpm],torque [Nm],fuel consumption [g/h]
600               ,-45        ,0
600               ,0          ,767
600               ,100        ,1759
600               ,200        ,2890
600               ,300        ,4185
600               ,400        ,5404
600               ,500        ,6535
600               ,600        ,7578
...

Gearbox File (.vgbx)

File for the definition of a gearbox in Vecto. Can be created with the Gearbox Editor.

Refers to other files:

Example:

{
  "Header": {
    "CreatedBy": "Michael Krisper (Graz University of Technology)",
    "Date": "2016-03-18T14:37:18+01:00",
    "AppVersion": "3.0.2",
    "FileVersion": 5
  },
  "Body": {
    "SavedInDeclMode": false,
    "ModelName": "Generic 8 Gears",
    "Inertia": 0.0,
    "TracInt": 1.0,
    "Gears": [
      {
        "Ratio": 3.2,
        "LossMap": "Axle.vtlm"
      },
      {
        "Ratio": 6.4,
        "LossMap": "Indirect Gear.vtlm",
        "TCactive": false,
        "ShiftPolygon": "ShiftPolygon.vgbs",
        "FullLoadCurve": "<NOFILE>"
      },
      {
        "Ratio": 4.6,
        "LossMap": "Indirect Gear.vtlm",
        "TCactive": false,
        "ShiftPolygon": "ShiftPolygon.vgbs",
        "FullLoadCurve": "<NOFILE>"
      },
      {
        "Ratio": 3.4,
        "LossMap": "Indirect Gear.vtlm",
        "TCactive": false,
        "ShiftPolygon": "ShiftPolygon.vgbs",
        "FullLoadCurve": "<NOFILE>"
      },
      {
        "Ratio": 2.6,
        "LossMap": "Indirect Gear.vtlm",
        "TCactive": false,
        "ShiftPolygon": "ShiftPolygon.vgbs",
        "FullLoadCurve": "<NOFILE>"
      },
      {
        "Ratio": 1.9,
        "LossMap": "Indirect Gear.vtlm",
        "TCactive": false,
        "ShiftPolygon": "ShiftPolygon.vgbs",
        "FullLoadCurve": "<NOFILE>"
      },
      {
        "Ratio": 1.3,
        "LossMap": "Indirect Gear.vtlm",
        "TCactive": false,
        "ShiftPolygon": "ShiftPolygon.vgbs",
        "FullLoadCurve": "<NOFILE>"
      },
      {
        "Ratio": 1,
        "LossMap": "Direct Gear.vtlm",
        "TCactive": false,
        "ShiftPolygon": "ShiftPolygon.vgbs",
        "FullLoadCurve": "<NOFILE>"
      },
      {
        "Ratio": 0.75,
        "LossMap": "Indirect Gear.vtlm",
        "TCactive": false,
        "ShiftPolygon": "ShiftPolygon.vgbs",
        "FullLoadCurve": "<NOFILE>"
      }
    ],
    "TqReserve": 20.0,
    "SkipGears": true,
    "ShiftTime": 2,
    "EaryShiftUp": true,
    "StartTqReserve": 20.0,
    "StartSpeed": 2.0,
    "StartAcc": 0.6,
    "GearboxType": "AMT",
    "TorqueConverter": {
      "Enabled": false,
      "File": "<NOFILE>",
      "RefRPM": 0.0,
      "Inertia": 0.0
    }
    "DownshiftAferUpshiftDelay": 10.0,
    "UpshiftAfterDownshiftDelay": 10.0,
    "UpshiftMinAcceleration": 0.1
  }
}

Shift Polygons Input File (.vgbs)

Defines up- and down-shift curves. See Gear Shift Model for details. The file uses the VECTO CSV format.

Example:

engine torque [Nm],downshift rpm [1/min],upshift rpm [1/min]
-400              ,560                  ,1289
759               ,560                  ,1289
1252              ,742                  ,1289
2372              ,1155                 ,1942
...

Example Graph:

A typical shift curve.

A typical shift curve.

Transmission Loss Map (.vtlm)

This file defines losses in transmission components, i.e. every gear, axlegear, angledrive. See Transmission Losses (#transmission-losses) for the formula how the losses are accounted in the components. The file uses the VECTO CSV format.

Input speed and input torque are meant at the engine-side.

Example:

Input Speed [rpm],Input Torque [Nm],Torque Loss [Nm]
0                ,-350             ,6.81
0                ,-150             ,5.81
0                ,50               ,5.31
0                ,250              ,6.31
0                ,450              ,7.31
0                ,650              ,8.31

Sign of torque values

  • Input Torque >0 means normal driving operation.
  • Input Torque <0 means motoring operation. The Torque Loss Map must include negative torque values for engine motoring operation!
  • Torque Loss must always be positive!

Torque Converter Characteristics (.vtcc)

The file uses the VECTO CSV format.

See Torque Converter Model for more information about the component model.

Example:

Speed Ratio, Torque Ratio, MP1000
        0.0,         1.93, 377.80
        0.1,         1.82, 365.21
        0.2,         1.70, 352.62
        0.3,         1.60, 340.02
        0.4,         1.49, 327.43
        0.5,         1.39, 314.84
        0.6,         1.28, 302.24
        0.7,         1.18, 264.46
        0.8,         1.07, 226.68
        0.9,         0.97, 188.90
        1.0,         0.97, 0.00
...

PTO Cycle (.vptoc)

The PTO cycle defines the power demands during standing still and doing a pto operation. This can only be used in Engineering Mode when a pto transmission is defined. It can be set in the Vehicle-Editor. The basic file format is Vecto-CSV and the file type ending is “.vptoc”. A PTO cycle is time-based and may have variable time steps, but it is recommended to use a resolution between 1[Hz] and 2[Hz]. Regardless of starting time, VECTO shifts it to always begin at 0[s].

Header: <t>, <Engine speed>, <PTO Torque>

Bold columns are mandatory. Only the listed columns are allowed (no other columns!).
The order is not important when the headers are annotated with <angle-brackets> (less-than-sign “<” and greater-than-sign “>”).
Units are optional and are enclosed in [square-brackets] after the header-column. Comments may be written with a preceding hash-sign “#”.

Identifier Unit Description
t [s] The time during the pto cycle. Must always be increasing. Gets shifted to begin with 0 by VECTO (if thats not already the case).
Engine speed [rpm] Actual engine speed
PTO Torque [Nm] The torque at the PTO consumer (including prop-shaft losses if applicable) as measured by the DIN test converted to torque at engine speed

Example:

<t> [s], <Engine speed> [rpm], <PTO Torque> [Nm]
0      , 600                 , 0
1      , 600                 , 0
2      , 900                 , 0
3      , 1200                , 50
4      , 1200                , 70
5      , 1200                , 100

PTO Idle Consumption Map (.vptoi)

The pto idle consumption map defines the speed-dependent power demand when the pto cycle is not active. This is only be used in Engineering Mode when a pto transmission is defined. The exact demand is interpolated based on the engine speed. PTO consumer idling losses are added to engine loads during any parts of the vehicle operation except the “PTO cycle”. It can be defined in the Vehicle-File and set via the Vehicle-Editor. The basic file format is Vecto-CSV and the file type ending is “.vptoi”.

Header: <Engine speed>, <PTO Torque>

Bold columns are mandatory. Only the listed columns are allowed (no other columns!).
The order is not important when the headers are annotated with <angle-brackets> (less-than-sign “<” and greater-than-sign “>”).
Units are optional and are enclosed in [square-brackets] after the header-column. Comments may be written with a preceding hash-sign “#”.

Identifier Unit Description
Engine speed [rpm] The engine speed.
PTO Torque [Nm] Torque Loss by the PTO consumer (including prop-shaft losses if applicable) as measured by the DIN test converted to torque at engine speed

Example:

<Engine speed> [rpm], <PTO Torque> [Nm]
600                   ,  8.0027
800                   , 12.2902
1000                  , 16.7431
1200                  , 20.3244
1400                  , 26.4444
1600                  , 32.1234

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. The file uses the VECTO CSV format with three additional parameters on top of the efficiency map.

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

Example:

Transmission ratio to engine rpm [-]
4.078
Efficiency to engine [-]
0.96
Efficiency auxiliary to supply [-]
1
Auxiliary speed [rpm],Mechanical power [kW],Supply power [kW]
1415                 ,0.07                 ,0
1415                 ,0.87                 ,0.53
1415                 ,1.03                 ,0.64
1415                 ,1.17                 ,0.75
...

Advanced Auxiliary Input Data (.aaux)

Example:

{
  "$type": "VectoAuxiliaries.AuxiliaryConfig, BusAuxiliaries",
  "VectoInputs": {
    "$type": "VectoAuxiliaries.VectoInputs, AdvancedAuxiliaryInterfaces",
    "Cycle": "Urban",
    "VehicleWeightKG": 16500.0,
    "PowerNetVoltage": 28.3,
    "FuelMap": "testFuelGoodMap.vmap",
    "FuelDensity": null
  },
  "ElectricalUserInputsConfig": {
    "$type": "VectoAuxiliaries.Electrics.ElectricsUserInputsConfig, BusAuxiliaries",
    "PowerNetVoltage": 28.3,
    "AlternatorMap": "testCombAlternatorMap_1Alt.AALT",
    "AlternatorGearEfficiency": 0.92,
    "ElectricalConsumers": {
      "$type": "VectoAuxiliaries.Electrics.ElectricalConsumerList, BusAuxiliaries",
      "DoorDutyCycleFraction": 0.096,
      "Items": [
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Doors",
          "ConsumerName": "Doors per Door",
          "NominalConsumptionAmps": 3.0,
          "NumberInActualVehicle": 3,
          "PhaseIdle_TractionOn": 0.096339,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": true,
          "Category": "Veh Electronics &Engine",
          "ConsumerName": "Controllers,Valves etc",
          "NominalConsumptionAmps": 25.0,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "Radio City",
          "NominalConsumptionAmps": 2.0,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 0.8,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "Radio Intercity",
          "NominalConsumptionAmps": 5.0,
          "NumberInActualVehicle": 0,
          "PhaseIdle_TractionOn": 0.8,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "Radio/Audio Tourism",
          "NominalConsumptionAmps": 9.0,
          "NumberInActualVehicle": 0,
          "PhaseIdle_TractionOn": 0.8,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "Fridge",
          "NominalConsumptionAmps": 4.0,
          "NumberInActualVehicle": 0,
          "PhaseIdle_TractionOn": 0.5,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "Kitchen Standard",
          "NominalConsumptionAmps": 67.0,
          "NumberInActualVehicle": 0,
          "PhaseIdle_TractionOn": 0.05,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "Interior lights City/ Intercity + Doorlights [1/m]",
          "NominalConsumptionAmps": 1.0,
          "NumberInActualVehicle": 12,
          "PhaseIdle_TractionOn": 0.7,
          "PowerNetVoltage": 28.3,
          "Info": "1 Per metre length of bus"
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "LED Interior lights ceiling city/ontercity + door [1/m]",
          "NominalConsumptionAmps": 0.6,
          "NumberInActualVehicle": 0,
          "PhaseIdle_TractionOn": 0.7,
          "PowerNetVoltage": 28.3,
          "Info": "1 Per metre length of bus"
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "Interior lights Tourism + reading [1/m]",
          "NominalConsumptionAmps": 1.1,
          "NumberInActualVehicle": 0,
          "PhaseIdle_TractionOn": 0.7,
          "PowerNetVoltage": 28.3,
          "Info": "1 Per metre length of bus"
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Vehicle basic equipment",
          "ConsumerName": "LED Interior lights ceiling Tourism + LED reading [1/m]",
          "NominalConsumptionAmps": 0.66,
          "NumberInActualVehicle": 0,
          "PhaseIdle_TractionOn": 0.7,
          "PowerNetVoltage": 28.3,
          "Info": "1 Per metre length of bus"
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Customer Specific Equipment",
          "ConsumerName": "External Displays Font/Side/Rear",
          "NominalConsumptionAmps": 2.65017676,
          "NumberInActualVehicle": 4,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Customer Specific Equipment",
          "ConsumerName": "Internal display per unit ( front side rear)",
          "NominalConsumptionAmps": 1.06007063,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Customer Specific Equipment",
          "ConsumerName": "CityBus Ref EBSF Table4 Devices ITS No Displays",
          "NominalConsumptionAmps": 9.3,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Lights",
          "ConsumerName": "Exterior Lights BULB",
          "NominalConsumptionAmps": 7.4,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Lights",
          "ConsumerName": "Day running lights LED bonus",
          "NominalConsumptionAmps": -0.723,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Lights",
          "ConsumerName": "Antifog rear lights LED bonus",
          "NominalConsumptionAmps": -0.17,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Lights",
          "ConsumerName": "Position lights LED bonus",
          "NominalConsumptionAmps": -1.2,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Lights",
          "ConsumerName": "Direction lights LED bonus",
          "NominalConsumptionAmps": -0.3,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        },
        {
          "$type": "VectoAuxiliaries.Electrics.ElectricalConsumer, BusAuxiliaries",
          "BaseVehicle": false,
          "Category": "Lights",
          "ConsumerName": "Brake Lights LED bonus",
          "NominalConsumptionAmps": -1.2,
          "NumberInActualVehicle": 1,
          "PhaseIdle_TractionOn": 1.0,
          "PowerNetVoltage": 28.3,
          "Info": ""
        }
      ]
    },
    "DoorActuationTimeSecond": 4,
    "ResultCardIdle": {
      "$type": "VectoAuxiliaries.Electrics.ResultCard, BusAuxiliaries",
      "Results": []
    },
    "ResultCardTraction": {
      "$type": "VectoAuxiliaries.Electrics.ResultCard, BusAuxiliaries",
      "Results": []
    },
    "ResultCardOverrun": {
      "$type": "VectoAuxiliaries.Electrics.ResultCard, BusAuxiliaries",
      "Results": []
    },
    "SmartElectrical": false
  },
  "PneumaticUserInputsConfig": {
    "$type": "VectoAuxiliaries.Pneumatics.PneumaticUserInputsConfig, BusAuxiliaries",
    "CompressorMap": "DEFAULT_2-Cylinder_1-Stage_650ccm.ACMP",
    "CompressorGearRatio": 1.0,
    "CompressorGearEfficiency": 0.8,
    "AdBlueDosing": "Pneumatic",
    "AirSuspensionControl": "Electrically",
    "Doors": "Pneumatic",
    "KneelingHeightMillimeters": 80.0,
    "ActuationsMap": "testPneumaticActuationsMap.APAC",
    "RetarderBrake": true,
    "SmartAirCompression": true,
    "SmartRegeneration": true
  },
  "PneumaticAuxillariesConfig": {
    "$type": "VectoAuxiliaries.Pneumatics.PneumaticsAuxilliariesConfig, BusAuxiliaries",
    "AdBlueNIperMinute": 21.25,
    "AirControlledSuspensionNIperMinute": 15.0,
    "BrakingNoRetarderNIperKG": 0.00081,
    "BrakingWithRetarderNIperKG": 0.0006,
    "BreakingPerKneelingNIperKGinMM": 6.6E-05,
    "DeadVolBlowOutsPerLitresperHour": 24.0,
    "DeadVolumeLitres": 30.0,
    "NonSmartRegenFractionTotalAirDemand": 0.26,
    "OverrunUtilisationForCompressionFraction": 0.97,
    "PerDoorOpeningNI": 12.7,
    "PerStopBrakeActuationNIperKG": 0.00064,
    "SmartRegenFractionTotalAirDemand": 0.12
  },
  "HvacUserInputsConfig": {
    "$type": "VectoAuxiliaries.Hvac.HVACUserInputsConfig, BusAuxiliaries",
    "SSMFilePath": "testHVACssm.AHSM",
    "BusDatabasePath": "BusDatabase.abdb",
    "SSMDisabled": false
  },
  "Signals": {
    "$type": "VectoAuxiliaries.Signals, AdvancedAuxiliaryInterfaces",
    "ClutchEngaged": false,
    "EngineDrivelinePower": 0.0,
    "EngineDrivelineTorque": 0.0,
    "EngineMotoringPower": 0.0,
    "EngineSpeed": 2000,
    "SmartElectrics": false,
    "SmartPneumatics": false,
    "TotalCycleTimeSeconds": 3114,
    "CurrentCycleTimeInSeconds": 0,
    "PreExistingAuxPower": 0.0,
    "Idle": false,
    "InNeutral": false,
    "AuxiliaryEventReportingLevel": 0,
    "EngineStopped": false,
    "DeclarationMode": false,
    "WHTC": 1.0,
    "EngineIdleSpeed": 0.0
  }
}

Alternator Input Data (.aalt)

[AlternatorName],[RPM],[Amps],[Efficiency],[PulleyRatio]
Alt1,2000,10.000,50.000,3.000
Alt1,2000,40.000,50.000,3.000
Alt1,2000,60.000,50.000,3.000
Alt1,4000,10.000,70.000,3.000
Alt1,4000,40.000,70.000,3.000
Alt1,4000,60.000,70.000,3.000
Alt1,6000,10.000,60.000,3.000
Alt1,6000,40.000,60.000,3.000
Alt1,6000,60.000,60.000,3.000
Alt2,2000,10.000,80.000,2.500
Alt2,2000,40.000,80.000,2.500
Alt2,2000,60.000,80.000,2.500
Alt2,4000,10.000,40.000,2.500
Alt2,4000,40.000,40.000,2.500
Alt2,4000,60.000,40.000,2.500
Alt2,6000,10.000,60.000,2.500
Alt2,6000,40.000,60.000,2.500
Alt2,6000,60.000,60.000,2.500
Alt3,2000,10.000,95.000,3.500
Alt3,2000,40.000,50.000,3.500
Alt3,2000,60.000,90.000,3.500
Alt3,4000,10.000,99.000,3.500
Alt3,4000,40.000,1.000,3.500
Alt3,4000,60.000,55.000,3.500
Alt3,6000,10.000,94.000,3.500
Alt3,6000,40.000,86.000,3.500
Alt3,6000,60.000,13.000,3.500
Alt4,2000,10.000,55.000,2.000
Alt4,2000,40.000,45.000,2.000
Alt4,2000,60.000,67.000,2.000
Alt4,4000,10.000,77.000,2.000
Alt4,4000,40.000,39.000,2.000
Alt4,4000,60.000,23.000,2.000
Alt4,6000,10.000,34.000,2.000
Alt4,6000,40.000,67.000,2.000
Alt4,6000,60.000,35.000,2.000
[MODELSOURCE]

** Alt1 ** , PulleyRatio 3
******************************************************************

Table 1 (2000)  Table 2 (4000)  Table 3 (6000)
Amps    Eff Amps    Eff Amps    Eff 

0   50.000  0   70.000  0   60.000  
10  50.000  10  70.000  10  60.000  
40  50.000  40  70.000  40  60.000  
60  50.000  60  70.000  60  60.000  
61  50.000  61  70.000  61  60.000  
200 50.000  200 70.000  200 60.000  

** Alt2 ** , PulleyRatio 2.5
******************************************************************

Table 1 (2000)  Table 2 (4000)  Table 3 (6000)
Amps    Eff Amps    Eff Amps    Eff 

0   80.000  0   40.000  0   60.000  
10  80.000  10  40.000  10  60.000  
40  80.000  40  40.000  40  60.000  
60  80.000  60  40.000  60  60.000  
61  80.000  61  40.000  61  60.000  
200 80.000  200 40.000  200 60.000  

** Alt3 ** , PulleyRatio 3.5
******************************************************************

Table 1 (2000)  Table 2 (4000)  Table 3 (6000)
Amps    Eff Amps    Eff Amps    Eff 

0   95.000  0   99.000  0   94.000  
10  95.000  10  99.000  10  94.000  
40  50.000  40  1.000   40  86.000  
60  90.000  60  55.000  60  13.000  
63  95.000  76  99.000  64  0.000   
200 95.000  200 99.000  200 0.000   

** Alt4 ** , PulleyRatio 2
******************************************************************

Table 1 (2000)  Table 2 (4000)  Table 3 (6000)
Amps    Eff Amps    Eff Amps    Eff 

0   55.000  0   77.000  0   34.000  
10  55.000  10  77.000  10  34.000  
40  45.000  40  39.000  40  67.000  
60  67.000  60  23.000  60  35.000  
61  67.000  89  0.000   82  0.000   
200 67.000  200 0.000   200 0.000   

********* COMBINED EFFICIENCY VALUES **************

    RPM VALUES
AMPS    500 1500    2500    3500    4500    5500    6500    7500
1   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
2   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
3   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
4   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
5   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
6   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
7   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
8   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
9   0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
10  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
11  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
12  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
13  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
14  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
15  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
16  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
17  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
18  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
19  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
20  0.659   0.686   0.644   0.521   0.430   0.371   0.330   0.308   
...

Advanced Compressor Map (.acmp)

This file is used to configure the compressor map for pneumatic auxiliaries, and contains data relating to the compressor performance at various engine speeds.

File Format

The file uses the VECTO CSV format, with an example provided below.

Format

Example Configuration for Advanced Compressor Map:

RPM, FlowRate [l/min], Power [on] [W], Power [off] [W]
1500, 200, 2000, 1000
2000, 400, 4000, 2000
3000, 600, 6000, 3000
4000, 800, 8000, 4000
5000, 1000, 10000, 5000
6000, 1200, 12000, 6000
7000, 1400, 14000, 7000

The following four Default maps have been provided for use until a certified test procedure is established:

  1. DEFAULT_1-Cylinder_1-Stage_393ccm
rpm,flowRate [l/min],power [on] [W],power [off] [W]
500,83.42357042,1428,181.9
750,141.6565216,1890,342.4
1000,198.5612781,2467.5,513.6
1250,241.9965577,3097.5,716.9
1500,293.5664883,3759,866.7
1750,335.5358341,4294.5,1080.7
2000,398.488427,5166,1273.3
2250,425.0944822,6006,1433.8
2500,458.3225806,6541.5,1540.8
2750,478.2312925,7066.5,1712
3000,511.85438,7665,1958.1
  1. DEFAULT_2-Cylinder_1-Stage_650ccm
rpm,flowRate [l/min],power [on] [W],power [off] [W]
800,250.5365596,3139.5,524.3
1200,374.3533986,4609.5,1027.2
1600,508.4123859,6205.5,1572.9
2000,619.1263282,7770,2065.1
2400,762.6185788,9723,2696.4
2550,819.2371476,10363.5,2856.9
2800,898.7501978,11613,3349.1
3200,979.4827586,13282.5,4012.5
  1. DEFAULT_2-Cylinder_2-Stage_398ccm
rpm,flowRate [l/min],power [on] [W],power [off] [W]
800,209.7130243,2079,160.5
1200,348.3681702,3160.5,342.4
1600,411.2603567,4315.5,604.55
2000,520.8333333,5901,963
2400,598.4042553,6961.5,1433.8
2550,618.1318681,7360.5,1637.1
2800,655.1473124,8127,1968.8
3200,806.2234795,10043.25,2755.25
3600,857.9169175,11571,3702.2
  1. DEFAULT_3-Cylinder_2-Stage_598ccm
rpm,flowRate [l/min],power [on] [W],power [off] [W]
700,268.8679245,2698.5,149.8
1200,455.170778,4641,363.8
1700,619.9877948,6772.5,823.9
2200,723.0141287,8778,1508.7
2550,800.5469547,10468.5,2075.8
2800,913.4228898,12253.5,2461
3300,996.5379955,14070,3145.8
3550,1048.442907,15078,3755.7

Pneumatic Actuations Map (.apac)

This file contains data on number of different kinds of pneumatic actuations on different duty cycles.

Important notes Note that the cycle file name used should ideally respect this syntax to be correctly associated with the actuation map (.apac), otherwise the number of actuations will be set at 0 by default:

Some flexibility in syntax is allowable (the model looks for ‘Bus’, ‘Coach’, ‘Urban’, etc. in the file name), meaning that the standard default cycles are fully/correctly supported. However, for newly created cycles (i.e. for use in Engineering Mode) it is recommended to follow the above convention to guarantee correct functionality.

This file contains also the estimated time required for a cycle which is required to estimate the air demand for certain actuations.

File Format

The file uses the VECTO CSV format, with an example provided below, with the default values based on the methodology agreed with the European Commission and the project Steering Group.

Format

Default Configuration for Pneumatic Actuations Map:

ConsumerName, CycleName, Actuations
Brakes, Heavy Urban, 191
Brakes, Urban, 153
Brakes, Suburban, 49
Brakes, Interurban, 190
Brakes, Coach, 27
Brakes, UnknownCycleName, 0
Park brake + 2 doors, Heavy Urban, 82
Park brake + 2 doors, Urban, 75
Park brake + 2 doors, Suburban, 25
Park brake + 2 doors, Interurban, 9
Park brake + 2 doors, Coach, 6
Park brake + 2 doors, UnknownCycleName, 0
Kneeling, Heavy Urban, 27
Kneeling, Urban, 25
Kneeling, Suburban, 6
Kneeling, Interurban, 0
Kneeling, Coach, 0
Kneeling, UnknownCycleName, 0,
CycleTime,Heavy urban,8912
CycleTime,Urban,8149
CycleTime,Suburban,3283
CycleTime,Interurban,12962
CycleTime,Coach,15086
CycleTime,UnknownCycleName,3600

Environmental Conditions Batch Input File (.aenv)

This file contains data on number of different environmental/climatic conditions that can be run through the HVAC SSM module when it is in batch-mode to generate a weighted average output for HVAC power and fuelling loads.

File Format

The file uses the VECTO CSV format, with an example provided below, with the default values based on the methodology agreed with the European Commission and the project Steering Group.

Format

Default Climatic Conditions input file:

ID, EnvTemp, Solar, WeightingFactor
1, -20, 10, 0.0053
2, -5, 30, 0.0826
3, 2, 30, 0.0826
4, 8, 20, 0.1661
5, 8, 155, 0.0826
6, 14, 30, 0.0826
7, 14, 175, 0.1243
8, 20.5, 30, 0.1243
9, 20.5, 200, 0.1243
10, 26, 150, 0.0826
11, 33, 150, 0.0427

Driving Cycles (.vdri)

A Driving Cycle defines the parameters of a simulated route in Vecto. It is either time-based or distance-based and has different fields depending on the driving cycle type. The basic file format is Vecto-CSV and the file type ending is “.vdri”. A Job must have at least one driving cycle (except in Declaration mode, where the driving cycles are predefined).

Driving Cycle Types

Declaration Mode Cycles

In Declaration Mode driving cycles are automatically chosen depending on vehicle category and cannot be changed by the user. These predefined cycles are of type target-speed, distance-based.

  • Coach: 275km
  • Construction: 21km
  • Heavy Urban: 30km
  • Inter Urban: 123km
  • Long Haul: 100km
  • Municipal Utility: 10km
  • Regional Delivery: 26km
  • Sub Urban: 23km
  • Urban: 40km
  • Urban Delivery: 28km

Verification Test Cycle

This kind of cycle is used for simulating vehicles defined in declaration mode (xml) on a real driving cycle.

Header: <t>, <v>, <n_eng>,<n_fan>, <tq_left>, <tq_right>, <n_wh_left>, <n_wh_right>, <fc>, <gear>

Bold columns are mandatory. Italic columns are optional. Only the listed columns are allowed (no other columns!).
Units are optional and are enclosed in [square-brackets] after the header-column. Comments may be written with a preceding hash-sign “#”.

Identifier Unit Description
t [s] The absolute time. Must always be increasing.
v [km/h] The actual velocity of the vehicle. Must be >= 0 km/h.
n_eng [rpm] The actual engine speed. Must be >= 0 rpm.
n_fan [rpm] The actual engine-fan speed. Must be >= 0 rpm.
tq_left [Nm] The actual torque at the driven wheel (left side)
tq_right [Nm] The actual torque at the driven wheel (left side)
n_wh_left [rpm] The actual wheel speed of the driven wheel (left side). Must be >= 0 rpm.
n_wh_right [rpm] The actual wheel speed of the driven wheel (right side). Must be >= 0 rpm.
fc [g/h] Fuel consumption
gear [-] The actual gear

Example:

<t> [s] <v> [km/h] <n_eng> [rpm] <n_fan> [rpm] <tq_left> [Nm] <tq_right> [Nm] <n_wh_left> [rpm] <n_wh_right> [rpm] <fc> [g/h] <gear>
0 0 599.7 727.3 319.1 429.8 0.78 0.78 836 3
0.5 0 600.2 727.3 316.7 430.0 0.78 0.78 836 3
1 0 600.1 726.9 319.9 430.8 0.78 0.78 836 3
1.5 0 599.9 726.6 317.4 431.1 0.78 0.79 836 3
2 0 600.1 726.2 319.5 421.7 0.78 0.78 836 3
2.5 0 599.7 726 319.0 434.1 0.78 0.78 836 3
3 0 600.2 725.4 322.2 428.5 0.78 0.78 836 3
3.5 0 599.9 724.7 317.3 430.4 0.78 0.78 836 3
4 0 599.5 724.0 320.9 428.0 0.78 0.78 836 3
4.5 0 599.9 723.4 187.0 247.6 0.78 0.78 836 3
5 0 598.7 722.5 156.9 171.5 0.78 0.78 1003.2 3

Engineering Mode: Target-Speed, Distance-Based Cycle

This driving cycle defines the target speed over distance. Vecto tries to achieve and maintain this target speed.

Header: <s>, <v>, <stop>[, <Padd>][, <grad>][, <PTO>][, <vair_res>, <vair_beta>][, <Aux_ID>]

Bold columns are mandatory. Italic columns are optional. Only the listed columns are allowed (no other columns!).
Units are optional and are enclosed in [square-brackets] after the header-column. Comments may be written with a preceding hash-sign “#”.

Note: if the cycle starts with a target speed of 0 km/h and the stop-time for the first entry is 0, VECTO sets the stop-time to 1s automatically.

Identifier Unit Description
s [m] Traveled distance. Must always be increasing.
v [km/h] The target vehicle velocity. Must be >= 0 km/h.
stop [s] Stopping Time. Defines the time span the vehicle is standing still (time the vehicle spending in a stop phase). After this time, the vehicle tries to accelerate to <v>. If during a stop phase the PTO cycle is activated, it is recommended to use at least 2 seconds of stop time (which gets split up: first half before the PTO cycle, second half after the PTO cycle).
Padd [kW] Additional auxiliary power demand. This power demand will be directly added to the engine power in addition to possible other auxiliaries. Must be >= 0 kW.
grad [%] The road gradient.
PTO [0/1] “0”=disabled or “1”=enabled. If at a vehicle stop (defined by target velocity=0) “1” is specified, the PTO cycle as specified in the *.vptoc–File is simulated. This is described in the PTO Simulation Model The PTO activation is added to the simulation time in the middle of the stopping time as defined by the cycle parameter “stop”. The PTO Cycle can be specified in the Vehicle Editor. When PTO is activated it is recommended to use at least 2 seconds as stop time.
vair_res [km/h] Air speed relative to vehicle for cross wind correction. Only required if Cross Wind Correction is set to Vair & Beta Input.
vair_beta [°] Wind Yaw Angle for cross wind correction. Only required if Cross Wind Correction is set to Vair & Beta Input.
Aux_ID [kW] Auxiliary Supply Power. Can be defined multiple times with different Identifiers. The supply power input for each auxiliary defined in the .vecto file with the corresponding ID. ID’s are not case sensitive and must only contain letters and numbers [a-z,A-Z,0-9]. Must be >= 0 kW.

Example:

<s> [m] <v> [km/h] <stop> [s] <grad> [%] <Padd> [kW]
0 10 10 2.95 1.5
1 20 0 2.97 1.3
2 35 0 3.03 1.3
3 50 0 2.99 1.3

Engineering Mode: Measured-Speed, Time-Based Cycle

This driving cycle defines the actual measured speed over time. Vecto tries to simulate the vehicle model using this speed as the actual vehicle speed. Due to differences in the real and simulated shift strategies a small difference in speed can occur, but Vecto immediately tries to catch up after the gear is engaged again.

Header: <t>, <v>[, <grad>][, <Padd>][, <vair_res>, <vair_beta>][, <Aux_ID>]

Bold columns are mandatory. Italic columns are optional. Only the listed columns are allowed (no other columns!).
Units are optional and are enclosed in [square-brackets] after the header-column. Comments may be written with a preceding hash-sign “#”.

Identifier Unit Description
t [s] The absolute time. Must always be increasing.
v [km/h] The actual velocity of the vehicle. Must be >= 0 km/h.
Padd [kW] Additional auxiliary power demand. This power demand will be directly added to the engine power in addition to possible other auxiliaries. Must be >= 0 kW.
grad [%] The road gradient.
vair_res [km/h] Air speed relative to vehicle for cross wind correction. Only required if Cross Wind Correction is set to Vair & Beta Input.
vair_beta [°] Wind Yaw Angle for cross wind correction. Only required if Cross Wind Correction is set to Vair & Beta Input.
Aux_ID [kW] Auxiliary Supply Power. Can be defined multiple times with different Identifiers. The supply power input for each auxiliary defined in the .vecto file with the corresponding ID. ID’s are not case sensitive and must only contain letters and numbers [a-z,A-Z,0-9]. Must be >= 0 kW.

Example:

<t> [s] <v> [km/h] <grad> [%] <Padd> [kW]
0 0 2.95 1.5
1 0.6 2.97 1.3
2 1.2 3.03 1.3
3 2.4 2.99 1.3

Engineering Mode: Measured-Speed With Gear, Time-Based Cycle

This driving cycle defines the actual measured speed of the vehicle, the gear, and the engine speed over time. It overrides the shift strategy of Vecto and also directly sets the engine speed.

Header: <t>, <v>, <gear>[, <tc_active>, <grad>][, <Padd>][, <vair_res>, <vair_beta>][, <Aux_ID>]

Bold columns are mandatory. Italic columns are optional. Only the listed columns are allowed (no other columns!).
Units are optional and are enclosed in [square-brackets] after the header-column. Comments may be written with a preceding hash-sign “#”.

Identifier Unit Description
t [s] The absolute time. Must always be increasing.
v [km/h] The actual velocity of the vehicle. Must be >= 0 km/h.
gear [-] The current gear. Must be >= 0 (0 is neutral).
tc_active [-] For AT gearboxes mandatory! Indicate if the torque converter is active or locked. Depending on the gearbox type only allowed for 1st gear or 1st and 2nd gear.
Padd [kW] Additional auxiliary power demand. This power demand will be directly added to the engine power in addition to possible other auxiliaries. Must be >= 0 kW.
grad [%] The road gradient.
vair_res [km/h] Air speed relative to vehicle for cross wind correction. Only required if Cross Wind Correction is set to Vair & Beta Input.
vair_beta [°] Wind Yaw Angle for cross wind correction. Only required if Cross Wind Correction is set to Vair & Beta Input.
Aux_ID [kW] Auxiliary Supply Power. Can be defined multiple times with different Identifiers. The supply power input for each auxiliary defined in the .vecto file with the corresponding ID. ID’s are not case sensitive and must only contain letters and numbers [a-z,A-Z,0-9]. Must be >= 0 kW.

Example:

<t> [s] <v> [km/h] <gear> [-] <grad> [%] <Padd> [kW]
0 0 0 2.95 1.5
1 0.6 3 2.97 1.3
2 1.2 3 3.03 1.3
3 2.4 3 2.99 1.3

Engineering Mode: Pwheel (SiCo), Time-Based

This driving cycle defines the power measured at the wheels over time. Vecto tries to simulate the vehicle with this power requirement.

Header: <t>, <Pwheel>, <gear>, <n>[, <Padd>]

Bold columns are mandatory. Italic columns are optional. Only the listed columns are allowed (no other columns!).
Units are optional and are enclosed in [square-brackets] after the header-column. Comments may be written with a preceding hash-sign “#”.

Identifier Unit Quantity Description
t [s] The absolute time. Must always be increasing.
Pwheel [kW] Power at the wheels.
gear [-] The current gear. Must be >= 0 (0 is neutral).
n [rpm] The actual engine speed. Must be >= 0 rpm.
Padd [kW] Additional auxiliary power demand. This power demand will be directly added to the engine power. Must be >= 0 kW.

Example:

<t> [s] <Pwheel> [kW] <gear> [-] <n> [rpm] <Padd> [kW]
0 0 0 600 1.5
1 4.003 3 950 1.3
2 15.333 3 1200 1.3
3 50.56 3 1400 1.3

Engine Only Mode: Engine Only Driving Cycle

This driving cycle directly defines the engine’s power or torque at the output shaft over time. Vecto adds the engine’s inertia to the given power demand and simulates the engine.

Header: <t>, <n>, (<Pe>|<Me>)[, <Padd>]

Bold columns are mandatory. Italic columns are optional. Only the listed columns are allowed (no other columns!).
Units are optional and are enclosed in [square-brackets] after the header-column. Comments may be written with a preceding hash-sign “#”.

Identifier Unit Description
t [s] The absolute time. Must always be increasing.
n [rpm] The actual engine speed. Must be >= 0 rpm.
Pe [kW] The power at the output shaft of the engine. Either <Pe> or <Me> must be defined.
Me [Nm] The torque at the output shaft of the engine. Either <Pe> or <Me> must be defined.
Padd [kW] Additional auxiliary power demand. This power demand will be directly added to the engine power. Must be >= 0 kW.

Example:

<t> [s] <n> [rpm] <Pe> [kW] <Padd> [kW]
0 600 0 1.5
1 950 25.3 1.3
2 1200 65.344 1.3
3 1400 110.1 1.3

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. The file uses the VECTO CSV format.

Note: The deceleration should be lower than a certain threshold for low speeds in order to guarantee accurate vehicle stops during simulation. The suggested deceleration should be lower than -0.5m/s^2 for vehicle speeds below 30 km/h.

Example Data:

v [km/h],acc [m/s^2],dec [m/s^2]
0       ,1          ,-1
25      ,1          ,-1
50      ,0.6        ,-1
60      ,0.5        ,-0.5
120     ,0.5        ,-0.5

Example Graph:

The graph shows the acceleration and deceleration limits depending on the current vehicle speed.

The graph shows the acceleration and deceleration limits depending on the current vehicle speed.

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 in the format “X-Y” (with X as filenumber, and Y as cycle number)
Input File [-] Name of the input job file (.vecto)
Cycle [-] Name of the cycle file (or cycle name in declaration mode)
Status [-] The result status of the run (Success, Aborted)
Mass [kg] Vehicle mass (Curb Weight Vehicle + Curb Weight Extra Trailer/Body, see Vehicle Editor)
Loading [kg] Vehicle loading (see Vehicle Editor)
Cargo Volume [m^3] Vehicle cargo volume (Declaration Mode only!)
time [s] Total simulation time
distance [km] Total traveled distance
speed [km/h] Average vehicle speed
altitudeDelta [m] Altitude difference between start and end of cycle
FC-Map [g/h], [g/km] Average fuel consumption before all corrections, interpolated from Fuel Map, based on torque and engine speed.
FC-AUXc [g/h], [g/km] Average fuel consumption after Auxiliary-Start/Stop Correction (Based on FC-Map)
FC-WHTCc [g/h], [g/km] Average fuel consumption after WHTC Correction (Based on FC-AUXc)
FC-AAUX [g/h], [g/km] Average fuel consumption after Smart Auxiliary Correction (still in development) (Based on FC-WHTCc)
FC-Final [g/h], [g/km], [l/100km], [l/100tkm], [l/100m^3km] Final average fuel consumption after ALL corrections. Value for calculation of CO2 value. If Loading = 0[kg] the column [l/100tkm] is left empty.
CO2 [g/km], [g/tkm], [g/m^3km] Average CO2 emissions (based on FC-Final value). Output for [l/100tkm] is empty when Loading = 0[kg].
P_wheel_in_pos [kW] Average positive power at the wheels
P_fcmap_pos [kW] Average positive power at engine (all non-negative values averaged over the whole cycle duration)
E_fcmap_pos [kWh] Total positive work provided by the combustion engine.
E_fcmap_neg [kWh] Total energy
E_powertrain_inertia [kWh] Total work of engine, torqueconverter, and gearbox inertia
E_aux_xxx [kWh] Energy demand of auxiliary with ID xxx. See also Aux Dialog and Driving Cycle. In Declaration Mode the following auxiliaries always exists: E_aux_FAN (Fan), E_aux_PS (Pneumatic System), E_aux_STP (Steering Pump), E_aux_ES (Electrical System), E_aux_AC (Air Condition)
E_aux_sum [kWh] Total energy demand of all auxiliaries. This is the sum for all E_aux_xxx columns.
E_clutch_loss [kWh] Total energy loss in the clutch
E_tc_loss [kWh] Total torque converter energy loss
E_gbx_loss [kWh] Total transmission energy losses at gearbox (includes loss-map, inertia, and gear-shifts). E_shift_loss is already included here.
E_shift_loss [kWh] Total energy losses due to gearshifts
E_ret_loss [kWh] Total retarder energy loss
E_angle_loss [kWh] Total torque converter energy loss
E_axl_loss [kWh] Total transmission energy losses at the axlegear
E_brake [kWh] Total work dissipated in mechanical braking (sum of service brakes, retader and additional engine exhaust brakes)
E_vehicle_inertia [kWh] Total work of wheels inertia and vehicle mass
E_air [kWh] Total work of air resistance
E_roll [kWh] Total work of rolling resistance
E_grad [kWh] Total work of gradient resistance
E_PTO_CONSUM [kWh] Total energy demand of the pto consumer (if a pto consumer was used).
E_PTO_TRANSM [kWh] Total energy demand of the pto transmission (if a pto transmission was used).
a [m/s2] Average acceleration
a_pos [m/s2] Average acceleration in acceleration phases (a3s > 0.125 [m/s2], a3s = 3-seconds-averaged acceleration)
a_neg [m/s2] Average deceleration in deceleration phases (a3s < 0.125 [m/s2], a3s = 3-seconds-averaged acceleration)
AccelerationTimeShare [%] Time share of acceleration phases (a3s > 0.125 [m/s2], a3s = 3-seconds-averaged acceleration)
DecelerationTimeShare [%] Time share of deceleration phases (a3s < 0.125 [m/s2], a3s = 3-seconds-averaged acceleration)
CruiseTimeShare [%] Time share of cruise phases (-0.125 ≤ a3s ≤ 0.125 [m/s2])
StopTimeShare [%] Time share of stop phases (v < 0.1 [m/s])

Energy Bilance

To ensure the energy bilance of the vehicle, the following formulas are always ensured:

Hint: E_shift_loss is not taken into account here, because it is already included in E_gbx_loss.

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 vecto@jrc.ec.europa.eu.

Changelog

VECTO 3.3.0

Build 1250 (2018-06-04)

VECTO 3.2.1

Build 1133 (2018-02-07)

Build 1079 (2017-12-15)

Build 1054 (2017-11-20)

VECTO 3.2.0

Build 1022 (2017-10-19)

Build 1005 (2017-10-01)

Build 940 (2017-07-28)

Build 925 (2017-07-13)

VECTO 3.1.2

Build 810 (2017-03-21)

Build 796 (2017-03-07)

VECTO 3.1.1

Build 748 (2017-01-18)

Build 742 (2017-01-12)

VECTO 3.1.0

Build 683 (2016-11-14)

Build 662 (2016-10-24)

Build 652 (2016-10-14)


VECTO 3.0.4

Build 565 (2016-07-19)

Build 544 (2016-06-28)


VECTO 3.0.3

Build 537 (2016-06-21)

Build 495 (2016-05-10)


VECTO 3.0.2

Build 466 (2016-04-11)

Build 448 (2016-03-24)

Build 434 (2016-03-10)