Week 14 (Industry Day)

Activity: Project Presentation (INDUSTRY DAY S2 2015)

Objective(s): To present our project to the assessors

Contents:

The Industry Day this semester falls on Wednesday, 16th of December 2015 and it was held at Dewan Gemilang, UniKL BMI. Earlier on week 14, we had seen the name of our assessors which are Sir Azuki and Sir Shaiful with their abbreviations of AAS and MSO respectively. However on Industry Day, Sir Shaiful was unable to make it and he was replaced by Dr. Syed Faiz Ahmed. We presented our project with confidence and with a slight of terrified feeling as the project presentation provides 40% of the carry marks for the subject.

Results/Analysis:

Shahrul on setting up our on Industry Day

Nadzmi with our draft report and the fingerprint device

Our colleagues; from left: Sobri, Nadzmi, Ameer and Shahrul

Conclusion:

Eventually, we have done with the 40% assessment of the Final Year Project. We may now focus on our thesis writing and preparing for the hard cover submission due to Week 17.

Week 13

Acitivity: Preparation for Industry Day S2'2015

Objective(s): To make a preparation and practice on the presentation for UniKL BMI Industry Day

Contents:

Right after the we conducted the experiment, we had started the preliminary writing of the project report. From the draft that we had written, we designed a poster which is required during our presentation of the project on Industry Day next week. We also practiced what we are going to present during the presentation. Plus, we met our supervisor to get some consult on our project and preparation.

Results/Analysis:

Finalised poster design for Industry Day S2 2015

Conclusion:

In conclusion, after the consultation meeting with our lecturer and corrected some details on the poster, we are now prepared to present our project for next week.

Week 12

Activity: Experiment Induction and Results Analysis

Objective(s):
i) To conduct an experiment to measure the efficiency of the development prototype.
ii) To analyse the obtained data for the thesis writing and project presentation.

Contents:

We conducted an experiment based on the procedure that we have planned on earlier. We ran three methods to take student attendance in a tutorial class and a lecture class. The first method is that we use what we call the manual method which is currently being used in the campus; writing student names. The second method is the manual method as well, but is more efficient that the first method which is by calling out student names. The third method is by using the attendance thumbprint device that we have built, but the sample students have to register their fingerprints first and foremost before they can start using the device. This is for the device to recognise the students that are being experimented.

Results/Analysis:

Throughout the experiment, these are the data obtained from the experiment conducted.

Time taken for students to mark attendance in a tutorial class

Time taken for students to mark attendance in a lecture class

The results are being distinguished into two samples of data which are time taken for students to mark attendance in a tutorial class and a lecture class. These two classes have different numbers of students, thus can make a more analysed data to justify the objective of the research and to measure the efficiency of each method.

It was found that between those three methods, marking attendance by using the fingerprint device offers the best service in the terms of having the shortest time consumed to mark attendance, strikes out the act of cheating an attendance and requires zero paperworks.

Conclusion:

In conclusion, it is found that by using fingerprint device in marking students attendance is the best option in substituting the current attendance system in the campus. We can now proceed for the preparation of the project presentation on Week 14 and start to write the thesis for this project.

Week 11

Activity: Experiment planning

Objective(s): To plan an experiment to measure the efficiency of the device.

Contents:

First of all, we discussed identify the limitations of the fingerprint device that we had built. It appears that the device can only register 5 users and 5 days of attendance data to be recorded. Then we list down the variables to be tested in the experiment.

Result/Analysis:

Based on the limitations of the device, we came out with the variables of the experiment. 

Manipulated variable: The method of taking attendance record.

Fixed variable: Number of users and days of taking attendance.

Responding variable: The efficiency of the tested system.

We picked out 5 students among our colleagues to be the samples of the experiment. We also picked out the classes we plan to use to conduct the experiment.

Classes in respect to the days of the experiment

List of users and their names

Conclusion:

In conclusion, we had set up an experiment procedure which will be conducted on the following week.

Week 10

Activity: Project testing and demo

Objective(s): To test the fully programmed device and its features.

Contents:

We test the project to be operating accordingly as based on what we had planned in the flowchart of the program. We then registered our fingerprints to test the fingerprint module. All the fundamental features are to be tested and demo. Any unsuccessful feature will be troubleshooted and overcome the problem.

Result/Analysis:

As we test the project, the fingerprint module appears to be operating successfully. On the startup of the device, it prompts a fingerprint to set up as the admin.

Command display to place a thumb on the module

On a successful cases, the LCD display this message

However, we discovered that the project cannot be stand alone project. It requires the UC00B to be plugged into a USB port to provide a necessity current to run the project. Therefore we planned to use a power bank to provide a power source for the device.

Conclusion:

In conclusion, we are now able to use the device and understood all the features. We may now moving on to the next agenda which is to plan an experiment for a research purpose.

Week 9

Activity: Interface with microcontroller

Objective(s): To load the hex file into microcontroller

Contents:

On previous week, we had gradually completed writing the programming for the project. As the programming has been compiled, the project is built and it created a hex file to load it into the microcontroller. We use the UC00B for interface of the device with the microcontroller. Then a set of procedure is followed from the Internet on "How to load hex file into PIC". 

The following is the link:

http://www.microchip.com/forums/m432845.aspx

the hex file to be loaded into the microcontroller

UC00B is connected to a USB port

Loading the hex file into microcontoller

Result/Analysis:

Now the void in the microcontroller has been programmed with the set of programming now the fingerprint device is ready to be used.

A fully programmed device which is ready to be used

Conclusion:
In conclusion, we learnt how to load a hex file into a pic microcontroller. Plus now we had built a fully functional fingerprint device. We will now proceed on the project features on our next activity.

Week 8

Activity: Continue in writing a C Programming from Mode 5 to Mode 8 by using MPLAB ID Software

Objective(s): To complete the C Programming based on the flowchart.

Content(s):
Since last week, the C Programming has been programmed based on the flowchart starting from Mode 1 until Mode 4, this week will be focused to complete and finished all the C Programming in order to start installing this C Programming and of course to make sure that this programming  will be compatible with the hardware.
Based on this mode, Admin also will be play as an important role to make sure the that all the system will follow as the flowchart.

Result(s):
The continual C Programming starting from Mode 5 till Mode 8.
Mode 5: Change Admin
Mode 6: View Attendance
Mode 7: Clear Attendance
Mode 8: Export

Based on this results, it is shows that the flowchart in case in this attendance thumbprint system the admin will be change. in order to change the admin, the whole attendance can be view and also after a day, the attendance can be clear. since that, the system also will export this attendance to the databased centre to centralized the data and mark the attendance.

The flowchart below shoes that the C Programming of the system starting from Mode 5 to Mode 8:

Mode 5

Mode 6

Mode 7

Mode 8

Conclusion: 
In conclusion, since all of mode C Programming has been setup and combine together, this programming will be synchronized with the hardware which is the project in order to make sure this software programming will be compatible the project hardware or not. If this programming compatible with the hardware, it shows that there is no error in programming and it is can be used in future.

Week 7

Activity: Writing a C Programming from Mode 1 to Mode 4 using MPLAB IDE Software.

Objective(s): To write down the C Programming based on the flowchart.

Content(s):
After 6 week, we have done the process of doing this project and this week we are now focusing on writing the C programming. Basically, we are write this program software is based on the Mode in the flowchart. For this program, it is actually set up by admin. Admin will play the role to set this program from Mode 1 to Mode 4.

Result(s):
Hereby, admin will set up from the operation Mode 1 to Mode 4 which is, the program will be setup:
Mode 1: Set Day
Mode 2: Add a New Data
Mode 3: Delete Data
Mode 4: Delete All Data

Mode 1

Mode 2

Mode 3

Mode 4

Conclusion:
In conclusion, this 4 Mode of flowchart will show the steps that will act by admin in order to run this C program. It should be done by steps in order to make sure there is no coding error while making this program. Quite difficult to fixed it back if has error in the coding.

Week 6

Activity: Drawing the flowchart for the programming

Objective(s): To draw the flowchart to assist us when write the programming.

Contents: 

We sat down for a discussion to generate the idea on how we want the project will be run. Then we drafted the flowchart for the overall program flow. Initially when the project is run, a new admin must be set. Then there will be two modes:

1. Admin mode
2. User mode

Under admin mode, there will be 8 sub modes for the admin to authorise the thumbprint device. The 8 modes are:

1. To set the day
2. Add new user/data
3. Delete a user/data
4. Delete all data
5. Change admin
6. View attendance
7. Clear attendance
8. Export data

Based on the draft, we drew the flowchart for the programming.

Result/Analysis:
The documented flowchart of the programming.

Overall flowchart

Conclusion:
In short, the overall flowchart will describe how the project will run and help us in developing the programming.

Week 5

Activity: Installation of MPLAB IDE and Hi-Tech PICC Lite

Objective(s): 

1. To install the MPLAB IDE editor software in our laptop.
2. To install Hi-Tech PICC Lite compiler software in our laptop.

Contents:

Briefly, MPLAB Integrated Development Environment (IDE) is a comprehensive editor, project manager and design desktop for application development of embedded designs using PIC microcontrollers. Whilst, Hi-Tech software is the third party compilers for PIC10/12/16 and PIC18, dsPIC, PIC24 and PIC32 devices. As for this project, the type of PIC that we are using is the PIC16.

The installation steps:

1. Double click on the Setup Launcher to install MPLAB V8.20a. 

2. The InstallShield Wizard will pop out 

3. After all the directions shown in the welcome note (as in following diagram) is done, click Next> for next step. 

 4. Select I accept the terms of the license agreement if it is not selected in the diagram, and click Next> after this. 

5. Select Complete for the setup type to install all program features, and click Next> to next step. 

6. Choose Destination Location, user is recommended to use the default destination folder, which is C:\Program Files\Microchip\ or user is also free to select the other destination folder by using the Browse... button to browse to the desired destination folder. After that, click Next> for next step. 

7. Select I accept the terms of the license agreement if it is not selected in the diagram, and click Next> after this. 

 

8. Select I accept the terms of the license agreement again for the window shown, and click Next> after this. 

9. Please click Next> for the diagram. 

10. Wait for awhile for the installation process shown in diagram. 

11. A window will pop out if there is any program that did not close at the beginning of the installation, user is recommended to close the entire unnecessary program and click Retry to proceed on the installation. User may also click on Ignore if you need to run the other program concurrently. For this example, Ignore is clicked. 

12. Wait for the installation process to be completed. 

13. A window for Question will pop out, please click OK to proceed with installation of HI-TECH C.. 

14. Please wait for the installation process to be completed. 

15. Please click Finish after successfully installed the HI-TECH C PRO. 

16. The installation of MPLAB V8.20a is completed. Please click Finish to exit. User may need to restart the computer just after the installation or restart later. 

17. After restart computer, a window MPLAB IDE Document Select will pop out, user may view the release notes from Microchip if want to. 

Result/Analysis:
The MPLAB IDE application appeared as in the diagram below and is ready to be used.

The MPLAB IDE will show as in diagram, user may start build your own project.

Conclusion: 
In conclusion, MPLAB IDE will be the platform for us to write the programming using the C language that we have learnt during our earliest semester and Hi-Tech PICC Lite will help us to build the program that we will be writing soon. Finally, the programming softwares are successfully installed in our personal computer.