Seat

• 1: Row2
• 1.1: Middle
• 1.1.1: Airbag
• 1.1.1.1: IsDeployed
• 1.1.1.2: IsEnabled
• 1.1.2: Backrest
• 1.1.2.1: BottomLumbarSupport
• 1.1.2.2: HeatingCooling
• 1.1.2.3: IsLessLumbarSupportSwitchEngaged
• 1.1.2.4: IsLessSideBolsterSupportSwitchEngaged
• 1.1.2.5: IsLumbarDownSwitchEngaged
• 1.1.2.6: IsLumbarUpSwitchEngaged
• 1.1.2.7: IsMoreLumbarSupportSwitchEngaged
• 1.1.2.8: IsMoreSideBolsterSupportSwitchEngaged
• 1.1.2.9: IsReclineBackwardSwitchEngaged
• 1.1.2.10: IsReclineForwardSwitchEngaged
• 1.1.2.11: LumbarHeight
• 1.1.2.12: LumbarSupport
• 1.1.2.13: MidLumbarSupport
• 1.1.2.14: Recline
• 1.1.2.15: SideBolsterSupport
• 1.1.2.16: SideBolsterSupportLeft
• 1.1.2.17: SideBolsterSupportRight
• 1.1.2.18: TopLumbarSupport
• 1.1.2.19: UpperShoulderSupport
• 1.1.3: Headrest
• 1.1.3.1: Angle
• 1.1.3.2: Height
• 1.1.3.3: IsBackwardSwitchEngaged
• 1.1.3.4: IsDownSwitchEngaged
• 1.1.3.5: IsForwardSwitchEngaged
• 1.1.3.6: IsUpSwitchEngaged
• 1.1.4: HeatingCooling
• 1.1.5: Height
• 1.1.6: IsBackwardSwitchEngaged
• 1.1.7: IsBelted
• 1.1.8: IsCoolerSwitchEngaged
• 1.1.9: IsDecreaseMassageLevelSwitchEngaged
• 1.1.10: IsDownSwitchEngaged
• 1.1.11: IsForwardSwitchEngaged
• 1.1.12: IsIncreaseMassageLevelSwitchEngaged
• 1.1.13: IsTiltBackwardSwitchEngaged
• 1.1.14: IsTiltForwardSwitchEngaged
• 1.1.15: IsUpSwitchEngaged
• 1.1.16: IsWarmerSwitchEngaged
• 1.1.17: Massage
• 1.1.17.1: IsAvailable
• 1.1.17.2: Level
• 1.1.17.3: Status
• 1.1.17.4: SupportedTypes
• 1.1.17.5: TypeActive
• 1.1.18: NeckScarf
• 1.1.18.1: FanSpeed
• 1.1.18.2: HeatingCooling
• 1.1.19: OccupancyStatus
• 1.1.20: Position
• 1.1.21: SeatBeltHeight
• 1.1.22: Seating
• 1.1.22.1: HeatingCooling
• 1.1.22.2: IsBackwardSwitchEngaged
• 1.1.22.3: IsForwardSwitchEngaged
• 1.1.22.4: Length
• 1.1.22.5: SideBolsterSupportLeft
• 1.1.22.6: SideBolsterSupportRight
• 1.1.23: Tilt
• 1.2: PassengerSide
• 1.2.1: Airbag
• 1.2.1.1: IsDeployed
• 1.2.1.2: IsEnabled
• 1.2.2: Headrest
• 1.2.2.1: Angle
• 1.2.2.2: Height
• 1.2.2.3: IsBackwardSwitchEngaged
• 1.2.2.4: IsDownSwitchEngaged
• 1.2.2.5: IsForwardSwitchEngaged
• 1.2.2.6: IsUpSwitchEngaged
• 1.2.3: IsBackwardSwitchEngaged
• 1.2.4: IsCoolerSwitchEngaged
• 1.2.5: IsDecreaseMassageLevelSwitchEngaged
• 1.2.6: IsDownSwitchEngaged
• 1.2.7: IsForwardSwitchEngaged
• 1.2.8: IsIncreaseMassageLevelSwitchEngaged
• 1.2.9: IsTiltBackwardSwitchEngaged
• 1.2.10: IsTiltForwardSwitchEngaged
• 1.2.11: IsUpSwitchEngaged
• 1.2.12: IsWarmerSwitchEngaged
• 1.2.13: NeckScarf
• 1.2.13.1: FanSpeed
• 1.2.13.2: HeatingCooling
• 1.2.14: Seating
• 1.2.14.1: HeatingCooling
• 1.2.14.2: IsBackwardSwitchEngaged
• 1.2.14.3: IsForwardSwitchEngaged
• 1.2.14.4: Length
• 1.2.14.5: SideBolsterSupportLeft
• 1.2.14.6: SideBolsterSupportRight
• 1.2.15: Backrest
• 1.2.15.1: BottomLumbarSupport
• 1.2.15.2: IsLessLumbarSupportSwitchEngaged
• 1.2.15.3: IsLessSideBolsterSupportSwitchEngaged
• 1.2.15.4: IsLumbarDownSwitchEngaged
• 1.2.15.5: IsLumbarUpSwitchEngaged
• 1.2.15.6: IsMoreLumbarSupportSwitchEngaged
• 1.2.15.7: IsMoreSideBolsterSupportSwitchEngaged
• 1.2.15.8: IsReclineBackwardSwitchEngaged
• 1.2.15.9: IsReclineForwardSwitchEngaged
• 1.2.15.10: LumbarHeight
• 1.2.15.11: SideBolsterSupport
• 1.2.15.12: SideBolsterSupportLeft
• 1.2.15.13: SideBolsterSupportRight
• 1.2.15.14: UpperShoulderSupport
• 1.2.15.15: HeatingCooling
• 1.2.15.16: LumbarSupport
• 1.2.15.17: MidLumbarSupport
• 1.2.15.18: Recline
• 1.2.15.19: TopLumbarSupport
• 1.2.16: HeatingCooling
• 1.2.17: Height
• 1.2.18: IsBelted
• 1.2.19: Massage
• 1.2.19.1: IsAvailable
• 1.2.19.2: Level
• 1.2.19.3: Status
• 1.2.19.4: SupportedTypes
• 1.2.19.5: TypeActive
• 1.2.20: OccupancyStatus
• 1.2.21: Position
• 1.2.22: SeatBeltHeight
• 1.2.23: Tilt
• 1.3: DriverSide
• 1.3.1: IsBackwardSwitchEngaged
• 1.3.2: IsCoolerSwitchEngaged
• 1.3.3: IsDecreaseMassageLevelSwitchEngaged
• 1.3.4: IsDownSwitchEngaged
• 1.3.5: IsForwardSwitchEngaged
• 1.3.6: IsIncreaseMassageLevelSwitchEngaged
• 1.3.7: IsTiltBackwardSwitchEngaged
• 1.3.8: IsTiltForwardSwitchEngaged
• 1.3.9: IsUpSwitchEngaged
• 1.3.10: IsWarmerSwitchEngaged
• 1.3.11: NeckScarf
• 1.3.11.1: FanSpeed
• 1.3.11.2: HeatingCooling
• 1.3.12: Airbag
• 1.3.12.1: IsDeployed
• 1.3.12.2: IsEnabled
• 1.3.13: Backrest
• 1.3.13.1: BottomLumbarSupport
• 1.3.13.2: HeatingCooling
• 1.3.13.3: IsLessLumbarSupportSwitchEngaged
• 1.3.13.4: IsLessSideBolsterSupportSwitchEngaged
• 1.3.13.5: IsLumbarDownSwitchEngaged
• 1.3.13.6: IsLumbarUpSwitchEngaged
• 1.3.13.7: IsMoreLumbarSupportSwitchEngaged
• 1.3.13.8: IsMoreSideBolsterSupportSwitchEngaged
• 1.3.13.9: IsReclineBackwardSwitchEngaged
• 1.3.13.10: IsReclineForwardSwitchEngaged
• 1.3.13.11: LumbarHeight
• 1.3.13.12: LumbarSupport
• 1.3.13.13: MidLumbarSupport
• 1.3.13.14: Recline
• 1.3.13.15: SideBolsterSupport
• 1.3.13.16: SideBolsterSupportLeft
• 1.3.13.17: SideBolsterSupportRight
• 1.3.13.18: TopLumbarSupport
• 1.3.13.19: UpperShoulderSupport
• 1.3.14: Headrest
• 1.3.14.1: Angle
• 1.3.14.2: Height
• 1.3.14.3: IsBackwardSwitchEngaged
• 1.3.14.4: IsDownSwitchEngaged
• 1.3.14.5: IsForwardSwitchEngaged
• 1.3.14.6: IsUpSwitchEngaged
• 1.3.15: HeatingCooling
• 1.3.16: Height
• 1.3.17: IsBelted
• 1.3.18: Massage
• 1.3.18.1: IsAvailable
• 1.3.18.2: Level
• 1.3.18.3: Status
• 1.3.18.4: SupportedTypes
• 1.3.18.5: TypeActive
• 1.3.19: OccupancyStatus
• 1.3.20: Position
• 1.3.21: SeatBeltHeight
• 1.3.22: Seating
• 1.3.22.1: HeatingCooling
• 1.3.22.2: IsBackwardSwitchEngaged
• 1.3.22.3: IsForwardSwitchEngaged
• 1.3.22.4: Length
• 1.3.22.5: SideBolsterSupportLeft
• 1.3.22.6: SideBolsterSupportRight
• 1.3.23: Tilt
• 2: Row1
• 2.1: Middle
• 2.1.1: Airbag
• 2.1.1.1: IsDeployed
• 2.1.1.2: IsEnabled
• 2.1.2: Backrest
• 2.1.2.1: BottomLumbarSupport
• 2.1.2.2: HeatingCooling
• 2.1.2.3: IsLessLumbarSupportSwitchEngaged
• 2.1.2.4: IsLessSideBolsterSupportSwitchEngaged
• 2.1.2.5: IsLumbarDownSwitchEngaged
• 2.1.2.6: IsLumbarUpSwitchEngaged
• 2.1.2.7: IsMoreLumbarSupportSwitchEngaged
• 2.1.2.8: IsMoreSideBolsterSupportSwitchEngaged
• 2.1.2.9: IsReclineBackwardSwitchEngaged
• 2.1.2.10: IsReclineForwardSwitchEngaged
• 2.1.2.11: LumbarHeight
• 2.1.2.12: LumbarSupport
• 2.1.2.13: MidLumbarSupport
• 2.1.2.14: Recline
• 2.1.2.15: SideBolsterSupport
• 2.1.2.16: SideBolsterSupportLeft
• 2.1.2.17: SideBolsterSupportRight
• 2.1.2.18: TopLumbarSupport
• 2.1.2.19: UpperShoulderSupport
• 2.1.3: Headrest
• 2.1.3.1: Angle
• 2.1.3.2: Height
• 2.1.3.3: IsBackwardSwitchEngaged
• 2.1.3.4: IsDownSwitchEngaged
• 2.1.3.5: IsForwardSwitchEngaged
• 2.1.3.6: IsUpSwitchEngaged
• 2.1.4: HeatingCooling
• 2.1.5: Height
• 2.1.6: IsBackwardSwitchEngaged
• 2.1.7: IsBelted
• 2.1.8: IsCoolerSwitchEngaged
• 2.1.9: IsDecreaseMassageLevelSwitchEngaged
• 2.1.10: IsDownSwitchEngaged
• 2.1.11: IsForwardSwitchEngaged
• 2.1.12: IsIncreaseMassageLevelSwitchEngaged
• 2.1.13: IsTiltBackwardSwitchEngaged
• 2.1.14: IsTiltForwardSwitchEngaged
• 2.1.15: IsUpSwitchEngaged
• 2.1.16: IsWarmerSwitchEngaged
• 2.1.17: Massage
• 2.1.17.1: IsAvailable
• 2.1.17.2: Level
• 2.1.17.3: Status
• 2.1.17.4: SupportedTypes
• 2.1.17.5: TypeActive
• 2.1.18: NeckScarf
• 2.1.18.1: FanSpeed
• 2.1.18.2: HeatingCooling
• 2.1.19: OccupancyStatus
• 2.1.20: Position
• 2.1.21: SeatBeltHeight
• 2.1.22: Seating
• 2.1.22.1: HeatingCooling
• 2.1.22.2: IsBackwardSwitchEngaged
• 2.1.22.3: IsForwardSwitchEngaged
• 2.1.22.4: Length
• 2.1.22.5: SideBolsterSupportLeft
• 2.1.22.6: SideBolsterSupportRight
• 2.1.23: Tilt
• 2.2: PassengerSide
• 2.2.1: Airbag
• 2.2.1.1: IsDeployed
• 2.2.1.2: IsEnabled
• 2.2.2: Headrest
• 2.2.2.1: Angle
• 2.2.2.2: Height
• 2.2.2.3: IsBackwardSwitchEngaged
• 2.2.2.4: IsDownSwitchEngaged
• 2.2.2.5: IsForwardSwitchEngaged
• 2.2.2.6: IsUpSwitchEngaged
• 2.2.3: IsBackwardSwitchEngaged
• 2.2.4: IsCoolerSwitchEngaged
• 2.2.5: IsDecreaseMassageLevelSwitchEngaged
• 2.2.6: IsDownSwitchEngaged
• 2.2.7: IsForwardSwitchEngaged
• 2.2.8: IsIncreaseMassageLevelSwitchEngaged
• 2.2.9: IsTiltBackwardSwitchEngaged
• 2.2.10: IsTiltForwardSwitchEngaged
• 2.2.11: IsUpSwitchEngaged
• 2.2.12: IsWarmerSwitchEngaged
• 2.2.13: NeckScarf
• 2.2.13.1: FanSpeed
• 2.2.13.2: HeatingCooling
• 2.2.14: Seating
• 2.2.14.1: HeatingCooling
• 2.2.14.2: IsBackwardSwitchEngaged
• 2.2.14.3: IsForwardSwitchEngaged
• 2.2.14.4: Length
• 2.2.14.5: SideBolsterSupportLeft
• 2.2.14.6: SideBolsterSupportRight
• 2.2.15: Backrest
• 2.2.15.1: BottomLumbarSupport
• 2.2.15.2: IsLessLumbarSupportSwitchEngaged
• 2.2.15.3: IsLessSideBolsterSupportSwitchEngaged
• 2.2.15.4: IsLumbarDownSwitchEngaged
• 2.2.15.5: IsLumbarUpSwitchEngaged
• 2.2.15.6: IsMoreLumbarSupportSwitchEngaged
• 2.2.15.7: IsMoreSideBolsterSupportSwitchEngaged
• 2.2.15.8: IsReclineBackwardSwitchEngaged
• 2.2.15.9: IsReclineForwardSwitchEngaged
• 2.2.15.10: LumbarHeight
• 2.2.15.11: MidLumbarSupport
• 2.2.15.12: SideBolsterSupport
• 2.2.15.13: SideBolsterSupportLeft
• 2.2.15.14: SideBolsterSupportRight
• 2.2.15.15: TopLumbarSupport
• 2.2.15.16: UpperShoulderSupport
• 2.2.15.17: HeatingCooling
• 2.2.15.18: LumbarSupport
• 2.2.15.19: Recline
• 2.2.16: HeatingCooling
• 2.2.17: Height
• 2.2.18: IsBelted
• 2.2.19: Massage
• 2.2.19.1: IsAvailable
• 2.2.19.2: Level
• 2.2.19.3: Status
• 2.2.19.4: SupportedTypes
• 2.2.19.5: TypeActive
• 2.2.20: OccupancyStatus
• 2.2.21: Position
• 2.2.22: SeatBeltHeight
• 2.2.23: Tilt
• 2.3: DriverSide
• 2.3.1: Airbag
• 2.3.1.1: IsDeployed
• 2.3.1.2: IsEnabled
• 2.3.2: IsBackwardSwitchEngaged
• 2.3.3: IsCoolerSwitchEngaged
• 2.3.4: IsDecreaseMassageLevelSwitchEngaged
• 2.3.5: IsDownSwitchEngaged
• 2.3.6: IsForwardSwitchEngaged
• 2.3.7: IsIncreaseMassageLevelSwitchEngaged
• 2.3.8: IsTiltBackwardSwitchEngaged
• 2.3.9: IsTiltForwardSwitchEngaged
• 2.3.10: IsUpSwitchEngaged
• 2.3.11: IsWarmerSwitchEngaged
• 2.3.12: NeckScarf
• 2.3.12.1: FanSpeed
• 2.3.12.2: HeatingCooling
• 2.3.13: Backrest
• 2.3.13.1: BottomLumbarSupport
• 2.3.13.2: HeatingCooling
• 2.3.13.3: IsLessLumbarSupportSwitchEngaged
• 2.3.13.4: IsLessSideBolsterSupportSwitchEngaged
• 2.3.13.5: IsLumbarDownSwitchEngaged
• 2.3.13.6: IsLumbarUpSwitchEngaged
• 2.3.13.7: IsMoreLumbarSupportSwitchEngaged
• 2.3.13.8: IsMoreSideBolsterSupportSwitchEngaged
• 2.3.13.9: IsReclineBackwardSwitchEngaged
• 2.3.13.10: IsReclineForwardSwitchEngaged
• 2.3.13.11: LumbarHeight
• 2.3.13.12: LumbarSupport
• 2.3.13.13: MidLumbarSupport
• 2.3.13.14: Recline
• 2.3.13.15: SideBolsterSupport
• 2.3.13.16: SideBolsterSupportLeft
• 2.3.13.17: SideBolsterSupportRight
• 2.3.13.18: TopLumbarSupport
• 2.3.13.19: UpperShoulderSupport
• 2.3.14: Headrest
• 2.3.14.1: Angle
• 2.3.14.2: Height
• 2.3.14.3: IsBackwardSwitchEngaged
• 2.3.14.4: IsDownSwitchEngaged
• 2.3.14.5: IsForwardSwitchEngaged
• 2.3.14.6: IsUpSwitchEngaged
• 2.3.15: HeatingCooling
• 2.3.16: Height
• 2.3.17: IsBelted
• 2.3.18: Massage
• 2.3.18.1: IsAvailable
• 2.3.18.2: Level
• 2.3.18.3: Status
• 2.3.18.4: SupportedTypes
• 2.3.18.5: TypeActive
• 2.3.19: OccupancyStatus
• 2.3.20: Position
• 2.3.21: SeatBeltHeight
• 2.3.22: Seating
• 2.3.22.1: HeatingCooling
• 2.3.22.2: IsBackwardSwitchEngaged
• 2.3.22.3: IsForwardSwitchEngaged
• 2.3.22.4: Length
• 2.3.22.5: SideBolsterSupportLeft
• 2.3.22.6: SideBolsterSupportRight
• 2.3.23: Tilt

1 - Row2

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.Cabin.Seat.Row2 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2 is 8c3aaf015ef8595cb45d9461a9c1195f

Children

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

• Vehicle.Cabin.Seat.Row2.DriverSide (All seats.)
• Vehicle.Cabin.Seat.Row2.Middle (All seats.)
• Vehicle.Cabin.Seat.Row2.PassengerSide (All seats.)

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

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.Cabin.Seat.Row2.Middle is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle is a27650921e1e5ee0bd56562364c7dd6f

Children

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

• Vehicle.Cabin.Seat.Row2.Middle.Airbag (Airbag signals.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest (Describes signals related to the backrest of the seat.)
• Vehicle.Cabin.Seat.Row2.Middle.Headrest (Headrest settings.)
• Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling (Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.)
• Vehicle.Cabin.Seat.Row2.Middle.Height (Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported.)
• Vehicle.Cabin.Seat.Row2.Middle.IsBackwardSwitchEngaged (Seat backward switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsBelted (Is the belt engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsCoolerSwitchEngaged (Cooler switch for Seat heater.)
• Vehicle.Cabin.Seat.Row2.Middle.IsDecreaseMassageLevelSwitchEngaged (Decrease massage level switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsDownSwitchEngaged (Seat down switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsForwardSwitchEngaged (Seat forward switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsIncreaseMassageLevelSwitchEngaged (Increase massage level switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsTiltBackwardSwitchEngaged (Tilt backward switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsTiltForwardSwitchEngaged (Tilt forward switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsUpSwitchEngaged (Seat up switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.IsWarmerSwitchEngaged (Warmer switch for Seat heater.)
• Vehicle.Cabin.Seat.Row2.Middle.Massage (Massage related information for the seat.)
• Vehicle.Cabin.Seat.Row2.Middle.NeckScarf (NeckScarf settings.)
• Vehicle.Cabin.Seat.Row2.Middle.OccupancyStatus (Occupancy status of the seat.)
• Vehicle.Cabin.Seat.Row2.Middle.Position (Seat position on vehicle x-axis. Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported.)
• Vehicle.Cabin.Seat.Row2.Middle.SeatBeltHeight (Seat belt position on vehicle z-axis. Position is relative within available movable range of the seat belt. 0 = Lowermost position supported.)
• Vehicle.Cabin.Seat.Row2.Middle.Seating (Describes signals related to the seat bottom of the seat.)
• Vehicle.Cabin.Seat.Row2.Middle.Tilt (Tilting of seat (seating and backrest) relative to vehicle x-axis. 0 = seat bottom is flat, seat bottom and vehicle x-axis are parallel. Positive degrees = seat tilted backwards, seat x-axis tilted upward, seat z-axis is tilted backward.)

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

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.Cabin.Seat.Row2.Middle.Airbag is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Airbag is aa6d77c09158565787a2e418a1c9ea98

Children

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

• Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed (Airbag deployment status. True = Airbag deployed. False = Airbag not deployed.)
• Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsEnabled (Airbag enabled status. True = Airbag enabled. False = Airbag not enabled.)

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.1.1 - IsDeployed

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed false
[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 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.Cabin.Seat.Row2.Middle.Airbag.IsDeployed is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed is cc06da5cab1e5b2e91d180c93c9e8eab

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.1.1.2 - IsEnabled

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsEnabled
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsEnabled false
[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 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.Cabin.Seat.Row2.Middle.Airbag.IsEnabled is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsEnabled is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsEnabled is aa6f761c9c0d57b4bbc63453e70521a1

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.1.2 - Backrest

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.Cabin.Seat.Row2.Middle.Backrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest is 4f54b32f4c85549b88acbe7cd19dcb20

Children

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

• Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport (Bottom lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling (Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged (Is switch for less lumbar support engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged (Is switch for less side bolster support engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged (Lumbar down switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged (Lumbar up switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged (Is switch for more lumbar support engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged (Is switch for more side bolster support engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged (Backrest recline backward switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged (Backrest recline forward switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight (Height of lumbar support. Position is relative within available movable range of the lumbar support. 0 = Lowermost position supported.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport (Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport (Mid lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.Recline (Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport (Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft (Side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight (Side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport (Top lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
• Vehicle.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport (Upper shoulder support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)

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.2.1 - BottomLumbarSupport

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport 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.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport is ca2fbaec7e4b5093a578380fd516217b

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.1.2.2 - HeatingCooling

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling is 03c3ba604f2b5ad1ad189138edd3ebbe

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.1.2.3 - IsLessLumbarSupportSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged is be65c02b330951ec901345de835154d7

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.1.2.4 - IsLessSideBolsterSupportSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged is ba58711dca4550bea968ef9ae5ce366a

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.1.2.5 - IsLumbarDownSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged is 73afa434e02c54fb830e2b714b1a4390

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.1.2.6 - IsLumbarUpSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged is 31901845ff865c888c8414039a2bccb7

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.1.2.7 - IsMoreLumbarSupportSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged is b482182275465841bca69b86f9a1e537

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.1.2.8 - IsMoreSideBolsterSupportSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged is dba443f0645e5a50b24bb10535157d8d

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.1.2.9 - IsReclineBackwardSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged is 108b15fceca25b4489a501641a60cd4b

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.1.2.10 - IsReclineForwardSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged is e485a9ecb2895869908c8aadd1e663bf

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.1.2.11 - LumbarHeight

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight 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 uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight is 287dc2e74c7f51e8b1a80e0d2082de5d

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.1.2.12 - LumbarSupport

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport 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.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport is c3e749661b695fec9bb47c945054d434

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.1.2.13 - MidLumbarSupport

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport 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.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport is 1a5050bd0d00587e93f9218656157bf3

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.1.2.14 - Recline

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.Recline
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.Recline 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.Cabin.Seat.Row2.Middle.Backrest.Recline is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.Recline is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.Recline is d24b223dcbb0534389c6c506126497e7

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.1.2.15 - SideBolsterSupport

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport 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.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport is 056d829d3b4754b6bd58eca3a5251807

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.1.2.16 - SideBolsterSupportLeft

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft 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.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft is 7c99b57e9de05252a939c2187461a7b9

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.1.2.17 - SideBolsterSupportRight

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight 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.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight is bd306fb69af95f1ab0a9ccf42c374d26

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.1.2.18 - TopLumbarSupport

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport 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.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport is 36611986baa45f24abf784798582e04c

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.1.2.19 - UpperShoulderSupport

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport 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.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport is 1e38aa6c85365114abb3baf78bcc9bf5

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.1.3 - Headrest

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.Cabin.Seat.Row2.Middle.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest is eb9a3ea623445fbab28e98ace9716f48

Children

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

• Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle (Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.)
• Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height (Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.)
• Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged (Headrest backward switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged (Headrest down switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged (Headrest forward switch engaged.)
• Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged (Headrest up switch engaged.)

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.3.1 - Angle

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle 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.Cabin.Seat.Row2.Middle.Headrest.Angle is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle is 41f7b225f1485deaba50f489d58656da

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.1.3.2 - Height

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height 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 uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height is 987682ae6e7a539897bab4d96458fe15

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.1.3.3 - IsBackwardSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged is be8984cd1ec55f3087dd41290be76ae1

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.1.3.4 - IsDownSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged is b1ece8266bf55bc394f96e08afc80f99

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.1.3.5 - IsForwardSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged is bce17ef4aabf5d8e9b444b268b4dc904

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.1.3.6 - IsUpSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged false
[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 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.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged is ee8aa5267d5b58cf8f71c4178b83f078

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.1.4 - HeatingCooling

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling is 1b0129f265225acba5f18aef705b9c54

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.1.5 - Height

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.Height 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 uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Middle.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Height is 5e2a819627075c7ea1a6fb2c6b7e550d

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.1.6 - IsBackwardSwitchEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Middle.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Middle.IsBackwardSwitchEngaged false
[set]  OK