| Full qualified VSS Path: | Vehicle.StartTime |
| Description: | Start time of current or latest trip, formatted according to ISO 8601 with UTC time zone. |
| Comment: | This signal is supposed to be set whenever a new trip starts. A new trip is considered to start when engine gets enabled (e.g. LowVoltageSystemState in ON or START mode). A trip is considered to end when engine is no longer enabled. The default value indicates that the vehicle never has been started, or that latest start time is unknown. |
Navigation
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.StartTime
[get] OK
Vehicle.StartTime: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.StartTime 0000-01-01T00:00Z
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
| Vehicle Model | Direct link to Vehicle Signal |
|---|---|
| ACME Car (EV) v0.1 | Vehicle.StartTime |
Data Type & Unit
| Path | Vehicle.StartTime |
VSS: Addressing nodes |
| Data type | string |
VSS: Datatypes |
| Default value | 0000-01-01T00:00Z |
VSS: Sensors & Actuators |
Note: The string datatype is a character string.
Signal Information
The vehicle signal Vehicle.StartTime is an Attribute.
The vehicle signal Vehicle.StartTime is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.StartTime is 3790b5f4513c5a3d90a0503a965bbbe0
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
| Enhancement request | Create COVESA GitHub Issue |
| Join COVESA | www.covesa.global |
| Discuss VSS on Slack | w3cauto.slack.com |
| VSS Data Experts on Google Groups | covesa.global data-expert-group |
About VSS
The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name | Type | Min | Max |
|---|---|---|---|
| uint8 | unsigned 8-bit integer | 0 | 255 |
| int8 | signed 8-bit integer | -128 | 127 |
| uint16 | unsigned 16-bit integer | 0 | 65535 |
| int16 | signed 16-bit integer | -32768 | 32767 |
| uint32 | unsigned 32-bit integer | 0 | 4294967295 |
| int32 | signed 32-bit integer | -2147483648 | 2147483647 |
| uint64 | unsigned 64-bit integer | 0 | 2^64 - 1 |
| int64 | signed 64-bit integer | -2^63 | 2^63 - 1 |
| boolean | boolean value | 0/false | 1/true |
| float | floating point number | -3.4e -38 | 3.4e 38 |
| double | double precision floating point number | -1.7e -300 | 1.7e 300 |
| string | character string | n/a | n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.