Vehicle

• 1: Connectivity
• 1.1: IsConnectivityAvailable
• 2: Exterior
• 2.1: AirTemperature
• 2.2: Humidity
• 2.3: LightIntensity
• 3: Service
• 3.1: DistanceToService
• 3.2: IsServiceDue
• 3.3: TimeToService
• 4: Driver
• 4.1: AttentiveProbability
• 4.2: DistractionLevel
• 4.3: FatigueLevel
• 4.4: HeartRate
• 4.5: IsEyesOnRoad
• 4.6: Identifier
• 4.6.1: Issuer
• 4.6.2: Subject
• 5: OBD
• 5.1: AbsoluteLoad
• 5.2: AcceleratorPositionD
• 5.3: AcceleratorPositionE
• 5.4: AcceleratorPositionF
• 5.5: AmbientAirTemperature
• 5.6: CommandedEquivalenceRatio
• 5.7: ControlModuleVoltage
• 5.8: DriveCycleStatus
• 5.8.1: DTCCount
• 5.8.2: IgnitionType
• 5.8.3: IsMILOn
• 5.9: EthanolPercent
• 5.10: EVAPVaporPressureAbsolute
• 5.11: EVAPVaporPressureAlternate
• 5.12: FuelInjectionTiming
• 5.13: FuelRailPressureAbsolute
• 5.14: FuelRate
• 5.15: FuelType
• 5.16: HybridBatteryRemaining
• 5.17: LongTermO2Trim1
• 5.18: LongTermO2Trim2
• 5.19: LongTermO2Trim3
• 5.20: LongTermO2Trim4
• 5.21: MaxMAF
• 5.22: OilTemperature
• 5.23: PidsC
• 5.24: RelativeAcceleratorPosition
• 5.25: RelativeThrottlePosition
• 5.26: RunTimeMIL
• 5.27: ShortTermO2Trim1
• 5.28: ShortTermO2Trim2
• 5.29: ShortTermO2Trim3
• 5.30: ShortTermO2Trim4
• 5.31: ThrottleActuator
• 5.32: ThrottlePositionB
• 5.33: ThrottlePositionC
• 5.34: TimeSinceDTCCleared
• 5.35: BarometricPressure
• 5.36: Catalyst
• 5.36.1: Bank1
• 5.36.1.1: Temperature1
• 5.36.1.2: Temperature2
• 5.36.2: Bank2
• 5.36.2.1: Temperature2
• 5.36.2.2: Temperature1
• 5.37: CommandedEGR
• 5.38: CommandedEVAP
• 5.39: DistanceSinceDTCClear
• 5.40: EGRError
• 5.41: EVAPVaporPressure
• 5.42: FuelLevel
• 5.43: WarmupsSinceDTCClear
• 5.44: DistanceWithMIL
• 5.45: FuelRailPressureDirect
• 5.46: FuelRailPressureVac
• 5.47: IsPTOActive
• 5.48: O2WR
• 5.48.1: Sensor4
• 5.48.1.1: Current
• 5.48.1.2: Lambda
• 5.48.1.3: Voltage
• 5.48.2: Sensor5
• 5.48.2.1: Current
• 5.48.2.2: Lambda
• 5.48.2.3: Voltage
• 5.48.3: Sensor6
• 5.48.3.1: Current
• 5.48.3.2: Lambda
• 5.48.3.3: Voltage
• 5.48.4: Sensor7
• 5.48.4.1: Current
• 5.48.4.2: Lambda
• 5.48.4.3: Voltage
• 5.48.5: Sensor8
• 5.48.5.1: Current
• 5.48.5.2: Lambda
• 5.48.5.3: Voltage
• 5.48.6: Sensor1
• 5.48.6.1: Current
• 5.48.6.2: Lambda
• 5.48.6.3: Voltage
• 5.48.7: Sensor2
• 5.48.7.1: Current
• 5.48.7.2: Lambda
• 5.48.7.3: Voltage
• 5.48.8: Sensor3
• 5.48.8.1: Current
• 5.48.8.2: Lambda
• 5.48.8.3: Voltage
• 5.49: OBDStandards
• 5.50: OxygenSensorsIn4Banks
• 5.51: PidsB
• 5.52: RunTime
• 5.53: AirStatus
• 5.54: CoolantTemperature
• 5.55: DTCList
• 5.56: EngineLoad
• 5.57: EngineSpeed
• 5.58: FreezeDTC
• 5.59: FuelPressure
• 5.60: FuelStatus
• 5.61: IntakeTemp
• 5.62: LongTermFuelTrim1
• 5.63: LongTermFuelTrim2
• 5.64: MAF
• 5.65: MAP
• 5.66: O2
• 5.66.1: Sensor4
• 5.66.1.1: ShortTermFuelTrim
• 5.66.1.2: Voltage
• 5.66.2: Sensor5
• 5.66.2.1: ShortTermFuelTrim
• 5.66.2.2: Voltage
• 5.66.3: Sensor6
• 5.66.3.1: ShortTermFuelTrim
• 5.66.3.2: Voltage
• 5.66.4: Sensor7
• 5.66.4.1: ShortTermFuelTrim
• 5.66.4.2: Voltage
• 5.66.5: Sensor8
• 5.66.5.1: ShortTermFuelTrim
• 5.66.5.2: Voltage
• 5.66.6: Sensor1
• 5.66.6.1: ShortTermFuelTrim
• 5.66.6.2: Voltage
• 5.66.7: Sensor2
• 5.66.7.1: ShortTermFuelTrim
• 5.66.7.2: Voltage
• 5.66.8: Sensor3
• 5.66.8.1: ShortTermFuelTrim
• 5.66.8.2: Voltage
• 5.67: OxygenSensorsIn2Banks
• 5.68: PidsA
• 5.69: ShortTermFuelTrim1
• 5.70: ShortTermFuelTrim2
• 5.71: Speed
• 5.72: Status
• 5.72.1: DTCCount
• 5.72.2: IgnitionType
• 5.72.3: IsMILOn
• 5.73: ThrottlePosition
• 5.74: TimingAdvance
• 6: Chassis
• 6.1: Accelerator
• 6.1.1: PedalPosition
• 6.2: AxleCount
• 6.3: Brake
• 6.3.1: IsDriverEmergencyBrakingDetected
• 6.3.2: PedalPosition
• 6.4: ParkingBrake
• 6.4.1: IsEngaged
• 6.5: SteeringWheel
• 6.5.1: Angle
• 6.5.2: Extension
• 6.5.3: Position
• 6.5.4: Tilt
• 6.6: Axle
• 6.6.1: Row1
• 6.6.1.1: SteeringAngle
• 6.6.1.2: TireAspectRatio
• 6.6.1.3: TireDiameter
• 6.6.1.4: TireWidth
• 6.6.1.5: Wheel
• 6.6.1.5.1: Left
• 6.6.1.5.1.1: Brake
• 6.6.1.5.1.1.1: FluidLevel
• 6.6.1.5.1.1.2: IsBrakesWorn
• 6.6.1.5.1.1.3: IsFluidLevelLow
• 6.6.1.5.1.1.4: PadWear
• 6.6.1.5.1.2: Speed
• 6.6.1.5.1.3: Tire
• 6.6.1.5.1.3.1: IsPressureLow
• 6.6.1.5.1.3.2: Pressure
• 6.6.1.5.1.3.3: Temperature
• 6.6.1.5.2: Right
• 6.6.1.5.2.1: Brake
• 6.6.1.5.2.1.1: FluidLevel
• 6.6.1.5.2.1.2: IsBrakesWorn
• 6.6.1.5.2.1.3: IsFluidLevelLow
• 6.6.1.5.2.1.4: PadWear
• 6.6.1.5.2.2: Speed
• 6.6.1.5.2.3: Tire
• 6.6.1.5.2.3.1: IsPressureLow
• 6.6.1.5.2.3.2: Pressure
• 6.6.1.5.2.3.3: Temperature
• 6.6.1.6: WheelCount
• 6.6.1.7: WheelDiameter
• 6.6.1.8: WheelWidth
• 6.6.2: Row2
• 6.6.2.1: SteeringAngle
• 6.6.2.2: TireAspectRatio
• 6.6.2.3: TireDiameter
• 6.6.2.4: TireWidth
• 6.6.2.5: Wheel
• 6.6.2.5.1: Right
• 6.6.2.5.1.1: Brake
• 6.6.2.5.1.1.1: FluidLevel
• 6.6.2.5.1.1.2: IsBrakesWorn
• 6.6.2.5.1.1.3: IsFluidLevelLow
• 6.6.2.5.1.1.4: PadWear
• 6.6.2.5.1.2: Speed
• 6.6.2.5.1.3: Tire
• 6.6.2.5.1.3.1: IsPressureLow
• 6.6.2.5.1.3.2: Pressure
• 6.6.2.5.1.3.3: Temperature
• 6.6.2.5.2: Left
• 6.6.2.5.2.1: Speed
• 6.6.2.5.2.2: Tire
• 6.6.2.5.2.2.1: IsPressureLow
• 6.6.2.5.2.2.2: Pressure
• 6.6.2.5.2.2.3: Temperature
• 6.6.2.5.2.3: Brake
• 6.6.2.5.2.3.1: FluidLevel
• 6.6.2.5.2.3.2: IsBrakesWorn
• 6.6.2.5.2.3.3: IsFluidLevelLow
• 6.6.2.5.2.3.4: PadWear
• 6.6.2.6: WheelCount
• 6.6.2.7: WheelDiameter
• 6.6.2.8: WheelWidth
• 6.7: Track
• 6.8: Wheelbase
• 7: ADAS
• 7.1: EBA
• 7.1.1: IsEnabled
• 7.1.2: IsEngaged
• 7.1.3: IsError
• 7.2: EBD
• 7.2.1: IsEnabled
• 7.2.2: IsEngaged
• 7.2.3: IsError
• 7.3: ESC
• 7.3.1: IsEnabled
• 7.3.2: IsEngaged
• 7.3.3: IsError
• 7.3.4: IsStrongCrossWindDetected
• 7.3.5: RoadFriction
• 7.3.5.1: LowerBound
• 7.3.5.2: MostProbable
• 7.3.5.3: UpperBound
• 7.4: PowerOptimizeLevel
• 7.5: ABS
• 7.5.1: IsEnabled
• 7.5.2: IsEngaged
• 7.5.3: IsError
• 7.6: ActiveAutonomyLevel
• 7.7: CruiseControl
• 7.7.1: IsActive
• 7.7.2: IsEnabled
• 7.7.3: IsError
• 7.7.4: SpeedSet
• 7.8: LaneDepartureDetection
• 7.8.1: IsEnabled
• 7.8.2: IsError
• 7.8.3: IsWarning
• 7.9: ObstacleDetection
• 7.9.1: IsEnabled
• 7.9.2: IsError
• 7.9.3: IsWarning
• 7.10: SupportedAutonomyLevel
• 7.11: TCS
• 7.11.1: IsEngaged
• 7.11.2: IsError
• 7.11.3: IsEnabled
• 8: Cabin
• 8.1: Convertible
• 8.1.1: Status
• 8.2: DriverPosition
• 8.3: PowerOptimizeLevel
• 8.4: SeatPosCount
• 8.5: SeatRowCount
• 8.6: DoorCount
• 8.7: Seat
• 8.7.1: Row2
• 8.7.1.1: Pos3
• 8.7.1.1.1: Airbag
• 8.7.1.1.1.1: IsDeployed
• 8.7.1.1.2: Headrest
• 8.7.1.1.2.1: Angle
• 8.7.1.1.2.2: Height
• 8.7.1.1.3: Switch
• 8.7.1.1.3.1: Headrest
• 8.7.1.1.3.1.1: IsBackwardEngaged
• 8.7.1.1.3.1.2: IsDownEngaged
• 8.7.1.1.3.1.3: IsForwardEngaged
• 8.7.1.1.3.1.4: IsUpEngaged
• 8.7.1.1.3.2: Massage
• 8.7.1.1.3.2.1: IsDecreaseEngaged
• 8.7.1.1.3.2.2: IsIncreaseEngaged
• 8.7.1.1.3.3: Backrest
• 8.7.1.1.3.3.1: IsReclineBackwardEngaged
• 8.7.1.1.3.3.2: IsReclineForwardEngaged
• 8.7.1.1.3.3.3: Lumbar
• 8.7.1.1.3.3.3.1: IsDownEngaged
• 8.7.1.1.3.3.3.2: IsLessSupportEngaged
• 8.7.1.1.3.3.3.3: IsMoreSupportEngaged
• 8.7.1.1.3.3.3.4: IsUpEngaged
• 8.7.1.1.3.3.4: SideBolster
• 8.7.1.1.3.3.4.1: IsLessSupportEngaged
• 8.7.1.1.3.3.4.2: IsMoreSupportEngaged
• 8.7.1.1.3.4: IsBackwardEngaged
• 8.7.1.1.3.5: IsCoolerEngaged
• 8.7.1.1.3.6: IsDownEngaged
• 8.7.1.1.3.7: IsForwardEngaged
• 8.7.1.1.3.8: IsTiltBackwardEngaged
• 8.7.1.1.3.9: IsTiltForwardEngaged
• 8.7.1.1.3.10: IsUpEngaged
• 8.7.1.1.3.11: IsWarmerEngaged
• 8.7.1.1.3.12: Seating
• 8.7.1.1.3.12.1: IsBackwardEngaged
• 8.7.1.1.3.12.2: IsForwardEngaged
• 8.7.1.1.4: Backrest
• 8.7.1.1.4.1: Lumbar
• 8.7.1.1.4.1.1: Height
• 8.7.1.1.4.1.2: Support
• 8.7.1.1.4.2: Recline
• 8.7.1.1.4.3: SideBolster
• 8.7.1.1.4.3.1: Support
• 8.7.1.1.5: Heating
• 8.7.1.1.6: Height
• 8.7.1.1.7: IsBelted
• 8.7.1.1.8: IsOccupied
• 8.7.1.1.9: Massage
• 8.7.1.1.10: Occupant
• 8.7.1.1.10.1: Identifier
• 8.7.1.1.10.1.1: Issuer
• 8.7.1.1.10.1.2: Subject
• 8.7.1.1.11: Position
• 8.7.1.1.12: Seating
• 8.7.1.1.12.1: Length
• 8.7.1.1.13: Tilt
• 8.7.1.2: Pos2
• 8.7.1.2.1: Airbag
• 8.7.1.2.1.1: IsDeployed
• 8.7.1.2.2: Headrest
• 8.7.1.2.2.1: Angle
• 8.7.1.2.2.2: Height
• 8.7.1.2.3: Seating
• 8.7.1.2.3.1: Length
• 8.7.1.2.4: Switch
• 8.7.1.2.4.1: Headrest
• 8.7.1.2.4.1.1: IsBackwardEngaged
• 8.7.1.2.4.1.2: IsDownEngaged
• 8.7.1.2.4.1.3: IsForwardEngaged
• 8.7.1.2.4.1.4: IsUpEngaged
• 8.7.1.2.4.2: Massage
• 8.7.1.2.4.2.1: IsDecreaseEngaged
• 8.7.1.2.4.2.2: IsIncreaseEngaged
• 8.7.1.2.4.3: Backrest
• 8.7.1.2.4.3.1: IsReclineBackwardEngaged
• 8.7.1.2.4.3.2: IsReclineForwardEngaged
• 8.7.1.2.4.3.3: Lumbar
• 8.7.1.2.4.3.3.1: IsDownEngaged
• 8.7.1.2.4.3.3.2: IsLessSupportEngaged
• 8.7.1.2.4.3.3.3: IsMoreSupportEngaged
• 8.7.1.2.4.3.3.4: IsUpEngaged
• 8.7.1.2.4.3.4: SideBolster
• 8.7.1.2.4.3.4.1: IsLessSupportEngaged
• 8.7.1.2.4.3.4.2: IsMoreSupportEngaged
• 8.7.1.2.4.4: IsBackwardEngaged
• 8.7.1.2.4.5: IsCoolerEngaged
• 8.7.1.2.4.6: IsDownEngaged
• 8.7.1.2.4.7: IsForwardEngaged
• 8.7.1.2.4.8: IsTiltBackwardEngaged
• 8.7.1.2.4.9: IsTiltForwardEngaged
• 8.7.1.2.4.10: IsUpEngaged
• 8.7.1.2.4.11: IsWarmerEngaged
• 8.7.1.2.4.12: Seating
• 8.7.1.2.4.12.1: IsBackwardEngaged
• 8.7.1.2.4.12.2: IsForwardEngaged
• 8.7.1.2.5: Backrest
• 8.7.1.2.5.1: SideBolster
• 8.7.1.2.5.1.1: Support
• 8.7.1.2.5.2: Lumbar
• 8.7.1.2.5.2.1: Height
• 8.7.1.2.5.2.2: Support
• 8.7.1.2.5.3: Recline
• 8.7.1.2.6: Heating
• 8.7.1.2.7: Height
• 8.7.1.2.8: IsBelted
• 8.7.1.2.9: IsOccupied
• 8.7.1.2.10: Massage
• 8.7.1.2.11: Occupant
• 8.7.1.2.11.1: Identifier
• 8.7.1.2.11.1.1: Issuer
• 8.7.1.2.11.1.2: Subject
• 8.7.1.2.12: Position
• 8.7.1.2.13: Tilt
• 8.7.1.3: Pos1
• 8.7.1.3.1: Airbag
• 8.7.1.3.1.1: IsDeployed
• 8.7.1.3.2: Backrest
• 8.7.1.3.2.1: Lumbar
• 8.7.1.3.2.1.1: Height
• 8.7.1.3.2.1.2: Support
• 8.7.1.3.2.2: Recline
• 8.7.1.3.2.3: SideBolster
• 8.7.1.3.2.3.1: Support
• 8.7.1.3.3: Headrest
• 8.7.1.3.3.1: Angle
• 8.7.1.3.3.2: Height
• 8.7.1.3.4: Heating
• 8.7.1.3.5: Height
• 8.7.1.3.6: IsBelted
• 8.7.1.3.7: IsOccupied
• 8.7.1.3.8: Massage
• 8.7.1.3.9: Occupant
• 8.7.1.3.9.1: Identifier
• 8.7.1.3.9.1.1: Issuer
• 8.7.1.3.9.1.2: Subject
• 8.7.1.3.10: Position
• 8.7.1.3.11: Seating
• 8.7.1.3.11.1: Length
• 8.7.1.3.12: Switch
• 8.7.1.3.12.1: Backrest
• 8.7.1.3.12.1.1: IsReclineBackwardEngaged
• 8.7.1.3.12.1.2: IsReclineForwardEngaged
• 8.7.1.3.12.1.3: Lumbar
• 8.7.1.3.12.1.3.1: IsDownEngaged
• 8.7.1.3.12.1.3.2: IsLessSupportEngaged
• 8.7.1.3.12.1.3.3: IsMoreSupportEngaged
• 8.7.1.3.12.1.3.4: IsUpEngaged
• 8.7.1.3.12.1.4: SideBolster
• 8.7.1.3.12.1.4.1: IsLessSupportEngaged
• 8.7.1.3.12.1.4.2: IsMoreSupportEngaged
• 8.7.1.3.12.2: Headrest
• 8.7.1.3.12.2.1: IsBackwardEngaged
• 8.7.1.3.12.2.2: IsDownEngaged
• 8.7.1.3.12.2.3: IsForwardEngaged
• 8.7.1.3.12.2.4: IsUpEngaged
• 8.7.1.3.12.3: IsDownEngaged
• 8.7.1.3.12.4: IsTiltBackwardEngaged
• 8.7.1.3.12.5: IsTiltForwardEngaged
• 8.7.1.3.12.6: IsUpEngaged
• 8.7.1.3.12.7: Massage
• 8.7.1.3.12.7.1: IsDecreaseEngaged
• 8.7.1.3.12.7.2: IsIncreaseEngaged
• 8.7.1.3.12.8: Seating
• 8.7.1.3.12.8.1: IsBackwardEngaged
• 8.7.1.3.12.8.2: IsForwardEngaged
• 8.7.1.3.12.9: IsBackwardEngaged
• 8.7.1.3.12.10: IsCoolerEngaged
• 8.7.1.3.12.11: IsForwardEngaged
• 8.7.1.3.12.12: IsWarmerEngaged
• 8.7.1.3.13: Tilt
• 8.7.2: Row1
• 8.7.2.1: Pos3
• 8.7.2.1.1: Switch
• 8.7.2.1.1.1: Backrest
• 8.7.2.1.1.1.1: IsReclineBackwardEngaged
• 8.7.2.1.1.1.2: IsReclineForwardEngaged
• 8.7.2.1.1.1.3: Lumbar
• 8.7.2.1.1.1.3.1: IsDownEngaged
• 8.7.2.1.1.1.3.2: IsLessSupportEngaged
• 8.7.2.1.1.1.3.3: IsMoreSupportEngaged
• 8.7.2.1.1.1.3.4: IsUpEngaged
• 8.7.2.1.1.1.4: SideBolster
• 8.7.2.1.1.1.4.1: IsLessSupportEngaged
• 8.7.2.1.1.1.4.2: IsMoreSupportEngaged
• 8.7.2.1.1.2: Headrest
• 8.7.2.1.1.2.1: IsBackwardEngaged
• 8.7.2.1.1.2.2: IsDownEngaged
• 8.7.2.1.1.2.3: IsForwardEngaged
• 8.7.2.1.1.2.4: IsUpEngaged
• 8.7.2.1.1.3: IsBackwardEngaged
• 8.7.2.1.1.4: IsCoolerEngaged
• 8.7.2.1.1.5: IsDownEngaged
• 8.7.2.1.1.6: IsForwardEngaged
• 8.7.2.1.1.7: IsTiltBackwardEngaged
• 8.7.2.1.1.8: IsTiltForwardEngaged
• 8.7.2.1.1.9: IsUpEngaged
• 8.7.2.1.1.10: IsWarmerEngaged
• 8.7.2.1.1.11: Massage
• 8.7.2.1.1.11.1: IsDecreaseEngaged
• 8.7.2.1.1.11.2: IsIncreaseEngaged
• 8.7.2.1.1.12: Seating
• 8.7.2.1.1.12.1: IsBackwardEngaged
• 8.7.2.1.1.12.2: IsForwardEngaged
• 8.7.2.1.2: Airbag
• 8.7.2.1.2.1: IsDeployed
• 8.7.2.1.3: Backrest
• 8.7.2.1.3.1: Lumbar
• 8.7.2.1.3.1.1: Height
• 8.7.2.1.3.1.2: Support
• 8.7.2.1.3.2: Recline
• 8.7.2.1.3.3: SideBolster
• 8.7.2.1.3.3.1: Support
• 8.7.2.1.4: Headrest
• 8.7.2.1.4.1: Angle
• 8.7.2.1.4.2: Height
• 8.7.2.1.5: Heating
• 8.7.2.1.6: Height
• 8.7.2.1.7: IsBelted
• 8.7.2.1.8: IsOccupied
• 8.7.2.1.9: Massage
• 8.7.2.1.10: Occupant
• 8.7.2.1.10.1: Identifier
• 8.7.2.1.10.1.1: Issuer
• 8.7.2.1.10.1.2: Subject
• 8.7.2.1.11: Position
• 8.7.2.1.12: Seating
• 8.7.2.1.12.1: Length
• 8.7.2.1.13: Tilt
• 8.7.2.2: Pos2
• 8.7.2.2.1: Airbag
• 8.7.2.2.1.1: IsDeployed
• 8.7.2.2.2: Headrest
• 8.7.2.2.2.1: Angle
• 8.7.2.2.2.2: Height
• 8.7.2.2.3: Seating
• 8.7.2.2.3.1: Length
• 8.7.2.2.4: Switch
• 8.7.2.2.4.1: Massage
• 8.7.2.2.4.1.1: IsDecreaseEngaged
• 8.7.2.2.4.1.2: IsIncreaseEngaged
• 8.7.2.2.4.2: Backrest
• 8.7.2.2.4.2.1: IsReclineBackwardEngaged
• 8.7.2.2.4.2.2: IsReclineForwardEngaged
• 8.7.2.2.4.2.3: Lumbar
• 8.7.2.2.4.2.3.1: IsDownEngaged
• 8.7.2.2.4.2.3.2: IsLessSupportEngaged
• 8.7.2.2.4.2.3.3: IsMoreSupportEngaged
• 8.7.2.2.4.2.3.4: IsUpEngaged
• 8.7.2.2.4.2.4: SideBolster
• 8.7.2.2.4.2.4.1: IsLessSupportEngaged
• 8.7.2.2.4.2.4.2: IsMoreSupportEngaged
• 8.7.2.2.4.3: Headrest
• 8.7.2.2.4.3.1: IsBackwardEngaged
• 8.7.2.2.4.3.2: IsDownEngaged
• 8.7.2.2.4.3.3: IsForwardEngaged
• 8.7.2.2.4.3.4: IsUpEngaged
• 8.7.2.2.4.4: IsBackwardEngaged
• 8.7.2.2.4.5: IsCoolerEngaged
• 8.7.2.2.4.6: IsDownEngaged
• 8.7.2.2.4.7: IsForwardEngaged
• 8.7.2.2.4.8: IsTiltBackwardEngaged
• 8.7.2.2.4.9: IsTiltForwardEngaged
• 8.7.2.2.4.10: IsUpEngaged
• 8.7.2.2.4.11: IsWarmerEngaged
• 8.7.2.2.4.12: Seating
• 8.7.2.2.4.12.1: IsBackwardEngaged
• 8.7.2.2.4.12.2: IsForwardEngaged
• 8.7.2.2.5: Backrest
• 8.7.2.2.5.1: SideBolster
• 8.7.2.2.5.1.1: Support
• 8.7.2.2.5.2: Lumbar
• 8.7.2.2.5.2.1: Height
• 8.7.2.2.5.2.2: Support
• 8.7.2.2.5.3: Recline
• 8.7.2.2.6: Heating
• 8.7.2.2.7: Height
• 8.7.2.2.8: IsBelted
• 8.7.2.2.9: IsOccupied
• 8.7.2.2.10: Massage
• 8.7.2.2.11: Occupant
• 8.7.2.2.11.1: Identifier
• 8.7.2.2.11.1.1: Issuer
• 8.7.2.2.11.1.2: Subject
• 8.7.2.2.12: Position
• 8.7.2.2.13: Tilt
• 8.7.2.3: Pos1
• 8.7.2.3.1: Airbag
• 8.7.2.3.1.1: IsDeployed
• 8.7.2.3.2: Backrest
• 8.7.2.3.2.1: Lumbar
• 8.7.2.3.2.1.1: Height
• 8.7.2.3.2.1.2: Support
• 8.7.2.3.2.2: Recline
• 8.7.2.3.2.3: SideBolster
• 8.7.2.3.2.3.1: Support
• 8.7.2.3.3: Headrest
• 8.7.2.3.3.1: Angle
• 8.7.2.3.3.2: Height
• 8.7.2.3.4: Heating
• 8.7.2.3.5: Height
• 8.7.2.3.6: IsBelted
• 8.7.2.3.7: Massage
• 8.7.2.3.8: Position
• 8.7.2.3.9: Seating
• 8.7.2.3.9.1: Length
• 8.7.2.3.10: Switch
• 8.7.2.3.10.1: Headrest
• 8.7.2.3.10.1.1: IsBackwardEngaged
• 8.7.2.3.10.1.2: IsDownEngaged
• 8.7.2.3.10.1.3: IsForwardEngaged
• 8.7.2.3.10.1.4: IsUpEngaged
• 8.7.2.3.10.2: Massage
• 8.7.2.3.10.2.1: IsDecreaseEngaged
• 8.7.2.3.10.2.2: IsIncreaseEngaged
• 8.7.2.3.10.3: Seating
• 8.7.2.3.10.3.1: IsBackwardEngaged
• 8.7.2.3.10.3.2: IsForwardEngaged
• 8.7.2.3.10.4: Backrest
• 8.7.2.3.10.4.1: SideBolster
• 8.7.2.3.10.4.1.1: IsLessSupportEngaged
• 8.7.2.3.10.4.1.2: IsMoreSupportEngaged
• 8.7.2.3.10.4.2: IsReclineBackwardEngaged
• 8.7.2.3.10.4.3: IsReclineForwardEngaged
• 8.7.2.3.10.4.4: Lumbar
• 8.7.2.3.10.4.4.1: IsDownEngaged
• 8.7.2.3.10.4.4.2: IsLessSupportEngaged
• 8.7.2.3.10.4.4.3: IsMoreSupportEngaged
• 8.7.2.3.10.4.4.4: IsUpEngaged
• 8.7.2.3.10.5: IsBackwardEngaged
• 8.7.2.3.10.6: IsCoolerEngaged
• 8.7.2.3.10.7: IsDownEngaged
• 8.7.2.3.10.8: IsForwardEngaged
• 8.7.2.3.10.9: IsTiltBackwardEngaged
• 8.7.2.3.10.10: IsTiltForwardEngaged
• 8.7.2.3.10.11: IsUpEngaged
• 8.7.2.3.10.12: IsWarmerEngaged
• 8.7.2.3.11: Tilt
• 8.7.2.3.12: IsOccupied
• 8.7.2.3.13: Occupant
• 8.7.2.3.13.1: Identifier
• 8.7.2.3.13.1.1: Issuer
• 8.7.2.3.13.1.2: Subject
• 8.8: Door
• 8.8.1: Row2
• 8.8.1.1: Right
• 8.8.1.1.1: IsChildLockActive
• 8.8.1.1.2: IsLocked
• 8.8.1.1.3: IsOpen
• 8.8.1.1.4: Shade
• 8.8.1.1.4.1: Position
• 8.8.1.1.4.2: Switch
• 8.8.1.1.5: Window
• 8.8.1.1.5.1: IsChildLockEngaged
• 8.8.1.1.5.2: IsOpen
• 8.8.1.1.5.3: Position
• 8.8.1.1.5.4: Switch
• 8.8.1.2: Left
• 8.8.1.2.1: IsChildLockActive
• 8.8.1.2.2: Shade
• 8.8.1.2.2.1: Position
• 8.8.1.2.2.2: Switch
• 8.8.1.2.3: IsLocked
• 8.8.1.2.4: IsOpen
• 8.8.1.2.5: Window
• 8.8.1.2.5.1: IsChildLockEngaged
• 8.8.1.2.5.2: Switch
• 8.8.1.2.5.3: IsOpen
• 8.8.1.2.5.4: Position
• 8.8.2: Row1
• 8.8.2.1: Left
• 8.8.2.1.1: IsChildLockActive
• 8.8.2.1.2: IsLocked
• 8.8.2.1.3: IsOpen
• 8.8.2.1.4: Shade
• 8.8.2.1.4.1: Position
• 8.8.2.1.4.2: Switch
• 8.8.2.1.5: Window
• 8.8.2.1.5.1: IsChildLockEngaged
• 8.8.2.1.5.2: IsOpen
• 8.8.2.1.5.3: Position
• 8.8.2.1.5.4: Switch
• 8.8.2.2: Right
• 8.8.2.2.1: IsChildLockActive
• 8.8.2.2.2: IsLocked
• 8.8.2.2.3: IsOpen
• 8.8.2.2.4: Shade
• 8.8.2.2.4.1: Position
• 8.8.2.2.4.2: Switch
• 8.8.2.2.5: Window
• 8.8.2.2.5.1: IsChildLockEngaged
• 8.8.2.2.5.2: IsOpen
• 8.8.2.2.5.3: Position
• 8.8.2.2.5.4: Switch
• 8.9: Lights
• 8.9.1: AmbientLight
• 8.9.2: IsDomeOn
• 8.9.3: IsGloveBoxOn
• 8.9.4: IsTrunkOn
• 8.9.5: LightIntensity
• 8.9.6: Spotlight
• 8.9.6.1: Row1
• 8.9.6.1.1: IsLeftOn
• 8.9.6.1.2: IsRightOn
• 8.9.6.1.3: IsSharedOn
• 8.9.6.2: Row2
• 8.9.6.2.1: IsLeftOn
• 8.9.6.2.2: IsRightOn
• 8.9.6.2.3: IsSharedOn
• 8.9.6.3: Row3
• 8.9.6.3.1: IsLeftOn
• 8.9.6.3.2: IsRightOn
• 8.9.6.3.3: IsSharedOn
• 8.9.6.4: Row4
• 8.9.6.4.1: IsLeftOn
• 8.9.6.4.2: IsRightOn
• 8.9.6.4.3: IsSharedOn
• 8.10: RearviewMirror
• 8.10.1: DimmingLevel
• 8.11: Sunroof
• 8.11.1: Position
• 8.11.2: Shade
• 8.11.2.1: Position
• 8.11.2.2: Switch
• 8.11.3: Switch
• 8.12: Infotainment
• 8.12.1: HMI
• 8.12.1.1: Brightness
• 8.12.1.2: CurrentLanguage
• 8.12.1.3: DateFormat
• 8.12.1.4: DayNightMode
• 8.12.1.5: DistanceUnit
• 8.12.1.6: EVEconomyUnits
• 8.12.1.7: FuelEconomyUnits
• 8.12.1.8: FuelVolumeUnit
• 8.12.1.9: TemperatureUnit
• 8.12.1.10: TimeFormat
• 8.12.1.11: TirePressureUnit
• 8.12.2: Navigation
• 8.12.2.1: DestinationSet
• 8.12.2.1.1: Latitude
• 8.12.2.1.2: Longitude
• 8.12.2.2: Mute
• 8.12.2.3: Volume
• 8.12.3: PowerOptimizeLevel
• 8.12.4: SmartphoneProjection
• 8.12.4.1: Active
• 8.12.4.2: Source
• 8.12.4.3: SupportedMode
• 8.12.5: Media
• 8.12.5.1: DeclinedURI
• 8.12.5.2: SelectedURI
• 8.12.5.3: Volume
• 8.12.5.4: Action
• 8.12.5.5: Played
• 8.12.5.5.1: PlaybackRate
• 8.12.5.5.2: Album
• 8.12.5.5.3: Artist
• 8.12.5.5.4: Source
• 8.12.5.5.5: Track
• 8.12.5.5.6: URI
• 8.13: HVAC
• 8.13.1: AmbientAirTemperature
• 8.13.2: IsAirConditioningActive
• 8.13.3: IsFrontDefrosterActive
• 8.13.4: IsRearDefrosterActive
• 8.13.5: IsRecirculationActive
• 8.13.6: PowerOptimizeLevel
• 8.13.7: Station
• 8.13.7.1: Row4
• 8.13.7.1.1: Left
• 8.13.7.1.1.1: AirDistribution
• 8.13.7.1.1.2: FanSpeed
• 8.13.7.1.1.3: Temperature
• 8.13.7.1.2: Right
• 8.13.7.1.2.1: AirDistribution
• 8.13.7.1.2.2: FanSpeed
• 8.13.7.1.2.3: Temperature
• 8.13.7.2: Row1
• 8.13.7.2.1: Left
• 8.13.7.2.1.1: AirDistribution
• 8.13.7.2.1.2: FanSpeed
• 8.13.7.2.1.3: Temperature
• 8.13.7.2.2: Right
• 8.13.7.2.2.1: AirDistribution
• 8.13.7.2.2.2: FanSpeed
• 8.13.7.2.2.3: Temperature
• 8.13.7.3: Row2
• 8.13.7.3.1: Left
• 8.13.7.3.1.1: AirDistribution
• 8.13.7.3.1.2: FanSpeed
• 8.13.7.3.1.3: Temperature
• 8.13.7.3.2: Right
• 8.13.7.3.2.1: AirDistribution
• 8.13.7.3.2.2: FanSpeed
• 8.13.7.3.2.3: Temperature
• 8.13.7.4: Row3
• 8.13.7.4.1: Left
• 8.13.7.4.1.1: AirDistribution
• 8.13.7.4.1.2: FanSpeed
• 8.13.7.4.1.3: Temperature
• 8.13.7.4.2: Right
• 8.13.7.4.2.1: AirDistribution
• 8.13.7.4.2.2: FanSpeed
• 8.13.7.4.2.3: Temperature
• 8.14: RearShade
• 8.14.1: Position
• 8.14.2: Switch
• 9: Body
• 9.1: PowerOptimizeLevel
• 9.2: RearMainSpoilerPosition
• 9.3: Mirrors
• 9.3.1: Right
• 9.3.1.1: IsHeatingOn
• 9.3.1.2: Pan
• 9.3.1.3: Tilt
• 9.3.2: Left
• 9.3.2.1: IsHeatingOn
• 9.3.2.2: Pan
• 9.3.2.3: Tilt
• 9.4: Lights
• 9.4.1: Backup
• 9.4.1.1: IsDefect
• 9.4.1.2: IsOn
• 9.4.2: Brake
• 9.4.2.1: IsActive
• 9.4.2.2: IsDefect
• 9.4.3: DirectionIndicator
• 9.4.3.1: Left
• 9.4.3.1.1: IsDefect
• 9.4.3.1.2: IsSignaling
• 9.4.3.2: Right
• 9.4.3.2.1: IsDefect
• 9.4.3.2.2: IsSignaling
• 9.4.4: Fog
• 9.4.4.1: Front
• 9.4.4.1.1: IsDefect
• 9.4.4.1.2: IsOn
• 9.4.4.2: Rear
• 9.4.4.2.1: IsDefect
• 9.4.4.2.2: IsOn
• 9.4.5: Hazard
• 9.4.5.1: IsDefect
• 9.4.5.2: IsSignaling
• 9.4.6: LicensePlate
• 9.4.6.1: IsDefect
• 9.4.6.2: IsOn
• 9.4.7: Parking
• 9.4.7.1: IsDefect
• 9.4.7.2: IsOn
• 9.4.8: Running
• 9.4.8.1: IsDefect
• 9.4.8.2: IsOn
• 9.4.9: Beam
• 9.4.9.1: High
• 9.4.9.1.1: IsDefect
• 9.4.9.1.2: IsOn
• 9.4.9.2: Low
• 9.4.9.2.1: IsDefect
• 9.4.9.2.2: IsOn
• 9.4.10: IsHighBeamSwitchOn
• 9.4.11: LightSwitch
• 9.5: Horn
• 9.5.1: IsActive
• 9.6: Raindetection
• 9.6.1: Intensity
• 9.7: Windshield
• 9.7.1: Front
• 9.7.1.1: IsHeatingOn
• 9.7.1.2: WasherFluid
• 9.7.1.2.1: IsLevelLow
• 9.7.1.2.2: Level
• 9.7.1.3: Wiping
• 9.7.1.3.1: Intensity
• 9.7.1.3.2: IsWipersWorn
• 9.7.1.3.3: Mode
• 9.7.1.3.4: System
• 9.7.1.3.4.1: ActualPosition
• 9.7.1.3.4.2: DriveCurrent
• 9.7.1.3.4.3: Frequency
• 9.7.1.3.4.4: IsBlocked
• 9.7.1.3.4.5: IsEndingWipeCycle
• 9.7.1.3.4.6: IsOverheated
• 9.7.1.3.4.7: IsPositionReached
• 9.7.1.3.4.8: IsWiperError
• 9.7.1.3.4.9: IsWiping
• 9.7.1.3.4.10: Mode
• 9.7.1.3.4.11: TargetPosition
• 9.7.1.3.5: WiperWear
• 9.7.2: Rear
• 9.7.2.1: IsHeatingOn
• 9.7.2.2: WasherFluid
• 9.7.2.2.1: IsLevelLow
• 9.7.2.2.2: Level
• 9.7.2.3: Wiping
• 9.7.2.3.1: Intensity
• 9.7.2.3.2: IsWipersWorn
• 9.7.2.3.3: Mode
• 9.7.2.3.4: System
• 9.7.2.3.4.1: ActualPosition
• 9.7.2.3.4.2: DriveCurrent
• 9.7.2.3.4.3: Frequency
• 9.7.2.3.4.4: IsBlocked
• 9.7.2.3.4.5: IsEndingWipeCycle
• 9.7.2.3.4.6: IsOverheated
• 9.7.2.3.4.7: IsPositionReached
• 9.7.2.3.4.8: IsWiperError
• 9.7.2.3.4.9: IsWiping
• 9.7.2.3.4.10: Mode
• 9.7.2.3.4.11: TargetPosition
• 9.7.2.3.5: WiperWear
• 9.8: BodyType
• 9.9: Hood
• 9.9.1: IsOpen
• 9.10: RefuelPosition
• 9.11: Trunk
• 9.11.1: Front
• 9.11.1.1: IsLocked
• 9.11.1.2: IsOpen
• 9.11.2: Rear
• 9.11.2.1: IsLocked
• 9.11.2.2: IsOpen
• 10: CurrentLocation
• 10.1: Altitude
• 10.2: GNSSReceiver
• 10.2.1: FixType
• 10.2.2: MountingPosition
• 10.2.2.1: true
• 10.2.2.2: X
• 10.2.2.3: Z
• 10.3: Heading
• 10.4: HorizontalAccuracy
• 10.5: Latitude
• 10.6: Longitude
• 10.7: Timestamp
• 10.8: VerticalAccuracy
• 11: PowerOptimizeLevel
• 12: Powertrain
• 12.1: FuelSystem
• 12.1.1: AverageConsumption
• 12.1.2: ConsumptionSinceStart
• 12.1.3: HybridType
• 12.1.4: InstantConsumption
• 12.1.5: IsEngineStopStartEnabled
• 12.1.6: IsFuelLevelLow
• 12.1.7: Level
• 12.1.8: Range
• 12.1.9: SupportedFuel
• 12.1.10: SupportedFuelTypes
• 12.1.11: TankCapacity
• 12.1.12: TimeSinceStart
• 12.2: TractionBattery
• 12.2.1: DCDC
• 12.2.1.1: PowerLoss
• 12.2.1.2: Temperature
• 12.2.2: Charging
• 12.2.2.1: ChargeCurrent
• 12.2.2.1.1: DC
• 12.2.2.1.2: Phase1
• 12.2.2.1.3: Phase2
• 12.2.2.1.4: Phase3
• 12.2.2.2: ChargeLimit
• 12.2.2.3: ChargePlugType
• 12.2.2.4: ChargePortFlap
• 12.2.2.5: ChargeRate
• 12.2.2.6: ChargeVoltage
• 12.2.2.6.1: DC
• 12.2.2.6.2: Phase1
• 12.2.2.6.3: Phase2
• 12.2.2.6.4: Phase3
• 12.2.2.7: IsCharging
• 12.2.2.8: IsChargingCableConnected
• 12.2.2.9: IsChargingCableLocked
• 12.2.2.10: IsDischarging
• 12.2.2.11: MaximumChargingCurrent
• 12.2.2.11.1: DC
• 12.2.2.11.2: Phase1
• 12.2.2.11.3: Phase2
• 12.2.2.11.4: Phase3
• 12.2.2.12: Mode
• 12.2.2.13: PowerLoss
• 12.2.2.14: StartStopCharging
• 12.2.2.15: Temperature
• 12.2.2.16: Timer
• 12.2.2.16.1: Mode
• 12.2.2.16.2: Time
• 12.2.2.17: TimeToComplete
• 12.2.3: PowerLoss
• 12.2.4: Range
• 12.2.5: AccumulatedChargedEnergy
• 12.2.6: AccumulatedChargedThroughput
• 12.2.7: AccumulatedConsumedEnergy
• 12.2.8: AccumulatedConsumedThroughput
• 12.2.9: CurrentCurrent
• 12.2.10: CurrentPower
• 12.2.11: CurrentVoltage
• 12.2.12: GrossCapacity
• 12.2.13: Id
• 12.2.14: IsGroundConnected
• 12.2.15: IsPowerConnected
• 12.2.16: MaxVoltage
• 12.2.17: NetCapacity
• 12.2.18: NominalVoltage
• 12.2.19: ProductionDate
• 12.2.20: StateOfCharge
• 12.2.20.1: Current
• 12.2.20.2: Displayed
• 12.2.21: StateOfHealth
• 12.2.22: Temperature
• 12.2.22.1: Average
• 12.2.22.2: Max
• 12.2.22.3: Min
• 12.3: ElectricMotor
• 12.3.1: CoolantTemperature
• 12.3.2: MaxRegenTorque
• 12.3.3: Power
• 12.3.4: Speed
• 12.3.5: Temperature
• 12.3.6: Torque
• 12.3.7: EngineCode
• 12.3.8: MaxPower
• 12.3.9: MaxRegenPower
• 12.3.10: MaxTorque
• 12.4: Transmission
• 12.4.1: ClutchEngagement
• 12.4.2: ClutchWear
• 12.4.3: CurrentGear
• 12.4.4: DiffLockFrontEngagement
• 12.4.5: DiffLockRearEngagement
• 12.4.6: DriveType
• 12.4.7: GearChangeMode
• 12.4.8: GearCount
• 12.4.9: IsElectricalPowertrainEngaged
• 12.4.10: IsLowRangeEngaged
• 12.4.11: IsParkLockEngaged
• 12.4.12: PerformanceMode
• 12.4.13: SelectedGear
• 12.4.14: Temperature
• 12.4.15: TorqueDistribution
• 12.4.16: TravelledDistance
• 12.4.17: Type
• 12.5: AccumulatedBrakingEnergy
• 12.6: CombustionEngine
• 12.6.1: AspirationType
• 12.6.2: CompressionRatio
• 12.6.3: DieselExhaustFluid
• 12.6.3.1: Capacity
• 12.6.3.2: IsLevelLow
• 12.6.3.3: Level
• 12.6.3.4: Range
• 12.6.4: DieselParticulateFilter
• 12.6.4.1: DeltaPressure
• 12.6.4.2: InletTemperature
• 12.6.4.3: OutletTemperature
• 12.6.5: ECT
• 12.6.6: EngineCoolantCapacity
• 12.6.7: EngineHours
• 12.6.8: EngineOilCapacity
• 12.6.9: EngineOilLevel
• 12.6.10: EOP
• 12.6.11: EOT
• 12.6.12: IdleHours
• 12.6.13: IsRunning
• 12.6.14: MAF
• 12.6.15: MAP
• 12.6.16: MaxPower
• 12.6.17: MaxTorque
• 12.6.18: NumberOfCylinders
• 12.6.19: NumberOfValvesPerCylinder
• 12.6.20: OilLifeRemaining
• 12.6.21: Power
• 12.6.22: Speed
• 12.6.23: Torque
• 12.6.24: TPS
• 12.6.25: Bore
• 12.6.26: Configuration
• 12.6.27: Displacement
• 12.6.28: EngineCode
• 12.6.29: StrokeLength
• 12.7: PowerOptimizeLevel
• 12.8: Range
• 12.9: Type
• 13: Trailer
• 13.1: IsConnected
• 14: Width
• 15: Acceleration
• 15.1: Lateral
• 15.2: Longitudinal
• 15.3: Vertical
• 16: AngularVelocity
• 16.1: Pitch
• 16.2: Roll
• 16.3: Yaw
• 17: AverageSpeed
• 18: CargoVolume
• 19: CurbWeight
• 20: CurrentOverallWeight
• 21: EmissionsCO2
• 22: GrossWeight
• 23: Height
• 24: IsBrokenDown
• 25: IsMoving
• 26: Length
• 27: LowVoltageBattery
• 27.1: CurrentCurrent
• 27.2: CurrentVoltage
• 27.3: NominalCapacity
• 27.4: NominalVoltage
• 28: MaxTowBallWeight
• 29: MaxTowWeight
• 30: RoofLoad
• 31: Speed
• 32: StartTime
• 33: TraveledDistance
• 34: TraveledDistanceSinceStart
• 35: TravelledDistance
• 36: TripDuration
• 37: TripMeterReading
• 38: LowVoltageSystemState
• 39: VehicleIdentification
• 39.1: AcrissCode
• 39.2: BodyType
• 39.3: Brand
• 39.4: DateVehicleFirstRegistered
• 39.5: KnownVehicleDamages
• 39.6: MeetsEmissionStandard
• 39.7: Model
• 39.8: OptionalExtras
• 39.9: ProductionDate
• 39.10: PurchaseDate
• 39.11: VehicleConfiguration
• 39.12: VehicleInteriorColor
• 39.13: VehicleInteriorType
• 39.14: VehicleModelDate
• 39.15: VehicleSeatingCapacity
• 39.16: VehicleSpecialUsage
• 39.17: VIN
• 39.18: WMI
• 39.19: Year
• 40: VersionVSS
• 40.1: Label
• 40.2: Major
• 40.3: Minor
• 40.4: Patch

1 - Connectivity

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

UUID

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

The UUID for Vehicle.Connectivity is 89c267fccea35f3da9871cca2b4dc4df

Children

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

• Vehicle.Connectivity.IsConnectivityAvailable (Indicates if connectivity between vehicle and cloud is available. True = Connectivity is available. False = Connectivity is not available.)

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Connectivity.IsConnectivityAvailable
[get]  OK
Vehicle.Connectivity.IsConnectivityAvailable: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Connectivity.IsConnectivityAvailable 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.Connectivity.IsConnectivityAvailable is a Sensor.

The vehicle signal Vehicle.Connectivity.IsConnectivityAvailable is a Signal.

UUID

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

The UUID for Vehicle.Connectivity.IsConnectivityAvailable is b6d11be2a6565996b68ffb07a96595a7

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

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

UUID

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

The UUID for Vehicle.Exterior is 06c5def549f3580e8cdaffa3e0f5d25c

Children

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

• Vehicle.Exterior.AirTemperature (Air temperature outside the vehicle.)
• Vehicle.Exterior.Humidity (Relative humidity outside the vehicle. 0 = Dry, 100 = Air fully saturated.)
• Vehicle.Exterior.LightIntensity (Light intensity outside the vehicle. 0 = No light detected, 100 = Fully lit.)

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

2.1 - AirTemperature

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirTemperature
[get]  OK
Vehicle.Exterior.AirTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirTemperature 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.Exterior.AirTemperature is a Sensor.

The vehicle signal Vehicle.Exterior.AirTemperature is a Signal.

UUID

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

The UUID for Vehicle.Exterior.AirTemperature is a38d3f5dfeb35317aca8b90453dc1a75

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

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

2.2 - Humidity

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.Humidity
[get]  OK
Vehicle.Exterior.Humidity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.Humidity 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.Exterior.Humidity is a Sensor.

The vehicle signal Vehicle.Exterior.Humidity is a Signal.

UUID

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

The UUID for Vehicle.Exterior.Humidity is 6c785ec5d9a5534f98be7ce198d25d6b

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.3 - LightIntensity

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.LightIntensity
[get]  OK
Vehicle.Exterior.LightIntensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.LightIntensity 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.Exterior.LightIntensity is a Sensor.

The vehicle signal Vehicle.Exterior.LightIntensity is a Signal.

UUID

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

The UUID for Vehicle.Exterior.LightIntensity is 9b46b70490f853e891e1cc35dd08dddc

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

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

UUID

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

The UUID for Vehicle.Service is b6463772705b56a7a993e23601bd3d47

Children

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

• Vehicle.Service.DistanceToService (Remaining distance to service (of any kind). Negative values indicate service overdue.)
• Vehicle.Service.IsServiceDue (Indicates if vehicle needs service (of any kind). True = Service needed now or in the near future. False = No known need for service.)
• Vehicle.Service.TimeToService (Remaining time to service (of any kind). Negative values indicate service overdue.)

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

3.1 - DistanceToService

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Service.DistanceToService
[get]  OK
Vehicle.Service.DistanceToService: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Service.DistanceToService 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.Service.DistanceToService is a Sensor.

The vehicle signal Vehicle.Service.DistanceToService is a Signal.

UUID

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

The UUID for Vehicle.Service.DistanceToService is 6f4347ce149759819572c8c3a17e8d93

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

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

3.2 - IsServiceDue

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Service.IsServiceDue
[get]  OK
Vehicle.Service.IsServiceDue: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Service.IsServiceDue 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.Service.IsServiceDue is a Sensor.

The vehicle signal Vehicle.Service.IsServiceDue is a Signal.

UUID

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

The UUID for Vehicle.Service.IsServiceDue is 3e28f85ccccd5702b9adbe9a761ea1b4

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.3 - TimeToService

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Service.TimeToService
[get]  OK
Vehicle.Service.TimeToService: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Service.TimeToService 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 int32 datatype is a signed 32-bit integer which technically allows values between -2147483648 and 2147483647 (inclusive).

Signal Information

The vehicle signal Vehicle.Service.TimeToService is a Sensor.

The vehicle signal Vehicle.Service.TimeToService is a Signal.

UUID

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

The UUID for Vehicle.Service.TimeToService is c968be91a5685fa9ae30b84a0f91934e

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

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

UUID

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

The UUID for Vehicle.Driver is 1cac57e7b7e756dc8a154eaacbce6426

Children

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

• Vehicle.Driver.AttentiveProbability (Probability of attentiveness of the driver.)
• Vehicle.Driver.DistractionLevel (Distraction level of the driver will be the level how much the driver is distracted, by multiple factors. E.g. Driving situation, acustical or optical signales inside the cockpit, phone calls.)
• Vehicle.Driver.FatigueLevel (Fatigueness level of driver. Evaluated by multiple factors like trip time, behaviour of steering, eye status.)
• Vehicle.Driver.HeartRate (Heart rate of the driver.)
• Vehicle.Driver.Identifier (Identifier attributes based on OAuth 2.0.)
• Vehicle.Driver.IsEyesOnRoad (Has driver the eyes on road or not?)

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

4.1 - AttentiveProbability

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.AttentiveProbability
[get]  OK
Vehicle.Driver.AttentiveProbability: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.AttentiveProbability 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.Driver.AttentiveProbability is a Sensor.

The vehicle signal Vehicle.Driver.AttentiveProbability is a Signal.

UUID

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

The UUID for Vehicle.Driver.AttentiveProbability is fcd202467afb533fbbf9e7da89cc1cee

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

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

4.2 - DistractionLevel

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.DistractionLevel
[get]  OK
Vehicle.Driver.DistractionLevel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.DistractionLevel 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.Driver.DistractionLevel is a Sensor.

The vehicle signal Vehicle.Driver.DistractionLevel is a Signal.

UUID

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

The UUID for Vehicle.Driver.DistractionLevel is cb35ec0b924e58979e1469146d65c3fa

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.3 - FatigueLevel

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.FatigueLevel
[get]  OK
Vehicle.Driver.FatigueLevel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.FatigueLevel 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.Driver.FatigueLevel is a Sensor.

The vehicle signal Vehicle.Driver.FatigueLevel is a Signal.

UUID

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

The UUID for Vehicle.Driver.FatigueLevel is 49b1626295705a79ae20d8a270c48b6b

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.4 - HeartRate

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.HeartRate
[get]  OK
Vehicle.Driver.HeartRate: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.HeartRate 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.Driver.HeartRate is a Sensor.

The vehicle signal Vehicle.Driver.HeartRate is a Signal.

UUID

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

The UUID for Vehicle.Driver.HeartRate is d71516905f785c4da867a2f86e774d93

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.5 - IsEyesOnRoad

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.IsEyesOnRoad
[get]  OK
Vehicle.Driver.IsEyesOnRoad: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.IsEyesOnRoad 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.Driver.IsEyesOnRoad is a Sensor.

The vehicle signal Vehicle.Driver.IsEyesOnRoad is a Signal.

UUID

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

The UUID for Vehicle.Driver.IsEyesOnRoad is 625e5009f1145aa0b797ee6c335ca2fe

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.6 - Identifier

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

UUID

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

The UUID for Vehicle.Driver.Identifier is 89705397069c5ec58d607318f2ff0ea8

Children

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

• Vehicle.Driver.Identifier.Issuer (Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com.)
• Vehicle.Driver.Identifier.Subject (Subject for the authentication of the occupant. E.g. UserID 7331677.)

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

4.6.1 - Issuer

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.Identifier.Issuer
[get]  OK
Vehicle.Driver.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.Identifier.Issuer 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.Driver.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Driver.Identifier.Issuer is a Signal.

UUID

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

The UUID for Vehicle.Driver.Identifier.Issuer is ee7988d26d7156d2a030ecc506ea97e7

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.6.2 - Subject

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.Identifier.Subject
[get]  OK
Vehicle.Driver.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.Identifier.Subject 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.Driver.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Driver.Identifier.Subject is a Signal.

UUID

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

The UUID for Vehicle.Driver.Identifier.Subject is b41ec688af265f10824bc9635989ac55

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

Navigation

Digital Auto: Playground

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

Signal Information

The vehicle signal Vehicle.OBD is a Branch.

UUID

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

The UUID for Vehicle.OBD is 7ad7c512ed5d52c8b31944d2d47a4bc3

Children

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

5.1 - AbsoluteLoad

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Data Type & Unit

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.OBD.AbsoluteLoad is b3dd889a42ce5de9a7904b7196ae325c

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

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

5.2 - AcceleratorPositionD

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Data Type & Unit

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.OBD.AcceleratorPositionD is 7e63256081ac5a7b8a28a6fa3c2c2ff9

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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.3 - AcceleratorPositionE

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Data Type & Unit

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.OBD.AcceleratorPositionE is 4104e7fc25355e25b4522d233565d84b

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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.4 - AcceleratorPositionF

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Data Type & Unit

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.OBD.AcceleratorPositionF is 95f5c2a209a857ff930e2f8e32ac2d3f

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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: