Skip to content

Releases: COVESA/vehicle_signal_specification

v5.0

09 Oct 08:27
Compare
Choose a tag to compare

Changes with this release

Signal Updates

  • Signals deprecated in 4.X versions removed
  • Some signals added, but nothing significant compared to 4.2

UUID removed from release artifacts

VSS Release artifacts (VSS standard catalog in various formats) will no longer contain UUID information.
If you need artifacts with UUID you need to generate the artifact yourself.

Instructions:

  1. Clone the repo and check out the tag you want, for example git checkout v5.0.
  2. Update submodules, for example git submodule update --init.
  3. Add --uuid as argument to the relevant command in Makefile.
  4. Run generation, for example make csv.

OBD Branch deprecated

The Vehicle.OBD branch is now deprecated. The plan is to remove it in VSS 6.0.
The background is a decision that VSS standard catalog shall not contain a one-to-one representation of the OBD standard.
Instead, VSS standard catalog may contain corresponding information elsewhere. As an example, instead of
Vehicle.OBD.EngineSpeed (PID 0C), the VSS signal Vehicle.Powertrain.CombustionEngine.Speed can be used.
Note that not all signals in Vehicle.OBD have "duplicates", especially in the area of combustion engine control
(like Oxygen sensor lambda and voltage readings) VSS currently does not have any counterparts in other parts of the tree.

What to do if you as of today use signals from the OBD file:

  • Check if any suitable replacement signal exist.
    Example: if you use Vehicle.OBD.Speed, consider using Vehicle.Speed instead.
  • If not and the data may be of general interest; consider creating a pull request
    with a replacement signal.
    Example: VSS as of today only have Lambda information in OBD branch.
    If you need VSS signals for Lambda, consider creating new signals in
    Vehicle.Powertrain.CombustionEngine branch.
  • If you really need the signals in this file and cannot replace them, then consider using the overlay file in the
    overlays directory from VSS 6.0 onwards.

Updated tool dependency

CLI updates

The vss-tools CLI has been refactored. Makefile in this repository updated.

Overlay Support

VSS-tools support for overlays have been improved. It is now in many cases not necessary to specify
type and datatype for items in the overlay if you are changing an existing item.

What's Changed

Full Changelog: v4.2...v5.0

v5.0rc0

19 Sep 12:00
Compare
Choose a tag to compare
v5.0rc0 Pre-release
Pre-release

Changes with this release

Signal Updates

  • Signals deprecated in 4.X versions removed
  • Some signals added, but nothing significant compared to 4.2

UUID removed from release artifacts

VSS Release artifacts (VSS standard catalog in various formats) will no longer contain UUID information.
If you need artifacts with UUID you need to generate the artifact yourself.

Instructions:

  1. Clone the repo and check out the tag you want, for example git checkout v5.0.
  2. Update submodules, for example git submodule update --init.
  3. Add --uuid as argument to the relevant command in Makefile.
  4. Run generation, for example make csv.

OBD Branch deprecated

The Vehicle.OBD branch is now deprecated. The plan is to remove it in VSS 6.0.
The background is a decision that VSS standard catalog shall not contain a one-to-one representation of the OBD standard.
Instead, VSS standard catalog may contain corresponding information elsewhere. As an example, instead of
Vehicle.OBD.EngineSpeed (PID 0C), the VSS signal Vehicle.Powertrain.CombustionEngine.Speed can be used.
Note that not all signals in Vehicle.OBD have "duplicates", especially in the area of combustion engine control
(like Oxygen sensor lambda and voltage readings) VSS currently does not have any counterparts in other parts of the tree.

What to do if you as of today use signals from the OBD file:

  • Check if any suitable replacement signal exist.
    Example: if you use Vehicle.OBD.Speed, consider using Vehicle.Speed instead.
  • If not and the data may be of general interest; consider creating a pull request
    with a replacement signal.
    Example: VSS as of today only have Lambda information in OBD branch.
    If you need VSS signals for Lambda, consider creating new signals in
    Vehicle.Powertrain.CombustionEngine branch.
  • If you really need the signals in this file and cannot replace them, then consider using the overlay file in the
    overlays directory from VSS 6.0 onwards.

Updated tool dependency

CLI updates

The vss-tools CLI has been refactored. Makefile in this repository updated.

Overlay Support

VSS-tools support for overlays have been improved. It is now in many cases not necessary to specify
type and datatype for items in the overlay if you are changing an existing item.

What's Changed

Full Changelog: v4.2...v5.0rc0

v4.2

03 Jun 12:10
Compare
Choose a tag to compare

Changes with this release

New signals

New signals in the following areas

  • Engine Coolant and Engine Oil
  • Wheel Angular Speed
  • Screen Mirroring
  • Head Position and Eye Gaze
  • TimeInUse for electrical motors
  • Battery Precondition

Struct support in vspec2ddsidl

The vspec2ddsidl tool now supports structs

Jsonschema tool added

A new tool vspec2jsonschema has been added

Id generator tool added

A new tool vspec2id has been added. It can be used to generate and maintain unique identifiers for signals.

Unit files and quantity files

A new syntax has been introduced for unit files. The old syntax is still supported.
Domains have now been renamed to Quantities.
In addition to this a quantity file format has been defined, and the tool will inform
if units refer to a quantity that has not been defined an information message will be printed.

Full Changelog: v4.1...v4.2

v4.2rc0

17 May 14:20
Compare
Choose a tag to compare
v4.2rc0 Pre-release
Pre-release

Changes with this release

New signals

New signals in the following areas

  • Engine Coolant and Engine Oil
  • Wheel Angular Speed
  • Screen Mirroring
  • Head Position and Eye Gaze
  • TimeInUse for electrical motors
  • Battery Precondition

Struct support in vspec2ddsidl

The vspec2ddsidl tool now supports structs

Jsonschema tool added

A new tool vspec2jsonschema has been added

Id generator tool added

A new tool vspec2id has been added. It can be used to generate and maintain unique identifiers for signals.

Unit files and quantity files

A new syntax has been introduced for unit files. The old syntax is still supported.
Domains have now been renamed to Quantities.
In addition to this a quantity file format has been defined, and the tool will inform
if units refer to a quantity that has not been defined an information message will be printed.

Full Changelog: v4.1...v4.2rc0

v4.1

22 Dec 14:49
Compare
Choose a tag to compare

Changes with this release

Unit file syntax updated, Quantity file introduced

A new syntax for unit files is introduced. Old syntax still supported.
It is also possible to define quantity files, and a default quantity file (quantities.yaml)
has been added

New signals

Some signal have been added.

Updated tool dependency

A new version of vss-tools is used, with support for static IDs and jsonschema.

What's Changed

Full Changelog: v4.0...v4.1

v4.1rc0

04 Dec 09:57
Compare
Choose a tag to compare
v4.1rc0 Pre-release
Pre-release

Changes with this release

Unit file syntax updated, Quantity file introduced

A new syntax for unit files is introduced. Old syntax still supported.
It is also possible to define quantity files, and a default quantity file (quantities.yaml)
has been added

New signals

Some signal have been added.

Updated tool dependency

A new version of vss-tools is used, with support for static IDs and jsonschema.

What's Changed

Full Changelog: v4.0...v4.1rc0

v4.0

22 May 08:15
Compare
Choose a tag to compare

Major Changes with this release:

Struct Support (Official)

The VSS-syntax now supports structs.
Note however that not all exporters in VSS-tools 4.0 support structs yet.

Change of instance handling for seats, doors, mirrors and other branches.

Previously many signals used position for instance, where position 1 meant the leftmost item.
This caused problems for some use-cases where it was more practical to reference to a door by its relative position,
like the "DriverSide" door, as you then can describe wanted behavior in the same way for both LHD and RHD vehicles.
By that reason instance handling has for some signal been changed to use ["DriverSide","Middle","PassengerSide"].

Actuator and Sensor Attributes

The attributes sensor and actuator, deprecated from VSS 3.1,
have been removed from the VSS syntax.

See VSS CHANGELOG and VSS-Tools CHANGELOG for more information. For complete list of commits see below.

What's Changed

Full Changelog: v3.1.1...v4.0

v3.1.1

01 Mar 15:24
af4f6a4
Compare
Choose a tag to compare

Patch to add description to "Vehicle.Body.Lights.Brake", required according to VSS syntax.
Apart from that identical to VSS 3.1.

What's Changed

Full Changelog: v3.1...v3.1.1

v3.1

24 Feb 13:13
a250305
Compare
Choose a tag to compare

Major Changes with this release:

  • Struct support added.
    In this release experimental and only support by JSON exporter
  • The rarely used attributes actuator and sensor are now deprecated. These attributes have never been used in the standard catalog, but they are described in documentation.
  • A new parameter --uuid has been introduced to expliclty request UUIDs to be generated. That is still default but will likely be changed in VSS 4.0
  • The tools vspec2c and vspe2ocf are now obsolete
  • A parameter -uhas been added to specify unit file.
  • Some signals have been refactored.

See VSS CHANGELOG and VSS-Tools CHANGELOG for more information. For complete list of commits see below.

Outlook

Major topics currently being discussed which possibly might be addressed in the next major release:

  • Official support for structs in most tools/exporters
  • UUID handling to be changed - default will be that no UUID is generated
  • Unit file file be removed from vss-tools repository, the file in vss repository will be used instead unless something else is specified.

What's Changed

Full Changelog: v3.0...v3.1

v3.0

09 Aug 07:57
525e2bd
Compare
Choose a tag to compare

Major changes with this release:

  • Overlays introduced to allow customization of VSS. See documentation. See vss-tools documentation on how to include overlays when transforming VSS. An initial set of overlay files added. It must be noted that the included overlay files still are experimental and are as of today not considered being part of the "official VSS release".
  • Introduction of instantiate keyword to exclude specific signals from instantiation. See documentation.
  • Refactoring of CombustionEngine signals
  • Battery branch renamed to TractionBattery
  • Refactoring and extensions of signals related to TractionBattery and Charging
  • Keyword enum changed to allowed
  • Refactoring of seat signals
  • Extension of wiper signals
  • First overlay files for profiles added

In addition to this multiple minor changes have been introduced, see complete list of changes below.

Outlook

Major topics currently being discussed which possibly might be addressed in the next major release:

  • How to represent complex types (structures) in VSS
  • Alignment and/or standardization of profiles for various vehicle types, for example motorbikes
  • Standardization or recommendation for signal metadata to specify e.g. security requirements or required accuracy or frequency of signals

What's Changed

Full Changelog: v2.2...v3.0