Cabin

• 1: Convertible
• 1.1: Status
• 2: DriverPosition
• 3: PowerOptimizeLevel
• 4: SeatPosCount
• 5: SeatRowCount
• 6: DoorCount
• 7: Seat
• 7.1: Row2
• 7.1.1: Pos3
• 7.1.1.1: Airbag
• 7.1.1.1.1: IsDeployed
• 7.1.1.2: Headrest
• 7.1.1.2.1: Angle
• 7.1.1.2.2: Height
• 7.1.1.3: Switch
• 7.1.1.3.1: Headrest
• 7.1.1.3.1.1: IsBackwardEngaged
• 7.1.1.3.1.2: IsDownEngaged
• 7.1.1.3.1.3: IsForwardEngaged
• 7.1.1.3.1.4: IsUpEngaged
• 7.1.1.3.2: Massage
• 7.1.1.3.2.1: IsDecreaseEngaged
• 7.1.1.3.2.2: IsIncreaseEngaged
• 7.1.1.3.3: Backrest
• 7.1.1.3.3.1: IsReclineBackwardEngaged
• 7.1.1.3.3.2: IsReclineForwardEngaged
• 7.1.1.3.3.3: Lumbar
• 7.1.1.3.3.3.1: IsDownEngaged
• 7.1.1.3.3.3.2: IsLessSupportEngaged
• 7.1.1.3.3.3.3: IsMoreSupportEngaged
• 7.1.1.3.3.3.4: IsUpEngaged
• 7.1.1.3.3.4: SideBolster
• 7.1.1.3.3.4.1: IsLessSupportEngaged
• 7.1.1.3.3.4.2: IsMoreSupportEngaged
• 7.1.1.3.4: IsBackwardEngaged
• 7.1.1.3.5: IsCoolerEngaged
• 7.1.1.3.6: IsDownEngaged
• 7.1.1.3.7: IsForwardEngaged
• 7.1.1.3.8: IsTiltBackwardEngaged
• 7.1.1.3.9: IsTiltForwardEngaged
• 7.1.1.3.10: IsUpEngaged
• 7.1.1.3.11: IsWarmerEngaged
• 7.1.1.3.12: Seating
• 7.1.1.3.12.1: IsBackwardEngaged
• 7.1.1.3.12.2: IsForwardEngaged
• 7.1.1.4: Backrest
• 7.1.1.4.1: Lumbar
• 7.1.1.4.1.1: Height
• 7.1.1.4.1.2: Support
• 7.1.1.4.2: Recline
• 7.1.1.4.3: SideBolster
• 7.1.1.4.3.1: Support
• 7.1.1.5: Heating
• 7.1.1.6: Height
• 7.1.1.7: IsBelted
• 7.1.1.8: IsOccupied
• 7.1.1.9: Massage
• 7.1.1.10: Occupant
• 7.1.1.10.1: Identifier
• 7.1.1.10.1.1: Issuer
• 7.1.1.10.1.2: Subject
• 7.1.1.11: Position
• 7.1.1.12: Seating
• 7.1.1.12.1: Length
• 7.1.1.13: Tilt
• 7.1.2: Pos2
• 7.1.2.1: Airbag
• 7.1.2.1.1: IsDeployed
• 7.1.2.2: Headrest
• 7.1.2.2.1: Angle
• 7.1.2.2.2: Height
• 7.1.2.3: Seating
• 7.1.2.3.1: Length
• 7.1.2.4: Switch
• 7.1.2.4.1: Headrest
• 7.1.2.4.1.1: IsBackwardEngaged
• 7.1.2.4.1.2: IsDownEngaged
• 7.1.2.4.1.3: IsForwardEngaged
• 7.1.2.4.1.4: IsUpEngaged
• 7.1.2.4.2: Massage
• 7.1.2.4.2.1: IsDecreaseEngaged
• 7.1.2.4.2.2: IsIncreaseEngaged
• 7.1.2.4.3: Backrest
• 7.1.2.4.3.1: IsReclineBackwardEngaged
• 7.1.2.4.3.2: IsReclineForwardEngaged
• 7.1.2.4.3.3: Lumbar
• 7.1.2.4.3.3.1: IsDownEngaged
• 7.1.2.4.3.3.2: IsLessSupportEngaged
• 7.1.2.4.3.3.3: IsMoreSupportEngaged
• 7.1.2.4.3.3.4: IsUpEngaged
• 7.1.2.4.3.4: SideBolster
• 7.1.2.4.3.4.1: IsLessSupportEngaged
• 7.1.2.4.3.4.2: IsMoreSupportEngaged
• 7.1.2.4.4: IsBackwardEngaged
• 7.1.2.4.5: IsCoolerEngaged
• 7.1.2.4.6: IsDownEngaged
• 7.1.2.4.7: IsForwardEngaged
• 7.1.2.4.8: IsTiltBackwardEngaged
• 7.1.2.4.9: IsTiltForwardEngaged
• 7.1.2.4.10: IsUpEngaged
• 7.1.2.4.11: IsWarmerEngaged
• 7.1.2.4.12: Seating
• 7.1.2.4.12.1: IsBackwardEngaged
• 7.1.2.4.12.2: IsForwardEngaged
• 7.1.2.5: Backrest
• 7.1.2.5.1: SideBolster
• 7.1.2.5.1.1: Support
• 7.1.2.5.2: Lumbar
• 7.1.2.5.2.1: Height
• 7.1.2.5.2.2: Support
• 7.1.2.5.3: Recline
• 7.1.2.6: Heating
• 7.1.2.7: Height
• 7.1.2.8: IsBelted
• 7.1.2.9: IsOccupied
• 7.1.2.10: Massage
• 7.1.2.11: Occupant
• 7.1.2.11.1: Identifier
• 7.1.2.11.1.1: Issuer
• 7.1.2.11.1.2: Subject
• 7.1.2.12: Position
• 7.1.2.13: Tilt
• 7.1.3: Pos1
• 7.1.3.1: Airbag
• 7.1.3.1.1: IsDeployed
• 7.1.3.2: Backrest
• 7.1.3.2.1: Lumbar
• 7.1.3.2.1.1: Height
• 7.1.3.2.1.2: Support
• 7.1.3.2.2: Recline
• 7.1.3.2.3: SideBolster
• 7.1.3.2.3.1: Support
• 7.1.3.3: Headrest
• 7.1.3.3.1: Angle
• 7.1.3.3.2: Height
• 7.1.3.4: Heating
• 7.1.3.5: Height
• 7.1.3.6: IsBelted
• 7.1.3.7: IsOccupied
• 7.1.3.8: Massage
• 7.1.3.9: Occupant
• 7.1.3.9.1: Identifier
• 7.1.3.9.1.1: Issuer
• 7.1.3.9.1.2: Subject
• 7.1.3.10: Position
• 7.1.3.11: Seating
• 7.1.3.11.1: Length
• 7.1.3.12: Switch
• 7.1.3.12.1: Backrest
• 7.1.3.12.1.1: IsReclineBackwardEngaged
• 7.1.3.12.1.2: IsReclineForwardEngaged
• 7.1.3.12.1.3: Lumbar
• 7.1.3.12.1.3.1: IsDownEngaged
• 7.1.3.12.1.3.2: IsLessSupportEngaged
• 7.1.3.12.1.3.3: IsMoreSupportEngaged
• 7.1.3.12.1.3.4: IsUpEngaged
• 7.1.3.12.1.4: SideBolster
• 7.1.3.12.1.4.1: IsLessSupportEngaged
• 7.1.3.12.1.4.2: IsMoreSupportEngaged
• 7.1.3.12.2: Headrest
• 7.1.3.12.2.1: IsBackwardEngaged
• 7.1.3.12.2.2: IsDownEngaged
• 7.1.3.12.2.3: IsForwardEngaged
• 7.1.3.12.2.4: IsUpEngaged
• 7.1.3.12.3: IsDownEngaged
• 7.1.3.12.4: IsTiltBackwardEngaged
• 7.1.3.12.5: IsTiltForwardEngaged
• 7.1.3.12.6: IsUpEngaged
• 7.1.3.12.7: Massage
• 7.1.3.12.7.1: IsDecreaseEngaged
• 7.1.3.12.7.2: IsIncreaseEngaged
• 7.1.3.12.8: Seating
• 7.1.3.12.8.1: IsBackwardEngaged
• 7.1.3.12.8.2: IsForwardEngaged
• 7.1.3.12.9: IsBackwardEngaged
• 7.1.3.12.10: IsCoolerEngaged
• 7.1.3.12.11: IsForwardEngaged
• 7.1.3.12.12: IsWarmerEngaged
• 7.1.3.13: Tilt
• 7.2: Row1
• 7.2.1: Pos3
• 7.2.1.1: Switch
• 7.2.1.1.1: Backrest
• 7.2.1.1.1.1: IsReclineBackwardEngaged
• 7.2.1.1.1.2: IsReclineForwardEngaged
• 7.2.1.1.1.3: Lumbar
• 7.2.1.1.1.3.1: IsDownEngaged
• 7.2.1.1.1.3.2: IsLessSupportEngaged
• 7.2.1.1.1.3.3: IsMoreSupportEngaged
• 7.2.1.1.1.3.4: IsUpEngaged
• 7.2.1.1.1.4: SideBolster
• 7.2.1.1.1.4.1: IsLessSupportEngaged
• 7.2.1.1.1.4.2: IsMoreSupportEngaged
• 7.2.1.1.2: Headrest
• 7.2.1.1.2.1: IsBackwardEngaged
• 7.2.1.1.2.2: IsDownEngaged
• 7.2.1.1.2.3: IsForwardEngaged
• 7.2.1.1.2.4: IsUpEngaged
• 7.2.1.1.3: IsBackwardEngaged
• 7.2.1.1.4: IsCoolerEngaged
• 7.2.1.1.5: IsDownEngaged
• 7.2.1.1.6: IsForwardEngaged
• 7.2.1.1.7: IsTiltBackwardEngaged
• 7.2.1.1.8: IsTiltForwardEngaged
• 7.2.1.1.9: IsUpEngaged
• 7.2.1.1.10: IsWarmerEngaged
• 7.2.1.1.11: Massage
• 7.2.1.1.11.1: IsDecreaseEngaged
• 7.2.1.1.11.2: IsIncreaseEngaged
• 7.2.1.1.12: Seating
• 7.2.1.1.12.1: IsBackwardEngaged
• 7.2.1.1.12.2: IsForwardEngaged
• 7.2.1.2: Airbag
• 7.2.1.2.1: IsDeployed
• 7.2.1.3: Backrest
• 7.2.1.3.1: Lumbar
• 7.2.1.3.1.1: Height
• 7.2.1.3.1.2: Support
• 7.2.1.3.2: Recline
• 7.2.1.3.3: SideBolster
• 7.2.1.3.3.1: Support
• 7.2.1.4: Headrest
• 7.2.1.4.1: Angle
• 7.2.1.4.2: Height
• 7.2.1.5: Heating
• 7.2.1.6: Height
• 7.2.1.7: IsBelted
• 7.2.1.8: IsOccupied
• 7.2.1.9: Massage
• 7.2.1.10: Occupant
• 7.2.1.10.1: Identifier
• 7.2.1.10.1.1: Issuer
• 7.2.1.10.1.2: Subject
• 7.2.1.11: Position
• 7.2.1.12: Seating
• 7.2.1.12.1: Length
• 7.2.1.13: Tilt
• 7.2.2: Pos2
• 7.2.2.1: Airbag
• 7.2.2.1.1: IsDeployed
• 7.2.2.2: Headrest
• 7.2.2.2.1: Angle
• 7.2.2.2.2: Height
• 7.2.2.3: Seating
• 7.2.2.3.1: Length
• 7.2.2.4: Switch
• 7.2.2.4.1: Massage
• 7.2.2.4.1.1: IsDecreaseEngaged
• 7.2.2.4.1.2: IsIncreaseEngaged
• 7.2.2.4.2: Backrest
• 7.2.2.4.2.1: IsReclineBackwardEngaged
• 7.2.2.4.2.2: IsReclineForwardEngaged
• 7.2.2.4.2.3: Lumbar
• 7.2.2.4.2.3.1: IsDownEngaged
• 7.2.2.4.2.3.2: IsLessSupportEngaged
• 7.2.2.4.2.3.3: IsMoreSupportEngaged
• 7.2.2.4.2.3.4: IsUpEngaged
• 7.2.2.4.2.4: SideBolster
• 7.2.2.4.2.4.1: IsLessSupportEngaged
• 7.2.2.4.2.4.2: IsMoreSupportEngaged
• 7.2.2.4.3: Headrest
• 7.2.2.4.3.1: IsBackwardEngaged
• 7.2.2.4.3.2: IsDownEngaged
• 7.2.2.4.3.3: IsForwardEngaged
• 7.2.2.4.3.4: IsUpEngaged
• 7.2.2.4.4: IsBackwardEngaged
• 7.2.2.4.5: IsCoolerEngaged
• 7.2.2.4.6: IsDownEngaged
• 7.2.2.4.7: IsForwardEngaged
• 7.2.2.4.8: IsTiltBackwardEngaged
• 7.2.2.4.9: IsTiltForwardEngaged
• 7.2.2.4.10: IsUpEngaged
• 7.2.2.4.11: IsWarmerEngaged
• 7.2.2.4.12: Seating
• 7.2.2.4.12.1: IsBackwardEngaged
• 7.2.2.4.12.2: IsForwardEngaged
• 7.2.2.5: Backrest
• 7.2.2.5.1: SideBolster
• 7.2.2.5.1.1: Support
• 7.2.2.5.2: Lumbar
• 7.2.2.5.2.1: Height
• 7.2.2.5.2.2: Support
• 7.2.2.5.3: Recline
• 7.2.2.6: Heating
• 7.2.2.7: Height
• 7.2.2.8: IsBelted
• 7.2.2.9: IsOccupied
• 7.2.2.10: Massage
• 7.2.2.11: Occupant
• 7.2.2.11.1: Identifier
• 7.2.2.11.1.1: Issuer
• 7.2.2.11.1.2: Subject
• 7.2.2.12: Position
• 7.2.2.13: Tilt
• 7.2.3: Pos1
• 7.2.3.1: Airbag
• 7.2.3.1.1: IsDeployed
• 7.2.3.2: Backrest
• 7.2.3.2.1: Lumbar
• 7.2.3.2.1.1: Height
• 7.2.3.2.1.2: Support
• 7.2.3.2.2: Recline
• 7.2.3.2.3: SideBolster
• 7.2.3.2.3.1: Support
• 7.2.3.3: Headrest
• 7.2.3.3.1: Angle
• 7.2.3.3.2: Height
• 7.2.3.4: Heating
• 7.2.3.5: Height
• 7.2.3.6: IsBelted
• 7.2.3.7: Massage
• 7.2.3.8: Position
• 7.2.3.9: Seating
• 7.2.3.9.1: Length
• 7.2.3.10: Switch
• 7.2.3.10.1: Headrest
• 7.2.3.10.1.1: IsBackwardEngaged
• 7.2.3.10.1.2: IsDownEngaged
• 7.2.3.10.1.3: IsForwardEngaged
• 7.2.3.10.1.4: IsUpEngaged
• 7.2.3.10.2: Massage
• 7.2.3.10.2.1: IsDecreaseEngaged
• 7.2.3.10.2.2: IsIncreaseEngaged
• 7.2.3.10.3: Seating
• 7.2.3.10.3.1: IsBackwardEngaged
• 7.2.3.10.3.2: IsForwardEngaged
• 7.2.3.10.4: Backrest
• 7.2.3.10.4.1: SideBolster
• 7.2.3.10.4.1.1: IsLessSupportEngaged
• 7.2.3.10.4.1.2: IsMoreSupportEngaged
• 7.2.3.10.4.2: IsReclineBackwardEngaged
• 7.2.3.10.4.3: IsReclineForwardEngaged
• 7.2.3.10.4.4: Lumbar
• 7.2.3.10.4.4.1: IsDownEngaged
• 7.2.3.10.4.4.2: IsLessSupportEngaged
• 7.2.3.10.4.4.3: IsMoreSupportEngaged
• 7.2.3.10.4.4.4: IsUpEngaged
• 7.2.3.10.5: IsBackwardEngaged
• 7.2.3.10.6: IsCoolerEngaged
• 7.2.3.10.7: IsDownEngaged
• 7.2.3.10.8: IsForwardEngaged
• 7.2.3.10.9: IsTiltBackwardEngaged
• 7.2.3.10.10: IsTiltForwardEngaged
• 7.2.3.10.11: IsUpEngaged
• 7.2.3.10.12: IsWarmerEngaged
• 7.2.3.11: Tilt
• 7.2.3.12: IsOccupied
• 7.2.3.13: Occupant
• 7.2.3.13.1: Identifier
• 7.2.3.13.1.1: Issuer
• 7.2.3.13.1.2: Subject
• 8: Door
• 8.1: Row2
• 8.1.1: Right
• 8.1.1.1: IsChildLockActive
• 8.1.1.2: IsLocked
• 8.1.1.3: IsOpen
• 8.1.1.4: Shade
• 8.1.1.4.1: Position
• 8.1.1.4.2: Switch
• 8.1.1.5: Window
• 8.1.1.5.1: IsChildLockEngaged
• 8.1.1.5.2: IsOpen
• 8.1.1.5.3: Position
• 8.1.1.5.4: Switch
• 8.1.2: Left
• 8.1.2.1: IsChildLockActive
• 8.1.2.2: Shade
• 8.1.2.2.1: Position
• 8.1.2.2.2: Switch
• 8.1.2.3: IsLocked
• 8.1.2.4: IsOpen
• 8.1.2.5: Window
• 8.1.2.5.1: IsChildLockEngaged
• 8.1.2.5.2: Switch
• 8.1.2.5.3: IsOpen
• 8.1.2.5.4: Position
• 8.2: Row1
• 8.2.1: Left
• 8.2.1.1: IsChildLockActive
• 8.2.1.2: IsLocked
• 8.2.1.3: IsOpen
• 8.2.1.4: Shade
• 8.2.1.4.1: Position
• 8.2.1.4.2: Switch
• 8.2.1.5: Window
• 8.2.1.5.1: IsChildLockEngaged
• 8.2.1.5.2: IsOpen
• 8.2.1.5.3: Position
• 8.2.1.5.4: Switch
• 8.2.2: Right
• 8.2.2.1: IsChildLockActive
• 8.2.2.2: IsLocked
• 8.2.2.3: IsOpen
• 8.2.2.4: Shade
• 8.2.2.4.1: Position
• 8.2.2.4.2: Switch
• 8.2.2.5: Window
• 8.2.2.5.1: IsChildLockEngaged
• 8.2.2.5.2: IsOpen
• 8.2.2.5.3: Position
• 8.2.2.5.4: Switch
• 9: Lights
• 9.1: AmbientLight
• 9.2: IsDomeOn
• 9.3: IsGloveBoxOn
• 9.4: IsTrunkOn
• 9.5: LightIntensity
• 9.6: Spotlight
• 9.6.1: Row1
• 9.6.1.1: IsLeftOn
• 9.6.1.2: IsRightOn
• 9.6.1.3: IsSharedOn
• 9.6.2: Row2
• 9.6.2.1: IsLeftOn
• 9.6.2.2: IsRightOn
• 9.6.2.3: IsSharedOn
• 9.6.3: Row3
• 9.6.3.1: IsLeftOn
• 9.6.3.2: IsRightOn
• 9.6.3.3: IsSharedOn
• 9.6.4: Row4
• 9.6.4.1: IsLeftOn
• 9.6.4.2: IsRightOn
• 9.6.4.3: IsSharedOn
• 10: RearviewMirror
• 10.1: DimmingLevel
• 11: Sunroof
• 11.1: Position
• 11.2: Shade
• 11.2.1: Position
• 11.2.2: Switch
• 11.3: Switch
• 12: Infotainment
• 12.1: HMI
• 12.1.1: Brightness
• 12.1.2: CurrentLanguage
• 12.1.3: DateFormat
• 12.1.4: DayNightMode
• 12.1.5: DistanceUnit
• 12.1.6: EVEconomyUnits
• 12.1.7: FuelEconomyUnits
• 12.1.8: FuelVolumeUnit
• 12.1.9: TemperatureUnit
• 12.1.10: TimeFormat
• 12.1.11: TirePressureUnit
• 12.2: Navigation
• 12.2.1: DestinationSet
• 12.2.1.1: Latitude
• 12.2.1.2: Longitude
• 12.2.2: Mute
• 12.2.3: Volume
• 12.3: PowerOptimizeLevel
• 12.4: SmartphoneProjection
• 12.4.1: Active
• 12.4.2: Source
• 12.4.3: SupportedMode
• 12.5: Media
• 12.5.1: DeclinedURI
• 12.5.2: SelectedURI
• 12.5.3: Volume
• 12.5.4: Action
• 12.5.5: Played
• 12.5.5.1: PlaybackRate
• 12.5.5.2: Album
• 12.5.5.3: Artist
• 12.5.5.4: Source
• 12.5.5.5: Track
• 12.5.5.6: URI
• 13: HVAC
• 13.1: AmbientAirTemperature
• 13.2: IsAirConditioningActive
• 13.3: IsFrontDefrosterActive
• 13.4: IsRearDefrosterActive
• 13.5: IsRecirculationActive
• 13.6: PowerOptimizeLevel
• 13.7: Station
• 13.7.1: Row4
• 13.7.1.1: Left
• 13.7.1.1.1: AirDistribution
• 13.7.1.1.2: FanSpeed
• 13.7.1.1.3: Temperature
• 13.7.1.2: Right
• 13.7.1.2.1: AirDistribution
• 13.7.1.2.2: FanSpeed
• 13.7.1.2.3: Temperature
• 13.7.2: Row1
• 13.7.2.1: Left
• 13.7.2.1.1: AirDistribution
• 13.7.2.1.2: FanSpeed
• 13.7.2.1.3: Temperature
• 13.7.2.2: Right
• 13.7.2.2.1: AirDistribution
• 13.7.2.2.2: FanSpeed
• 13.7.2.2.3: Temperature
• 13.7.3: Row2
• 13.7.3.1: Left
• 13.7.3.1.1: AirDistribution
• 13.7.3.1.2: FanSpeed
• 13.7.3.1.3: Temperature
• 13.7.3.2: Right
• 13.7.3.2.1: AirDistribution
• 13.7.3.2.2: FanSpeed
• 13.7.3.2.3: Temperature
• 13.7.4: Row3
• 13.7.4.1: Left
• 13.7.4.1.1: AirDistribution
• 13.7.4.1.2: FanSpeed
• 13.7.4.1.3: Temperature
• 13.7.4.2: Right
• 13.7.4.2.1: AirDistribution
• 13.7.4.2.2: FanSpeed
• 13.7.4.2.3: Temperature
• 14: RearShade
• 14.1: Position
• 14.2: Switch

1 - Convertible

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.Convertible is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Convertible is 2aece85d39d6569e93cf842387a645d9

Children

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

• Vehicle.Cabin.Convertible.Status (Roof status on convertible vehicles.)

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

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.Convertible.Status
[get]  OK
Vehicle.Cabin.Convertible.Status: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Convertible.Status Foo
[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 string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Convertible.Status is a Sensor.

The vehicle signal Vehicle.Cabin.Convertible.Status is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Convertible.Status is c8812698198a56d7a1adcc8bbe87845f

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

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.DriverPosition
[get]  OK
Vehicle.Cabin.DriverPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.DriverPosition 1
[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.DriverPosition is an Attribute.

The vehicle signal Vehicle.Cabin.DriverPosition is a Signal.

UUID

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

The UUID for Vehicle.Cabin.DriverPosition is bca9ccd50358584d8d20865694b0d15f

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

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.PowerOptimizeLevel
[get]  OK
Vehicle.Cabin.PowerOptimizeLevel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.PowerOptimizeLevel 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.PowerOptimizeLevel is an Actuator.

The vehicle signal Vehicle.Cabin.PowerOptimizeLevel is a Signal.

UUID

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

The UUID for Vehicle.Cabin.PowerOptimizeLevel is 728b62b170055bd8b1530ec423dd5a9a

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

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.SeatPosCount
[get]  OK
Vehicle.Cabin.SeatPosCount: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.SeatPosCount [2, 3]
[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

Signal Information

The vehicle signal Vehicle.Cabin.SeatPosCount is an Attribute.

The vehicle signal Vehicle.Cabin.SeatPosCount is a Signal.

UUID

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

The UUID for Vehicle.Cabin.SeatPosCount is 8dd40ecd47ab51c79ed9c74ae4296d7e

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

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.SeatRowCount
[get]  OK
Vehicle.Cabin.SeatRowCount: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.SeatRowCount 2
[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.SeatRowCount is an Attribute.

The vehicle signal Vehicle.Cabin.SeatRowCount is a Signal.

UUID

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

The UUID for Vehicle.Cabin.SeatRowCount is 1002a7a4a954581b9cbc72fa438c5292

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

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.DoorCount
[get]  OK
Vehicle.Cabin.DoorCount: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.DoorCount 4
[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.DoorCount is an Attribute.

The vehicle signal Vehicle.Cabin.DoorCount is a Signal.

UUID

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

The UUID for Vehicle.Cabin.DoorCount is c293fbef75725c57a9918dd5a34055c4

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat is b0b253106b2851e3bb5c71ae3b09f09d

Children

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

• Vehicle.Cabin.Seat.Row1 (All seats.)
• Vehicle.Cabin.Seat.Row2 (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.

7.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.Pos1 (All seats.)
• Vehicle.Cabin.Seat.Row2.Pos2 (All seats.)
• Vehicle.Cabin.Seat.Row2.Pos3 (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.

7.1.1 - Pos3

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.Pos3 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3 is a40aa679981551e7a92b8438533911d4

Children

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

• Vehicle.Cabin.Seat.Row2.Pos3.Airbag (Airbag signals.)
• Vehicle.Cabin.Seat.Row2.Pos3.Backrest (Describes signals related to the backrest of the seat.)
• Vehicle.Cabin.Seat.Row2.Pos3.Headrest (Headrest settings.)
• Vehicle.Cabin.Seat.Row2.Pos3.Heating (Seat cooling / heating. 0 = off. -100 = max cold. +100 = max heat.)
• Vehicle.Cabin.Seat.Row2.Pos3.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.Pos3.IsBelted (Is the belt engaged.)
• Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied (Does the seat have a passenger in it.)
• Vehicle.Cabin.Seat.Row2.Pos3.Massage (Seat massage level. 0 = off. 100 = max massage.)
• Vehicle.Cabin.Seat.Row2.Pos3.Occupant (Occupant data.)
• Vehicle.Cabin.Seat.Row2.Pos3.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.Pos3.Seating (Describes signals related to the seat bottom of the seat.)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch (Seat switch signals)
• Vehicle.Cabin.Seat.Row2.Pos3.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.

7.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.Pos3.Airbag is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Airbag is e1d14ad055955eac914a47ee180a6e78

Children

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

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

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed is 6802243fcb3155b196cca3a825c12bcb

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.1.1.2 - 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.Pos3.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest is a14ecc5524645ca883e2838f666bce70

Children

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

• Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle (Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.)
• Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height (Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.)

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle is bf6f63ab87e453af965c90f0495ea972

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.1.1.2.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.Pos3.Headrest.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Pos3.Headrest.Height is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height is 2ae8b66df4045f46a96acbcdd6d2d452

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.1.1.3 - Switch

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.Pos3.Switch is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch is e0cfa7aceac75980b33075ceef5c9125

Children

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

• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest (Describes switches related to the backrest of the seat.)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest (Switches for SingleSeat.Headrest.)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged (Seat backward switch engaged (SingleSeat.Position).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged (Cooler switch for Seat heater (SingleSeat.Heating).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged (Seat down switch engaged (SingleSeat.Height).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged (Seat forward switch engaged (SingleSeat.Position).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged (Tilt backward switch engaged (SingleSeat.Tilt).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged (Tilt forward switch engaged (SingleSeat.Tilt).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged (Seat up switch engaged (SingleSeat.Height).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged (Warmer switch for Seat heater (SingleSeat.Heating).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage (Switches for SingleSeat.Massage.)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating (Describes switches related to the seating of the seat.)

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.1.3.1 - 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.Pos3.Switch.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest is dd4de742803250eaa1efeceaad116e1d

Children

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

• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged (Head rest backward switch engaged (SingleSeat.Headrest.Angle).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged (Head rest down switch engaged (SingleSeat.Headrest.Height).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged (Head rest forward switch engaged (SingleSeat.Headrest.Angle).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged (Head rest up switch engaged (SingleSeat.Headrest.Height).)

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.1.3.1.1 - IsBackwardEngaged

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.Pos3.Switch.Headrest.IsBackwardEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged 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.Pos3.Switch.Headrest.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged is 04e14e79404b5ff7ac9067841f81bbc9

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.1.1.3.1.2 - IsDownEngaged

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.Pos3.Switch.Headrest.IsDownEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged 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.Pos3.Switch.Headrest.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged is 61a58c7fa7ed5e08a17067193bb9c951

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.1.1.3.1.3 - IsForwardEngaged

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.Pos3.Switch.Headrest.IsForwardEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged 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.Pos3.Switch.Headrest.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged is 3c94aab710ff5e8f8a48fdbf6dc7b989

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.1.1.3.1.4 - IsUpEngaged

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.Pos3.Switch.Headrest.IsUpEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged 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.Pos3.Switch.Headrest.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged is e40c92c141f6562382f4f29d783cfa26

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.1.1.3.2 - Massage

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.Pos3.Switch.Massage is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage is ac2bb22d6acf56988582353a1453cbe3

Children

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

• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged (Decrease massage level switch engaged (SingleSeat.Massage).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged (Increase massage level switch engaged (SingleSeat.Massage).)

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.1.3.2.1 - IsDecreaseEngaged

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.Pos3.Switch.Massage.IsDecreaseEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged 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.Pos3.Switch.Massage.IsDecreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged is 7226bc97842452099d5484baad0af620

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.1.1.3.2.2 - IsIncreaseEngaged

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.Pos3.Switch.Massage.IsIncreaseEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged 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.Pos3.Switch.Massage.IsIncreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged is fb062e9f85fd568cbd774b36fbf5113f

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.1.1.3.3 - 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.Pos3.Switch.Backrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest is 583a22d4a1365db9bf386a96bcafd292

Children

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

• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged (Backrest recline backward switch engaged (SingleSeat.Backrest.Recline).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged (Backrest recline forward switch engaged (SingleSeat.Backrest.Recline).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar (Switches for SingleSeat.Backrest.Lumbar.)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster (Switches for SingleSeat.Backrest.SideBolster.)

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.1.3.3.1 - IsReclineBackwardEngaged

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.Pos3.Switch.Backrest.IsReclineBackwardEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged 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.Pos3.Switch.Backrest.IsReclineBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged is eed918c7f0b558a99bbe804582a31b64

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.1.1.3.3.2 - IsReclineForwardEngaged

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.Pos3.Switch.Backrest.IsReclineForwardEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged 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.Pos3.Switch.Backrest.IsReclineForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged is 0cc4f8336f0d585f93f4ab5c89e133d8

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.1.1.3.3.3 - Lumbar

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.Pos3.Switch.Backrest.Lumbar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar is 1d631b9c90a25a858a6caabe8ead1826

Children

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

• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged (Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged (Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged (Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged (Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.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.

7.1.1.3.3.3.1 - IsDownEngaged

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.Pos3.Switch.Backrest.Lumbar.IsDownEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged 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.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is dcd08d675e7e5f4eafe85311a3e40f1e

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.1.1.3.3.3.2 - IsLessSupportEngaged

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.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged 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.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is 866f9a7d358e5eb5985c9c675b4f7eb4

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.1.1.3.3.3.3 - IsMoreSupportEngaged

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.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged 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.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is cf9c077f2f4d5573a6022f5f08e807d3

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.1.1.3.3.3.4 - IsUpEngaged

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.Pos3.Switch.Backrest.Lumbar.IsUpEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged 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.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is f0fd5a54865452bcbf2939d8acd4273c

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.1.1.3.3.4 - SideBolster

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.Pos3.Switch.Backrest.SideBolster is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster is 79d8d65b4c1d54a4ab1306d56e839c49

Children

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

• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged (Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).)
• Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged (Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.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.

7.1.1.3.3.4.1 - IsLessSupportEngaged

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.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged 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.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is e99b4f4b07af511b9d86454eec1c483c

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.1.1.3.3.4.2 - IsMoreSupportEngaged

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.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged 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.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is 92341df5af725c8282f6f93644f1ec9f

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.1.1.3.4 - IsBackwardEngaged

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.Pos3.Switch.IsBackwardEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged 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.Pos3.Switch.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged is 267429a5f95d5f47ac47ec301755df32

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.1.1.3.5 - IsCoolerEngaged

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.Pos3.Switch.IsCoolerEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged 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.Pos3.Switch.IsCoolerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged is ffff3283b2cf5f7292e241ec2ee27e77

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.1.1.3.6 - IsDownEngaged

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.Pos3.Switch.IsDownEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged 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.Pos3.Switch.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged is 73d2e688696a507b826230d5b53c429f

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.1.1.3.7 - IsForwardEngaged

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.Pos3.Switch.IsForwardEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged 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.Pos3.Switch.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged is 397a8afd0dd1533b8899248596ae7566

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: