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.

All

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

Add files to Job List

Remove selected files from List

Move selected files up or down in list

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

Write modal results

Toggle output of modal results (.vmod files). Summary files (.vsum, .vres) are always created.

Modal results in 1Hz

If selected, the modal results (.vmod file) will be converted into 1Hz after the simulation.

Controls

New Job File

Create a new .vecto file using the VECTO Editor

Open existing Job or Input File

Open an existing input file (Job, Engine, etc.)

Tools

• Job, Vehicle, Engine, Gearbox Editor
  • Opens the respective Editor
• Graph
  • Open a new Graph Window
• Open Log
  • Opens the Log File in the system’s default text editor
• Settings
  • Opens the Settings dialog.

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

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

Fuel Density [kg/l]

The Fuel Density is used to calculate the l/km results.

CO₂ -to-Fuel Ratio[-]

Mass ratio (kg_CO2 / kg_FC) used to calculate CO₂ emissions.

These settings are only used in Engineering mode. In Declaration mode the default values are 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

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 Engine File (.veng)
• Driving Cycles including engine torque (or power) and engine speed

Filepath to the Vehicle File (.vveh)

Files can be created and edited using the Vehicle Editor.

Filepath to the Engine File (.veng)

Files can be created and edited using the Engine Editor.

Filepath ot the Gearbox File(.vgbx)

Files can be created and edited using the Gearbox Editor.

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.

Add cycle (.vdri)

Remove the selected cycle from the list

Driver Assist Tab

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

Engine Start/Stop

See Engine Start/Stop for details.

Overspeed

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 Job File

Create a new empty .vecto file

Open existing Job File

Open an existing .vecto file

Save current Job File

Save Job File as…

Send current file to Job List in Main Form

Note: The file will be sent to the Job List automatically when saved.

Open Vehicle Editor

Open Engine Editor

Open Gearbox Editor

Browse for vehicle/engine/gearbox files

Save and close file

File will be added to Job List in the Main Form.

Cancel without saving

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

Controls

Save and close

Close without saving

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

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

List of Electrical Consumables

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

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

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

Pneumatic Variables

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

INP - Boundary Conditions tab

Boundary Conditions

INP - Other

Enviromental Conditions

AC-system

Ventilation

Aux. Heater

*TechList Input**

Insulation

Ventilation

Heating

Cooling

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:

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

File Format

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

Description

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

Relative File Paths

It is recommended to 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

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.

Air Resistance and Corss Wind Correction Options

The product of Drag Coefficient [-] and Cross Sectional Area [m²] (c_d x A) and Air Density [kg/m³] (see Settings) 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.

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.

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, RRC_ISO and F_zISO have to be given in order to calculate the total Rolling Resistance Coefficient.

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

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.

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

Chart Area

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

Controls

New file

Create a new empty .veng file

Open existing file

Open an existing .veng 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.

Open file browser.

Open file (see File Open Command).

Save and close file

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

Cancel without saving

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

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

Open existing file

Open an existing .vgbx 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.

Open file browser

Open file (see File Open Command).

Save and close file

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

Cancel without saving

Description

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

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

Channels

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

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

X Axis Controls

The X Axis can either show distance or time.

Min, Max

Sets the range for the x axis.

Reset button

Reset the x axis range to display the complete cycle.

+, - buttons

Zoom in/out on the x axis.

<, > buttons

Move the x axis range left/right.

Controls

Open a .vmod file

Open a new Graph Window

Reload the currently open file

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.

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.

• Target speed, distance-based

  This option is the a target vehicle speed distance based cycle (like in Declaration Mode). With this option experiments can be made by the manufacturer.

• Measured speed, time-based

  Driving Mode where the actual speed from measurements is simulated.

• Measured speed with gear, time-based

  Driving Mode where the actual speed from measurements is simulated. Also defines the chosen gear.

• Pwheel (SiCo) Mode, time-based

  In Pwheel mode the measured power at the wheels is given, and the simulation takes that as input.

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

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 overview (.pdf). One file for each job.

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

AMT Transmission Input Retarder

AMT Transmission Output Retarder

AT Transmission Input Retarder

AT Transmission Output Retarder

Axle

Decision Factor for target velocity lookup (DF_vel)

Example (default values):

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

Decision Factor for velocity drop lookup (DF_vdrop)

Example (default values):

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

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.

Speed dependent correction (Declaration Mode)

This is the mode which is used in Declaration Mode. The speed dependent C_dA curve (see below) is calculated based on generic parameters for each vehicle class and the C_dA value from the Vehicle File.

Speed dependent correction (User-defined)

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

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

\(C_dA_{effective} = C_dA * 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 ΔC_dA value in [m²] depending on the wind angle. The driving cycle must include the air speed relative to the vehicle v_air (<vair_res>) and the wind yaw angle (<vair_beta>).

The C_dA 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_{effective} = C_dA + {\Delta}C_d(\beta)\)

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

Gearshift losses for AT Gearboxes

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

Power-shift loss computation

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

Engine speed, clutch speed during power-shift

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

\(T_{inertia} = f_I * I_{engine} * \Delta\omega_I / dt\)

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

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

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.

Generic shift conditions

• Only allow upshifts if the vehicle is not decelerating and the estimated acceleration in the next gear is higher than a certain threshold (default: 0.1 m/s²)
• Do not allow downshifts with less time than a certain amount after an upshift (default 10 s)
• Do not allow upshifts with less time than a certain amount after an downshift (default 10 s)

Parameters in Gearbox File:

• DownshiftAferUpshiftDelay
• UpshiftAfterDownshiftDelay
• UpshiftMinAcceleration

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 (and C to C) gear shifts

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

\(μ(ν) = \frac{T_{out}}{T_{in}}\)

with:

• T_in = engine torque [Nm]
• T_ref(ν) = reference torque at reference rpm (from .vtcc file) [Nm]
• n_in = engine speed [1/min]
• n_ref = reference rpm [1/min] (see below)

The torque converter characteristics must also be defined for speed ratios 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!

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

Requirements

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

Example driving cycle with P_wheel input.

Losses in the PTO “Transmission” part (blue)

Considered by constant power consumption as a function of the PTO type. Power consumption added in all vehicle operation conditions as VECTO does not differentiate between clutch open/closed and gear engaged/disengaged. Configurable in the Vehicle Editor. The values are displayed in the following table:

Idling losses of the PTO “Consumer” (red)

Torque loss as a function of speed as determined by the DIN 30752-1 procedure. If PTO transmission includes shifting element (i.e. declutching of consumer part possible) the torque losses of the consumer in VECTO input shall be defined with zero. Not relevant during PTO cycle. Configurable in the Vehicle Editor and following the file format described in PTO-Consumer.

Power consumption of the PTO “Consumer” (red) during the PTO cycle

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 additionally labelled as “with PTO activation”. 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.

Definition

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:

• Speed Dependent Cross Wind Correction Input File (.vcdv)
• Vair & Beta Cross Wind Correction Input File (.vcdb)
• Retarder Loss Torque Input File (.vrlm)
• Full Load and Drag Curves (.vfld)
• Fuel Consumption Map (.vmap)
• Shift Polygons Input File (.vgbs)
• Transmission Loss Map (.vtlm)
• Torque Converter Characteristics (.vtcc)
• Auxiliary Input File (.vaux)
• Driving Cycles (.vdri)
• Acceleration Limiting Input File (.vacc)
• Modal Results (.vmod)
• Summary Results (.vsum)

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

Examples

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

<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

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

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!

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

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

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

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

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

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 Cycle Types

• Declaration Mode: Target speed, distance-based
• Engineering Mode:
  • Target speed, distance-based
  • Measured speed, time-based
  • Measured speed with gear, time-based
  • Pwheel (SiCo) Mode, time-based

• Engine Only Mode: Engine Only Mode, time-based

• Distance-based cycles can be defined in any distance resolution, including variable distance steps.

• Time-based cycles can be defined in any time resolution, including variable time steps.

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

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 “#”.

Example:

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 “#”.

Example:

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 “#”.

Example:

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 “#”.

Example:

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 “#”.

Example:

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.