1. Traffic Light Dashboard Display ECE 411 Practicum Project Joe Davis (EE: Analog) Russell Ellis (EE: Analog) JJ Hartley (CE: Computer HW) David Dang (EE: Analog)

3. Problem Or Need  Traffic lights can frequently be difficult to see  In front of the sun.  Blocked by large vehicles.  Lights behind sharp turns.

4. Motivation  According to NHTSA in 2008* ~800k intersection related traffic accidents Majority (>50%) of these accidents attributed to traffic light recognition errors >7400 were fatal  Increase Traffic Safety  Save Lives! * NHTSA. (2010). “Crash factors in Intersection-Related Crashes: An On-Scene Perspective”. DOTCrash factors in Intersection-Related Crashes: An On-Scene Perspective HS 811 366. Washington, DC: National Highway Traffic Safety Administration.

5. Objective  Create a dashboard mounted device that displays relevant traffic light information.  Current light state  Amount of time left for relevant light state  Proof of concept design, not a complete solution!

6. Requirements  Should display accurately and be simple to understand  Low Cost/Power Consumption  Durable/Reliable  Safe, easy to use  Should be able to fit and operate in a vehicle  Software should be easy/readily available.

7. Alternatives  Google utilizes a related design in its driverless car.*  Still susceptible to line of sight  Requires extensive optical algorithms  NHTSA is researching options * Crider, Michael (2012-05-09). Back To Basics: How Google’s Driverless Car Stays On The Road.Back To Basics: How Google’s Driverless Car Stays On The Road. SlashgearSlashgear.

8. Approach  Universal Design  Develop a transmitting board that simulates traffic light  Develop receiving board that displays traffic light information sent from transmitting board

9. Development Tools  PCB123  Atmel Studio 6.0 environment

10. Hardware Design

14. Bill Of Materials

15. Software Design main: setup ports and USART loop1: read and store DIP Switches set changedDIP = 0 store testMode, dash, and streetSelect values loop2: if testMode examine DIP Switch values stored, execute test number else if dash read from USART if byte matches streetSelect display info recieved else //this is streetlight run FSM logic transmit state over USART if DIP Switches changed goto loop1 else goto loop2

16. Software Design

23. IP and Prior Work  Utilized open source code from datasheets

24. Testing  Correct function of individual components  Correct S/W implementation  S/W & H/W test cases  Correct functioning of communications between transmitter/receiver  Power consumption testing  Testing Modes

25. Hardware Design

26. Results/Demonstration  Everything works!

27. Contributions  Joe Davis – Schematic/Layout, SW/HW debug  JJ Hartley – Software design, Layout, SW/HW debug  David Dang – Testing/documentation, SW/HW debug  Russell Ellis – Decoder prototyping, SW/HW debug

28. Lessons Learned  PCB Layout design  Wireless is hard  Order surplus parts  AVR programming  JTAG fuses

29. Q&A

30. Back-up

31. Patent