31
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)

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

Embed Size (px)

Citation preview

Traffic Light Dashboard DisplayECE 411 Practicum Project

Joe Davis (EE: Analog)

Russell Ellis (EE: Analog)

JJ Hartley (CE: Computer HW)

David Dang (EE: Analog)

Problem Or Need Traffic lights can frequently be difficult to see

In front of the sun.

Blocked by large vehicles.

Lights behind sharp turns.

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”. DOTHS 811 366. Washington, DC: National Highway Traffic Safety Administration.

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!

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.

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.Slashgear.

Approach Universal Design

Develop a transmitting board that simulates traffic light

Develop receiving board that displays traffic light information sent from transmitting board

Development Tools PCB123

Atmel Studio 6.0 environment

Hardware Design

Hardware Design

Hardware Design

Bill Of Materials

Software Designmain:setup ports and USARTloop1:

read and store DIP Switchesset changedDIP = 0store testMode, dash, and streetSelect values

loop2:if testMode

examine DIP Switch values stored, execute test numberelse if dash

read from USARTif byte matches streetSelect

display info recievedelse //this is streetlight

run FSM logictransmit state over USART

if DIP Switches changedgoto loop1

elsegoto loop2

Software Design Software Design

Software Design

Software Design

Software Design

Software Design

Software Design

IP and Prior Work Utilized open source code from datasheets

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

Hardware Design

Results/Demonstration Everything works!

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

Lessons Learned PCB Layout design

Wireless is hard

Order surplus parts

AVR programming JTAG fuses

Q&A

Back-up

Patent