You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The question is when is the in-vehicle compute platform online and able to sample data? Various data points are desired at the time the vehicle starts, the majority (see list below) are not incredibly time sensitive and can be collected when the environment is ready.
From the initial set of recommended data points (in a spreadsheet for now) only one is time sensitive. It is desired to sample 12V DC voltage (Vehicle.LowVoltageBattery.CurrentVoltage) for first couple minutes after crank on ICE vehicles, so a pronounced delay (even 10s) will mean loss of data that would impact assessment of battery and alternator health.
TCU or other might not be finished booting and receiving data until after ignition, missing the Vehicle.LowVoltageSystemState='START' event altogether. We need some other event to base sampling on. In defining it would a VSS signal help, in-vehicle.compute-environment='READY'? We could leave to implementations but inconsistency can lead to degradation of data quality/usefulness.
The question is when is the in-vehicle compute platform online and able to sample data? Various data points are desired at the time the vehicle starts, the majority (see list below) are not incredibly time sensitive and can be collected when the environment is ready.
From the initial set of recommended data points (in a spreadsheet for now) only one is time sensitive. It is desired to sample 12V DC voltage (Vehicle.LowVoltageBattery.CurrentVoltage) for first couple minutes after crank on ICE vehicles, so a pronounced delay (even 10s) will mean loss of data that would impact assessment of battery and alternator health.
TCU or other might not be finished booting and receiving data until after ignition, missing the Vehicle.LowVoltageSystemState='START' event altogether. We need some other event to base sampling on. In defining it would a VSS signal help, in-vehicle.compute-environment='READY'? We could leave to implementations but inconsistency can lead to degradation of data quality/usefulness.
Partial list
Vehicle.VehicleIdentification.VIN
Vehicle.Powertrain.CombusitionEngine.OilLifeRemaining
Vehicle.Powertrain.CombustionEngine.EngineOilLevel
Vehicle.Powertrain.CombustionEngine.EngineHours
Vehicle.Service.TimeToService
Vehicle.Powertrain.CombustionEngine.IdleHours
Vehicle.Service.DistanceToService
Vehicle.TraveledDistance
Vehicle.Chassis.ParkingBreak.IsEngaged
Vehicle.OBD.FuelType
Vehicle.Powertrain.CombustionEngine.IdleHours
The text was updated successfully, but these errors were encountered: