This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Sensor1
|
|
Full qualified VSS Path: |
Vehicle.OBD.O2WR.Sensor1 |
Description: |
Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B) |
Navigation
flowchart LR
Vehicle-->OBD
OBD-->O2WR
O2WR-->Sensor1
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.OBD.O2WR.Sensor1
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.OBD.O2WR.Sensor1
is 496074cec04a5260b60fd39bb7ed1479
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:
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 - Current
|
|
Full qualified VSS Path: |
Vehicle.OBD.O2WR.Sensor1.Current |
Description: |
PID 3x (byte CD) - Current for wide range/band oxygen sensor |
Navigation
flowchart LR
Vehicle-->OBD
OBD-->O2WR
O2WR-->Sensor1
Sensor1-->Current
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.O2WR.Sensor1.Current
[get] OK
Vehicle.OBD.O2WR.Sensor1.Current: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor1.Current 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.OBD.O2WR.Sensor1.Current
is a Sensor.
The vehicle signal Vehicle.OBD.O2WR.Sensor1.Current
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.OBD.O2WR.Sensor1.Current
is bb4c70d9d2ae56c8a9a3be446db6f54c
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:
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 - Lambda
|
|
Full qualified VSS Path: |
Vehicle.OBD.O2WR.Sensor1.Lambda |
Description: |
PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor |
Navigation
flowchart LR
Vehicle-->OBD
OBD-->O2WR
O2WR-->Sensor1
Sensor1-->Lambda
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.O2WR.Sensor1.Lambda
[get] OK
Vehicle.OBD.O2WR.Sensor1.Lambda: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor1.Lambda 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.OBD.O2WR.Sensor1.Lambda
is a Sensor.
The vehicle signal Vehicle.OBD.O2WR.Sensor1.Lambda
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.OBD.O2WR.Sensor1.Lambda
is b809083454a5516f995477c59bf4d3c6
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:
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 - Voltage
|
|
Full qualified VSS Path: |
Vehicle.OBD.O2WR.Sensor1.Voltage |
Description: |
PID 2x (byte CD) - Voltage for wide range/band oxygen sensor |
Navigation
flowchart LR
Vehicle-->OBD
OBD-->O2WR
O2WR-->Sensor1
Sensor1-->Voltage
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.O2WR.Sensor1.Voltage
[get] OK
Vehicle.OBD.O2WR.Sensor1.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor1.Voltage 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.OBD.O2WR.Sensor1.Voltage
is a Sensor.
The vehicle signal Vehicle.OBD.O2WR.Sensor1.Voltage
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.OBD.O2WR.Sensor1.Voltage
is 396251cbfa5a57ffb1dd743298dfcdf9
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:
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.