Class-8 Heavy Truck Duty Cycle Project Final Report - Center for ...

Significant research has been accomplished by this partnership and recent discussions have focused
on the development of an integrated demonstrator (tentatively called SuperTruck) that reflects the
results of the 21CTP research, and that can be utilized for testing and evaluation via simulation
modeling, test track testing, and field operational testing. ORNL has engaged in discussions with
DOE on utilizing the HTDC data and duty cycles as a baseline for comparison with the SuperTruck
testing and evaluation results.
1.1.3.4 Industry/academia interests
ORNL has received a number of inquiries from industry requesting data and information that was
generated by the HTDC project. These requests included the following:
• Duty cycle and situational data for input into an industry developed engine model, and fuel
consumption data for comparison to modeling results.
• Long-duration duty cycle data for input into a model of heavy hybrid performance.
Subsequently, the HTDC fuel efficiency data would be a benchmark against which the results
of the heavy hybrid model could be compared.
• Grade and position data as a basis for understanding driver steering behavior
• Duty cycle and situational data for input into heavy hybrid control module that incorporates
terrain features for optimal control.
• Use of HTDC data to assess characteristics of long-haul driver behavior.
• Use of HTDC data to characterize long-haul performance (e.g., percent of time spent in
congestion, time spent in various speed categories, idling time, etc.).
1.2 DATA COLLECTED DURING PHASE 1 (PILOT TEST)
Early in Phase 1, a meeting was held between ORNL’s engine specialists and the duty cycle research
team. It was determined that an attempt would be made to collect emissions data from a real-world
operating truck using laboratory-quality sensors. It was determined that mass air flow data would be
taken from the vehicle’s data bus, exhaust temperature would be taken using a type-K thermocouple
installed in the exhaust manifold, and NOx would be measured in the combined exhaust stream. This
data would be part of the data suite to be collected by the Pilot Test vehicle.
A finalized set of 106 channels of data was formulated and reviewed by DOE, the research team, and
engine and modeling experts at ORNL and ANL. The list was finalized in July, 2005, and a list of
these channels and their descriptions are presented in Table 1. Additional information regarding these
channels is given in a more comprehensive table in Appendix A (p. A-29ff).
Table 1. Pilot Test List of Signals
Data # Performance Measure Benefit of the Performance Measure Units
Scan Rate
(Hz)
1 Date and Time Time Reference EST 100
2 Latitude Route Identification; Mapping deg 10
3 Longitude Route Identification; Mapping deg 10
4 Altitude Route Mapping; Road Grade deg 10
5 North Velocity Vehicle Speed Vector km/h 10
6 East Velocity Vehicle Speed Vector km/h 10
7 Down Velocity Vehicle Speed Vector km/h 10
8 Forward Velocity Vehicle Speed Vector km/h 10
9