SummaryEcoTrakRecord

Time that the first ignition on ping was received

Time that the last ignition on ping was received

Time in between StartTime and EndTime when the ignition is off

Total seconds that the ignition has been on. If CANBus data is available, RPM is also checked to be > 0. This is done to (where available) disclude time that the vehicle spends in accessory mode.

Running time spent stationary and not using PTO for a contiguous period of time in excess of the IdleThreshold assigned to that vehicle.

Running time spent stationary that a PTO signal has been broadcast on the CANBus for

Running time spent stationary that the engine's RPM registers as between the minimum PTO RPM and maximum PTO RPM assigned to that vehicle. This is sometimes used over PTOEngagedTime as some vehicle models are known to broadcast a spurious CAN signal

Running time spent stationary that a binary sensor fitted to the vehicle and configured in SupaTrak as PTO reads positive. These are often used if it is not feasible to read data from the CANBus or if full waste body integration is not feasible.

Time when PTO is active (precedence across the previous three properties is taken in reverse order, i.e. PTOInputTime first, PTOEngagedTime last). This is not done because PTOEngaged time is the least accurate (often it is the most preferable), but because if the installation on the vehicle is using one of the other two methods then it is likely that data from the CANBus may be unreliable.

Time when PTO is active (precedence across the previous three properties is taken in reverse order, i.e. PTOInputTime first, PTOEngagedTime last). This is not done because PTOEngaged time is the least accurate (often it is the most preferable), but the vehicle is not stationary (unlike all other forms of PTO time.

Running time when the vehicle is not idling or using PTO.

Driving time when the CANBus is broadcasting a cruise control signal.

Driving time when the vehicle's engine RPM value registers as between a MinOptimumRPM and MaxOptimumRPM value assigned to the vehicle.

Driving time when the engine's RPM exceeds a threshold value assigned to the vehicle.

Driving time when the vehicle's speed exceeds (depending on account-level configuration) either a threshold set against the vehicle or the signposted road speed; a multiplicative and static offset can be applied to this (e.g. SpeedLimit * 1.1 + 2), but this is rarely utilised.

Driving time when the throttle position exceeds a threshold value assigned to the vehicle.

Driving time when acceleration g-force exceeds a threshold value assigned to the vehicle.

Driving time when braking g-force exceeds a threshold value assigned to the vehicle.

Driving time when cornering g-force exceeds a threshold value assigned to the vehicle.

Driving time when engine load exceeds a threshold value assigned to the vehicle.

Driving time when the throttle position is less than 1%, cruise control is off and the vehicle is moving at > 1 MPH for a contiguous number of seconds (default: 3 seconds) assigned to the vehicle.

Driving time outside of working hours time range assigned to the driver.

Driving time when the vehicle has reported a CrashLog, a high negative z-axis gforce event (default 1.2g).

Average speed in MPH for this record - CANBus wheel speed is used where available with GPS speed as a fallback.

Maximum speed in MPH for this record - CANBus wheel speed is used where available with GPS speed as a fallback.

Total distance for this record as measured by GPS. Second-level interpolation is used where available, otherwise point to point distance between device messages is used.

First odometer value recieved for this record.

Last odometer value recieved for this record.

Total distance for this record according to the vehicle's odometer.

Total volume of fuel to have passed through the vehicle's injectors for this record.

Total carbon output for this record - calculated by FuelUsed * CarbonCoefficient. Coefficient values come from DEFRA annually.

Measurement of the average engine load for this record.

Count of the number of times that the vehicle's brake has been applied for this record.

Target MPG assigned to the vehicle

Unique integer key for the record. Please note that if a user needs to work with multiple accounts, these will be unique only by account only, not globally.

A unique ID representing a vehicle.

The Asset Name visible on the SupaTrak portal of the asset from which the data on the record was collected.

The date that for the data on the record was collected. Though a time component is held, it will always have a value of zero.

A unique ID representing a driver.

The driver identified as using the asset for the date aforelisted. This field will be string.Empty if DriverID has not been used (Keyfob, Tacho card, etc) and if multiple drivers are detected using an asset on one given day there will be one record per driver.