O2

• 1: Sensor4
• 1.1: ShortTermFuelTrim
• 1.2: Voltage
• 2: Sensor5
• 2.1: ShortTermFuelTrim
• 2.2: Voltage
• 3: Sensor6
• 3.1: ShortTermFuelTrim
• 3.2: Voltage
• 4: Sensor7
• 4.1: ShortTermFuelTrim
• 4.2: Voltage
• 5: Sensor8
• 5.1: ShortTermFuelTrim
• 5.2: Voltage
• 6: Sensor1
• 6.1: ShortTermFuelTrim
• 6.2: Voltage
• 7: Sensor2
• 7.1: ShortTermFuelTrim
• 7.2: Voltage
• 8: Sensor3
• 8.1: ShortTermFuelTrim
• 8.2: Voltage

1 - Sensor4

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

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:

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.1 - ShortTermFuelTrim

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

1.2 - Voltage

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2 - Sensor5

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

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:

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.

2.1 - ShortTermFuelTrim

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2.2 - Voltage

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

3 - Sensor6

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

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:

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.

3.1 - ShortTermFuelTrim

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

3.2 - Voltage

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

4 - Sensor7

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

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:

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.

4.1 - ShortTermFuelTrim

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

4.2 - Voltage

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

5 - Sensor8

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

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:

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.

5.1 - ShortTermFuelTrim

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

5.2 - Voltage

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6 - Sensor1

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

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:

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.

6.1 - ShortTermFuelTrim

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.2 - Voltage

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

7 - Sensor2

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

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:

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.

7.1 - ShortTermFuelTrim

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim
[get]  OK
Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Data Type & Unit

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

7.2 - Voltage

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.OBD.O2.Sensor2.Voltage
[get]  OK
Vehicle.OBD.O2.Sensor2.Voltage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.OBD.O2.Sensor2.Voltage 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Data Type & Unit

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

8 - Sensor3

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

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:

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

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

8.2 - Voltage

Navigation

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.

Data Type & Unit

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:

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.