This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Sensor2
|
|
| Full qualified VSS Path: |
Vehicle.OBD.O2.Sensor2 |
| Description: |
Oxygen sensors (PID 14 - PID 1B) |
Navigation
flowchart LR
Vehicle-->OBD
OBD-->O2
O2-->Sensor2
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.O2.Sensor2 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.OBD.O2.Sensor2 is efcb337cf94056c8a724e76bcfee6765
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 - ShortTermFuelTrim
|
|
| Full qualified VSS Path: |
Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim |
| Description: |
PID 1x (byte B) - Short term fuel trim |
Navigation
flowchart LR
Vehicle-->OBD
OBD-->O2
O2-->Sensor2
Sensor2-->ShortTermFuelTrim
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim
[get] OK
Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim 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.O2.Sensor2.ShortTermFuelTrim is a Sensor.
The vehicle signal Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim is 92e6e172777457a9866ca045d0d79853
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 - Voltage
|
|
| Full qualified VSS Path: |
Vehicle.OBD.O2.Sensor2.Voltage |
| Description: |
PID 1x (byte A) - Sensor voltage |
Navigation
flowchart LR
Vehicle-->OBD
OBD-->O2
O2-->Sensor2
Sensor2-->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.O2.Sensor2.Voltage
[get] OK
Vehicle.OBD.O2.Sensor2.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor2.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.O2.Sensor2.Voltage is a Sensor.
The vehicle signal Vehicle.OBD.O2.Sensor2.Voltage is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.OBD.O2.Sensor2.Voltage is 5f1781bde96b53ce9b810a5a56b7c8ed
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.