Group Project Part 1: An Automated Traffic System

Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit

Group Project Part 1: An Automated Traffic System

In this part of the project, we’ ll be starting the traffic light system which is the major

assessment task for the second half of this semester. This part of the project will focus on creating an automated traffic light system; i.e. one that does not require pedestrians to

push a button to cross the road but is on a timer instead using combinational logic design.

The project will consist of Two (2) parts; Part A will consist of a simulation to make sure all   logic and system behaviour is correct before attempting part B which will be to deploy your

model to a physical system consisting of a breadboard, LEDs and the Arduino Uno microcontroller platform.

Part A

Begin by using the Counter block (in the DSP System Toolbox) to generate the counter for the traffic light system. Set the counter’s block parameters to the following:

- Count Event: Free Running

- Maximum count: 15

- Initial count: 0

- Output: Count

Use an Integer to Bit Converter block (number of bits per integer = 4) followed by a Demux block (number of outputs = 4) to convert the decimal counter output (Cnt) to individual bits.

Use this binary counter along with Simulink logic blocks and dashboard components to design a Simulink model that:

- Consists of Three (3) traffic lights (red, yellow and green) and Two (2) pedestrian lights (red and green).

- The system should start off by allowing traffic togo for Seven (7) seconds (the green traffic and red pedestrian lights will both be

on, all other lights will be off).

- Next, the system will give the traffic a caution signal for Three (3) seconds (the yellow/amber traffic and red pedestrian lights will

both be on, all other lights will be off).

- Lastly, the pedestrians should be able to cross the road for Six (6)

seconds (the red traffic and green pedestrian lights will be on, all other lights will be off).

-  The system must then reset back to the start and repeat this process.

Use truth-tables and K-maps to find and minimise the Boolean expressions for each light. The inputs will be the bits output from the binary counter: A, B, C, D, where A is the most significant bit (MSB) from the counter and D is the least significant bit (LSB).

Part B

Once you’re happy your simulation is working, and

you’ve troubleshot anything that needs fixing,

replace the simulation blocks (Lamps) with the

appropriate Arduino outputs and deploy this

system to the Arduino Uno hardware. The system

should behave the same as before, but red, green,

and yellow LEDs should light up instead of the

simulated lamps.

Your final documentation (report) MUST include

evidence of you having simulated your system first

and then that the hardware implementation worked correctly (photographs from your in- class demo will suffice for this).

Due date and further details on this task:

The first part of your group project must be demonstrated to your tutor during your practical class in week 10.

The documentation for this part of the project (including the design methodology and     evidence of simulating and testing your system) is due as part of the final report for this project, due at the end of week 13 (Friday, before 11:59pm).

You’ ll be required to submit your Simulink model files (.slx file format) to Canvas along with your report (.docxor .pdf file). More details on this can be found on Canvas under Modules -> Week 1 -> Assessment Task Instructions (IMPORTANT) -> Group Project Instructions.

Part 1 of this project should consist of the automated traffic light system utilising a counter. To fulfil the requirements, you need to do the following:

-     Implement a counter in Simulink that counts from 0 – 15 in a repetitive manner.

-     Ensure you’ve simulated your system first using the Simulink Dashboard

components. Lamps must work in a two state, active high implementation only to reflect how the actual hardware works (i.e. The Dashboard Lamps must come on    when a 1 (HIGH) is detected and must be off when a 0 (LOW) is detected).

-     Ensure your system has been deployed to the Arduino Uno and can drive the LEDs as per the above specifications, this should not be a simulation only. Again,

implementation must be active high (LEDs will come on for a 1 and be off for a 0).

-     Your model must not consist of any Stateflow blocks to perform these tasks.

-     Your breadboard should be wired neatly.