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


Full qualified VSS Path:	`Vehicle.Body.Mirrors.Right`
Description:	All mirrors.

flowchart LR Vehicle-->Body Body-->Mirrors Mirrors-->Right

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.Body.Mirrors.Right

Signal Information

The vehicle signal Vehicle.Body.Mirrors.Right is a Branch.

UUID

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

The UUID for Vehicle.Body.Mirrors.Right is 64291c99f7e752c2b035262c17dc85dd

Children

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

Vehicle.Body.Mirrors.Right.IsHeatingOn (Mirror Heater on or off. True = Heater On. False = Heater Off.)
Vehicle.Body.Mirrors.Right.Pan (Mirror pan as a percent. 0 = Center Position. 100 = Fully Left Position. -100 = Fully Right Position.)
Vehicle.Body.Mirrors.Right.Tilt (Mirror tilt as a percent. 0 = Center Position. 100 = Fully Upward Position. -100 = Fully Downward Position.)

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


Full qualified VSS Path:	`Vehicle.Body.Mirrors.Right.IsHeatingOn`
Description:	Mirror Heater on or off. True = Heater On. False = Heater Off.

flowchart LR Vehicle-->Body Body-->Mirrors Mirrors-->Right Right-->IsHeatingOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Body.Mirrors.Right.IsHeatingOn`	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.Body.Mirrors.Right.IsHeatingOn is an Actuator.

The vehicle signal Vehicle.Body.Mirrors.Right.IsHeatingOn is a Signal.

UUID

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

The UUID for Vehicle.Body.Mirrors.Right.IsHeatingOn is 9a57455f48ea5fdbb7a998905dda318c

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name	Type	Min	Max
uint8	unsigned 8-bit integer	0	255
int8	signed 8-bit integer	-128	127
uint16	unsigned 16-bit integer	0	65535
int16	signed 16-bit integer	-32768	32767
uint32	unsigned 32-bit integer	0	4294967295
int32	signed 32-bit integer	-2147483648	2147483647
uint64	unsigned 64-bit integer	0	2^64 - 1
int64	signed 64-bit integer	-2^63	2^63 - 1
boolean	boolean value	0/false	1/true
float	floating point number	-3.4e -38	3.4e 38
double	double precision floating point number	-1.7e -300	1.7e 300
string	character string	n/a	n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

1.2 - Pan


Full qualified VSS Path:	`Vehicle.Body.Mirrors.Right.Pan`
Description:	Mirror pan as a percent. 0 = Center Position. 100 = Fully Left Position. -100 = Fully Right Position.

flowchart LR Vehicle-->Body Body-->Mirrors Mirrors-->Right Right-->Pan

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Body.Mirrors.Right.Pan`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`-100`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Body.Mirrors.Right.Pan is an Actuator.

The vehicle signal Vehicle.Body.Mirrors.Right.Pan is a Signal.

UUID

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

The UUID for Vehicle.Body.Mirrors.Right.Pan is 26088f96804d5d7e811ba50bfb1113eb

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name	Type	Min	Max
uint8	unsigned 8-bit integer	0	255
int8	signed 8-bit integer	-128	127
uint16	unsigned 16-bit integer	0	65535
int16	signed 16-bit integer	-32768	32767
uint32	unsigned 32-bit integer	0	4294967295
int32	signed 32-bit integer	-2147483648	2147483647
uint64	unsigned 64-bit integer	0	2^64 - 1
int64	signed 64-bit integer	-2^63	2^63 - 1
boolean	boolean value	0/false	1/true
float	floating point number	-3.4e -38	3.4e 38
double	double precision floating point number	-1.7e -300	1.7e 300
string	character string	n/a	n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

1.3 - Tilt


Full qualified VSS Path:	`Vehicle.Body.Mirrors.Right.Tilt`
Description:	Mirror tilt as a percent. 0 = Center Position. 100 = Fully Upward Position. -100 = Fully Downward Position.

flowchart LR Vehicle-->Body Body-->Mirrors Mirrors-->Right Right-->Tilt

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Body.Mirrors.Right.Tilt`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`-100`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Body.Mirrors.Right.Tilt is an Actuator.

The vehicle signal Vehicle.Body.Mirrors.Right.Tilt is a Signal.

UUID

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

The UUID for Vehicle.Body.Mirrors.Right.Tilt is 9a28a6ec824c57408881b916a1a0e32b

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name	Type	Min	Max
uint8	unsigned 8-bit integer	0	255
int8	signed 8-bit integer	-128	127
uint16	unsigned 16-bit integer	0	65535
int16	signed 16-bit integer	-32768	32767
uint32	unsigned 32-bit integer	0	4294967295
int32	signed 32-bit integer	-2147483648	2147483647
uint64	unsigned 64-bit integer	0	2^64 - 1
int64	signed 64-bit integer	-2^63	2^63 - 1
boolean	boolean value	0/false	1/true
float	floating point number	-3.4e -38	3.4e 38
double	double precision floating point number	-1.7e -300	1.7e 300
string	character string	n/a	n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2 - Left


Full qualified VSS Path:	`Vehicle.Body.Mirrors.Left`
Description:	All mirrors.

flowchart LR Vehicle-->Body Body-->Mirrors Mirrors-->Left

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.Body.Mirrors.Left

Signal Information

The vehicle signal Vehicle.Body.Mirrors.Left is a Branch.

UUID

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

The UUID for Vehicle.Body.Mirrors.Left is 22609e45a09d58fc85cb77959a686abc

Children

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

Vehicle.Body.Mirrors.Left.IsHeatingOn (Mirror Heater on or off. True = Heater On. False = Heater Off.)
Vehicle.Body.Mirrors.Left.Pan (Mirror pan as a percent. 0 = Center Position. 100 = Fully Left Position. -100 = Fully Right Position.)
Vehicle.Body.Mirrors.Left.Tilt (Mirror tilt as a percent. 0 = Center Position. 100 = Fully Upward Position. -100 = Fully Downward Position.)

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


Full qualified VSS Path:	`Vehicle.Body.Mirrors.Left.IsHeatingOn`
Description:	Mirror Heater on or off. True = Heater On. False = Heater Off.

flowchart LR Vehicle-->Body Body-->Mirrors Mirrors-->Left Left-->IsHeatingOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Body.Mirrors.Left.IsHeatingOn`	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.Body.Mirrors.Left.IsHeatingOn is an Actuator.

The vehicle signal Vehicle.Body.Mirrors.Left.IsHeatingOn is a Signal.

UUID

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

The UUID for Vehicle.Body.Mirrors.Left.IsHeatingOn is b8591c0592d8525e91e1a04495b6995d

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name	Type	Min	Max
uint8	unsigned 8-bit integer	0	255
int8	signed 8-bit integer	-128	127
uint16	unsigned 16-bit integer	0	65535
int16	signed 16-bit integer	-32768	32767
uint32	unsigned 32-bit integer	0	4294967295
int32	signed 32-bit integer	-2147483648	2147483647
uint64	unsigned 64-bit integer	0	2^64 - 1
int64	signed 64-bit integer	-2^63	2^63 - 1
boolean	boolean value	0/false	1/true
float	floating point number	-3.4e -38	3.4e 38
double	double precision floating point number	-1.7e -300	1.7e 300
string	character string	n/a	n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2.2 - Pan


Full qualified VSS Path:	`Vehicle.Body.Mirrors.Left.Pan`
Description:	Mirror pan as a percent. 0 = Center Position. 100 = Fully Left Position. -100 = Fully Right Position.

flowchart LR Vehicle-->Body Body-->Mirrors Mirrors-->Left Left-->Pan

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Body.Mirrors.Left.Pan`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`-100`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Body.Mirrors.Left.Pan is an Actuator.

The vehicle signal Vehicle.Body.Mirrors.Left.Pan is a Signal.

UUID

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

The UUID for Vehicle.Body.Mirrors.Left.Pan is 9dae4bc33a28531199fce500e0562f82

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name	Type	Min	Max
uint8	unsigned 8-bit integer	0	255
int8	signed 8-bit integer	-128	127
uint16	unsigned 16-bit integer	0	65535
int16	signed 16-bit integer	-32768	32767
uint32	unsigned 32-bit integer	0	4294967295
int32	signed 32-bit integer	-2147483648	2147483647
uint64	unsigned 64-bit integer	0	2^64 - 1
int64	signed 64-bit integer	-2^63	2^63 - 1
boolean	boolean value	0/false	1/true
float	floating point number	-3.4e -38	3.4e 38
double	double precision floating point number	-1.7e -300	1.7e 300
string	character string	n/a	n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2.3 - Tilt


Full qualified VSS Path:	`Vehicle.Body.Mirrors.Left.Tilt`
Description:	Mirror tilt as a percent. 0 = Center Position. 100 = Fully Upward Position. -100 = Fully Downward Position.

flowchart LR Vehicle-->Body Body-->Mirrors Mirrors-->Left Left-->Tilt

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Body.Mirrors.Left.Tilt`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`-100`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Body.Mirrors.Left.Tilt is an Actuator.

The vehicle signal Vehicle.Body.Mirrors.Left.Tilt is a Signal.

UUID

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

The UUID for Vehicle.Body.Mirrors.Left.Tilt is 698fee82cc115f3cba54825a298b46ab

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name	Type	Min	Max
uint8	unsigned 8-bit integer	0	255
int8	signed 8-bit integer	-128	127
uint16	unsigned 16-bit integer	0	65535
int16	signed 16-bit integer	-32768	32767
uint32	unsigned 32-bit integer	0	4294967295
int32	signed 32-bit integer	-2147483648	2147483647
uint64	unsigned 64-bit integer	0	2^64 - 1
int64	signed 64-bit integer	-2^63	2^63 - 1
boolean	boolean value	0/false	1/true
float	floating point number	-3.4e -38	3.4e 38
double	double precision floating point number	-1.7e -300	1.7e 300
string	character string	n/a	n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

Mirrors

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - Right

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1 - IsHeatingOn

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.2 - Pan

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.3 - Tilt

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2 - Left

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

2.1 - IsHeatingOn

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.2 - Pan

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.3 - Tilt

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information