Vehicle.OBD.AbsoluteLoad (PID 43 - Absolute load value)
Vehicle.OBD.AcceleratorPositionD (PID 49 - Accelerator pedal position D)
Vehicle.OBD.AcceleratorPositionE (PID 4A - Accelerator pedal position E)
Vehicle.OBD.AcceleratorPositionF (PID 4B - Accelerator pedal position F)
Vehicle.OBD.AirStatus (PID 12 - Secondary air status)
Vehicle.OBD.AmbientAirTemperature (PID 46 - Ambient air temperature)
Vehicle.OBD.BarometricPressure (PID 33 - Barometric pressure)
Vehicle.OBD.Catalyst (Catalyst signals)
Vehicle.OBD.CommandedEGR (PID 2C - Commanded exhaust gas recirculation (EGR))
Vehicle.OBD.CommandedEVAP (PID 2E - Commanded evaporative purge (EVAP) valve)
Vehicle.OBD.CommandedEquivalenceRatio (PID 44 - Commanded equivalence ratio)
Vehicle.OBD.ControlModuleVoltage (PID 42 - Control module voltage)
Vehicle.OBD.CoolantTemperature (PID 05 - Coolant temperature)
Vehicle.OBD.DTCList (List of currently active DTCs formatted according OBD II (SAE-J2012DA_201812) standard ([P|C|B|U]XXXXX ))
Vehicle.OBD.DistanceSinceDTCClear (PID 31 - Distance traveled since codes cleared)
Vehicle.OBD.DistanceWithMIL (PID 21 - Distance traveled with MIL on)
Vehicle.OBD.DriveCycleStatus (PID 41 - OBD status for the current drive cycle)
Vehicle.OBD.EGRError (PID 2D - Exhaust gas recirculation (EGR) error)
Vehicle.OBD.EVAPVaporPressure (PID 32 - Evaporative purge (EVAP) system pressure)
Vehicle.OBD.EVAPVaporPressureAbsolute (PID 53 - Absolute evaporative purge (EVAP) system pressure)
Vehicle.OBD.EVAPVaporPressureAlternate (PID 54 - Alternate evaporative purge (EVAP) system pressure)
Vehicle.OBD.EngineLoad (PID 04 - Engine load in percent - 0 = no load, 100 = full load)
Vehicle.OBD.EngineSpeed (PID 0C - Engine speed measured as rotations per minute)
Vehicle.OBD.EthanolPercent (PID 52 - Percentage of ethanol in the fuel)
Vehicle.OBD.FreezeDTC (PID 02 - DTC that triggered the freeze frame)
Vehicle.OBD.FuelInjectionTiming (PID 5D - Fuel injection timing)
Vehicle.OBD.FuelLevel (PID 2F - Fuel level in the fuel tank)
Vehicle.OBD.FuelPressure (PID 0A - Fuel pressure)
Vehicle.OBD.FuelRailPressureAbsolute (PID 59 - Absolute fuel rail pressure)
Vehicle.OBD.FuelRailPressureDirect (PID 23 - Fuel rail pressure direct inject)
Vehicle.OBD.FuelRailPressureVac (PID 22 - Fuel rail pressure relative to vacuum)
Vehicle.OBD.FuelRate (PID 5E - Engine fuel rate)
Vehicle.OBD.FuelStatus (PID 03 - Fuel status)
Vehicle.OBD.FuelType (PID 51 - Fuel type)
Vehicle.OBD.HybridBatteryRemaining (PID 5B - Remaining life of hybrid battery)
Vehicle.OBD.IntakeTemp (PID 0F - Intake temperature)
Vehicle.OBD.IsPTOActive (PID 1E - Auxiliary input status (power take off))
Vehicle.OBD.LongTermFuelTrim1 (PID 07 - Long Term (learned) Fuel Trim - Bank 1 - negative percent leaner, positive percent richer)
Vehicle.OBD.LongTermFuelTrim2 (PID 09 - Long Term (learned) Fuel Trim - Bank 2 - negative percent leaner, positive percent richer)
Vehicle.OBD.LongTermO2Trim1 (PID 56 (byte A) - Long term secondary O2 trim - Bank 1)
Vehicle.OBD.LongTermO2Trim2 (PID 58 (byte A) - Long term secondary O2 trim - Bank 2)
Vehicle.OBD.LongTermO2Trim3 (PID 56 (byte B) - Long term secondary O2 trim - Bank 3)
Vehicle.OBD.LongTermO2Trim4 (PID 58 (byte B) - Long term secondary O2 trim - Bank 4)
Vehicle.OBD.MAF (PID 10 - Grams of air drawn into engine per second)
Vehicle.OBD.MAP (PID 0B - Intake manifold pressure)
Vehicle.OBD.MaxMAF (PID 50 - Maximum flow for mass air flow sensor)
Vehicle.OBD.O2 (Oxygen sensors (PID 14 - PID 1B))
Vehicle.OBD.O2WR (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))
Vehicle.OBD.OBDStandards (PID 1C - OBD standards this vehicle conforms to)
Vehicle.OBD.OilTemperature (PID 5C - Engine oil temperature)
Vehicle.OBD.OxygenSensorsIn2Banks (PID 13 - Presence of oxygen sensors in 2 banks. [A0..A3] == Bank 1, Sensors 1-4. [A4..A7] == Bank 2, Sensors 1-4)
Vehicle.OBD.OxygenSensorsIn4Banks (PID 1D - Presence of oxygen sensors in 4 banks. Similar to PID 13, but [A0..A7] == [B1S1, B1S2, B2S1, B2S2, B3S1, B3S2, B4S1, B4S2])
Vehicle.OBD.PidsA (PID 00 - Bit array of the supported pids 01 to 20)
Vehicle.OBD.PidsB (PID 20 - Bit array of the supported pids 21 to 40)
Vehicle.OBD.PidsC (PID 40 - Bit array of the supported pids 41 to 60)
Vehicle.OBD.RelativeAcceleratorPosition (PID 5A - Relative accelerator pedal position)
Vehicle.OBD.RelativeThrottlePosition (PID 45 - Relative throttle position)
Vehicle.OBD.RunTime (PID 1F - Engine run time)
Vehicle.OBD.RunTimeMIL (PID 4D - Run time with MIL on)
Vehicle.OBD.ShortTermFuelTrim1 (PID 06 - Short Term (immediate) Fuel Trim - Bank 1 - negative percent leaner, positive percent richer)
Vehicle.OBD.ShortTermFuelTrim2 (PID 08 - Short Term (immediate) Fuel Trim - Bank 2 - negative percent leaner, positive percent richer)
Vehicle.OBD.ShortTermO2Trim1 (PID 55 (byte A) - Short term secondary O2 trim - Bank 1)
Vehicle.OBD.ShortTermO2Trim2 (PID 57 (byte A) - Short term secondary O2 trim - Bank 2)
Vehicle.OBD.ShortTermO2Trim3 (PID 55 (byte B) - Short term secondary O2 trim - Bank 3)
Vehicle.OBD.ShortTermO2Trim4 (PID 57 (byte B) - Short term secondary O2 trim - Bank 4)
Vehicle.OBD.Speed (PID 0D - Vehicle speed)
Vehicle.OBD.Status (PID 01 - OBD status)
Vehicle.OBD.ThrottleActuator (PID 4C - Commanded throttle actuator)
Vehicle.OBD.ThrottlePosition (PID 11 - Throttle position - 0 = closed throttle, 100 = open throttle)
Vehicle.OBD.ThrottlePositionB (PID 47 - Absolute throttle position B)
Vehicle.OBD.ThrottlePositionC (PID 48 - Absolute throttle position C)
Vehicle.OBD.TimeSinceDTCCleared (PID 4E - Time since trouble codes cleared)
Vehicle.OBD.TimingAdvance (PID 0E - Time advance)
Vehicle.OBD.WarmupsSinceDTCClear (PID 30 - Number of warm-ups since codes cleared)

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


Full qualified VSS Path:	`Vehicle.OBD.AbsoluteLoad`
Description:	PID 43 - Absolute load value

flowchart LR Vehicle-->OBD OBD-->AbsoluteLoad

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.AbsoluteLoad
[get]  OK
Vehicle.OBD.AbsoluteLoad: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.AbsoluteLoad 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.OBD.AbsoluteLoad

Data Type & Unit


Path	`Vehicle.OBD.AbsoluteLoad`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.AbsoluteLoad is a Sensor.

The vehicle signal Vehicle.OBD.AbsoluteLoad is a Signal.

UUID

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

The UUID for Vehicle.OBD.AbsoluteLoad is b3dd889a42ce5de9a7904b7196ae325c

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

2 - AcceleratorPositionD


Full qualified VSS Path:	`Vehicle.OBD.AcceleratorPositionD`
Description:	PID 49 - Accelerator pedal position D

flowchart LR Vehicle-->OBD OBD-->AcceleratorPositionD

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.AcceleratorPositionD
[get]  OK
Vehicle.OBD.AcceleratorPositionD: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.AcceleratorPositionD 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.OBD.AcceleratorPositionD

Data Type & Unit


Path	`Vehicle.OBD.AcceleratorPositionD`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.AcceleratorPositionD is a Sensor.

The vehicle signal Vehicle.OBD.AcceleratorPositionD is a Signal.

UUID

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

The UUID for Vehicle.OBD.AcceleratorPositionD is 7e63256081ac5a7b8a28a6fa3c2c2ff9

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

3 - AcceleratorPositionE


Full qualified VSS Path:	`Vehicle.OBD.AcceleratorPositionE`
Description:	PID 4A - Accelerator pedal position E

flowchart LR Vehicle-->OBD OBD-->AcceleratorPositionE

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.AcceleratorPositionE
[get]  OK
Vehicle.OBD.AcceleratorPositionE: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.AcceleratorPositionE 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.OBD.AcceleratorPositionE

Data Type & Unit


Path	`Vehicle.OBD.AcceleratorPositionE`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.AcceleratorPositionE is a Sensor.

The vehicle signal Vehicle.OBD.AcceleratorPositionE is a Signal.

UUID

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

The UUID for Vehicle.OBD.AcceleratorPositionE is 4104e7fc25355e25b4522d233565d84b

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

4 - AcceleratorPositionF


Full qualified VSS Path:	`Vehicle.OBD.AcceleratorPositionF`
Description:	PID 4B - Accelerator pedal position F

flowchart LR Vehicle-->OBD OBD-->AcceleratorPositionF

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.AcceleratorPositionF
[get]  OK
Vehicle.OBD.AcceleratorPositionF: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.AcceleratorPositionF 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.OBD.AcceleratorPositionF

Data Type & Unit


Path	`Vehicle.OBD.AcceleratorPositionF`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.AcceleratorPositionF is a Sensor.

The vehicle signal Vehicle.OBD.AcceleratorPositionF is a Signal.

UUID

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

The UUID for Vehicle.OBD.AcceleratorPositionF is 95f5c2a209a857ff930e2f8e32ac2d3f

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

5 - AmbientAirTemperature


Full qualified VSS Path:	`Vehicle.OBD.AmbientAirTemperature`
Description:	PID 46 - Ambient air temperature

flowchart LR Vehicle-->OBD OBD-->AmbientAirTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.AmbientAirTemperature
[get]  OK
Vehicle.OBD.AmbientAirTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.AmbientAirTemperature 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.OBD.AmbientAirTemperature

Data Type & Unit


Path	`Vehicle.OBD.AmbientAirTemperature`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`celsius`	VSS: Units
Label	degree celsius
Description	Temperature measured in degree celsius	VSS: Sensors & Actuators
Domain	temperature

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.OBD.AmbientAirTemperature is a Sensor.

The vehicle signal Vehicle.OBD.AmbientAirTemperature is a Signal.

UUID

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

The UUID for Vehicle.OBD.AmbientAirTemperature is 220a90f183c5583ea8b8b6454d774517

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

6 - CommandedEquivalenceRatio


Full qualified VSS Path:	`Vehicle.OBD.CommandedEquivalenceRatio`
Description:	PID 44 - Commanded equivalence ratio

flowchart LR Vehicle-->OBD OBD-->CommandedEquivalenceRatio

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.CommandedEquivalenceRatio
[get]  OK
Vehicle.OBD.CommandedEquivalenceRatio: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.CommandedEquivalenceRatio 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.OBD.CommandedEquivalenceRatio

Data Type & Unit


Path	`Vehicle.OBD.CommandedEquivalenceRatio`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`ratio`	VSS: Units
Label	ratio
Description	Relation measured as ratio	VSS: Sensors & Actuators
Domain	relation

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.OBD.CommandedEquivalenceRatio is a Sensor.

The vehicle signal Vehicle.OBD.CommandedEquivalenceRatio is a Signal.

UUID

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

The UUID for Vehicle.OBD.CommandedEquivalenceRatio is 104e39e816f65fa791d0afa24603292b

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

7 - ControlModuleVoltage


Full qualified VSS Path:	`Vehicle.OBD.ControlModuleVoltage`
Description:	PID 42 - Control module voltage

flowchart LR Vehicle-->OBD OBD-->ControlModuleVoltage

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ControlModuleVoltage
[get]  OK
Vehicle.OBD.ControlModuleVoltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ControlModuleVoltage 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.OBD.ControlModuleVoltage

Data Type & Unit


Path	`Vehicle.OBD.ControlModuleVoltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.ControlModuleVoltage is a Sensor.

The vehicle signal Vehicle.OBD.ControlModuleVoltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.ControlModuleVoltage is 59e072b932605ffc88a299c874d885c4

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

8 - DriveCycleStatus


Full qualified VSS Path:	`Vehicle.OBD.DriveCycleStatus`
Description:	PID 41 - OBD status for the current drive cycle

flowchart LR Vehicle-->OBD OBD-->DriveCycleStatus

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.OBD.DriveCycleStatus

Signal Information

The vehicle signal Vehicle.OBD.DriveCycleStatus is a Branch.

UUID

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

The UUID for Vehicle.OBD.DriveCycleStatus is 5215e28062f75154822789b8a5f30630

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.DriveCycleStatus.DTCCount (Number of sensor Trouble Codes (DTC))
Vehicle.OBD.DriveCycleStatus.IgnitionType (Type of the ignition for ICE - spark = spark plug ignition, compression = self-igniting (Diesel engines))
Vehicle.OBD.DriveCycleStatus.IsMILOn (Malfunction Indicator Light (MIL) - False = Off, True = On)

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.

8.1 - DTCCount


Full qualified VSS Path:	`Vehicle.OBD.DriveCycleStatus.DTCCount`
Description:	Number of sensor Trouble Codes (DTC)

flowchart LR Vehicle-->OBD OBD-->DriveCycleStatus DriveCycleStatus-->DTCCount

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DriveCycleStatus.DTCCount
[get]  OK
Vehicle.OBD.DriveCycleStatus.DTCCount: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DriveCycleStatus.DTCCount 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.OBD.DriveCycleStatus.DTCCount

Data Type & Unit


Path	`Vehicle.OBD.DriveCycleStatus.DTCCount`	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.OBD.DriveCycleStatus.DTCCount is a Sensor.

The vehicle signal Vehicle.OBD.DriveCycleStatus.DTCCount is a Signal.

UUID

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

The UUID for Vehicle.OBD.DriveCycleStatus.DTCCount is 312856f746ff560e8098c19196964d3b

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

8.2 - IgnitionType


Full qualified VSS Path:	`Vehicle.OBD.DriveCycleStatus.IgnitionType`
Description:	Type of the ignition for ICE - spark = spark plug ignition, compression = self-igniting (Diesel engines)

flowchart LR Vehicle-->OBD OBD-->DriveCycleStatus DriveCycleStatus-->IgnitionType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DriveCycleStatus.IgnitionType
[get]  OK
Vehicle.OBD.DriveCycleStatus.IgnitionType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DriveCycleStatus.IgnitionType Foo
[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.OBD.DriveCycleStatus.IgnitionType

Data Type & Unit


Path	`Vehicle.OBD.DriveCycleStatus.IgnitionType`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['SPARK', 'COMPRESSION']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.OBD.DriveCycleStatus.IgnitionType is a Sensor.

The vehicle signal Vehicle.OBD.DriveCycleStatus.IgnitionType is a Signal.

UUID

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

The UUID for Vehicle.OBD.DriveCycleStatus.IgnitionType is 1aeb7b6d025f5a8693104824abaa1c49

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

8.3 - IsMILOn


Full qualified VSS Path:	`Vehicle.OBD.DriveCycleStatus.IsMILOn`
Description:	Malfunction Indicator Light (MIL) - False = Off, True = On

flowchart LR Vehicle-->OBD OBD-->DriveCycleStatus DriveCycleStatus-->IsMILOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DriveCycleStatus.IsMILOn
[get]  OK
Vehicle.OBD.DriveCycleStatus.IsMILOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DriveCycleStatus.IsMILOn 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.OBD.DriveCycleStatus.IsMILOn

Data Type & Unit


Path	`Vehicle.OBD.DriveCycleStatus.IsMILOn`	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.OBD.DriveCycleStatus.IsMILOn is a Sensor.

The vehicle signal Vehicle.OBD.DriveCycleStatus.IsMILOn is a Signal.

UUID

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

The UUID for Vehicle.OBD.DriveCycleStatus.IsMILOn is e367394c9a075eef8fd66499e3d9cf14

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

9 - EthanolPercent


Full qualified VSS Path:	`Vehicle.OBD.EthanolPercent`
Description:	PID 52 - Percentage of ethanol in the fuel

flowchart LR Vehicle-->OBD OBD-->EthanolPercent

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.EthanolPercent
[get]  OK
Vehicle.OBD.EthanolPercent: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.EthanolPercent 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.OBD.EthanolPercent

Data Type & Unit


Path	`Vehicle.OBD.EthanolPercent`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.EthanolPercent is a Sensor.

The vehicle signal Vehicle.OBD.EthanolPercent is a Signal.

UUID

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

The UUID for Vehicle.OBD.EthanolPercent is a207e7de17e1520c894b412af6f2522c

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

10 - EVAPVaporPressureAbsolute


Full qualified VSS Path:	`Vehicle.OBD.EVAPVaporPressureAbsolute`
Description:	PID 53 - Absolute evaporative purge (EVAP) system pressure

flowchart LR Vehicle-->OBD OBD-->EVAPVaporPressureAbsolute

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.EVAPVaporPressureAbsolute
[get]  OK
Vehicle.OBD.EVAPVaporPressureAbsolute: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.EVAPVaporPressureAbsolute 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.OBD.EVAPVaporPressureAbsolute

Data Type & Unit


Path	`Vehicle.OBD.EVAPVaporPressureAbsolute`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.EVAPVaporPressureAbsolute is a Sensor.

The vehicle signal Vehicle.OBD.EVAPVaporPressureAbsolute is a Signal.

UUID

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

The UUID for Vehicle.OBD.EVAPVaporPressureAbsolute is ef188a1e1a1356f7bc425081e3e00805

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

11 - EVAPVaporPressureAlternate


Full qualified VSS Path:	`Vehicle.OBD.EVAPVaporPressureAlternate`
Description:	PID 54 - Alternate evaporative purge (EVAP) system pressure

flowchart LR Vehicle-->OBD OBD-->EVAPVaporPressureAlternate

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.EVAPVaporPressureAlternate
[get]  OK
Vehicle.OBD.EVAPVaporPressureAlternate: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.EVAPVaporPressureAlternate 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.OBD.EVAPVaporPressureAlternate

Data Type & Unit


Path	`Vehicle.OBD.EVAPVaporPressureAlternate`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`Pa`	VSS: Units
Label	pascal
Description	Pressure measured in pascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.EVAPVaporPressureAlternate is a Sensor.

The vehicle signal Vehicle.OBD.EVAPVaporPressureAlternate is a Signal.

UUID

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

The UUID for Vehicle.OBD.EVAPVaporPressureAlternate is 68eaba3c79975d61bc35b92cd3e5e8d0

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

12 - FuelInjectionTiming


Full qualified VSS Path:	`Vehicle.OBD.FuelInjectionTiming`
Description:	PID 5D - Fuel injection timing

flowchart LR Vehicle-->OBD OBD-->FuelInjectionTiming

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelInjectionTiming
[get]  OK
Vehicle.OBD.FuelInjectionTiming: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelInjectionTiming 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.OBD.FuelInjectionTiming

Data Type & Unit


Path	`Vehicle.OBD.FuelInjectionTiming`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`degrees`	VSS: Units
Label	degree
Description	Angle measured in degrees	VSS: Sensors & Actuators
Domain	angle

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.OBD.FuelInjectionTiming is a Sensor.

The vehicle signal Vehicle.OBD.FuelInjectionTiming is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelInjectionTiming is ab4869446f5357d6936838983e1b8949

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

13 - FuelRailPressureAbsolute


Full qualified VSS Path:	`Vehicle.OBD.FuelRailPressureAbsolute`
Description:	PID 59 - Absolute fuel rail pressure

flowchart LR Vehicle-->OBD OBD-->FuelRailPressureAbsolute

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelRailPressureAbsolute
[get]  OK
Vehicle.OBD.FuelRailPressureAbsolute: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelRailPressureAbsolute 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.OBD.FuelRailPressureAbsolute

Data Type & Unit


Path	`Vehicle.OBD.FuelRailPressureAbsolute`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.FuelRailPressureAbsolute is a Sensor.

The vehicle signal Vehicle.OBD.FuelRailPressureAbsolute is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelRailPressureAbsolute is 83c88b13d30153949eeca1b1180a9061

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

14 - FuelRate


Full qualified VSS Path:	`Vehicle.OBD.FuelRate`
Description:	PID 5E - Engine fuel rate

flowchart LR Vehicle-->OBD OBD-->FuelRate

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelRate
[get]  OK
Vehicle.OBD.FuelRate: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelRate 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.OBD.FuelRate

Data Type & Unit


Path	`Vehicle.OBD.FuelRate`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l/h`	VSS: Units
Label	liter per hour
Description	Flow measured in liters per hour	VSS: Sensors & Actuators
Domain	flow

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.OBD.FuelRate is a Sensor.

The vehicle signal Vehicle.OBD.FuelRate is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelRate is 4ab7c2b710f95ceb9c7d01d19dabac38

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

15 - FuelType


Full qualified VSS Path:	`Vehicle.OBD.FuelType`
Description:	PID 51 - Fuel type

flowchart LR Vehicle-->OBD OBD-->FuelType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelType
[get]  OK
Vehicle.OBD.FuelType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelType Foo
[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.OBD.FuelType

Data Type & Unit


Path	`Vehicle.OBD.FuelType`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.OBD.FuelType is a Sensor.

The vehicle signal Vehicle.OBD.FuelType is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelType is aefb45bdd8035904b0c8f3ffcedc53a9

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

16 - HybridBatteryRemaining


Full qualified VSS Path:	`Vehicle.OBD.HybridBatteryRemaining`
Description:	PID 5B - Remaining life of hybrid battery

flowchart LR Vehicle-->OBD OBD-->HybridBatteryRemaining

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.HybridBatteryRemaining
[get]  OK
Vehicle.OBD.HybridBatteryRemaining: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.HybridBatteryRemaining 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.OBD.HybridBatteryRemaining

Data Type & Unit


Path	`Vehicle.OBD.HybridBatteryRemaining`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.HybridBatteryRemaining is a Sensor.

The vehicle signal Vehicle.OBD.HybridBatteryRemaining is a Signal.

UUID

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

The UUID for Vehicle.OBD.HybridBatteryRemaining is c9517b6243df5e8d8f3aa3e57f71ec37

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

17 - LongTermO2Trim1


Full qualified VSS Path:	`Vehicle.OBD.LongTermO2Trim1`
Description:	PID 56 (byte A) - Long term secondary O2 trim - Bank 1

flowchart LR Vehicle-->OBD OBD-->LongTermO2Trim1

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.LongTermO2Trim1
[get]  OK
Vehicle.OBD.LongTermO2Trim1: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.LongTermO2Trim1 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.OBD.LongTermO2Trim1

Data Type & Unit


Path	`Vehicle.OBD.LongTermO2Trim1`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.LongTermO2Trim1 is a Sensor.

The vehicle signal Vehicle.OBD.LongTermO2Trim1 is a Signal.

UUID

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

The UUID for Vehicle.OBD.LongTermO2Trim1 is 9a9586e29a02567e9920cb9b0aa2e3f5

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

18 - LongTermO2Trim2


Full qualified VSS Path:	`Vehicle.OBD.LongTermO2Trim2`
Description:	PID 58 (byte A) - Long term secondary O2 trim - Bank 2

flowchart LR Vehicle-->OBD OBD-->LongTermO2Trim2

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.LongTermO2Trim2
[get]  OK
Vehicle.OBD.LongTermO2Trim2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.LongTermO2Trim2 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.OBD.LongTermO2Trim2

Data Type & Unit


Path	`Vehicle.OBD.LongTermO2Trim2`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.LongTermO2Trim2 is a Sensor.

The vehicle signal Vehicle.OBD.LongTermO2Trim2 is a Signal.

UUID

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

The UUID for Vehicle.OBD.LongTermO2Trim2 is e579f6c930605b389e8ce2d7edd92999

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

19 - LongTermO2Trim3


Full qualified VSS Path:	`Vehicle.OBD.LongTermO2Trim3`
Description:	PID 56 (byte B) - Long term secondary O2 trim - Bank 3

flowchart LR Vehicle-->OBD OBD-->LongTermO2Trim3

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.LongTermO2Trim3
[get]  OK
Vehicle.OBD.LongTermO2Trim3: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.LongTermO2Trim3 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.OBD.LongTermO2Trim3

Data Type & Unit


Path	`Vehicle.OBD.LongTermO2Trim3`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.LongTermO2Trim3 is a Sensor.

The vehicle signal Vehicle.OBD.LongTermO2Trim3 is a Signal.

UUID

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

The UUID for Vehicle.OBD.LongTermO2Trim3 is 50ea51ad343a5e59b1d214053e522a45

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

20 - LongTermO2Trim4


Full qualified VSS Path:	`Vehicle.OBD.LongTermO2Trim4`
Description:	PID 58 (byte B) - Long term secondary O2 trim - Bank 4

flowchart LR Vehicle-->OBD OBD-->LongTermO2Trim4

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.LongTermO2Trim4
[get]  OK
Vehicle.OBD.LongTermO2Trim4: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.LongTermO2Trim4 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.OBD.LongTermO2Trim4

Data Type & Unit


Path	`Vehicle.OBD.LongTermO2Trim4`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.LongTermO2Trim4 is a Sensor.

The vehicle signal Vehicle.OBD.LongTermO2Trim4 is a Signal.

UUID

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

The UUID for Vehicle.OBD.LongTermO2Trim4 is f9c20edd12f456e5ace21581cea484bd

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

21 - MaxMAF


Full qualified VSS Path:	`Vehicle.OBD.MaxMAF`
Description:	PID 50 - Maximum flow for mass air flow sensor

flowchart LR Vehicle-->OBD OBD-->MaxMAF

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.MaxMAF
[get]  OK
Vehicle.OBD.MaxMAF: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.MaxMAF 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.OBD.MaxMAF

Data Type & Unit


Path	`Vehicle.OBD.MaxMAF`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`g/s`	VSS: Units
Label	grams per second
Description	Mass per time measured in grams per second	VSS: Sensors & Actuators
Domain	mass per time

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.OBD.MaxMAF is a Sensor.

The vehicle signal Vehicle.OBD.MaxMAF is a Signal.

UUID

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

The UUID for Vehicle.OBD.MaxMAF is e21826479f715ee7afe8dc485f109b11

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

22 - OilTemperature


Full qualified VSS Path:	`Vehicle.OBD.OilTemperature`
Description:	PID 5C - Engine oil temperature

flowchart LR Vehicle-->OBD OBD-->OilTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.OilTemperature
[get]  OK
Vehicle.OBD.OilTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.OilTemperature 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.OBD.OilTemperature

Data Type & Unit


Path	`Vehicle.OBD.OilTemperature`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`celsius`	VSS: Units
Label	degree celsius
Description	Temperature measured in degree celsius	VSS: Sensors & Actuators
Domain	temperature

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.OBD.OilTemperature is a Sensor.

The vehicle signal Vehicle.OBD.OilTemperature is a Signal.

UUID

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

The UUID for Vehicle.OBD.OilTemperature is ef3dfc11085d5077b363b1a4e8e4a84e

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

23 - PidsC


Full qualified VSS Path:	`Vehicle.OBD.PidsC`
Description:	PID 40 - Bit array of the supported pids 41 to 60

flowchart LR Vehicle-->OBD OBD-->PidsC

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.PidsC
[get]  OK
Vehicle.OBD.PidsC: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.PidsC 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.OBD.PidsC

Data Type & Unit


Path	`Vehicle.OBD.PidsC`	VSS: Addressing nodes
Data type	`uint32`	VSS: Datatypes

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.OBD.PidsC is a Sensor.

The vehicle signal Vehicle.OBD.PidsC is a Signal.

UUID

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

The UUID for Vehicle.OBD.PidsC is 7c3a3f0ecc5d593aa996892668afe4b0

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

24 - RelativeAcceleratorPosition


Full qualified VSS Path:	`Vehicle.OBD.RelativeAcceleratorPosition`
Description:	PID 5A - Relative accelerator pedal position

flowchart LR Vehicle-->OBD OBD-->RelativeAcceleratorPosition

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.RelativeAcceleratorPosition
[get]  OK
Vehicle.OBD.RelativeAcceleratorPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.RelativeAcceleratorPosition 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.OBD.RelativeAcceleratorPosition

Data Type & Unit


Path	`Vehicle.OBD.RelativeAcceleratorPosition`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.RelativeAcceleratorPosition is a Sensor.

The vehicle signal Vehicle.OBD.RelativeAcceleratorPosition is a Signal.

UUID

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

The UUID for Vehicle.OBD.RelativeAcceleratorPosition is e25de9aacad3549285b4fb234f10be8f

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

25 - RelativeThrottlePosition


Full qualified VSS Path:	`Vehicle.OBD.RelativeThrottlePosition`
Description:	PID 45 - Relative throttle position

flowchart LR Vehicle-->OBD OBD-->RelativeThrottlePosition

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.RelativeThrottlePosition
[get]  OK
Vehicle.OBD.RelativeThrottlePosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.RelativeThrottlePosition 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.OBD.RelativeThrottlePosition

Data Type & Unit


Path	`Vehicle.OBD.RelativeThrottlePosition`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.RelativeThrottlePosition is a Sensor.

The vehicle signal Vehicle.OBD.RelativeThrottlePosition is a Signal.

UUID

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

The UUID for Vehicle.OBD.RelativeThrottlePosition is 54ecf7dd671c5053aac4bc1bb061d64b

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

26 - RunTimeMIL


Full qualified VSS Path:	`Vehicle.OBD.RunTimeMIL`
Description:	PID 4D - Run time with MIL on

flowchart LR Vehicle-->OBD OBD-->RunTimeMIL

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.RunTimeMIL
[get]  OK
Vehicle.OBD.RunTimeMIL: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.RunTimeMIL 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.OBD.RunTimeMIL

Data Type & Unit


Path	`Vehicle.OBD.RunTimeMIL`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`min`	VSS: Units
Label	minute
Description	Time measured in minutes	VSS: Sensors & Actuators
Domain	time

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.OBD.RunTimeMIL is a Sensor.

The vehicle signal Vehicle.OBD.RunTimeMIL is a Signal.

UUID

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

The UUID for Vehicle.OBD.RunTimeMIL is 555604a484535f60adf8894a6bd895b6

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

27 - ShortTermO2Trim1


Full qualified VSS Path:	`Vehicle.OBD.ShortTermO2Trim1`
Description:	PID 55 (byte A) - Short term secondary O2 trim - Bank 1

flowchart LR Vehicle-->OBD OBD-->ShortTermO2Trim1

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ShortTermO2Trim1
[get]  OK
Vehicle.OBD.ShortTermO2Trim1: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ShortTermO2Trim1 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.OBD.ShortTermO2Trim1

Data Type & Unit


Path	`Vehicle.OBD.ShortTermO2Trim1`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ShortTermO2Trim1 is a Sensor.

The vehicle signal Vehicle.OBD.ShortTermO2Trim1 is a Signal.

UUID

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

The UUID for Vehicle.OBD.ShortTermO2Trim1 is be7ed33a854557ba802da0c51f9f4564

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

28 - ShortTermO2Trim2


Full qualified VSS Path:	`Vehicle.OBD.ShortTermO2Trim2`
Description:	PID 57 (byte A) - Short term secondary O2 trim - Bank 2

flowchart LR Vehicle-->OBD OBD-->ShortTermO2Trim2

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ShortTermO2Trim2
[get]  OK
Vehicle.OBD.ShortTermO2Trim2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ShortTermO2Trim2 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.OBD.ShortTermO2Trim2

Data Type & Unit


Path	`Vehicle.OBD.ShortTermO2Trim2`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ShortTermO2Trim2 is a Sensor.

The vehicle signal Vehicle.OBD.ShortTermO2Trim2 is a Signal.

UUID

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

The UUID for Vehicle.OBD.ShortTermO2Trim2 is c8b962f8990e51d294621408ceaa21d9

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

29 - ShortTermO2Trim3


Full qualified VSS Path:	`Vehicle.OBD.ShortTermO2Trim3`
Description:	PID 55 (byte B) - Short term secondary O2 trim - Bank 3

flowchart LR Vehicle-->OBD OBD-->ShortTermO2Trim3

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ShortTermO2Trim3
[get]  OK
Vehicle.OBD.ShortTermO2Trim3: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ShortTermO2Trim3 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.OBD.ShortTermO2Trim3

Data Type & Unit


Path	`Vehicle.OBD.ShortTermO2Trim3`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ShortTermO2Trim3 is a Sensor.

The vehicle signal Vehicle.OBD.ShortTermO2Trim3 is a Signal.

UUID

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

The UUID for Vehicle.OBD.ShortTermO2Trim3 is af58212df970568b9edcc5e58fa36f8d

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

30 - ShortTermO2Trim4


Full qualified VSS Path:	`Vehicle.OBD.ShortTermO2Trim4`
Description:	PID 57 (byte B) - Short term secondary O2 trim - Bank 4

flowchart LR Vehicle-->OBD OBD-->ShortTermO2Trim4

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ShortTermO2Trim4
[get]  OK
Vehicle.OBD.ShortTermO2Trim4: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ShortTermO2Trim4 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.OBD.ShortTermO2Trim4

Data Type & Unit


Path	`Vehicle.OBD.ShortTermO2Trim4`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ShortTermO2Trim4 is a Sensor.

The vehicle signal Vehicle.OBD.ShortTermO2Trim4 is a Signal.

UUID

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

The UUID for Vehicle.OBD.ShortTermO2Trim4 is 8ef0516c0c965fd6aecbacd6b9120a5b

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

31 - ThrottleActuator


Full qualified VSS Path:	`Vehicle.OBD.ThrottleActuator`
Description:	PID 4C - Commanded throttle actuator

flowchart LR Vehicle-->OBD OBD-->ThrottleActuator

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ThrottleActuator
[get]  OK
Vehicle.OBD.ThrottleActuator: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ThrottleActuator 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.OBD.ThrottleActuator

Data Type & Unit


Path	`Vehicle.OBD.ThrottleActuator`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ThrottleActuator is a Sensor.

The vehicle signal Vehicle.OBD.ThrottleActuator is a Signal.

UUID

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

The UUID for Vehicle.OBD.ThrottleActuator is 49a19905a1005ee3abe0c0a84d7112d1

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

32 - ThrottlePositionB


Full qualified VSS Path:	`Vehicle.OBD.ThrottlePositionB`
Description:	PID 47 - Absolute throttle position B

flowchart LR Vehicle-->OBD OBD-->ThrottlePositionB

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ThrottlePositionB
[get]  OK
Vehicle.OBD.ThrottlePositionB: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ThrottlePositionB 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.OBD.ThrottlePositionB

Data Type & Unit


Path	`Vehicle.OBD.ThrottlePositionB`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ThrottlePositionB is a Sensor.

The vehicle signal Vehicle.OBD.ThrottlePositionB is a Signal.

UUID

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

The UUID for Vehicle.OBD.ThrottlePositionB is 701712a565ed5bf8b6630487a7152c87

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

33 - ThrottlePositionC


Full qualified VSS Path:	`Vehicle.OBD.ThrottlePositionC`
Description:	PID 48 - Absolute throttle position C

flowchart LR Vehicle-->OBD OBD-->ThrottlePositionC

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ThrottlePositionC
[get]  OK
Vehicle.OBD.ThrottlePositionC: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ThrottlePositionC 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.OBD.ThrottlePositionC

Data Type & Unit


Path	`Vehicle.OBD.ThrottlePositionC`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ThrottlePositionC is a Sensor.

The vehicle signal Vehicle.OBD.ThrottlePositionC is a Signal.

UUID

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

The UUID for Vehicle.OBD.ThrottlePositionC is 06f162dc00a85f628f9d5d1bc952665c

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

34 - TimeSinceDTCCleared


Full qualified VSS Path:	`Vehicle.OBD.TimeSinceDTCCleared`
Description:	PID 4E - Time since trouble codes cleared

flowchart LR Vehicle-->OBD OBD-->TimeSinceDTCCleared

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.TimeSinceDTCCleared
[get]  OK
Vehicle.OBD.TimeSinceDTCCleared: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.TimeSinceDTCCleared 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.OBD.TimeSinceDTCCleared

Data Type & Unit


Path	`Vehicle.OBD.TimeSinceDTCCleared`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`min`	VSS: Units
Label	minute
Description	Time measured in minutes	VSS: Sensors & Actuators
Domain	time

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.OBD.TimeSinceDTCCleared is a Sensor.

The vehicle signal Vehicle.OBD.TimeSinceDTCCleared is a Signal.

UUID

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

The UUID for Vehicle.OBD.TimeSinceDTCCleared is 66ea3984a2585dcdaaf6452eef835c0d

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

35 - BarometricPressure


Full qualified VSS Path:	`Vehicle.OBD.BarometricPressure`
Description:	PID 33 - Barometric pressure

flowchart LR Vehicle-->OBD OBD-->BarometricPressure

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.BarometricPressure
[get]  OK
Vehicle.OBD.BarometricPressure: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.BarometricPressure 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.OBD.BarometricPressure

Data Type & Unit


Path	`Vehicle.OBD.BarometricPressure`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.BarometricPressure is a Sensor.

The vehicle signal Vehicle.OBD.BarometricPressure is a Signal.

UUID

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

The UUID for Vehicle.OBD.BarometricPressure is 1966bfff4d235767bfd9a21afb445ac7

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

36 - Catalyst


Full qualified VSS Path:	`Vehicle.OBD.Catalyst`
Description:	Catalyst signals

flowchart LR Vehicle-->OBD OBD-->Catalyst

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.OBD.Catalyst

Signal Information

The vehicle signal Vehicle.OBD.Catalyst is a Branch.

UUID

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

The UUID for Vehicle.OBD.Catalyst is 4eb0b191d6445de081f3f3f759af31c2

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.Catalyst.Bank1 (Catalyst bank 1 signals)
Vehicle.OBD.Catalyst.Bank2 (Catalyst bank 2 signals)

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.

36.1 - Bank1


Full qualified VSS Path:	`Vehicle.OBD.Catalyst.Bank1`
Description:	Catalyst bank 1 signals

flowchart LR Vehicle-->OBD OBD-->Catalyst Catalyst-->Bank1

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.OBD.Catalyst.Bank1

Signal Information

The vehicle signal Vehicle.OBD.Catalyst.Bank1 is a Branch.

UUID

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

The UUID for Vehicle.OBD.Catalyst.Bank1 is 0c3aaf014ba95b938b639d4202ef8b25

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.Catalyst.Bank1.Temperature1 (PID 3C - Catalyst temperature from bank 1, sensor 1)
Vehicle.OBD.Catalyst.Bank1.Temperature2 (PID 3E - Catalyst temperature from bank 1, sensor 2)

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.

36.1.1 - Temperature1


Full qualified VSS Path:	`Vehicle.OBD.Catalyst.Bank1.Temperature1`
Description:	PID 3C - Catalyst temperature from bank 1, sensor 1

flowchart LR Vehicle-->OBD OBD-->Catalyst Catalyst-->Bank1 Bank1-->Temperature1

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.Catalyst.Bank1.Temperature1
[get]  OK
Vehicle.OBD.Catalyst.Bank1.Temperature1: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.Catalyst.Bank1.Temperature1 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.OBD.Catalyst.Bank1.Temperature1

Data Type & Unit


Path	`Vehicle.OBD.Catalyst.Bank1.Temperature1`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`celsius`	VSS: Units
Label	degree celsius
Description	Temperature measured in degree celsius	VSS: Sensors & Actuators
Domain	temperature

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.OBD.Catalyst.Bank1.Temperature1 is a Sensor.

The vehicle signal Vehicle.OBD.Catalyst.Bank1.Temperature1 is a Signal.

UUID

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

The UUID for Vehicle.OBD.Catalyst.Bank1.Temperature1 is 5a770f13939e5d069682d408f160a895

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

36.1.2 - Temperature2


Full qualified VSS Path:	`Vehicle.OBD.Catalyst.Bank1.Temperature2`
Description:	PID 3E - Catalyst temperature from bank 1, sensor 2

flowchart LR Vehicle-->OBD OBD-->Catalyst Catalyst-->Bank1 Bank1-->Temperature2

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.Catalyst.Bank1.Temperature2
[get]  OK
Vehicle.OBD.Catalyst.Bank1.Temperature2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.Catalyst.Bank1.Temperature2 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.OBD.Catalyst.Bank1.Temperature2

Data Type & Unit


Path	`Vehicle.OBD.Catalyst.Bank1.Temperature2`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`celsius`	VSS: Units
Label	degree celsius
Description	Temperature measured in degree celsius	VSS: Sensors & Actuators
Domain	temperature

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.OBD.Catalyst.Bank1.Temperature2 is a Sensor.

The vehicle signal Vehicle.OBD.Catalyst.Bank1.Temperature2 is a Signal.

UUID

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

The UUID for Vehicle.OBD.Catalyst.Bank1.Temperature2 is ca9419a5d23b5937af23b51d823722fa

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

36.2 - Bank2


Full qualified VSS Path:	`Vehicle.OBD.Catalyst.Bank2`
Description:	Catalyst bank 2 signals

flowchart LR Vehicle-->OBD OBD-->Catalyst Catalyst-->Bank2

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.OBD.Catalyst.Bank2

Signal Information

The vehicle signal Vehicle.OBD.Catalyst.Bank2 is a Branch.

UUID

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

The UUID for Vehicle.OBD.Catalyst.Bank2 is 9a20459754755146a3b9608bf6384835

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.Catalyst.Bank2.Temperature1 (PID 3D - Catalyst temperature from bank 2, sensor 1)
Vehicle.OBD.Catalyst.Bank2.Temperature2 (PID 3F - Catalyst temperature from bank 2, sensor 2)

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.

36.2.1 - Temperature2


Full qualified VSS Path:	`Vehicle.OBD.Catalyst.Bank2.Temperature2`
Description:	PID 3F - Catalyst temperature from bank 2, sensor 2

flowchart LR Vehicle-->OBD OBD-->Catalyst Catalyst-->Bank2 Bank2-->Temperature2

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.Catalyst.Bank2.Temperature2
[get]  OK
Vehicle.OBD.Catalyst.Bank2.Temperature2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.Catalyst.Bank2.Temperature2 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.OBD.Catalyst.Bank2.Temperature2

Data Type & Unit


Path	`Vehicle.OBD.Catalyst.Bank2.Temperature2`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`celsius`	VSS: Units
Label	degree celsius
Description	Temperature measured in degree celsius	VSS: Sensors & Actuators
Domain	temperature

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.OBD.Catalyst.Bank2.Temperature2 is a Sensor.

The vehicle signal Vehicle.OBD.Catalyst.Bank2.Temperature2 is a Signal.

UUID

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

The UUID for Vehicle.OBD.Catalyst.Bank2.Temperature2 is f60c68f0ebca5fcf97086ce04e16d661

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

36.2.2 - Temperature1


Full qualified VSS Path:	`Vehicle.OBD.Catalyst.Bank2.Temperature1`
Description:	PID 3D - Catalyst temperature from bank 2, sensor 1

flowchart LR Vehicle-->OBD OBD-->Catalyst Catalyst-->Bank2 Bank2-->Temperature1

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.Catalyst.Bank2.Temperature1
[get]  OK
Vehicle.OBD.Catalyst.Bank2.Temperature1: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.Catalyst.Bank2.Temperature1 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.OBD.Catalyst.Bank2.Temperature1

Data Type & Unit


Path	`Vehicle.OBD.Catalyst.Bank2.Temperature1`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`celsius`	VSS: Units
Label	degree celsius
Description	Temperature measured in degree celsius	VSS: Sensors & Actuators
Domain	temperature

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.OBD.Catalyst.Bank2.Temperature1 is a Sensor.

The vehicle signal Vehicle.OBD.Catalyst.Bank2.Temperature1 is a Signal.

UUID

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

The UUID for Vehicle.OBD.Catalyst.Bank2.Temperature1 is 011658e4ee89502c9a33877c92dbf888

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

37 - CommandedEGR


Full qualified VSS Path:	`Vehicle.OBD.CommandedEGR`
Description:	PID 2C - Commanded exhaust gas recirculation (EGR)

flowchart LR Vehicle-->OBD OBD-->CommandedEGR

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.CommandedEGR
[get]  OK
Vehicle.OBD.CommandedEGR: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.CommandedEGR 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.OBD.CommandedEGR

Data Type & Unit


Path	`Vehicle.OBD.CommandedEGR`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.CommandedEGR is a Sensor.

The vehicle signal Vehicle.OBD.CommandedEGR is a Signal.

UUID

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

The UUID for Vehicle.OBD.CommandedEGR is 0265890a4a695ee6952c9b9f565ddaa5

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

38 - CommandedEVAP


Full qualified VSS Path:	`Vehicle.OBD.CommandedEVAP`
Description:	PID 2E - Commanded evaporative purge (EVAP) valve

flowchart LR Vehicle-->OBD OBD-->CommandedEVAP

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.CommandedEVAP
[get]  OK
Vehicle.OBD.CommandedEVAP: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.CommandedEVAP 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.OBD.CommandedEVAP

Data Type & Unit


Path	`Vehicle.OBD.CommandedEVAP`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.CommandedEVAP is a Sensor.

The vehicle signal Vehicle.OBD.CommandedEVAP is a Signal.

UUID

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

The UUID for Vehicle.OBD.CommandedEVAP is 5e6295d04a9159b88f4698b561b86842

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

39 - DistanceSinceDTCClear


Full qualified VSS Path:	`Vehicle.OBD.DistanceSinceDTCClear`
Description:	PID 31 - Distance traveled since codes cleared

flowchart LR Vehicle-->OBD OBD-->DistanceSinceDTCClear

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DistanceSinceDTCClear
[get]  OK
Vehicle.OBD.DistanceSinceDTCClear: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DistanceSinceDTCClear 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.OBD.DistanceSinceDTCClear

Data Type & Unit


Path	`Vehicle.OBD.DistanceSinceDTCClear`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km`	VSS: Units
Label	kilometer
Description	Distance measured in kilometers	VSS: Sensors & Actuators
Domain	distance

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.OBD.DistanceSinceDTCClear is a Sensor.

The vehicle signal Vehicle.OBD.DistanceSinceDTCClear is a Signal.

UUID

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

The UUID for Vehicle.OBD.DistanceSinceDTCClear is 0da628e2c69d561eb86216ddcb6e7b2a

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

40 - EGRError


Full qualified VSS Path:	`Vehicle.OBD.EGRError`
Description:	PID 2D - Exhaust gas recirculation (EGR) error

flowchart LR Vehicle-->OBD OBD-->EGRError

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.EGRError
[get]  OK
Vehicle.OBD.EGRError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.EGRError 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.OBD.EGRError

Data Type & Unit


Path	`Vehicle.OBD.EGRError`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.EGRError is a Sensor.

The vehicle signal Vehicle.OBD.EGRError is a Signal.

UUID

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

The UUID for Vehicle.OBD.EGRError is 80a7000c5c7b5444b5571a26264061e5

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

41 - EVAPVaporPressure


Full qualified VSS Path:	`Vehicle.OBD.EVAPVaporPressure`
Description:	PID 32 - Evaporative purge (EVAP) system pressure

flowchart LR Vehicle-->OBD OBD-->EVAPVaporPressure

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.EVAPVaporPressure
[get]  OK
Vehicle.OBD.EVAPVaporPressure: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.EVAPVaporPressure 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.OBD.EVAPVaporPressure

Data Type & Unit


Path	`Vehicle.OBD.EVAPVaporPressure`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`Pa`	VSS: Units
Label	pascal
Description	Pressure measured in pascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.EVAPVaporPressure is a Sensor.

The vehicle signal Vehicle.OBD.EVAPVaporPressure is a Signal.

UUID

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

The UUID for Vehicle.OBD.EVAPVaporPressure is 70b5dae2ffd0561eab73efed8ad2f0ad

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

42 - FuelLevel


Full qualified VSS Path:	`Vehicle.OBD.FuelLevel`
Description:	PID 2F - Fuel level in the fuel tank

flowchart LR Vehicle-->OBD OBD-->FuelLevel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelLevel
[get]  OK
Vehicle.OBD.FuelLevel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelLevel 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.OBD.FuelLevel

Data Type & Unit


Path	`Vehicle.OBD.FuelLevel`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.FuelLevel is a Sensor.

The vehicle signal Vehicle.OBD.FuelLevel is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelLevel is fd39813424ee5cd08c44714b35697287

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

43 - WarmupsSinceDTCClear


Full qualified VSS Path:	`Vehicle.OBD.WarmupsSinceDTCClear`
Description:	PID 30 - Number of warm-ups since codes cleared

flowchart LR Vehicle-->OBD OBD-->WarmupsSinceDTCClear

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.WarmupsSinceDTCClear
[get]  OK
Vehicle.OBD.WarmupsSinceDTCClear: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.WarmupsSinceDTCClear 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.OBD.WarmupsSinceDTCClear

Data Type & Unit


Path	`Vehicle.OBD.WarmupsSinceDTCClear`	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.OBD.WarmupsSinceDTCClear is a Sensor.

The vehicle signal Vehicle.OBD.WarmupsSinceDTCClear is a Signal.

UUID

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

The UUID for Vehicle.OBD.WarmupsSinceDTCClear is a63ba60721785fc591e3dd067c4dc2ae

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

44 - DistanceWithMIL


Full qualified VSS Path:	`Vehicle.OBD.DistanceWithMIL`
Description:	PID 21 - Distance traveled with MIL on

flowchart LR Vehicle-->OBD OBD-->DistanceWithMIL

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DistanceWithMIL
[get]  OK
Vehicle.OBD.DistanceWithMIL: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DistanceWithMIL 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.OBD.DistanceWithMIL

Data Type & Unit


Path	`Vehicle.OBD.DistanceWithMIL`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km`	VSS: Units
Label	kilometer
Description	Distance measured in kilometers	VSS: Sensors & Actuators
Domain	distance

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.OBD.DistanceWithMIL is a Sensor.

The vehicle signal Vehicle.OBD.DistanceWithMIL is a Signal.

UUID

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

The UUID for Vehicle.OBD.DistanceWithMIL is a9a522e343f25522b08f11e81bb91349

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

45 - FuelRailPressureDirect


Full qualified VSS Path:	`Vehicle.OBD.FuelRailPressureDirect`
Description:	PID 23 - Fuel rail pressure direct inject

flowchart LR Vehicle-->OBD OBD-->FuelRailPressureDirect

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelRailPressureDirect
[get]  OK
Vehicle.OBD.FuelRailPressureDirect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelRailPressureDirect 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.OBD.FuelRailPressureDirect

Data Type & Unit


Path	`Vehicle.OBD.FuelRailPressureDirect`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.FuelRailPressureDirect is a Sensor.

The vehicle signal Vehicle.OBD.FuelRailPressureDirect is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelRailPressureDirect is 039cb7bf1a8356a98d09eaf4fc029fe9

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

46 - FuelRailPressureVac


Full qualified VSS Path:	`Vehicle.OBD.FuelRailPressureVac`
Description:	PID 22 - Fuel rail pressure relative to vacuum

flowchart LR Vehicle-->OBD OBD-->FuelRailPressureVac

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelRailPressureVac
[get]  OK
Vehicle.OBD.FuelRailPressureVac: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelRailPressureVac 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.OBD.FuelRailPressureVac

Data Type & Unit


Path	`Vehicle.OBD.FuelRailPressureVac`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.FuelRailPressureVac is a Sensor.

The vehicle signal Vehicle.OBD.FuelRailPressureVac is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelRailPressureVac is b3b0adf44aa3572fa07e7434993e6458

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

47 - IsPTOActive


Full qualified VSS Path:	`Vehicle.OBD.IsPTOActive`
Description:	PID 1E - Auxiliary input status (power take off)

flowchart LR Vehicle-->OBD OBD-->IsPTOActive

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.IsPTOActive
[get]  OK
Vehicle.OBD.IsPTOActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.IsPTOActive 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.OBD.IsPTOActive

Data Type & Unit


Path	`Vehicle.OBD.IsPTOActive`	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.OBD.IsPTOActive is a Sensor.

The vehicle signal Vehicle.OBD.IsPTOActive is a Signal.

UUID

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

The UUID for Vehicle.OBD.IsPTOActive is ce291dc40bba5a969e57b17f11ae23a9

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

48 - O2WR


Full qualified VSS Path:	`Vehicle.OBD.O2WR`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

flowchart LR Vehicle-->OBD OBD-->O2WR

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.OBD.O2WR

Signal Information

The vehicle signal Vehicle.OBD.O2WR is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2WR is a439f2bc16575318afe20d0bc6a8cacf

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2WR.Sensor1 (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))
Vehicle.OBD.O2WR.Sensor2 (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))
Vehicle.OBD.O2WR.Sensor3 (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))
Vehicle.OBD.O2WR.Sensor4 (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))
Vehicle.OBD.O2WR.Sensor5 (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))
Vehicle.OBD.O2WR.Sensor6 (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))
Vehicle.OBD.O2WR.Sensor7 (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))
Vehicle.OBD.O2WR.Sensor8 (Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B))

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.

48.1 - Sensor4


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor4`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor4

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.OBD.O2WR.Sensor4

Signal Information

The vehicle signal Vehicle.OBD.O2WR.Sensor4 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor4 is bb67047ddad158ba98876a6a87d02e97

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2WR.Sensor4.Current (PID 3x (byte CD) - Current for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor4.Lambda (PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor4.Voltage (PID 2x (byte CD) - Voltage for wide range/band oxygen sensor)

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.

48.1.1 - Current


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor4.Current`
Description:	PID 3x (byte CD) - Current for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor4 Sensor4-->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.Sensor4.Current
[get]  OK
Vehicle.OBD.O2WR.Sensor4.Current: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor4.Current 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.OBD.O2WR.Sensor4.Current

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor4.Current`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`A`	VSS: Units
Label	ampere
Description	Electric current measured in amperes	VSS: Sensors & Actuators
Domain	electric current

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.OBD.O2WR.Sensor4.Current is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor4.Current is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor4.Current is f16b31fde63a516db04cb44feaa7c27b

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

48.1.2 - Lambda


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor4.Lambda`
Description:	PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor4 Sensor4-->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.Sensor4.Lambda
[get]  OK
Vehicle.OBD.O2WR.Sensor4.Lambda: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor4.Lambda 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.OBD.O2WR.Sensor4.Lambda

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor4.Lambda`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes

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.OBD.O2WR.Sensor4.Lambda is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor4.Lambda is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor4.Lambda is be09013f423c588eae9c06da9ddf290f

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

48.1.3 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor4.Voltage`
Description:	PID 2x (byte CD) - Voltage for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor4 Sensor4-->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.Sensor4.Voltage
[get]  OK
Vehicle.OBD.O2WR.Sensor4.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor4.Voltage 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.OBD.O2WR.Sensor4.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor4.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2WR.Sensor4.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor4.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor4.Voltage is abeca90ba22d5c32a34ee907cedf3192

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

48.2 - Sensor5


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor5`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor5

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.OBD.O2WR.Sensor5

Signal Information

The vehicle signal Vehicle.OBD.O2WR.Sensor5 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor5 is 01c4160d39af5db59c66db844646195e

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2WR.Sensor5.Current (PID 3x (byte CD) - Current for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor5.Lambda (PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor5.Voltage (PID 2x (byte CD) - Voltage for wide range/band oxygen sensor)

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.

48.2.1 - Current


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor5.Current`
Description:	PID 3x (byte CD) - Current for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor5 Sensor5-->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.Sensor5.Current
[get]  OK
Vehicle.OBD.O2WR.Sensor5.Current: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor5.Current 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.OBD.O2WR.Sensor5.Current

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor5.Current`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`A`	VSS: Units
Label	ampere
Description	Electric current measured in amperes	VSS: Sensors & Actuators
Domain	electric current

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.OBD.O2WR.Sensor5.Current is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor5.Current is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor5.Current is 40494cb5826554929f5ecadd5b9173fd

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

48.2.2 - Lambda


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor5.Lambda`
Description:	PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor5 Sensor5-->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.Sensor5.Lambda
[get]  OK
Vehicle.OBD.O2WR.Sensor5.Lambda: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor5.Lambda 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.OBD.O2WR.Sensor5.Lambda

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor5.Lambda`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes

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.OBD.O2WR.Sensor5.Lambda is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor5.Lambda is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor5.Lambda is 16a957200f5c51f89824bbb76a23b9c0

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

48.2.3 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor5.Voltage`
Description:	PID 2x (byte CD) - Voltage for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor5 Sensor5-->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.Sensor5.Voltage
[get]  OK
Vehicle.OBD.O2WR.Sensor5.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor5.Voltage 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.OBD.O2WR.Sensor5.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor5.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2WR.Sensor5.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor5.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor5.Voltage is 699c4db2439f51af8465e823687018b8

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

48.3 - Sensor6


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor6`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor6

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.OBD.O2WR.Sensor6

Signal Information

The vehicle signal Vehicle.OBD.O2WR.Sensor6 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor6 is cff12c30bde957798daaa3a91758b48b

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2WR.Sensor6.Current (PID 3x (byte CD) - Current for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor6.Lambda (PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor6.Voltage (PID 2x (byte CD) - Voltage for wide range/band oxygen sensor)

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.

48.3.1 - Current


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor6.Current`
Description:	PID 3x (byte CD) - Current for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor6 Sensor6-->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.Sensor6.Current
[get]  OK
Vehicle.OBD.O2WR.Sensor6.Current: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor6.Current 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.OBD.O2WR.Sensor6.Current

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor6.Current`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`A`	VSS: Units
Label	ampere
Description	Electric current measured in amperes	VSS: Sensors & Actuators
Domain	electric current

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.OBD.O2WR.Sensor6.Current is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor6.Current is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor6.Current is 06a38b6b4784545bb637279e96d48eb5

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

48.3.2 - Lambda


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor6.Lambda`
Description:	PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor6 Sensor6-->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.Sensor6.Lambda
[get]  OK
Vehicle.OBD.O2WR.Sensor6.Lambda: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor6.Lambda 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.OBD.O2WR.Sensor6.Lambda

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor6.Lambda`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes

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.OBD.O2WR.Sensor6.Lambda is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor6.Lambda is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor6.Lambda is fdae9bb9a3a45b4680450f0347cf6d66

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

48.3.3 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor6.Voltage`
Description:	PID 2x (byte CD) - Voltage for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor6 Sensor6-->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.Sensor6.Voltage
[get]  OK
Vehicle.OBD.O2WR.Sensor6.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor6.Voltage 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.OBD.O2WR.Sensor6.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor6.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2WR.Sensor6.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor6.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor6.Voltage is 304c181c76d55c3abe75382a935c7bde

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

48.4 - Sensor7


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor7`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor7

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.OBD.O2WR.Sensor7

Signal Information

The vehicle signal Vehicle.OBD.O2WR.Sensor7 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor7 is 44459df1f25f5d43a07b00f2bad65ef5

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2WR.Sensor7.Current (PID 3x (byte CD) - Current for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor7.Lambda (PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor7.Voltage (PID 2x (byte CD) - Voltage for wide range/band oxygen sensor)

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.

48.4.1 - Current


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor7.Current`
Description:	PID 3x (byte CD) - Current for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor7 Sensor7-->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.Sensor7.Current
[get]  OK
Vehicle.OBD.O2WR.Sensor7.Current: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor7.Current 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.OBD.O2WR.Sensor7.Current

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor7.Current`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`A`	VSS: Units
Label	ampere
Description	Electric current measured in amperes	VSS: Sensors & Actuators
Domain	electric current

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.OBD.O2WR.Sensor7.Current is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor7.Current is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor7.Current is 6ed46315325d540eb95c86ec61eef8e4

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

48.4.2 - Lambda


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor7.Lambda`
Description:	PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor7 Sensor7-->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.Sensor7.Lambda
[get]  OK
Vehicle.OBD.O2WR.Sensor7.Lambda: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor7.Lambda 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.OBD.O2WR.Sensor7.Lambda

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor7.Lambda`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes

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.OBD.O2WR.Sensor7.Lambda is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor7.Lambda is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor7.Lambda is 9221a5289157538b9dcaa0d961c335fa

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

48.4.3 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor7.Voltage`
Description:	PID 2x (byte CD) - Voltage for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor7 Sensor7-->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.Sensor7.Voltage
[get]  OK
Vehicle.OBD.O2WR.Sensor7.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor7.Voltage 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.OBD.O2WR.Sensor7.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor7.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2WR.Sensor7.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor7.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor7.Voltage is 0ad1d79dcce65c00ac48421b5b54ca0e

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

48.5 - Sensor8


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor8`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor8

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.OBD.O2WR.Sensor8

Signal Information

The vehicle signal Vehicle.OBD.O2WR.Sensor8 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor8 is b8865e72055d52a086f6935d5c188cc1

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2WR.Sensor8.Current (PID 3x (byte CD) - Current for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor8.Lambda (PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor8.Voltage (PID 2x (byte CD) - Voltage for wide range/band oxygen sensor)

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.

48.5.1 - Current


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor8.Current`
Description:	PID 3x (byte CD) - Current for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor8 Sensor8-->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.Sensor8.Current
[get]  OK
Vehicle.OBD.O2WR.Sensor8.Current: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor8.Current 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.OBD.O2WR.Sensor8.Current

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor8.Current`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`A`	VSS: Units
Label	ampere
Description	Electric current measured in amperes	VSS: Sensors & Actuators
Domain	electric current

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.OBD.O2WR.Sensor8.Current is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor8.Current is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor8.Current is 96de3c3b036c50c2978ab2aa490d4d9e

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

48.5.2 - Lambda


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor8.Lambda`
Description:	PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor8 Sensor8-->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.Sensor8.Lambda
[get]  OK
Vehicle.OBD.O2WR.Sensor8.Lambda: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor8.Lambda 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.OBD.O2WR.Sensor8.Lambda

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor8.Lambda`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes

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.OBD.O2WR.Sensor8.Lambda is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor8.Lambda is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor8.Lambda is c56db1195fa3519ab6718ab57d2cd543

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

48.5.3 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor8.Voltage`
Description:	PID 2x (byte CD) - Voltage for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor8 Sensor8-->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.Sensor8.Voltage
[get]  OK
Vehicle.OBD.O2WR.Sensor8.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor8.Voltage 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.OBD.O2WR.Sensor8.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor8.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2WR.Sensor8.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor8.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor8.Voltage is ab7d6c739f025782bba640e58123f0c8

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

48.6 - Sensor1


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor1`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2WR.Sensor1

Signal Information

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:

Vehicle.OBD.O2WR.Sensor1.Current (PID 3x (byte CD) - Current for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor1.Lambda (PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor1.Voltage (PID 2x (byte CD) - Voltage for wide range/band oxygen sensor)

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.

48.6.1 - Current


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor1.Current`
Description:	PID 3x (byte CD) - Current for wide range/band oxygen sensor

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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2WR.Sensor1.Current

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor1.Current`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`A`	VSS: Units
Label	ampere
Description	Electric current measured in amperes	VSS: Sensors & Actuators
Domain	electric current

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.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:


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

48.6.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

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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2WR.Sensor1.Lambda

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor1.Lambda`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes

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.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:


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

48.6.3 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor1.Voltage`
Description:	PID 2x (byte CD) - Voltage for wide range/band oxygen sensor

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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2WR.Sensor1.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor1.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.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:


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

48.7 - Sensor2


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor2`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor2

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.OBD.O2WR.Sensor2

Signal Information

The vehicle signal Vehicle.OBD.O2WR.Sensor2 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor2 is 079f9960f75d5f399df7ff86fcea8f0c

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2WR.Sensor2.Current (PID 3x (byte CD) - Current for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor2.Lambda (PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor2.Voltage (PID 2x (byte CD) - Voltage for wide range/band oxygen sensor)

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.

48.7.1 - Current


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor2.Current`
Description:	PID 3x (byte CD) - Current for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor2 Sensor2-->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.Sensor2.Current
[get]  OK
Vehicle.OBD.O2WR.Sensor2.Current: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor2.Current 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.OBD.O2WR.Sensor2.Current

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor2.Current`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`A`	VSS: Units
Label	ampere
Description	Electric current measured in amperes	VSS: Sensors & Actuators
Domain	electric current

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.OBD.O2WR.Sensor2.Current is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor2.Current is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor2.Current is 442ab33180ca5028a37a487056ba4a51

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

48.7.2 - Lambda


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor2.Lambda`
Description:	PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor2 Sensor2-->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.Sensor2.Lambda
[get]  OK
Vehicle.OBD.O2WR.Sensor2.Lambda: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor2.Lambda 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.OBD.O2WR.Sensor2.Lambda

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor2.Lambda`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes

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.OBD.O2WR.Sensor2.Lambda is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor2.Lambda is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor2.Lambda is ce55aed0e8705a49970566db71ebcf90

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

48.7.3 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor2.Voltage`
Description:	PID 2x (byte CD) - Voltage for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->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.O2WR.Sensor2.Voltage
[get]  OK
Vehicle.OBD.O2WR.Sensor2.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2WR.Sensor2.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor2.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2WR.Sensor2.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor2.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor2.Voltage is a784675c3b765d42ad023d8ee412be26

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

48.8 - Sensor3


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor3`
Description:	Wide range/band oxygen sensors (PID 24 - 2B and PID 34 - 3B)

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor3

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.OBD.O2WR.Sensor3

Signal Information

The vehicle signal Vehicle.OBD.O2WR.Sensor3 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor3 is a8a83d3e33f9584b824088e830bcbaec

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2WR.Sensor3.Current (PID 3x (byte CD) - Current for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor3.Lambda (PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor)
Vehicle.OBD.O2WR.Sensor3.Voltage (PID 2x (byte CD) - Voltage for wide range/band oxygen sensor)

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.

48.8.1 - Current


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor3.Current`
Description:	PID 3x (byte CD) - Current for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor3 Sensor3-->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.Sensor3.Current
[get]  OK
Vehicle.OBD.O2WR.Sensor3.Current: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor3.Current 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.OBD.O2WR.Sensor3.Current

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor3.Current`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`A`	VSS: Units
Label	ampere
Description	Electric current measured in amperes	VSS: Sensors & Actuators
Domain	electric current

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.OBD.O2WR.Sensor3.Current is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor3.Current is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor3.Current is c942468e349e5aaebde4d90ee0bc3814

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

48.8.2 - Lambda


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor3.Lambda`
Description:	PID 2x (byte AB) and PID 3x (byte AB) - Lambda for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor3 Sensor3-->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.Sensor3.Lambda
[get]  OK
Vehicle.OBD.O2WR.Sensor3.Lambda: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor3.Lambda 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.OBD.O2WR.Sensor3.Lambda

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor3.Lambda`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes

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.OBD.O2WR.Sensor3.Lambda is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor3.Lambda is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor3.Lambda is f2ae7c781b0a5dcf8db91558e3cf4c13

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

48.8.3 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2WR.Sensor3.Voltage`
Description:	PID 2x (byte CD) - Voltage for wide range/band oxygen sensor

flowchart LR Vehicle-->OBD OBD-->O2WR O2WR-->Sensor3 Sensor3-->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.Sensor3.Voltage
[get]  OK
Vehicle.OBD.O2WR.Sensor3.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2WR.Sensor3.Voltage 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.OBD.O2WR.Sensor3.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2WR.Sensor3.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2WR.Sensor3.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2WR.Sensor3.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2WR.Sensor3.Voltage is a78f7621a3f75df2adc1dc940219834a

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

49 - OBDStandards


Full qualified VSS Path:	`Vehicle.OBD.OBDStandards`
Description:	PID 1C - OBD standards this vehicle conforms to

flowchart LR Vehicle-->OBD OBD-->OBDStandards

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.OBDStandards
[get]  OK
Vehicle.OBD.OBDStandards: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.OBDStandards 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.OBD.OBDStandards

Data Type & Unit


Path	`Vehicle.OBD.OBDStandards`	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.OBD.OBDStandards is an Attribute.

The vehicle signal Vehicle.OBD.OBDStandards is a Signal.

UUID

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

The UUID for Vehicle.OBD.OBDStandards is 1aa8d7d055cf5a29a31b04a12124f673

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

50 - OxygenSensorsIn4Banks


Full qualified VSS Path:	`Vehicle.OBD.OxygenSensorsIn4Banks`
Description:	PID 1D - Presence of oxygen sensors in 4 banks. Similar to PID 13, but [A0..A7] == [B1S1, B1S2, B2S1, B2S2, B3S1, B3S2, B4S1, B4S2]

flowchart LR Vehicle-->OBD OBD-->OxygenSensorsIn4Banks

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.OxygenSensorsIn4Banks
[get]  OK
Vehicle.OBD.OxygenSensorsIn4Banks: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.OxygenSensorsIn4Banks 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.OBD.OxygenSensorsIn4Banks

Data Type & Unit


Path	`Vehicle.OBD.OxygenSensorsIn4Banks`	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.OBD.OxygenSensorsIn4Banks is a Sensor.

The vehicle signal Vehicle.OBD.OxygenSensorsIn4Banks is a Signal.

UUID

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

The UUID for Vehicle.OBD.OxygenSensorsIn4Banks is 41d3377813d651aa9b9344ba9fd2f880

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

51 - PidsB


Full qualified VSS Path:	`Vehicle.OBD.PidsB`
Description:	PID 20 - Bit array of the supported pids 21 to 40

flowchart LR Vehicle-->OBD OBD-->PidsB

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.PidsB
[get]  OK
Vehicle.OBD.PidsB: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.PidsB 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.OBD.PidsB

Data Type & Unit


Path	`Vehicle.OBD.PidsB`	VSS: Addressing nodes
Data type	`uint32`	VSS: Datatypes

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.OBD.PidsB is a Sensor.

The vehicle signal Vehicle.OBD.PidsB is a Signal.

UUID

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

The UUID for Vehicle.OBD.PidsB is 00193c560a0a5525baa45681e07b50f6

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

52 - RunTime


Full qualified VSS Path:	`Vehicle.OBD.RunTime`
Description:	PID 1F - Engine run time

flowchart LR Vehicle-->OBD OBD-->RunTime

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.RunTime
[get]  OK
Vehicle.OBD.RunTime: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.RunTime 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.OBD.RunTime

Data Type & Unit


Path	`Vehicle.OBD.RunTime`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`s`	VSS: Units
Label	second
Description	Time measured in seconds	VSS: Sensors & Actuators
Domain	time

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.OBD.RunTime is a Sensor.

The vehicle signal Vehicle.OBD.RunTime is a Signal.

UUID

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

The UUID for Vehicle.OBD.RunTime is acf70773752256d1a227ab48257624b5

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

53 - AirStatus


Full qualified VSS Path:	`Vehicle.OBD.AirStatus`
Description:	PID 12 - Secondary air status

flowchart LR Vehicle-->OBD OBD-->AirStatus

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.AirStatus
[get]  OK
Vehicle.OBD.AirStatus: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.AirStatus Foo
[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.OBD.AirStatus

Data Type & Unit


Path	`Vehicle.OBD.AirStatus`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.OBD.AirStatus is a Sensor.

The vehicle signal Vehicle.OBD.AirStatus is a Signal.

UUID

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

The UUID for Vehicle.OBD.AirStatus is 548f65bf59ed505a86dfaa1c33342e4d

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

54 - CoolantTemperature


Full qualified VSS Path:	`Vehicle.OBD.CoolantTemperature`
Description:	PID 05 - Coolant temperature

flowchart LR Vehicle-->OBD OBD-->CoolantTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.CoolantTemperature
[get]  OK
Vehicle.OBD.CoolantTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.CoolantTemperature 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.OBD.CoolantTemperature

Data Type & Unit


Path	`Vehicle.OBD.CoolantTemperature`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`celsius`	VSS: Units
Label	degree celsius
Description	Temperature measured in degree celsius	VSS: Sensors & Actuators
Domain	temperature

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.OBD.CoolantTemperature is a Sensor.

The vehicle signal Vehicle.OBD.CoolantTemperature is a Signal.

UUID

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

The UUID for Vehicle.OBD.CoolantTemperature is 824892cdc72d5f92a38ef3136576edc8

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

55 - DTCList


Full qualified VSS Path:	`Vehicle.OBD.DTCList`
Description:	List of currently active DTCs formatted according OBD II (SAE-J2012DA_201812) standard ([P

flowchart LR Vehicle-->OBD OBD-->DTCList

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.DTCList
[get]  OK
Vehicle.OBD.DTCList: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.DTCList 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.OBD.DTCList

Data Type & Unit


Path	`Vehicle.OBD.DTCList`	VSS: Addressing nodes
Data type	`string[]`	VSS: Datatypes

Signal Information

The vehicle signal Vehicle.OBD.DTCList is a Sensor.

The vehicle signal Vehicle.OBD.DTCList is a Signal.

UUID

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

The UUID for Vehicle.OBD.DTCList is eee1b64e69845d5ab5e793b74631f9dc

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

56 - EngineLoad


Full qualified VSS Path:	`Vehicle.OBD.EngineLoad`
Description:	PID 04 - Engine load in percent - 0 = no load, 100 = full load

flowchart LR Vehicle-->OBD OBD-->EngineLoad

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.EngineLoad
[get]  OK
Vehicle.OBD.EngineLoad: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.EngineLoad 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.OBD.EngineLoad

Data Type & Unit


Path	`Vehicle.OBD.EngineLoad`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.EngineLoad is a Sensor.

The vehicle signal Vehicle.OBD.EngineLoad is a Signal.

UUID

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

The UUID for Vehicle.OBD.EngineLoad is a8fda8a1b4c6534aa49c447bafc1c700

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

57 - EngineSpeed


Full qualified VSS Path:	`Vehicle.OBD.EngineSpeed`
Description:	PID 0C - Engine speed measured as rotations per minute

flowchart LR Vehicle-->OBD OBD-->EngineSpeed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.EngineSpeed
[get]  OK
Vehicle.OBD.EngineSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.EngineSpeed 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.OBD.EngineSpeed

Data Type & Unit


Path	`Vehicle.OBD.EngineSpeed`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`rpm`	VSS: Units
Label	revolutions per minute
Description	Rotational speed measured in revolutions per minute	VSS: Sensors & Actuators
Domain	rotational speed

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.OBD.EngineSpeed is a Sensor.

The vehicle signal Vehicle.OBD.EngineSpeed is a Signal.

UUID

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

The UUID for Vehicle.OBD.EngineSpeed is b682eea93b3e5874ab3b52e95a1fad37

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

58 - FreezeDTC


Full qualified VSS Path:	`Vehicle.OBD.FreezeDTC`
Description:	PID 02 - DTC that triggered the freeze frame

flowchart LR Vehicle-->OBD OBD-->FreezeDTC

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FreezeDTC
[get]  OK
Vehicle.OBD.FreezeDTC: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FreezeDTC Foo
[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.OBD.FreezeDTC

Data Type & Unit


Path	`Vehicle.OBD.FreezeDTC`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.OBD.FreezeDTC is a Sensor.

The vehicle signal Vehicle.OBD.FreezeDTC is a Signal.

UUID

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

The UUID for Vehicle.OBD.FreezeDTC is 5b87fae8dda4522aae209ae528960782

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

59 - FuelPressure


Full qualified VSS Path:	`Vehicle.OBD.FuelPressure`
Description:	PID 0A - Fuel pressure

flowchart LR Vehicle-->OBD OBD-->FuelPressure

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelPressure
[get]  OK
Vehicle.OBD.FuelPressure: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelPressure 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.OBD.FuelPressure

Data Type & Unit


Path	`Vehicle.OBD.FuelPressure`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.FuelPressure is a Sensor.

The vehicle signal Vehicle.OBD.FuelPressure is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelPressure is 34e6b0689f025d7b9bfa1fc49bb30c0f

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

60 - FuelStatus


Full qualified VSS Path:	`Vehicle.OBD.FuelStatus`
Description:	PID 03 - Fuel status

flowchart LR Vehicle-->OBD OBD-->FuelStatus

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.FuelStatus
[get]  OK
Vehicle.OBD.FuelStatus: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.FuelStatus Foo
[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.OBD.FuelStatus

Data Type & Unit


Path	`Vehicle.OBD.FuelStatus`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.OBD.FuelStatus is a Sensor.

The vehicle signal Vehicle.OBD.FuelStatus is a Signal.

UUID

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

The UUID for Vehicle.OBD.FuelStatus is 15fa2f3f667a5f5786eda5c83435ef16

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

61 - IntakeTemp


Full qualified VSS Path:	`Vehicle.OBD.IntakeTemp`
Description:	PID 0F - Intake temperature

flowchart LR Vehicle-->OBD OBD-->IntakeTemp

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.IntakeTemp
[get]  OK
Vehicle.OBD.IntakeTemp: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.IntakeTemp 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.OBD.IntakeTemp

Data Type & Unit


Path	`Vehicle.OBD.IntakeTemp`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`celsius`	VSS: Units
Label	degree celsius
Description	Temperature measured in degree celsius	VSS: Sensors & Actuators
Domain	temperature

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.OBD.IntakeTemp is a Sensor.

The vehicle signal Vehicle.OBD.IntakeTemp is a Signal.

UUID

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

The UUID for Vehicle.OBD.IntakeTemp is 7c108305178b5854b430a23e125588bd

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

62 - LongTermFuelTrim1


Full qualified VSS Path:	`Vehicle.OBD.LongTermFuelTrim1`
Description:	PID 07 - Long Term (learned) Fuel Trim - Bank 1 - negative percent leaner, positive percent richer

flowchart LR Vehicle-->OBD OBD-->LongTermFuelTrim1

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.LongTermFuelTrim1
[get]  OK
Vehicle.OBD.LongTermFuelTrim1: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.LongTermFuelTrim1 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.OBD.LongTermFuelTrim1

Data Type & Unit


Path	`Vehicle.OBD.LongTermFuelTrim1`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.LongTermFuelTrim1 is a Sensor.

The vehicle signal Vehicle.OBD.LongTermFuelTrim1 is a Signal.

UUID

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

The UUID for Vehicle.OBD.LongTermFuelTrim1 is 1c203b11667150f0b4ee1be26a60c084

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

63 - LongTermFuelTrim2


Full qualified VSS Path:	`Vehicle.OBD.LongTermFuelTrim2`
Description:	PID 09 - Long Term (learned) Fuel Trim - Bank 2 - negative percent leaner, positive percent richer

flowchart LR Vehicle-->OBD OBD-->LongTermFuelTrim2

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.LongTermFuelTrim2
[get]  OK
Vehicle.OBD.LongTermFuelTrim2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.LongTermFuelTrim2 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.OBD.LongTermFuelTrim2

Data Type & Unit


Path	`Vehicle.OBD.LongTermFuelTrim2`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.LongTermFuelTrim2 is a Sensor.

The vehicle signal Vehicle.OBD.LongTermFuelTrim2 is a Signal.

UUID

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

The UUID for Vehicle.OBD.LongTermFuelTrim2 is b02aff2efce05632b5694a256e5b9ec7

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

64 - MAF


Full qualified VSS Path:	`Vehicle.OBD.MAF`
Description:	PID 10 - Grams of air drawn into engine per second

flowchart LR Vehicle-->OBD OBD-->MAF

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.MAF
[get]  OK
Vehicle.OBD.MAF: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.MAF 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.OBD.MAF

Data Type & Unit


Path	`Vehicle.OBD.MAF`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`g/s`	VSS: Units
Label	grams per second
Description	Mass per time measured in grams per second	VSS: Sensors & Actuators
Domain	mass per time

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.OBD.MAF is a Sensor.

The vehicle signal Vehicle.OBD.MAF is a Signal.

UUID

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

The UUID for Vehicle.OBD.MAF is f3acdf89fb865313883d5d3126f15518

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

65 - MAP


Full qualified VSS Path:	`Vehicle.OBD.MAP`
Description:	PID 0B - Intake manifold pressure

flowchart LR Vehicle-->OBD OBD-->MAP

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.MAP
[get]  OK
Vehicle.OBD.MAP: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.MAP 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.OBD.MAP

Data Type & Unit


Path	`Vehicle.OBD.MAP`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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.OBD.MAP is a Sensor.

The vehicle signal Vehicle.OBD.MAP is a Signal.

UUID

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

The UUID for Vehicle.OBD.MAP is 335991b1b53f56f097fea7b05d4db83b

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

66 - O2


Full qualified VSS Path:	`Vehicle.OBD.O2`
Description:	Oxygen sensors (PID 14 - PID 1B)

flowchart LR Vehicle-->OBD OBD-->O2

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.OBD.O2

Signal Information

The vehicle signal Vehicle.OBD.O2 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2 is 31f007df72af50f0925d2b4647682a4d

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2.Sensor1 (Oxygen sensors (PID 14 - PID 1B))
Vehicle.OBD.O2.Sensor2 (Oxygen sensors (PID 14 - PID 1B))
Vehicle.OBD.O2.Sensor3 (Oxygen sensors (PID 14 - PID 1B))
Vehicle.OBD.O2.Sensor4 (Oxygen sensors (PID 14 - PID 1B))
Vehicle.OBD.O2.Sensor5 (Oxygen sensors (PID 14 - PID 1B))
Vehicle.OBD.O2.Sensor6 (Oxygen sensors (PID 14 - PID 1B))
Vehicle.OBD.O2.Sensor7 (Oxygen sensors (PID 14 - PID 1B))
Vehicle.OBD.O2.Sensor8 (Oxygen sensors (PID 14 - PID 1B))

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.

66.1 - Sensor4


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor4`
Description:	Oxygen sensors (PID 14 - PID 1B)

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor4

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.OBD.O2.Sensor4

Signal Information

The vehicle signal Vehicle.OBD.O2.Sensor4 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor4 is 853945bce86c5c4f95081075ae32261c

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2.Sensor4.ShortTermFuelTrim (PID 1x (byte B) - Short term fuel trim)
Vehicle.OBD.O2.Sensor4.Voltage (PID 1x (byte A) - Sensor voltage)

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.

66.1.1 - ShortTermFuelTrim


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor4.ShortTermFuelTrim`
Description:	PID 1x (byte B) - Short term fuel trim

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor4 Sensor4-->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.Sensor4.ShortTermFuelTrim
[get]  OK
Vehicle.OBD.O2.Sensor4.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor4.ShortTermFuelTrim 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.OBD.O2.Sensor4.ShortTermFuelTrim

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor4.ShortTermFuelTrim`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.O2.Sensor4.ShortTermFuelTrim is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor4.ShortTermFuelTrim is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor4.ShortTermFuelTrim is b71dcf9d850c5d5686f14ad46cd2cae3

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

66.1.2 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor4.Voltage`
Description:	PID 1x (byte A) - Sensor voltage

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor4 Sensor4-->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.Sensor4.Voltage
[get]  OK
Vehicle.OBD.O2.Sensor4.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor4.Voltage 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.OBD.O2.Sensor4.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor4.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2.Sensor4.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor4.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor4.Voltage is 772cbfab91be59f7bbf3ec4140ffbcc4

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

66.2 - Sensor5


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor5`
Description:	Oxygen sensors (PID 14 - PID 1B)

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor5

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.OBD.O2.Sensor5

Signal Information

The vehicle signal Vehicle.OBD.O2.Sensor5 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor5 is f48c76c9c7ec5ddcb6838ced0bd7517b

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2.Sensor5.ShortTermFuelTrim (PID 1x (byte B) - Short term fuel trim)
Vehicle.OBD.O2.Sensor5.Voltage (PID 1x (byte A) - Sensor voltage)

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.

66.2.1 - ShortTermFuelTrim


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor5.ShortTermFuelTrim`
Description:	PID 1x (byte B) - Short term fuel trim

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor5 Sensor5-->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.Sensor5.ShortTermFuelTrim
[get]  OK
Vehicle.OBD.O2.Sensor5.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor5.ShortTermFuelTrim 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.OBD.O2.Sensor5.ShortTermFuelTrim

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor5.ShortTermFuelTrim`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.O2.Sensor5.ShortTermFuelTrim is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor5.ShortTermFuelTrim is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor5.ShortTermFuelTrim is 7604de26198b51e28a441f79b1d84242

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

66.2.2 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor5.Voltage`
Description:	PID 1x (byte A) - Sensor voltage

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor5 Sensor5-->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.Sensor5.Voltage
[get]  OK
Vehicle.OBD.O2.Sensor5.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor5.Voltage 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.OBD.O2.Sensor5.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor5.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2.Sensor5.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor5.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor5.Voltage is 155a0816093b5aee8012ed2a8d532b7f

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

66.3 - Sensor6


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor6`
Description:	Oxygen sensors (PID 14 - PID 1B)

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor6

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.OBD.O2.Sensor6

Signal Information

The vehicle signal Vehicle.OBD.O2.Sensor6 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor6 is 5269c1877ded507b87d7d1d7bec10605

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2.Sensor6.ShortTermFuelTrim (PID 1x (byte B) - Short term fuel trim)
Vehicle.OBD.O2.Sensor6.Voltage (PID 1x (byte A) - Sensor voltage)

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.

66.3.1 - ShortTermFuelTrim


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor6.ShortTermFuelTrim`
Description:	PID 1x (byte B) - Short term fuel trim

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor6 Sensor6-->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.Sensor6.ShortTermFuelTrim
[get]  OK
Vehicle.OBD.O2.Sensor6.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor6.ShortTermFuelTrim 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.OBD.O2.Sensor6.ShortTermFuelTrim

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor6.ShortTermFuelTrim`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.O2.Sensor6.ShortTermFuelTrim is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor6.ShortTermFuelTrim is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor6.ShortTermFuelTrim is 2fb034769cab5089986d90bf7f9000ca

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

66.3.2 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor6.Voltage`
Description:	PID 1x (byte A) - Sensor voltage

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor6 Sensor6-->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.Sensor6.Voltage
[get]  OK
Vehicle.OBD.O2.Sensor6.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor6.Voltage 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.OBD.O2.Sensor6.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor6.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2.Sensor6.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor6.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor6.Voltage is 85430592fb795e848d7bb91e6b9f1e00

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

66.4 - Sensor7


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor7`
Description:	Oxygen sensors (PID 14 - PID 1B)

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor7

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.OBD.O2.Sensor7

Signal Information

The vehicle signal Vehicle.OBD.O2.Sensor7 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor7 is 4b565102e4a052aa8aa64f27dc678ce3

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2.Sensor7.ShortTermFuelTrim (PID 1x (byte B) - Short term fuel trim)
Vehicle.OBD.O2.Sensor7.Voltage (PID 1x (byte A) - Sensor voltage)

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.

66.4.1 - ShortTermFuelTrim


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor7.ShortTermFuelTrim`
Description:	PID 1x (byte B) - Short term fuel trim

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor7 Sensor7-->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.Sensor7.ShortTermFuelTrim
[get]  OK
Vehicle.OBD.O2.Sensor7.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor7.ShortTermFuelTrim 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.OBD.O2.Sensor7.ShortTermFuelTrim

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor7.ShortTermFuelTrim`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.O2.Sensor7.ShortTermFuelTrim is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor7.ShortTermFuelTrim is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor7.ShortTermFuelTrim is 81f34b16b5e05d1ab159de9474eaf5bc

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

66.4.2 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor7.Voltage`
Description:	PID 1x (byte A) - Sensor voltage

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor7 Sensor7-->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.Sensor7.Voltage
[get]  OK
Vehicle.OBD.O2.Sensor7.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor7.Voltage 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.OBD.O2.Sensor7.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor7.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2.Sensor7.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor7.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor7.Voltage is 23984a68e63f532bab18679e1174130d

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

66.5 - Sensor8


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor8`
Description:	Oxygen sensors (PID 14 - PID 1B)

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor8

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.OBD.O2.Sensor8

Signal Information

The vehicle signal Vehicle.OBD.O2.Sensor8 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor8 is d5eef24c35f1561982127404b50ece11

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2.Sensor8.ShortTermFuelTrim (PID 1x (byte B) - Short term fuel trim)
Vehicle.OBD.O2.Sensor8.Voltage (PID 1x (byte A) - Sensor voltage)

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.

66.5.1 - ShortTermFuelTrim


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor8.ShortTermFuelTrim`
Description:	PID 1x (byte B) - Short term fuel trim

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor8 Sensor8-->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.Sensor8.ShortTermFuelTrim
[get]  OK
Vehicle.OBD.O2.Sensor8.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor8.ShortTermFuelTrim 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.OBD.O2.Sensor8.ShortTermFuelTrim

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor8.ShortTermFuelTrim`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.O2.Sensor8.ShortTermFuelTrim is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor8.ShortTermFuelTrim is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor8.ShortTermFuelTrim is 1699eb2267615e258259e480be0fa606

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

66.5.2 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor8.Voltage`
Description:	PID 1x (byte A) - Sensor voltage

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor8 Sensor8-->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.Sensor8.Voltage
[get]  OK
Vehicle.OBD.O2.Sensor8.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor8.Voltage 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.OBD.O2.Sensor8.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor8.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2.Sensor8.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor8.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor8.Voltage is 23e057b3629a5136bb585638725fe0a2

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

66.6 - Sensor1


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor1`
Description:	Oxygen sensors (PID 14 - PID 1B)

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor1

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.OBD.O2.Sensor1

Signal Information

The vehicle signal Vehicle.OBD.O2.Sensor1 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor1 is 3aa8859203d4545083196a9690d72627

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2.Sensor1.ShortTermFuelTrim (PID 1x (byte B) - Short term fuel trim)
Vehicle.OBD.O2.Sensor1.Voltage (PID 1x (byte A) - Sensor voltage)

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.

66.6.1 - ShortTermFuelTrim


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor1.ShortTermFuelTrim`
Description:	PID 1x (byte B) - Short term fuel trim

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor1 Sensor1-->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.Sensor1.ShortTermFuelTrim
[get]  OK
Vehicle.OBD.O2.Sensor1.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor1.ShortTermFuelTrim 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.OBD.O2.Sensor1.ShortTermFuelTrim

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor1.ShortTermFuelTrim`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.O2.Sensor1.ShortTermFuelTrim is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor1.ShortTermFuelTrim is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor1.ShortTermFuelTrim is ee366d40132456c0bce8cac3a837f16a

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

66.6.2 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor1.Voltage`
Description:	PID 1x (byte A) - Sensor voltage

flowchart LR Vehicle-->OBD OBD-->O2 O2-->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.O2.Sensor1.Voltage
[get]  OK
Vehicle.OBD.O2.Sensor1.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2.Sensor1.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor1.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2.Sensor1.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor1.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor1.Voltage is e95f4ea667265ee3a68ab57b86ecbf66

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

66.7 - Sensor2


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor2`
Description:	Oxygen sensors (PID 14 - PID 1B)

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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2.Sensor2

Signal Information

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:

Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim (PID 1x (byte B) - Short term fuel trim)
Vehicle.OBD.O2.Sensor2.Voltage (PID 1x (byte A) - Sensor voltage)

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.

66.7.1 - ShortTermFuelTrim


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim`
Description:	PID 1x (byte B) - Short term fuel trim

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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.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:


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

66.7.2 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor2.Voltage`
Description:	PID 1x (byte A) - Sensor voltage

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.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.OBD.O2.Sensor2.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor2.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.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:


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

66.8 - Sensor3


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor3`
Description:	Oxygen sensors (PID 14 - PID 1B)

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor3

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.OBD.O2.Sensor3

Signal Information

The vehicle signal Vehicle.OBD.O2.Sensor3 is a Branch.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor3 is b8c145402b7a5cffaa2699ed61b056fa

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.O2.Sensor3.ShortTermFuelTrim (PID 1x (byte B) - Short term fuel trim)
Vehicle.OBD.O2.Sensor3.Voltage (PID 1x (byte A) - Sensor voltage)

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.

66.8.1 - ShortTermFuelTrim


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor3.ShortTermFuelTrim`
Description:	PID 1x (byte B) - Short term fuel trim

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor3 Sensor3-->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.Sensor3.ShortTermFuelTrim
[get]  OK
Vehicle.OBD.O2.Sensor3.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor3.ShortTermFuelTrim 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.OBD.O2.Sensor3.ShortTermFuelTrim

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor3.ShortTermFuelTrim`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.O2.Sensor3.ShortTermFuelTrim is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor3.ShortTermFuelTrim is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor3.ShortTermFuelTrim is 66c300d35eb85e7387dc42528cca48d9

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

66.8.2 - Voltage


Full qualified VSS Path:	`Vehicle.OBD.O2.Sensor3.Voltage`
Description:	PID 1x (byte A) - Sensor voltage

flowchart LR Vehicle-->OBD OBD-->O2 O2-->Sensor3 Sensor3-->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.Sensor3.Voltage
[get]  OK
Vehicle.OBD.O2.Sensor3.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor3.Voltage 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.OBD.O2.Sensor3.Voltage

Data Type & Unit


Path	`Vehicle.OBD.O2.Sensor3.Voltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.OBD.O2.Sensor3.Voltage is a Sensor.

The vehicle signal Vehicle.OBD.O2.Sensor3.Voltage is a Signal.

UUID

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

The UUID for Vehicle.OBD.O2.Sensor3.Voltage is a86a1986f0fe5d25b6c438a00438ff60

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

67 - OxygenSensorsIn2Banks


Full qualified VSS Path:	`Vehicle.OBD.OxygenSensorsIn2Banks`
Description:	PID 13 - Presence of oxygen sensors in 2 banks. [A0..A3] == Bank 1, Sensors 1-4. [A4..A7] == Bank 2, Sensors 1-4

flowchart LR Vehicle-->OBD OBD-->OxygenSensorsIn2Banks

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.OxygenSensorsIn2Banks
[get]  OK
Vehicle.OBD.OxygenSensorsIn2Banks: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.OxygenSensorsIn2Banks 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.OBD.OxygenSensorsIn2Banks

Data Type & Unit


Path	`Vehicle.OBD.OxygenSensorsIn2Banks`	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.OBD.OxygenSensorsIn2Banks is a Sensor.

The vehicle signal Vehicle.OBD.OxygenSensorsIn2Banks is a Signal.

UUID

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

The UUID for Vehicle.OBD.OxygenSensorsIn2Banks is 0a9ba3f0a9b256d78bafd62ee8ce73cd

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

68 - PidsA


Full qualified VSS Path:	`Vehicle.OBD.PidsA`
Description:	PID 00 - Bit array of the supported pids 01 to 20

flowchart LR Vehicle-->OBD OBD-->PidsA

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.PidsA
[get]  OK
Vehicle.OBD.PidsA: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.PidsA 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.OBD.PidsA

Data Type & Unit


Path	`Vehicle.OBD.PidsA`	VSS: Addressing nodes
Data type	`uint32`	VSS: Datatypes

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.OBD.PidsA is a Sensor.

The vehicle signal Vehicle.OBD.PidsA is a Signal.

UUID

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

The UUID for Vehicle.OBD.PidsA is ba1c1b9034955d2d97249c3b4516beef

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

69 - ShortTermFuelTrim1


Full qualified VSS Path:	`Vehicle.OBD.ShortTermFuelTrim1`
Description:	PID 06 - Short Term (immediate) Fuel Trim - Bank 1 - negative percent leaner, positive percent richer

flowchart LR Vehicle-->OBD OBD-->ShortTermFuelTrim1

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ShortTermFuelTrim1
[get]  OK
Vehicle.OBD.ShortTermFuelTrim1: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ShortTermFuelTrim1 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.OBD.ShortTermFuelTrim1

Data Type & Unit


Path	`Vehicle.OBD.ShortTermFuelTrim1`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ShortTermFuelTrim1 is a Sensor.

The vehicle signal Vehicle.OBD.ShortTermFuelTrim1 is a Signal.

UUID

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

The UUID for Vehicle.OBD.ShortTermFuelTrim1 is 569c983874335fb392d4e82a002654cb

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

70 - ShortTermFuelTrim2


Full qualified VSS Path:	`Vehicle.OBD.ShortTermFuelTrim2`
Description:	PID 08 - Short Term (immediate) Fuel Trim - Bank 2 - negative percent leaner, positive percent richer

flowchart LR Vehicle-->OBD OBD-->ShortTermFuelTrim2

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ShortTermFuelTrim2
[get]  OK
Vehicle.OBD.ShortTermFuelTrim2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ShortTermFuelTrim2 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.OBD.ShortTermFuelTrim2

Data Type & Unit


Path	`Vehicle.OBD.ShortTermFuelTrim2`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ShortTermFuelTrim2 is a Sensor.

The vehicle signal Vehicle.OBD.ShortTermFuelTrim2 is a Signal.

UUID

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

The UUID for Vehicle.OBD.ShortTermFuelTrim2 is 53a39620773a523a8182169027169ec2

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

71 - Speed


Full qualified VSS Path:	`Vehicle.OBD.Speed`
Description:	PID 0D - Vehicle speed

flowchart LR Vehicle-->OBD OBD-->Speed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.Speed
[get]  OK
Vehicle.OBD.Speed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.Speed 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.OBD.Speed

Data Type & Unit


Path	`Vehicle.OBD.Speed`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/h`	VSS: Units
Label	kilometer per hour
Description	Speed measured in kilometers per hours	VSS: Sensors & Actuators
Domain	speed

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.OBD.Speed is a Sensor.

The vehicle signal Vehicle.OBD.Speed is a Signal.

UUID

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

The UUID for Vehicle.OBD.Speed is 91ed0bb43eb054759813cd784b071764

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

72 - Status


Full qualified VSS Path:	`Vehicle.OBD.Status`
Description:	PID 01 - OBD status

flowchart LR Vehicle-->OBD OBD-->Status

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.OBD.Status

Signal Information

The vehicle signal Vehicle.OBD.Status is a Branch.

UUID

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

The UUID for Vehicle.OBD.Status is 474f58e593ee5bfebbb9c6ce4a453f96

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.OBD.Status.DTCCount (Number of sensor Trouble Codes (DTC))
Vehicle.OBD.Status.IgnitionType (Type of the ignition for ICE - spark = spark plug ignition, compression = self-igniting (Diesel engines))
Vehicle.OBD.Status.IsMILOn (Malfunction Indicator Light (MIL) False = Off, True = On)

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.

72.1 - DTCCount


Full qualified VSS Path:	`Vehicle.OBD.Status.DTCCount`
Description:	Number of sensor Trouble Codes (DTC)

flowchart LR Vehicle-->OBD OBD-->Status Status-->DTCCount

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.Status.DTCCount
[get]  OK
Vehicle.OBD.Status.DTCCount: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.Status.DTCCount 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.OBD.Status.DTCCount

Data Type & Unit


Path	`Vehicle.OBD.Status.DTCCount`	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.OBD.Status.DTCCount is a Sensor.

The vehicle signal Vehicle.OBD.Status.DTCCount is a Signal.

UUID

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

The UUID for Vehicle.OBD.Status.DTCCount is 4afdf65e788c5f69baf682597e69fb67

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

72.2 - IgnitionType


Full qualified VSS Path:	`Vehicle.OBD.Status.IgnitionType`
Description:	Type of the ignition for ICE - spark = spark plug ignition, compression = self-igniting (Diesel engines)

flowchart LR Vehicle-->OBD OBD-->Status Status-->IgnitionType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.Status.IgnitionType
[get]  OK
Vehicle.OBD.Status.IgnitionType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.Status.IgnitionType Foo
[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.OBD.Status.IgnitionType

Data Type & Unit


Path	`Vehicle.OBD.Status.IgnitionType`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['SPARK', 'COMPRESSION']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.OBD.Status.IgnitionType is a Sensor.

The vehicle signal Vehicle.OBD.Status.IgnitionType is a Signal.

UUID

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

The UUID for Vehicle.OBD.Status.IgnitionType is 7ffd71caac8e5bd18f93366afdfe534d

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

72.3 - IsMILOn


Full qualified VSS Path:	`Vehicle.OBD.Status.IsMILOn`
Description:	Malfunction Indicator Light (MIL) False = Off, True = On

flowchart LR Vehicle-->OBD OBD-->Status Status-->IsMILOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.Status.IsMILOn
[get]  OK
Vehicle.OBD.Status.IsMILOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.Status.IsMILOn 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.OBD.Status.IsMILOn

Data Type & Unit


Path	`Vehicle.OBD.Status.IsMILOn`	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.OBD.Status.IsMILOn is a Sensor.

The vehicle signal Vehicle.OBD.Status.IsMILOn is a Signal.

UUID

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

The UUID for Vehicle.OBD.Status.IsMILOn is 8744bcb275205630932320b66185502c

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

73 - ThrottlePosition


Full qualified VSS Path:	`Vehicle.OBD.ThrottlePosition`
Description:	PID 11 - Throttle position - 0 = closed throttle, 100 = open throttle

flowchart LR Vehicle-->OBD OBD-->ThrottlePosition

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.ThrottlePosition
[get]  OK
Vehicle.OBD.ThrottlePosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.ThrottlePosition 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.OBD.ThrottlePosition

Data Type & Unit


Path	`Vehicle.OBD.ThrottlePosition`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation

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.OBD.ThrottlePosition is a Sensor.

The vehicle signal Vehicle.OBD.ThrottlePosition is a Signal.

UUID

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

The UUID for Vehicle.OBD.ThrottlePosition is ec1d372020205bb4a846a014b33801e1

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

74 - TimingAdvance


Full qualified VSS Path:	`Vehicle.OBD.TimingAdvance`
Description:	PID 0E - Time advance

flowchart LR Vehicle-->OBD OBD-->TimingAdvance

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.TimingAdvance
[get]  OK
Vehicle.OBD.TimingAdvance: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.TimingAdvance 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.OBD.TimingAdvance

Data Type & Unit


Path	`Vehicle.OBD.TimingAdvance`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`degrees`	VSS: Units
Label	degree
Description	Angle measured in degrees	VSS: Sensors & Actuators
Domain	angle

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.OBD.TimingAdvance is a Sensor.

The vehicle signal Vehicle.OBD.TimingAdvance is a Signal.

UUID

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

The UUID for Vehicle.OBD.TimingAdvance is 35533b7e327d5f839b17c932b630767c

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

OBD

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - AbsoluteLoad

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2 - AcceleratorPositionD

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

3 - AcceleratorPositionE

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

4 - AcceleratorPositionF

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

5 - AmbientAirTemperature

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

6 - CommandedEquivalenceRatio

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

7 - ControlModuleVoltage

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

8 - DriveCycleStatus

Navigation