F16: Real Time Traffic Control System (RTTCS)
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Project Title
Real Time Traffic Control System (RTTCS)
Abstract
This section should be a couple lines to describe what your project does.
RTTCS converts our cyclic time-based traffic light system into an efficient queue based system where
intersections are managed by the physical presence of vehicles rather than timed cycles. It reduces the
amount of useless-repetitive braking and/or idling by detecting real time traffic flow and making a
decision based on the environmental inputs of the detection system.
Objectives & Introduction
Show list of your objectives. This section includes the high level details of your project. You can
write about the various sensors or peripherals you used to get your project completed.
Objectives:
-Learn and incorporate the various RTOS resources for overall system design
-Map out the software state machine diagram
-Design RTTCS physical layer
-Compile a Bill of Materials (BOM)
-Manufacture the prototype and test for reliability
-Record and document results for analysis and reports
-Develop product proposal presentation (Powerpoint, Video, Website/Report)
Team Members & Responsibilities
- Brian Josefowicz
- Jonathan Arroyo
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the
project. Then in another table column, write down the actual schedule so that readers can see the
planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if
they are doing a similar project.
| Week# | Date | Task | Actual | Comments |
|---|---|---|---|---|
| 1 | 11/2 | Perform research on FreeRTOS resources. Layout the required applications. Apply the FreeRTOS concepts to these applications. Begin hardware/circuit design. Specify parts required. | Overdue | ... |
| 2 | 11/11 | Design the System State Machine including, states, conditions, transitions, and control signals. Order parts and materials. Layout software logic diagram, and pseudocode. | Overdue | ... |
| 3 | 11/18 | Begin software development. | Pending | |
| 4 | 11/25 | Begin manufacturing. Continue with software development. | Pending | |
| 5 | 12/02 | Complete manufacturing. Begin software testing. Begin Presentation development. | Pending | |
| 6 | 12/09 | Complete software testing and development. Complete presentation production | Pending | |
| 7 | 12/16 | Rehearse final demonstration. Revise and edit any presentation material needed. | Pending | |
| Last Day | 12/20 | Demonstrate full system functionality. Present project. | Pending |
Parts List & Cost
| Item# | Nomenclature | Qty | Cost($) | Details (mfr, pn, etc.) |
|---|---|---|---|---|
| 1 | IR Sensor | 4 | unk | unk |
| 2 | SJOne Development Board | 2 | unk | unk |
| 3 | Set of LED's (Red, Yellow, Green) | 4 | unk | unk |
| 4 | Vehicle Controllers | 2 | unk | unk |
| 5 | Power-Slide Set with 90 deg cross section | 1 | 160 | Scalextric Item Code: C1343T |
General Hardware x Bolts x Screws x Nuts
Materials (x) ft - hook-up wire (x) ft - Road tracks
Electrical Components (Resistors, Capacitors, MOSFETs, etc.)
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-
sections that go over your design and implementation.
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can
discuss your driver implementation here, such that the Software Design section is isolated to talk
about high level workings rather than inner working of your project.
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are
using, and what they are doing at a high level. Do not show the details of the code. For example, do
not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are
showing DESIGN of your software, not the inner workings of it.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you
can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory
onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your
project can be started from scratch again?
Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
My Issue #1
Discuss the issue and resolution.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what"
part here to indicate what you ultimately learnt from this project. How has this project increased your
knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
List any references used in project.
Appendix
You can list the references you used.
