This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

DriveCycleStatus
Full qualified VSS Path: Vehicle.OBD.DriveCycleStatus
Description: PID 41 - OBD status for the current drive cycle
flowchart LR Vehicle-->OBD OBD-->DriveCycleStatus

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.OBD.DriveCycleStatus

Signal Information

The vehicle signal Vehicle.OBD.DriveCycleStatus is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.OBD.DriveCycleStatus is 5215e28062f75154822789b8a5f30630

Children

This vehicle signal is a branch or structure and thus has sub-pages:

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.

1 - DTCCount
Full qualified VSS Path: Vehicle.OBD.DriveCycleStatus.DTCCount
Description: Number of sensor Trouble Codes (DTC)
flowchart LR Vehicle-->OBD OBD-->DriveCycleStatus DriveCycleStatus-->DTCCount

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DriveCycleStatus.DTCCount
[get]  OK
Vehicle.OBD.DriveCycleStatus.DTCCount: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DriveCycleStatus.DTCCount 0
[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.OBD.DriveCycleStatus.DTCCount

Data Type & Unit
Path Vehicle.OBD.DriveCycleStatus.DTCCount VSS: Addressing nodes
Data type uint8 VSS: Datatypes

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.OBD.DriveCycleStatus.DTCCount is a Sensor.

The vehicle signal Vehicle.OBD.DriveCycleStatus.DTCCount is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.OBD.DriveCycleStatus.DTCCount is 312856f746ff560e8098c19196964d3b

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.

2 - IgnitionType
Full qualified VSS Path: Vehicle.OBD.DriveCycleStatus.IgnitionType
Description: Type of the ignition for ICE - spark = spark plug ignition, compression = self-igniting (Diesel engines)
flowchart LR Vehicle-->OBD OBD-->DriveCycleStatus DriveCycleStatus-->IgnitionType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DriveCycleStatus.IgnitionType
[get]  OK
Vehicle.OBD.DriveCycleStatus.IgnitionType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DriveCycleStatus.IgnitionType Foo
[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.OBD.DriveCycleStatus.IgnitionType

Data Type & Unit
Path Vehicle.OBD.DriveCycleStatus.IgnitionType VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['SPARK', 'COMPRESSION'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.OBD.DriveCycleStatus.IgnitionType is a Sensor.

The vehicle signal Vehicle.OBD.DriveCycleStatus.IgnitionType is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.OBD.DriveCycleStatus.IgnitionType is 1aeb7b6d025f5a8693104824abaa1c49

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.

3 - IsMILOn
Full qualified VSS Path: Vehicle.OBD.DriveCycleStatus.IsMILOn
Description: Malfunction Indicator Light (MIL) - False = Off, True = On
flowchart LR Vehicle-->OBD OBD-->DriveCycleStatus DriveCycleStatus-->IsMILOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DriveCycleStatus.IsMILOn
[get]  OK
Vehicle.OBD.DriveCycleStatus.IsMILOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DriveCycleStatus.IsMILOn false
[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.OBD.DriveCycleStatus.IsMILOn

Data Type & Unit
Path Vehicle.OBD.DriveCycleStatus.IsMILOn VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.OBD.DriveCycleStatus.IsMILOn is a Sensor.

The vehicle signal Vehicle.OBD.DriveCycleStatus.IsMILOn is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.OBD.DriveCycleStatus.IsMILOn is e367394c9a075eef8fd66499e3d9cf14

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.