Abstract

21st Century Truck Partnership whose stretch goals involve a reduction by 50% of the fuel consumption of heavy vehicles on a ton-mile basis. This Medium Truck Duty Cycle (MTDC) Project is a critical element in DOE s vision for improved heavy vehicle energy efficiency and is unique in that there is no other national database of characteristic duty cycles for medium trucks. It involves the collection of real-world data for various situational characteristics (rural/urban, freeway/arterial, congested/free-flowing, good/bad weather, etc.) and looks at the unique nature of medium trucks drive cycles (stop-and-go delivery, power takeoff, idle time, short-radius trips), to provide a rich source of data that can contribute to the development of new tools for fuel efficiency and modeling, provide DOE a sound basis upon which to make technology investment decisions, and provide a national archive of real-world-based medium-truck operational data to support heavy vehicle energy efficiency research. The MTDC project involves a two-part field operational test (FOT). For the Part-1 FOT, three vehicles, each from two vocations (urban transit and dry-box delivery) were instrumented for one year of data collection. The Part-2 FOT will involve the towing/recovery and utility vocations. The vehicles participating in the MTDC project are doing so through gratis partnerships in return for early access to the results of this study. Partnerships such as these are critical to FOTs in which real-world data is being collected. In Part 1 of the project, Oak Ridge National Laboratory(ORNL) established partnerships with the H.T. Hackney Company, one of the largest wholesale distributors in the country, distributing products to 21 states; and with the Knoxville Area Transit (KAT), the City of Knoxville s transit system, operating services across the city of Knoxville and parts of Knox co. These partnerships and agreements provided ORNL access to three Class-7 2005/2007 International day-cab tractors, model 8600, which regularly haul 28 ft pup trailers (H.T. Hackney Co) and three Class-7 2005 Optima LF-34 buses (KAT), for collection of duty cycle data. In addition, ORNL has collaborated with the Federal Motor Carrier Safety Administration (FMCSA) to determine if there were possible synergies between this duty cycle data collection effort and FMCSA s need to learn more about the operation and duty cycles of the second-largest fuel consuming commercial vehicle category in the US. FMCSA s primary interest was in collecting safety data relative to the driver, carrier, and vehicle. In order to collect the duty cycle and safety-related data, ORNL developed a data acquisition and wireless communication system that was placed on each test vehicle. Each signal recorded in this FOT was collected by means of one of the instruments incorporated into each data acquisition system (DAS). Native signals were obtained directly from the vehicle s J1939 and J1708 data buses. A VBOX II Lite collected Global Positioning System related information including speed, acceleration, and spatial location information at a rate of 5 Hz, and communicated this data via the CAN (J1939) protocol. The Air-Weigh LoadMaxx, a self-weighing system which determines the vehicle s gross weight by means of pressure transducers and posts the weight to the vehicle s J1939 data bus, was used to collect vehicle payload information. A cellular modem, the Raven X EVDO V4221, facilitated the communication between the eDAQ-lite (the data collection engine of the system) and the user, via the internet. The modem functioned as a wireless gateway, allowing data retrievals and system checks to be performed remotely. Also, and in partnership with FMCSA, two additional safety sensors were installed on the combination vehicles: the MGM e-Stroke brake monitoring system and the Tire SafeGuard tire pressure monitoring system. Both of these systems posted data to the J1939 data bus, enabling these signals to be read without any additional DAS interface hardware. Seventy-three signals from the different deployed sensors and available vehicle systems were collected. Because of the differences in vehicle data buses (i.e., J1939 and J1708 data buses), not all desired signals were available for both types of vehicles. The s...

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.