ENS2257: MICROPROCESSOR SYSTEMS

PROJECT
Demonstration: 9:00am 12.00pm Wednesday, 19th October 2016
Report Due: 5.00pm Thursday 27th October 2016
This project is worth 20% of the unit mark.
This project is divided into 2 parts. Task 1 is worth 30 marks and Task 2 is worth 20 marks.
There are two parts to the assessment of this project: a demonstration of the solution during
the last class and a project report. Due dates are given above.
This project is meant to be done in team, the same teams as for Assignment 1. Only one
report is required per team.
You will also need to reference all external sources of information.
IMPORTANT: Report Submission Instructions
All project documents should be submitted via Blackboard. The link for submitting the
written section will be activated 2 weeks prior to the deadline.
You should upload a zip file containing:
1) the commented source code files
2) a technical report on all tasks completed in Adobe PDF file (preferred) or Microsoft
Word document format containing:
a) A circuit diagram / schematic diagram showing processor and all components of your
solution. You do NOT need to show standard kit elements like power regulator,
oscillator, LCD interface etc.
b) A brief description of principles of operation and the algorithms used (in the form of
pseudo-code, flow charts or similar), explanation why those methods were used, any
relevant assumptions made, and any special features of the solution
Note: Documentation for each task should be separate sections.
This submission must be made by 5 p.m. on the due date or late penalties of 10% per day
will apply. If a fault in the University network prevents submission by the deadline then
appropriate extensions will be allowed.
N.B. By submitting your assignment electronically you are certifying that the work submitted
is your own work and that any material drawn from other sources has been acknowledged.

PROJECT DESCRIPTION
Microprocessors are used to control a wide variety of devices from commercial appliances to large
industrial plants and complex scientific equipment.
The project is to design a controller for a set of simple pumps in a plant. As it is not feasible to test
your kits on real equipment, we will be modelling the pumps (or rather, the relay switches for the
pumps) using a set of 3 LEDs one red, one yellow and one green. For the purposes of the project
demonstration, turning an LED on represents the corresponding pump being turned on.
Task 1: (Demonstration- 20 marks, Report 10 marks)
Using the lab kit, design a circuit for the processor to control the 3 pumps (LEDs). The system should
be able to receive inputs from a 12-key keypad that will allow users to select one of a series of preset
programs. Each program has a different sequence and timing for the pumps as described below.
Program No

Operation sequence

Red 3 seconds, Yellow 3 sec, Green 4 sec, back to Red (continuous loop)

Green 3 sec, All pumps off - 2 sec, Red 2 sec, All pumps off - 2 sec, back to Green
(continuous loop)

Red 5 sec, stop (this does not loop).

Pressing 4 again should extend the pump run time for another 5 seconds from time
the key is pressed.

Same as Program 4, but for Yellow LED and using 6 to extend run

Red on continuously. Pressing 7 again stops red.

Yellow on continuously. Pressing 8 again stops yellow.

Green on continuously. Pressing 9 again stops green.

The program being run should be displayed on the LCD screen.

Safety Constraints
The system also has to cater for the following safety features/constraints:
1) Only one pump can be turned on at a time.
2) To minimise current surges during pump switching, there should be a 0.5 sec delay between
one pump turning off and the next being turned on.
3) Emergency stop switch: This will be a push button switch to stop the pumps in the event of
an emergency.

Pumps will not run until the emergency has been cleared by pressing the * key on
the keypad.

The system will ignore all other inputs while in this emergency state.

When resuming normal operation, previous program selection is cleared.

Users should be able to select a new program at any point during the normal operation sequence
and the system should switch to the new program, but still comply with the safety constraints
above.
Even though the user interface is limited to the LCD screen and keypad, marks will be given for
making this as user-friendly as possible.

Task 2: (Demonstration- 14 marks, Report 6 marks)

Extend the system in Task 1 to include a user defined option as described below.
1. User calls up the user defined option by selecting 0.
2. User enters how long the RED motor should be on in minutes and seconds (up to 80
minutes).
3. User starts program by pressing #. The appropriate pump is turned on and a countdown
timer is displayed on LCD showing how long is left before pump turns off.
4. If the user presses # before countdown reaches zero, the program is paused. The pump is
turned off, and the countdown timer stops. Pressing # again causes program to resume
pump is turned on and countdown continues.
5. When countdown reaches zero (0 mins and 0 secs), the pump will stop and system comes
out of user program mode.
Note: The system still has to comply with all safety constraints as in Task 1.
Note: You can use your solution to Assignment 1 Task 2 as the basis (design) for this task.

MARKING SCHEME
Task 1 Demo

Total 20 (marks)

Fulfils requirements

13

Circuit well laid out and follows good interfacing principles

User-friendly interface

Innovative features & robustness of program

Task 1 Report

Total 10 (marks)

Well-structured and modular code good use of functions and

procedures, meaningful identifiers, indentation

Clear and meaningful comments in code

Circuit diagram

Description of principles of operation, algorithms, assumptions and

special features

Task 2 Demo

Total 14 (marks)

Fulfils requirements

10

User-friendly interface

Innovative features & robustness of program

Task 2 Report

Total 6 (marks)

Well-structured and modular code good use of functions and

procedures, meaningful identifiers, indentation

Clear and meaningful comments in code

Description of principles of operation, algorithms, assumptions and

special features

~ End ~

Academic Misconduct
Edith Cowan University has firm rules governing academic misconduct and there are substantial
penalties that can be applied to students who are found in breach of these rules. Academic
misconduct includes, but is not limited to:

plagiarism;

unauthorised collaboration;

cheating in examinations;

theft of other students work.

Additionally, any material submitted for assessment purposes must be work that has not been
submitted previously, by any person, for any other unit at ECU or elsewhere.
The ECU rules and policies governing all academic activities, including misconduct, can be accessed
through the ECU website.