Opportunities in ITS Technologies for Hybrid Electric Vehicles

1. Opportunities in ITS Technologies for Hybrid Electric Vehicles Prof. Umit Ozguner The Ohio State UniversityDept. of Electrical and Computer Engineering and Center for Automotive Research Control and Intelligent Transportation Research Lab

2. A review of two parallel developments:1. ITS, specifically Vehicle-to-Vehicle (V2V) Communication issues2. Hybrid Electric Vehicles (and more recently, Plug-In Hybrid Electric Vehicles) CAR: Vehicle-to-Vehicle Communication Consortium

3. Relevant ITS Technologies CAR: Vehicle-to-Vehicle Communication Consortium

4. Transmission using infrastructure (highway or in-city) Vehicle 1 Vehicle 2 ●Transmit incident information which occurred a long distance away. x km CAR: Vehicle-to-Vehicle Communication Consortium

5. Transmission using infrastructure (in city) Traffic light broadcasting timing Vehicle • Transmit red-green signal timing so that upcoming vehicle may slow down. • Transmit GPS correction signal. • Transmit detailed map of intersection. CAR: Vehicle-to-Vehicle Communication Consortium

6. Inter-Vehicle Communication • Sending information regarding forward traffic jam. • Sending information to allow tight following Vehicle 1 Vehicle 2 Traffic Jam Vehicle 1 Vehicle 2 CAR: Vehicle-to-Vehicle Communication Consortium

7. CAR: Vehicle-to-Vehicle Communication Consortium

8. An example from the US: The CICAS-V Program Control and Intelligent Transportation Research Lab

9. Control and Intelligent Transportation Research Lab

10. CAR: Vehicle-to-Vehicle Communication Consortium

11. CAR: Vehicle-to-Vehicle Communication Consortium

12. Relevant CONTROL ISSUES CAR: Vehicle-to-Vehicle Communication Consortium

13. What can we provide HEV’s? • Intersection issues: Stop-and-go traffic (cold start problems). “time to stop”, “time to accelerate” • In-traffic driving: We can generate true “look-ahead speed profiles” (not statistical drive cycles). • We can generate “look-ahead load profiles” based on road grade and other real-time estimates • For plug-in hybrid usage: we can estimate re-charge schedules and locations CAR: Vehicle-to-Vehicle Communication Consortium

14. Control Approaches • One approach to this problem requires the use of the anticipated “effective load” on the vehicle. Our group and others have considered this and preliminary investigations have been reported on simple road-grade effects. Presently we are considering a more general issue of “look-ahead effective load variation” where grade is one (possibly, but not necessarily, dominant) factor. • Many HEV control problems have been formulated as a receding horizon control problem. With an EECC, preview information of road profile and traffic flow information would be assumed to be available for a look-ahead time/distance as the horizon information. An optimal controller can be implemented to minimize fuel consumption by controlling the torque profile for the time horizon. As the car moves forward with preview information control is also updated CAR: Vehicle-to-Vehicle Communication Consortium

15. CAR: Vehicle-to-Vehicle Communication Consortium

16. A TESTBED AT OHIO STATE UNIVERSITY CAR: Vehicle-to-Vehicle Communication Consortium

17. Introducing L-VIS: a VI Communication Testbed at OSU CAR: Vehicle-to-Vehicle Communication Consortium

18. Presently only one Base Station set up. CAR: Vehicle-to-Vehicle Communication Consortium

19. CAR: Vehicle-to-Vehicle Communication Consortium

20. Microhard Spectra 910A900 MHz Modems • 1 Watt, 902-928 MHz, Frequency Hopping with user defined hopping pattern • 115,200 Baud over the air • Range up to 20 miles (line of sight)- significantly less at CAR due to low-lying terrain and surrounding buildings • Single Master (base station) and Multiple Slave (mobile) Units, repeater units are also possible • CRC error detection, forward error correction, encryption with 16 bit key CAR: Vehicle-to-Vehicle Communication Consortium

21. Dlink DWL-AG530 802.11a/b/g Wifi PCI Interface • Commercial Off the Shelf Interface Adapter • Support Windows XP and Linux • High speed network communication at either 2.4 GHz (802.11b/g) or 5.8 GHz (802.11a) • Stand-in for 802.11p or other short distance, high data rate, encrypted communications link • Drivers are open source and may provide significant access to network/MAC layer for customization and experimentation CAR: Vehicle-to-Vehicle Communication Consortium

22. Hardware Testbed: Vehicles • 1999 Honda Odessy Minivan • Rack-mount CPU running Linux and Windows XP and front mounted touch screen display • Roof mounted passenger display • OBD-2 vehicle data bus reader and brake,turn signal, windshield wiper switch detectors • Forward and read laser rangefinders (SICK LMS-221) • Forward radar (Eaton-Vorad) • Differential GPS and fiber optic yaw sensor • Forward and rear cameras • 2006 Highlander Hybrid SUV • Several rack mount CPUs running Linux and QNX • 360 degree surround sensing • Ibeo AlascaXT and Sick LMS-221 (2) • MaCom SRS Radar Sensors (3) • Vision based lane tracking and forward obstacle detection • Differential GPS and high-accuracy 6 DOF FOG IMU • CAN vehicle data bus reader • 1999 Honda Odessy Minivan • CPU running Linux and front mounted touch screen display • Roof mounted passenger display • OBD-2 vehicle data bus reader and brake, turn signal, windshield wiper switch detectors • 1996 Chevrolet Tahoe CAR: Vehicle-to-Vehicle Communication Consortium

23. What about PHEV’s? • Communication needed to determine the location of cars • Communication needed to plan based on the “intent” of cars • Although data regarding payment may be possible through special “plugs” (implying wired ground line connection), the wireless network connection to the car may provide wider possibilities especially with the two points above. CAR: Vehicle-to-Vehicle Communication Consortium

24. Conclusion • We have only scratched the surface of possibilities! CAR: Vehicle-to-Vehicle Communication Consortium