PowerOptimizeLevel
Full qualified VSS Path: | Vehicle.Powertrain.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. |
Navigation
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.PowerOptimizeLevel
[get] OK
Vehicle.Powertrain.PowerOptimizeLevel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.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.Powertrain.PowerOptimizeLevel |
Data Type & Unit
Path | Vehicle.Powertrain.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.Powertrain.PowerOptimizeLevel
is an Actuator.
The vehicle signal Vehicle.Powertrain.PowerOptimizeLevel
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Powertrain.PowerOptimizeLevel
is d740b02e2fb35c07bf88a6e5ebe2f6e4
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.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.