IsHighBeamSwitchOn
Full qualified VSS Path: | Vehicle.Body.Lights.IsHighBeamSwitchOn |
Description: | Status of the high beam switch. True = high beam enabled. False = high beam not enabled. |
Comment: | This signal indicates the status of the switch and does not indicate if low or high beam actually are on. That typically depends on vehicle logic and other signals like Lights.LightSwitch and Vehicle.LowVoltageSystemState. |
Navigation
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.IsHighBeamSwitchOn
[get] OK
Vehicle.Body.Lights.IsHighBeamSwitchOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.IsHighBeamSwitchOn 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.Lights.IsHighBeamSwitchOn |
Data Type & Unit
Path | Vehicle.Body.Lights.IsHighBeamSwitchOn |
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.Lights.IsHighBeamSwitchOn
is an Actuator.
The vehicle signal Vehicle.Body.Lights.IsHighBeamSwitchOn
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.IsHighBeamSwitchOn
is ac7db3cd30f55650bc6939df504f1a79
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.