06.08.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Frequency<br />

100<br />

90<br />

80<br />

70<br />

60<br />

50<br />

40<br />

30<br />

20<br />

10<br />

0<br />

3000<br />

7000<br />

11000<br />

15000<br />

19000<br />

23000<br />

27000<br />

31000<br />

35000<br />

39000<br />

43000<br />

<strong>Truck</strong> Weight [lb]<br />

Fig. 61. <strong>Truck</strong> Total Weight (All <strong>Truck</strong>s, AirWeight Devices on Both the Tractor and Trailer)<br />

6.2.2 Fuel In<strong>for</strong>mation<br />

The main objective of the data analysis <strong>for</strong> this project was to determine the effect of the different<br />

types of tires (i.e., regular duals vs. NGSWBTs) on the fuel efficiency of <strong>Class</strong>-8 trucks. In order to<br />

accomplish this objective, fuel consumption needed to be measured; moreover, to determine fuel<br />

efficiency under different conditions (e.g., peak-hour vs. off-peak, urban vs. rural, etc.) it was<br />

necessary to determine fuel consumption instantaneously. As described elsewhere in this report, the<br />

vehicle databus provided this type of in<strong>for</strong>mation (i.e., the instantaneous fuel consumption rate,<br />

measured in liters/hour) which was captured through one of the data channels (see Table 5) and saved<br />

every 0.2 seconds into the collected in<strong>for</strong>mation database.<br />

It is obvious that to determine the absolute fuel efficiency of any vehicle, the fuel consumption needs<br />

to be measured accurately. At the beginning of the project, it was decided to collect fuel tickets every<br />

time one of the participating tractors was fueled. The fuel ticket in<strong>for</strong>mation (i.e., total number of<br />

gallons of fuel) was to be used to calibrate the observed fuel consumption as reported by the vehicle<br />

databus. The calibration methodology consisted of a comparison of the total fuel consumed obtained<br />

by adding the fuel reported in the fuel tickets against the total fuel consumed obtained from the<br />

collected in<strong>for</strong>mation database <strong>for</strong> the same trip, or series of trips.<br />

Three assumptions were made when this fuel consumption calibration methodology was adopted: 1)<br />

there would not be any gaps in the data collected; 2) the date and time at which the vehicle was fueled<br />

would be recorded; and 3) every time a vehicle was fueled the tank would be completely filled. None<br />

of these assumptions were valid. As described elsewhere in this report, there were instances in which<br />

a participating tractor was not at the company’s parking lot when the researchers were there to<br />

download the data collected and to clear the storage capacity of the on-board data collection<br />

equipment. For such instances, if the DAS’s memory became full, then no more collected data could<br />

be saved, and part of the in<strong>for</strong>mation was lost, thus creating a gap in the in<strong>for</strong>mation. On other<br />

occasions, a sensor (e.g., GPS device) may have malfunctioned <strong>for</strong> some period of time, resulting in<br />

73<br />

47000<br />

51000<br />

55000<br />

59000<br />

63000<br />

67000<br />

71000<br />

75000<br />

79000

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!