Vehicle.ADAS.ABS (Antilock Braking System signals.)
Vehicle.ADAS.ActiveAutonomyLevel (Indicates the currently active level of autonomy according to SAE J3016 taxonomy.)
Vehicle.ADAS.CruiseControl (Signals from Cruise Control system.)
Vehicle.ADAS.EBA (Emergency Brake Assist (EBA) System signals.)
Vehicle.ADAS.EBD (Electronic Brakeforce Distribution (EBD) System signals.)
Vehicle.ADAS.ESC (Electronic Stability Control System signals.)
Vehicle.ADAS.LaneDepartureDetection (Signals from Lane Departure Detection System.)
Vehicle.ADAS.ObstacleDetection (Signals form Obstacle Sensor System.)
Vehicle.ADAS.PowerOptimizeLevel (Power optimization level for this branch/subsystem. A higher number indicates more aggressive power optimization. Level 0 indicates that all functionality is enabled, no power optimization enabled. Level 10 indicates most aggressive power optimization mode, only essential functionality enabled.)
Vehicle.ADAS.SupportedAutonomyLevel (Indicates the highest level of autonomy according to SAE J3016 taxonomy the vehicle is capable of.)
Vehicle.ADAS.TCS (Traction Control System signals.)

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 - EBA


Full qualified VSS Path:	`Vehicle.ADAS.EBA`
Description:	Emergency Brake Assist (EBA) System signals.

flowchart LR Vehicle-->ADAS ADAS-->EBA

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.ADAS.EBA

Signal Information

The vehicle signal Vehicle.ADAS.EBA is a Branch.

UUID

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

The UUID for Vehicle.ADAS.EBA is 51ec0930d0af5b91b84a0775c6e87a97

Children

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

Vehicle.ADAS.EBA.IsEnabled (Indicates if EBA is enabled. True = Enabled. False = Disabled.)
Vehicle.ADAS.EBA.IsEngaged (Indicates if EBA is currently regulating brake pressure. True = Engaged. False = Not Engaged.)
Vehicle.ADAS.EBA.IsError (Indicates if EBA incurred an error condition. True = Error. False = No Error.)

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.1 - IsEnabled


Full qualified VSS Path:	`Vehicle.ADAS.EBA.IsEnabled`
Description:	Indicates if EBA is enabled. True = Enabled. False = Disabled.

flowchart LR Vehicle-->ADAS ADAS-->EBA EBA-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.EBA.IsEnabled
[get]  OK
Vehicle.ADAS.EBA.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.EBA.IsEnabled 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.ADAS.EBA.IsEnabled

Data Type & Unit


Path	`Vehicle.ADAS.EBA.IsEnabled`	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.ADAS.EBA.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.EBA.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.ADAS.EBA.IsEnabled is 3ae9171b69555fb08855054ab38e9b17

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

1.2 - IsEngaged


Full qualified VSS Path:	`Vehicle.ADAS.EBA.IsEngaged`
Description:	Indicates if EBA is currently regulating brake pressure. True = Engaged. False = Not Engaged.

flowchart LR Vehicle-->ADAS ADAS-->EBA EBA-->IsEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.EBA.IsEngaged
[get]  OK
Vehicle.ADAS.EBA.IsEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.EBA.IsEngaged 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.ADAS.EBA.IsEngaged

Data Type & Unit


Path	`Vehicle.ADAS.EBA.IsEngaged`	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.ADAS.EBA.IsEngaged is a Sensor.

The vehicle signal Vehicle.ADAS.EBA.IsEngaged is a Signal.

UUID

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

The UUID for Vehicle.ADAS.EBA.IsEngaged is 86360c44ead354d18af7ff14176151f6

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

1.3 - IsError


Full qualified VSS Path:	`Vehicle.ADAS.EBA.IsError`
Description:	Indicates if EBA incurred an error condition. True = Error. False = No Error.

flowchart LR Vehicle-->ADAS ADAS-->EBA EBA-->IsError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.EBA.IsError
[get]  OK
Vehicle.ADAS.EBA.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.EBA.IsError 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.ADAS.EBA.IsError

Data Type & Unit


Path	`Vehicle.ADAS.EBA.IsError`	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.ADAS.EBA.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.EBA.IsError is a Signal.

UUID

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

The UUID for Vehicle.ADAS.EBA.IsError is bae0fe856398502ba4a09283867c6c81

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

2 - EBD


Full qualified VSS Path:	`Vehicle.ADAS.EBD`
Description:	Electronic Brakeforce Distribution (EBD) System signals.

flowchart LR Vehicle-->ADAS ADAS-->EBD

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.ADAS.EBD

Signal Information

The vehicle signal Vehicle.ADAS.EBD is a Branch.

UUID

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

The UUID for Vehicle.ADAS.EBD is 3f4c74a588735b10ac9fe918d305cd5a

Children

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

Vehicle.ADAS.EBD.IsEnabled (Indicates if EBD is enabled. True = Enabled. False = Disabled.)
Vehicle.ADAS.EBD.IsEngaged (Indicates if EBD is currently regulating vehicle brakeforce distribution. True = Engaged. False = Not Engaged.)
Vehicle.ADAS.EBD.IsError (Indicates if EBD incurred an error condition. True = Error. False = No Error.)

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.

2.1 - IsEnabled


Full qualified VSS Path:	`Vehicle.ADAS.EBD.IsEnabled`
Description:	Indicates if EBD is enabled. True = Enabled. False = Disabled.

flowchart LR Vehicle-->ADAS ADAS-->EBD EBD-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.EBD.IsEnabled
[get]  OK
Vehicle.ADAS.EBD.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.EBD.IsEnabled 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.ADAS.EBD.IsEnabled

Data Type & Unit


Path	`Vehicle.ADAS.EBD.IsEnabled`	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.ADAS.EBD.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.EBD.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.ADAS.EBD.IsEnabled is 30f88d3e68575b67853b14ce5f7a08e5

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

2.2 - IsEngaged


Full qualified VSS Path:	`Vehicle.ADAS.EBD.IsEngaged`
Description:	Indicates if EBD is currently regulating vehicle brakeforce distribution. True = Engaged. False = Not Engaged.

flowchart LR Vehicle-->ADAS ADAS-->EBD EBD-->IsEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.EBD.IsEngaged
[get]  OK
Vehicle.ADAS.EBD.IsEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.EBD.IsEngaged 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.ADAS.EBD.IsEngaged

Data Type & Unit


Path	`Vehicle.ADAS.EBD.IsEngaged`	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.ADAS.EBD.IsEngaged is a Sensor.

The vehicle signal Vehicle.ADAS.EBD.IsEngaged is a Signal.

UUID

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

The UUID for Vehicle.ADAS.EBD.IsEngaged is 67aa2a598f635edda6eb944af99b06db

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

2.3 - IsError


Full qualified VSS Path:	`Vehicle.ADAS.EBD.IsError`
Description:	Indicates if EBD incurred an error condition. True = Error. False = No Error.

flowchart LR Vehicle-->ADAS ADAS-->EBD EBD-->IsError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.EBD.IsError
[get]  OK
Vehicle.ADAS.EBD.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.EBD.IsError 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.ADAS.EBD.IsError

Data Type & Unit


Path	`Vehicle.ADAS.EBD.IsError`	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.ADAS.EBD.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.EBD.IsError is a Signal.

UUID

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

The UUID for Vehicle.ADAS.EBD.IsError is 918157073be95015ae38913cd7a9796a

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

3 - ESC


Full qualified VSS Path:	`Vehicle.ADAS.ESC`
Description:	Electronic Stability Control System signals.

flowchart LR Vehicle-->ADAS ADAS-->ESC

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.ADAS.ESC

Signal Information

The vehicle signal Vehicle.ADAS.ESC is a Branch.

UUID

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

The UUID for Vehicle.ADAS.ESC is 636b4586ce7854b4b270a2f3b6c0af4f

Children

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

Vehicle.ADAS.ESC.IsEnabled (Indicates if ESC is enabled. True = Enabled. False = Disabled.)
Vehicle.ADAS.ESC.IsEngaged (Indicates if ESC is currently regulating vehicle stability. True = Engaged. False = Not Engaged.)
Vehicle.ADAS.ESC.IsError (Indicates if ESC incurred an error condition. True = Error. False = No Error.)
Vehicle.ADAS.ESC.IsStrongCrossWindDetected (Indicates if the ESC system is detecting strong cross winds. True = Strong cross winds detected. False = No strong cross winds detected.)
Vehicle.ADAS.ESC.RoadFriction (Road friction values reported by the ESC system.)

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.

3.1 - IsEnabled


Full qualified VSS Path:	`Vehicle.ADAS.ESC.IsEnabled`
Description:	Indicates if ESC is enabled. True = Enabled. False = Disabled.

flowchart LR Vehicle-->ADAS ADAS-->ESC ESC-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ESC.IsEnabled
[get]  OK
Vehicle.ADAS.ESC.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ESC.IsEnabled 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.ADAS.ESC.IsEnabled

Data Type & Unit


Path	`Vehicle.ADAS.ESC.IsEnabled`	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.ADAS.ESC.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.ESC.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ESC.IsEnabled is 3f4f39b8d8c05c97a6de685282ba74b7

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

3.2 - IsEngaged


Full qualified VSS Path:	`Vehicle.ADAS.ESC.IsEngaged`
Description:	Indicates if ESC is currently regulating vehicle stability. True = Engaged. False = Not Engaged.

flowchart LR Vehicle-->ADAS ADAS-->ESC ESC-->IsEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ESC.IsEngaged
[get]  OK
Vehicle.ADAS.ESC.IsEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ESC.IsEngaged 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.ADAS.ESC.IsEngaged

Data Type & Unit


Path	`Vehicle.ADAS.ESC.IsEngaged`	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.ADAS.ESC.IsEngaged is a Sensor.

The vehicle signal Vehicle.ADAS.ESC.IsEngaged is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ESC.IsEngaged is 2088953a28385353a9d46b3a3dc11cac

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

3.3 - IsError


Full qualified VSS Path:	`Vehicle.ADAS.ESC.IsError`
Description:	Indicates if ESC incurred an error condition. True = Error. False = No Error.

flowchart LR Vehicle-->ADAS ADAS-->ESC ESC-->IsError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ESC.IsError
[get]  OK
Vehicle.ADAS.ESC.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ESC.IsError 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.ADAS.ESC.IsError

Data Type & Unit


Path	`Vehicle.ADAS.ESC.IsError`	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.ADAS.ESC.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.ESC.IsError is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ESC.IsError is 6c237535654b5bc7a70f6a70c760b9d4

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

3.4 - IsStrongCrossWindDetected


Full qualified VSS Path:	`Vehicle.ADAS.ESC.IsStrongCrossWindDetected`
Description:	Indicates if the ESC system is detecting strong cross winds. True = Strong cross winds detected. False = No strong cross winds detected.

flowchart LR Vehicle-->ADAS ADAS-->ESC ESC-->IsStrongCrossWindDetected

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ESC.IsStrongCrossWindDetected
[get]  OK
Vehicle.ADAS.ESC.IsStrongCrossWindDetected: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ESC.IsStrongCrossWindDetected 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.ADAS.ESC.IsStrongCrossWindDetected

Data Type & Unit


Path	`Vehicle.ADAS.ESC.IsStrongCrossWindDetected`	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.ADAS.ESC.IsStrongCrossWindDetected is a Sensor.

The vehicle signal Vehicle.ADAS.ESC.IsStrongCrossWindDetected is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ESC.IsStrongCrossWindDetected is ebfd609531345c37914b89e553df80cb

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

3.5 - RoadFriction


Full qualified VSS Path:	`Vehicle.ADAS.ESC.RoadFriction`
Description:	Road friction values reported by the ESC system.

flowchart LR Vehicle-->ADAS ADAS-->ESC ESC-->RoadFriction

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.ADAS.ESC.RoadFriction

Signal Information

The vehicle signal Vehicle.ADAS.ESC.RoadFriction is a Branch.

UUID

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

The UUID for Vehicle.ADAS.ESC.RoadFriction is 71a32e4eb131532c82195508d93807ed

Children

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

Vehicle.ADAS.ESC.RoadFriction.LowerBound (Lower bound road friction, as calculated by the ESC system. 5% possibility that road friction is below this value. 0 = no friction, 100 = maximum friction.)
Vehicle.ADAS.ESC.RoadFriction.MostProbable (Most probable road friction, as calculated by the ESC system. Exact meaning of most probable is implementation specific. 0 = no friction, 100 = maximum friction.)
Vehicle.ADAS.ESC.RoadFriction.UpperBound (Upper bound road friction, as calculated by the ESC system. 95% possibility that road friction is below this value. 0 = no friction, 100 = maximum friction.)

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.

3.5.1 - LowerBound


Full qualified VSS Path:	`Vehicle.ADAS.ESC.RoadFriction.LowerBound`
Description:	Lower bound road friction, as calculated by the ESC system. 5% possibility that road friction is below this value. 0 = no friction, 100 = maximum friction.

flowchart LR Vehicle-->ADAS ADAS-->ESC ESC-->RoadFriction RoadFriction-->LowerBound

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ESC.RoadFriction.LowerBound
[get]  OK
Vehicle.ADAS.ESC.RoadFriction.LowerBound: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ESC.RoadFriction.LowerBound 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.ADAS.ESC.RoadFriction.LowerBound

Data Type & Unit


Path	`Vehicle.ADAS.ESC.RoadFriction.LowerBound`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.ADAS.ESC.RoadFriction.LowerBound is a Sensor.

The vehicle signal Vehicle.ADAS.ESC.RoadFriction.LowerBound is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ESC.RoadFriction.LowerBound is 634289f58b5d511ea9979f04a9d0f2ab

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

3.5.2 - MostProbable


Full qualified VSS Path:	`Vehicle.ADAS.ESC.RoadFriction.MostProbable`
Description:	Most probable road friction, as calculated by the ESC system. Exact meaning of most probable is implementation specific. 0 = no friction, 100 = maximum friction.

flowchart LR Vehicle-->ADAS ADAS-->ESC ESC-->RoadFriction RoadFriction-->MostProbable

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ESC.RoadFriction.MostProbable
[get]  OK
Vehicle.ADAS.ESC.RoadFriction.MostProbable: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ESC.RoadFriction.MostProbable 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.ADAS.ESC.RoadFriction.MostProbable

Data Type & Unit


Path	`Vehicle.ADAS.ESC.RoadFriction.MostProbable`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.ADAS.ESC.RoadFriction.MostProbable is a Sensor.

The vehicle signal Vehicle.ADAS.ESC.RoadFriction.MostProbable is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ESC.RoadFriction.MostProbable is b0eb72430cd95bfbba0d187fcb6e2a62

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

3.5.3 - UpperBound


Full qualified VSS Path:	`Vehicle.ADAS.ESC.RoadFriction.UpperBound`
Description:	Upper bound road friction, as calculated by the ESC system. 95% possibility that road friction is below this value. 0 = no friction, 100 = maximum friction.

flowchart LR Vehicle-->ADAS ADAS-->ESC ESC-->RoadFriction RoadFriction-->UpperBound

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ESC.RoadFriction.UpperBound
[get]  OK
Vehicle.ADAS.ESC.RoadFriction.UpperBound: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ESC.RoadFriction.UpperBound 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.ADAS.ESC.RoadFriction.UpperBound

Data Type & Unit


Path	`Vehicle.ADAS.ESC.RoadFriction.UpperBound`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.ADAS.ESC.RoadFriction.UpperBound is a Sensor.

The vehicle signal Vehicle.ADAS.ESC.RoadFriction.UpperBound is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ESC.RoadFriction.UpperBound is ad0415a799575fcd8d1f49bed9a2baeb

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

4 - PowerOptimizeLevel


Full qualified VSS Path:	`Vehicle.ADAS.PowerOptimizeLevel`
Description:	Power optimization level for this branch/subsystem. A higher number indicates more aggressive power optimization. Level 0 indicates that all functionality is enabled, no power optimization enabled. Level 10 indicates most aggressive power optimization mode, only essential functionality enabled.

flowchart LR Vehicle-->ADAS ADAS-->PowerOptimizeLevel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.ADAS.PowerOptimizeLevel`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`10`	VSS: Sensors & Actuators

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.ADAS.PowerOptimizeLevel is an Actuator.

The vehicle signal Vehicle.ADAS.PowerOptimizeLevel is a Signal.

UUID

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

The UUID for Vehicle.ADAS.PowerOptimizeLevel is 044ad42893e65993bfc439455fb08faa

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

5 - ABS


Full qualified VSS Path:	`Vehicle.ADAS.ABS`
Description:	Antilock Braking System signals.

flowchart LR Vehicle-->ADAS ADAS-->ABS

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.ADAS.ABS

Signal Information

The vehicle signal Vehicle.ADAS.ABS is a Branch.

UUID

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

The UUID for Vehicle.ADAS.ABS is 219270ef27c4531f874bbda63743b330

Children

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

Vehicle.ADAS.ABS.IsEnabled (Indicates if ABS is enabled. True = Enabled. False = Disabled.)
Vehicle.ADAS.ABS.IsEngaged (Indicates if ABS is currently regulating brake pressure. True = Engaged. False = Not Engaged.)
Vehicle.ADAS.ABS.IsError (Indicates if ABS incurred an error condition. True = Error. False = No Error.)

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.

5.1 - IsEnabled


Full qualified VSS Path:	`Vehicle.ADAS.ABS.IsEnabled`
Description:	Indicates if ABS is enabled. True = Enabled. False = Disabled.

flowchart LR Vehicle-->ADAS ADAS-->ABS ABS-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ABS.IsEnabled
[get]  OK
Vehicle.ADAS.ABS.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ABS.IsEnabled 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.ADAS.ABS.IsEnabled

Data Type & Unit


Path	`Vehicle.ADAS.ABS.IsEnabled`	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.ADAS.ABS.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.ABS.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ABS.IsEnabled is cad374fbfdc65df9b777508f04d5b073

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

5.2 - IsEngaged


Full qualified VSS Path:	`Vehicle.ADAS.ABS.IsEngaged`
Description:	Indicates if ABS is currently regulating brake pressure. True = Engaged. False = Not Engaged.

flowchart LR Vehicle-->ADAS ADAS-->ABS ABS-->IsEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ABS.IsEngaged
[get]  OK
Vehicle.ADAS.ABS.IsEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ABS.IsEngaged 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.ADAS.ABS.IsEngaged

Data Type & Unit


Path	`Vehicle.ADAS.ABS.IsEngaged`	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.ADAS.ABS.IsEngaged is a Sensor.

The vehicle signal Vehicle.ADAS.ABS.IsEngaged is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ABS.IsEngaged is 6dd21979a2225e31940dc2ece1aa9a04

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

5.3 - IsError


Full qualified VSS Path:	`Vehicle.ADAS.ABS.IsError`
Description:	Indicates if ABS incurred an error condition. True = Error. False = No Error.

flowchart LR Vehicle-->ADAS ADAS-->ABS ABS-->IsError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ABS.IsError
[get]  OK
Vehicle.ADAS.ABS.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ABS.IsError 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.ADAS.ABS.IsError

Data Type & Unit


Path	`Vehicle.ADAS.ABS.IsError`	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.ADAS.ABS.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.ABS.IsError is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ABS.IsError is 13cfabb3122254128234f9a696f14678

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

6 - ActiveAutonomyLevel


Full qualified VSS Path:	`Vehicle.ADAS.ActiveAutonomyLevel`
Description:	Indicates the currently active level of autonomy according to SAE J3016 taxonomy.
Comment:	Follows https://www.sae.org/news/2019/01/sae-updates-j3016-automated-driving-graphic taxonomy. For SAE levels 3 and 4 the system is required to alert the driver before it will disengage. Level 4 systems are required to reach a safe state even if a driver does not take over. Only level 5 systems are required to not rely on a driver at all. While level 2 systems require the driver to be monitoring the system at all times, many level 2 systems, often termed “level 2.5” systems, do warn the driver shortly before reaching their operational limits, therefore we also support the DISENGAGING state for SAE_2.

flowchart LR Vehicle-->ADAS ADAS-->ActiveAutonomyLevel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.ADAS.ActiveAutonomyLevel`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['SAE_0', 'SAE_1', 'SAE_2_DISENGAGING', 'SAE_2', 'SAE_3_DISENGAGING', 'SAE_3', 'SAE_4_DISENGAGING', 'SAE_4', 'SAE_5']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.ADAS.ActiveAutonomyLevel is a Sensor.

The vehicle signal Vehicle.ADAS.ActiveAutonomyLevel is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ActiveAutonomyLevel is b101c6928fc55948b1cc485e568ecd8d

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

7 - CruiseControl


Full qualified VSS Path:	`Vehicle.ADAS.CruiseControl`
Description:	Signals from Cruise Control system.

flowchart LR Vehicle-->ADAS ADAS-->CruiseControl

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.ADAS.CruiseControl

Signal Information

The vehicle signal Vehicle.ADAS.CruiseControl is a Branch.

UUID

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

The UUID for Vehicle.ADAS.CruiseControl is c4d751cf74f9576dbba3cc820991c1fb

Children

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

Vehicle.ADAS.CruiseControl.IsActive (Indicates if cruise control system is active (i.e. actively controls speed). True = Active. False = Inactive.)
Vehicle.ADAS.CruiseControl.IsEnabled (Indicates if cruise control system is enabled (e.g. ready to receive configurations and settings) True = Enabled. False = Disabled.)
Vehicle.ADAS.CruiseControl.IsError (Indicates if cruise control system incurred an error condition. True = Error. False = No Error.)
Vehicle.ADAS.CruiseControl.SpeedSet (Set cruise control speed in kilometers per hour.)

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.

7.1 - IsActive


Full qualified VSS Path:	`Vehicle.ADAS.CruiseControl.IsActive`
Description:	Indicates if cruise control system is active (i.e. actively controls speed). True = Active. False = Inactive.

flowchart LR Vehicle-->ADAS ADAS-->CruiseControl CruiseControl-->IsActive

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.CruiseControl.IsActive
[get]  OK
Vehicle.ADAS.CruiseControl.IsActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.CruiseControl.IsActive 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.ADAS.CruiseControl.IsActive

Data Type & Unit


Path	`Vehicle.ADAS.CruiseControl.IsActive`	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.ADAS.CruiseControl.IsActive is an Actuator.

The vehicle signal Vehicle.ADAS.CruiseControl.IsActive is a Signal.

UUID

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

The UUID for Vehicle.ADAS.CruiseControl.IsActive is 78ab5ce923dc5aa1a6622bcb948e1561

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

7.2 - IsEnabled


Full qualified VSS Path:	`Vehicle.ADAS.CruiseControl.IsEnabled`
Description:	Indicates if cruise control system is enabled (e.g. ready to receive configurations and settings) True = Enabled. False = Disabled.

flowchart LR Vehicle-->ADAS ADAS-->CruiseControl CruiseControl-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.CruiseControl.IsEnabled
[get]  OK
Vehicle.ADAS.CruiseControl.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.CruiseControl.IsEnabled 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.ADAS.CruiseControl.IsEnabled

Data Type & Unit


Path	`Vehicle.ADAS.CruiseControl.IsEnabled`	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.ADAS.CruiseControl.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.CruiseControl.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.ADAS.CruiseControl.IsEnabled is 018417f6c8535315895d0f54d209035a

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

7.3 - IsError


Full qualified VSS Path:	`Vehicle.ADAS.CruiseControl.IsError`
Description:	Indicates if cruise control system incurred an error condition. True = Error. False = No Error.

flowchart LR Vehicle-->ADAS ADAS-->CruiseControl CruiseControl-->IsError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.CruiseControl.IsError
[get]  OK
Vehicle.ADAS.CruiseControl.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.CruiseControl.IsError 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.ADAS.CruiseControl.IsError

Data Type & Unit


Path	`Vehicle.ADAS.CruiseControl.IsError`	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.ADAS.CruiseControl.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.CruiseControl.IsError is a Signal.

UUID

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

The UUID for Vehicle.ADAS.CruiseControl.IsError is 22923d4a36bc5192a08e40fe9e5ed458

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

7.4 - SpeedSet


Full qualified VSS Path:	`Vehicle.ADAS.CruiseControl.SpeedSet`
Description:	Set cruise control speed in kilometers per hour.

flowchart LR Vehicle-->ADAS ADAS-->CruiseControl CruiseControl-->SpeedSet

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.CruiseControl.SpeedSet
[get]  OK
Vehicle.ADAS.CruiseControl.SpeedSet: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.CruiseControl.SpeedSet 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.ADAS.CruiseControl.SpeedSet

Data Type & Unit


Path	`Vehicle.ADAS.CruiseControl.SpeedSet`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/h`	VSS: Units
Label	kilometer per hour
Description	Speed measured in kilometers per hours	VSS: Sensors & Actuators
Domain	speed

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.ADAS.CruiseControl.SpeedSet is an Actuator.

The vehicle signal Vehicle.ADAS.CruiseControl.SpeedSet is a Signal.

UUID

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

The UUID for Vehicle.ADAS.CruiseControl.SpeedSet is b3f3a53ccd825e4da5cb1226f94dc005

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

8 - LaneDepartureDetection


Full qualified VSS Path:	`Vehicle.ADAS.LaneDepartureDetection`
Description:	Signals from Lane Departure Detection System.

flowchart LR Vehicle-->ADAS ADAS-->LaneDepartureDetection

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.ADAS.LaneDepartureDetection

Signal Information

The vehicle signal Vehicle.ADAS.LaneDepartureDetection is a Branch.

UUID

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

The UUID for Vehicle.ADAS.LaneDepartureDetection is e45f33fdcf245f11981b2f201ee8281a

Children

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

Vehicle.ADAS.LaneDepartureDetection.IsEnabled (Indicates if lane departure detection system is enabled. True = Enabled. False = Disabled.)
Vehicle.ADAS.LaneDepartureDetection.IsError (Indicates if lane departure system incurred an error condition. True = Error. False = No Error.)
Vehicle.ADAS.LaneDepartureDetection.IsWarning (Indicates if lane departure detection registered a lane departure.)

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.

8.1 - IsEnabled


Full qualified VSS Path:	`Vehicle.ADAS.LaneDepartureDetection.IsEnabled`
Description:	Indicates if lane departure detection system is enabled. True = Enabled. False = Disabled.

flowchart LR Vehicle-->ADAS ADAS-->LaneDepartureDetection LaneDepartureDetection-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.LaneDepartureDetection.IsEnabled
[get]  OK
Vehicle.ADAS.LaneDepartureDetection.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.LaneDepartureDetection.IsEnabled 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.ADAS.LaneDepartureDetection.IsEnabled

Data Type & Unit


Path	`Vehicle.ADAS.LaneDepartureDetection.IsEnabled`	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.ADAS.LaneDepartureDetection.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.LaneDepartureDetection.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.ADAS.LaneDepartureDetection.IsEnabled is c099ae97260f5c418977cd14631e95be

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

8.2 - IsError


Full qualified VSS Path:	`Vehicle.ADAS.LaneDepartureDetection.IsError`
Description:	Indicates if lane departure system incurred an error condition. True = Error. False = No Error.

flowchart LR Vehicle-->ADAS ADAS-->LaneDepartureDetection LaneDepartureDetection-->IsError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.LaneDepartureDetection.IsError
[get]  OK
Vehicle.ADAS.LaneDepartureDetection.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.LaneDepartureDetection.IsError 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.ADAS.LaneDepartureDetection.IsError

Data Type & Unit


Path	`Vehicle.ADAS.LaneDepartureDetection.IsError`	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.ADAS.LaneDepartureDetection.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.LaneDepartureDetection.IsError is a Signal.

UUID

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

The UUID for Vehicle.ADAS.LaneDepartureDetection.IsError is 73b2fc4f6a4952e4b7886671450e7798

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

8.3 - IsWarning


Full qualified VSS Path:	`Vehicle.ADAS.LaneDepartureDetection.IsWarning`
Description:	Indicates if lane departure detection registered a lane departure.

flowchart LR Vehicle-->ADAS ADAS-->LaneDepartureDetection LaneDepartureDetection-->IsWarning

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.LaneDepartureDetection.IsWarning
[get]  OK
Vehicle.ADAS.LaneDepartureDetection.IsWarning: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.LaneDepartureDetection.IsWarning 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.ADAS.LaneDepartureDetection.IsWarning

Data Type & Unit


Path	`Vehicle.ADAS.LaneDepartureDetection.IsWarning`	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.ADAS.LaneDepartureDetection.IsWarning is a Sensor.

The vehicle signal Vehicle.ADAS.LaneDepartureDetection.IsWarning is a Signal.

UUID

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

The UUID for Vehicle.ADAS.LaneDepartureDetection.IsWarning is c32fcd1d56035cb08acfd380be224c6a

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

9 - ObstacleDetection


Full qualified VSS Path:	`Vehicle.ADAS.ObstacleDetection`
Description:	Signals form Obstacle Sensor System.

flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection

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.ADAS.ObstacleDetection

Signal Information

The vehicle signal Vehicle.ADAS.ObstacleDetection is a Branch.

UUID

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

The UUID for Vehicle.ADAS.ObstacleDetection is e7b6d81631cc5ac584d027d4c1a66cb5

Children

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

Vehicle.ADAS.ObstacleDetection.IsEnabled (Indicates if obstacle sensor system is enabled (i.e. monitoring for obstacles). True = Enabled. False = Disabled.)
Vehicle.ADAS.ObstacleDetection.IsError (Indicates if obstacle sensor system incurred an error condition. True = Error. False = No Error.)
Vehicle.ADAS.ObstacleDetection.IsWarning (Indicates if obstacle sensor system registered an obstacle.)

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.

9.1 - IsEnabled


Full qualified VSS Path:	`Vehicle.ADAS.ObstacleDetection.IsEnabled`
Description:	Indicates if obstacle sensor system is enabled (i.e. monitoring for obstacles). True = Enabled. False = Disabled.

flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ObstacleDetection.IsEnabled
[get]  OK
Vehicle.ADAS.ObstacleDetection.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.IsEnabled 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.ADAS.ObstacleDetection.IsEnabled

Data Type & Unit


Path	`Vehicle.ADAS.ObstacleDetection.IsEnabled`	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.ADAS.ObstacleDetection.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.ObstacleDetection.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ObstacleDetection.IsEnabled is cc0cd497285e5034a1cccb25f02e9db9

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

9.2 - IsError


Full qualified VSS Path:	`Vehicle.ADAS.ObstacleDetection.IsError`
Description:	Indicates if obstacle sensor system incurred an error condition. True = Error. False = No Error.

flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->IsError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ObstacleDetection.IsError
[get]  OK
Vehicle.ADAS.ObstacleDetection.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.IsError 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.ADAS.ObstacleDetection.IsError

Data Type & Unit


Path	`Vehicle.ADAS.ObstacleDetection.IsError`	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.ADAS.ObstacleDetection.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.ObstacleDetection.IsError is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ObstacleDetection.IsError is 368b74e2468d5217925a478ed6e34f9f

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

9.3 - IsWarning


Full qualified VSS Path:	`Vehicle.ADAS.ObstacleDetection.IsWarning`
Description:	Indicates if obstacle sensor system registered an obstacle.

flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->IsWarning

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ObstacleDetection.IsWarning
[get]  OK
Vehicle.ADAS.ObstacleDetection.IsWarning: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.IsWarning 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.ADAS.ObstacleDetection.IsWarning

Data Type & Unit


Path	`Vehicle.ADAS.ObstacleDetection.IsWarning`	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.ADAS.ObstacleDetection.IsWarning is a Sensor.

The vehicle signal Vehicle.ADAS.ObstacleDetection.IsWarning is a Signal.

UUID

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

The UUID for Vehicle.ADAS.ObstacleDetection.IsWarning is b0b1eab51f135ffcb2a17a7603415fec

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

10 - SupportedAutonomyLevel


Full qualified VSS Path:	`Vehicle.ADAS.SupportedAutonomyLevel`
Description:	Indicates the highest level of autonomy according to SAE J3016 taxonomy the vehicle is capable of.

flowchart LR Vehicle-->ADAS ADAS-->SupportedAutonomyLevel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.ADAS.SupportedAutonomyLevel`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['SAE_0', 'SAE_1', 'SAE_2', 'SAE_3', 'SAE_4', 'SAE_5']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.ADAS.SupportedAutonomyLevel is an Attribute.

The vehicle signal Vehicle.ADAS.SupportedAutonomyLevel is a Signal.

UUID

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

The UUID for Vehicle.ADAS.SupportedAutonomyLevel is 020410189ab4517cb85ceda268b40f51

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

11 - TCS


Full qualified VSS Path:	`Vehicle.ADAS.TCS`
Description:	Traction Control System signals.

flowchart LR Vehicle-->ADAS ADAS-->TCS

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.ADAS.TCS

Signal Information

The vehicle signal Vehicle.ADAS.TCS is a Branch.

UUID

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

The UUID for Vehicle.ADAS.TCS is 0572e9f6b1aa5fb5b2f68086aff05073

Children

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

Vehicle.ADAS.TCS.IsEnabled (Indicates if TCS is enabled. True = Enabled. False = Disabled.)
Vehicle.ADAS.TCS.IsEngaged (Indicates if TCS is currently regulating traction. True = Engaged. False = Not Engaged.)
Vehicle.ADAS.TCS.IsError (Indicates if TCS incurred an error condition. True = Error. False = No Error.)

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.

11.1 - IsEngaged


Full qualified VSS Path:	`Vehicle.ADAS.TCS.IsEngaged`
Description:	Indicates if TCS is currently regulating traction. True = Engaged. False = Not Engaged.

flowchart LR Vehicle-->ADAS ADAS-->TCS TCS-->IsEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.TCS.IsEngaged
[get]  OK
Vehicle.ADAS.TCS.IsEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.TCS.IsEngaged 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.ADAS.TCS.IsEngaged

Data Type & Unit


Path	`Vehicle.ADAS.TCS.IsEngaged`	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.ADAS.TCS.IsEngaged is a Sensor.

The vehicle signal Vehicle.ADAS.TCS.IsEngaged is a Signal.

UUID

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

The UUID for Vehicle.ADAS.TCS.IsEngaged is b33d70009ad5589fbffe17fa7e827242

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

11.2 - IsError


Full qualified VSS Path:	`Vehicle.ADAS.TCS.IsError`
Description:	Indicates if TCS incurred an error condition. True = Error. False = No Error.

flowchart LR Vehicle-->ADAS ADAS-->TCS TCS-->IsError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.TCS.IsError
[get]  OK
Vehicle.ADAS.TCS.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.TCS.IsError 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.ADAS.TCS.IsError

Data Type & Unit


Path	`Vehicle.ADAS.TCS.IsError`	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.ADAS.TCS.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.TCS.IsError is a Signal.

UUID

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

The UUID for Vehicle.ADAS.TCS.IsError is 08f88723ba63558b8c804b8fe8e3f149

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

11.3 - IsEnabled


Full qualified VSS Path:	`Vehicle.ADAS.TCS.IsEnabled`
Description:	Indicates if TCS is enabled. True = Enabled. False = Disabled.

flowchart LR Vehicle-->ADAS ADAS-->TCS TCS-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.TCS.IsEnabled
[get]  OK
Vehicle.ADAS.TCS.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.TCS.IsEnabled 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.ADAS.TCS.IsEnabled

Data Type & Unit


Path	`Vehicle.ADAS.TCS.IsEnabled`	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.ADAS.TCS.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.TCS.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.ADAS.TCS.IsEnabled is 1d2dda19b11758a19ba7c1d5cd2d7956

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

ADAS

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - EBA

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1 - IsEnabled

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.2 - IsEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.3 - IsError

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2 - EBD

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

2.1 - IsEnabled

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.2 - IsEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.3 - IsError

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information