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

Return to the regular view of this page.

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:

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 - AdaptiveDistanceSet
Full qualified VSS Path: Vehicle.ADAS.CruiseControl.AdaptiveDistanceSet
Description: Distance in meters to keep from lead vehicle
flowchart LR Vehicle-->ADAS ADAS-->CruiseControl CruiseControl-->AdaptiveDistanceSet

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

Data Type & Unit
Path Vehicle.ADAS.CruiseControl.AdaptiveDistanceSet VSS: Addressing nodes
Data type float VSS: Datatypes
Unit m VSS: Units
Label meter
Description Length measured in meters VSS: Sensors & Actuators
Domain length
Minimum value 0.0 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.CruiseControl.AdaptiveDistanceSet is an Actuator.

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

UUID

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

The UUID for Vehicle.ADAS.CruiseControl.AdaptiveDistanceSet is 72b605a1903750219d50732b4c92084c

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 - AdaptiveIntervalSet
Full qualified VSS Path: Vehicle.ADAS.CruiseControl.AdaptiveIntervalSet
Description: Follow distance setting, commonly 1-5 with 1 being closest.
flowchart LR Vehicle-->ADAS ADAS-->CruiseControl CruiseControl-->AdaptiveIntervalSet

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

Data Type & Unit
Path Vehicle.ADAS.CruiseControl.AdaptiveIntervalSet VSS: Addressing nodes
Data type uint8 VSS: Datatypes

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.ADAS.CruiseControl.AdaptiveIntervalSet is abce234cbded57f4bfea3d859a5fb269

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

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

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

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

4 - IsAdaptive
Full qualified VSS Path: Vehicle.ADAS.CruiseControl.IsAdaptive
Description: Indicates if cruise control system is adaptive (i.e. actively controls speed).
flowchart LR Vehicle-->ADAS ADAS-->CruiseControl CruiseControl-->IsAdaptive

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

Data Type & Unit
Path Vehicle.ADAS.CruiseControl.IsAdaptive 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.IsAdaptive is an Actuator.

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

UUID

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

The UUID for Vehicle.ADAS.CruiseControl.IsAdaptive is cc0e3a46706e5490a184f6982a0c847c

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.

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

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

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

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

7 - 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 Velocity measured in kilometers per hours VSS: Sensors & Actuators
Domain velocity

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

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