LED-Outlined Traffic Signs on the ISU Campus

1. LED-Outlined Traffic Signs on the ISU Campus May 07-01 Jacob Bonner Dustin Nekvinda Hieu Pham Brian Schnurr David Wallace

2. System Operation Master On Demand Automatic

3. System Operation Master Start Class Break End Class Break On Demand Automatic

4. Problem description Definitions Acknowledgement Operating Environment Intended Users/Uses Assumptions and Limitations Presentation Outline • Expected End Product • Present Accomplishments • Project Definition of Activities • Resources and Schedule • Closing Material

5. Definitions • Programmable Integrated Chip (PIC) - A small chip that can be programmed to control data flow and overall system functionality. • Manual On Uniform Traffic Control Devices (MUTCD) - The MUTCD defines the standards used by road managers nationwide to install and maintain traffic control devices on all streets and highways. • DOT - Department of Transportation • DPS - Department of Public Safety • FP&M - Facilities Planning and Management • CCEE - Department of Civil, Construction, and Environmental Engineering

6. Introductory Material • Problem Statement • Operating Environment • Intended Users & Uses • Assumptions & Limitations • End Product & Deliverables

7. Rob Stupka Pedestrian traffic is extremely high on campus. Need to alert drivers of pedestrian. The signs have lights that will flash to get the driver’s attention. Problem Statement

8. Iowa State University campus. The signs will be able to stand up to Iowa weather conditions. Solar powered Operating Environment

9. Alert drivers of situations that may involve pedestrians. To allow pedestrians to cross the street more safely. Intended Users/Uses • Iowa State University Department of Public Safety. • Motorists • Students, faculty and visitors to campus.

10. LED cluster in each corner Automatic flashing during regular 10 minute class breaks Solar powered Wireless communication Limitations Assumptions • Sunlight availability • Unprecedented extreme weather conditions • LEDs must be seen at required distances and not blind motorists at night

11. Prototype Two working signs with components. One working master control circuit. Design Report Documentation and schematics Parts list and assembly instructions. End Product & Deliverables

12. Project Activity • Approaches Considered/Used • Accomplishments • Project Activities • Project Definition • Research • Design • Implementation • Testing/Results • Other

13. Approaches Considered/Used • LEDs – 106,200 milli-Candela • Advantages • High level of illumination (925 ft) • Low energy consumption • Disadvantage • High current (90mA) • Flasher-dimmer module • Advantage • Energy saving • DOT regulation – 50 to 60 flash per minute

14. Approaches Considered/Used (cont.) • Evaluated power system options • Hard wired AC • Solar power • Acquired software from May06-06 to calculate solar power needs • Determined necessary battery and panel size • PIC requirements

15. Approaches Considered/Used (cont.) • Programmable integrated chip – PIC16F877A • Advantages • Low cost ($9) • Powerful (RAM, data size, speed)

16. Approaches Considered/Used (cont.)

17. Accomplishments • Sign display • Capture motorist attention • Inform pedestrian • Reliablepower source • Battery - primary • Solar - secondary

18. Accomplishments (cont.) • Communication network • Coordination -transmit/receive • Signal identification • Programmable integrated chip (PIC) • Real time • On demand - pushbutton • Automatic on/off

19. Project Activities (1/6)Project Definition • Composed project plan • Designed physical sign system • Wrote controller software

20. Solar Power Need Calculator

21. Project Activities (2/6)Research • Battery – Seal absorbed glass mat • Advantage • Seal completely • Operating temperature (-25° C to 80° C) • Less maintenance • Disadvantage • More expensive • Big and heavy • Charge controller – SunGuard • Advantage • Improve performance (30% per day) • Over current protection • Over voltage protection • Low cost ($27)

22. Project Activities (2/6)Research (cont.) • Battery • Store power

23. Project Activities (3/6)Design

24. Project Activities (4/6)Implementation • Master system -Using PIC microcontroller’s internal clock for time keeping • Slave system – Using a signaling LED cluster vs. countdown timer. • High cost -$650 to $1,300 • Bulky on the sign • False sense of security

25. Project Activities (5/6)Testing • Three main test areas • Subsystems component testing • Integrated systems testing • Outdoor site testing

26. Project Activities (5/6)Testing - Subsystems

27. Project Activities (5/6)Testing – Subsystem Integration

28. Project Activities (5/6)Testing – Site Testing

29. Project Activities (6/6)Other • Using round tube instead of Telespar • Evaluated software language (C, ASM, JAL)

30. Resources & Schedule • Personal Effort • Financial Requirements • Schedule

31. Personal Effort Total Hours: 975.5

32. Financial Requirements Total Cost: $13,056

33. Schedule

34. Closing Material • Project Evaluation • Commercialization • Additional Work • Lessons Learned • Risk & Risk Management • Closing Summary • Questions

35. Project Evaluation

36. Commercialization • This product is already commercially available. • Around $6,250 • May 07-01 price is much cheaper • Around $1,400 (w/o labor) TAPCO sign May 07-01 sign

37. Additional Work • Audio system for the blind • Logging system for tracking use of system • Proximity sensor to automatically turn the system on • WWVB and Real Time Clock

38. Lessons Learned (1/5)What Went Well • Client-team interaction • Team communication • On schedule throughout most of project • Constantly working even when parts were missing

39. Lessons Learned (2/5)What Did Not Go Well • Delayed arrival of components • Could not get the system installed in time • Testing was delayed • Inadequate research prior to initial ordering • Area researched ≠ area implemented • Communication with supporting departments

40. Lessons Learned (3/5)Technical Knowledge Gained • PIC programming and functionality • Communication technologies • Mechanical engineering skills • MUTCD regulations

41. Lessons Learned (4/5)Non-Technical Knowledge Gained • Project management • Schedule management using Gantt charts • Communication management between multiple departments • DPS • FP&M • CCEE • DOT

42. Lessons Learned (5/5)Things Done Different Next Time • Divide into sub-sections earlier • Make sure components are finalized with client so ordering can take place sooner • Start testing earlier

43. Risk & Risk Management Anticipated potential risks • Loss of team member • Every member knows what the other is doing • Not encountered Unanticipated encountered risks • Flasher/Dimmer module was incorrectly labeled and destroyed. • Team pulled same module from another project • Lack of interest by certain contacts involved with the project. • Client was addressed and assured the team of the project’s importance

44. Closing Summary • System is intended to save lives • Provide a means of warning • No guarantees • Give a chance to avoid tragedy

45. Any Questions?