Portable Fingerprint Attendence System

PORTABLE CLASSROOM ATTENDANCE SYSTEM
AN ISO 9001:2015 CERTIFIED TRAINING INSTITUTION
NETTUR TECHNICAL TRAINING FOUNDATION
PROJECT REPORT
On
PORTABLE CLASSROOM ATTENDANCE

SYSTEM BASED ON NODEMCU & FINGERPRINT
BIOMETRIC
PROJECT DONE BY
HARIKRISHNAN S SU 15 16 015
GAUTAM RAJ R SU 15 16 013
GOWSIKRAM V SU 15 16 014
ADARSH KS SU 15 16 003
B.Eng. IN MECHATRONICS
NTTF ELECTRONICS CENTRE
ELECTRONICS CITY, BANGALORE-560100
B.Eng. IN MECHATRONICS 1
2016-2019
AN ISO 9001:2015 CERTIFIED TRAINING INSTITUTION
NETTUR TECHNICAL TRAINING FOUNDATION
CERTIFICATE
This is to certify that the Project titled
PROJECT REPORT ON
PORTABLE CLASSROOM ATTENDANCE
SYSTEM BASED ON NODEMCU & FINGERPRINT
BIOMETRIC
is a bonafide report of Project done by
HARIKRISHNAN S SU 15 16 015
GAUTAM RAJ R SU 15 16 013
GOWSIKRAM V SU 15 16 014
ADARSH KS SU 15 16 003
IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR THE AWARD OF BE.

Eng.IN MECHATRONICS UNDER THE INSTITUTION NETTUR TECHNICAL TRAINING F
OUNDATION, STEINBIS UNIVERSITY PROGRAM CENTRE, BANGALORE DURING THE
ACADEMIC YEAR 2016-2019.
PROJECT INCHARGE COURSE INCHARGE
PRINCIPAL EXTERNAL EXAMINER
ACKNOWLEDGEMENT
We would like to take this opportunity to mention a few names, without

whom, our project would not be successful. To begin with, we would
like to thank our Principal, Mr. Gibbson M for his constant
encouragement and words which pushed us to do better.
Our Unit Head Mr. C V Madhu & SU15 Head Mr. A A Ghori for
their observations and suggestions. A very vital support from our
Project Coordinator EDLA BLESSY PHOBIA, SHYAM who continuously
helped us by allowing us time, place and guidance to complete the
project.
A moment to appreciate our project in-charges, who were
remarkable with their knowledge, patients and wisdom, EDLA BLESSY
PHOBIA, SHYAM for their endurance and advices would never let us go
down. They provided us with continuous guidance and support.
We would like to thank all our teaching and non-teaching staff who
have helped us throughout our Mechatronics System Design project
within the given time period.
CHAPTER 01
ABSTRACT
Biometric student attendance system increases the efficiency of

the process of taking student attendance. This paper presents a
simple and portable approach to student attendance in the form of an
Internet of Things (IOT) based system that records the attendance
using fingerprint based biometric scanner and stores them securely
over cloud.
This system aims to automate the cumbersome process of
manually taking and storing student attendance records. It will also
prevent proxy attendance, thus increasing the reliability of
attendance records. The records are securely stored and can be
reliably retrieved whenever required by the teacher.
INTRODUCTION
Attendance plays a major role in educational institutions. The

most common means of taking attendance in the classroom is by
calling out the roll numbers of students or asking the students to
manually sign the attendance sheet, which is passed around during the
lecture. The process of manually taking and maintaining the
attendance records becomes highly cumbersome.
Biometric systems have reached a sufficiently advanced stage
where in they can now be deployed in systems without hampering
portability. With the recent development of various cloud-based
computing and storage systems, data can be securely stored and
retrieved whenever required. Primarily, fingerprints and iris images are
considered to be the most reliable for use in biometric systems.
A system that records the attendance making use of biometric
scanners and stores them securely over cloud and shows the
attendance in an android application called Blynk can help resolve
issues.
The system consists of a fingerprint scanner which is used for
ascertaining a student’s identity. If the fingerprint scanned matches
with the fingerprint saved in the program, the attendance of the
student will be displayed on the application screen and can be stored
for future purposes.
CHAPTER 02
PROJECT IN BRIEF
2.1 AIM
The aim of the project is design and development of a portable classroom

attendance system based on fingerprint biometric.
2.2 PROJECT OBJECTIVE
 Record attendance for academic purposes.

 Prevent queueing while taking attendance.
2.3 PROJECT TARGET
To reduce queuing and preserve data integrity.
CHAPTER 03
BLOCK DIAGRAM
POWER SUPPLY CIRCUIT MODULE

MODULE1
230V/50Hz AC 12V,1A
STEP DOWN RECTIFIER FILTER 7805
TRANSFORMER REGUALATOR
OUTPUT 5V DC
CONTROL CIRCUIT MODULE:
MODULE3 M0DULE2
5V/1A
3.6V/120mA
N
FINGERPRINT O
SCANNER D
E
M
C MODULE4
U
3.3V/800mA 5V/0.5A
RTC
MODULE
ANDROID
CHAPTER 04
BLOCK DIAGRAM DESCRIPTION
MODULE1: POWER SUPPLY DESIGN
 It consists of a 12V / 1.3Ah battery.

 Battery is used as power source of the controller and other
modules.
 Power supply is used to supply the required power to all the
modules.
 It consists of 5v regulator.
 The desired output voltage for certain modules are obtained using
a regulator.
 The IC7805 provides an output of 5V / 1A.
 5v power is used to give a supply for RTC module, fingerprint
module and NodeMCU.
MODULE 2: ESP8266 NODEMCU
 It is the controller and wi-fi module.

 The specification is 3.6-5V, 12mA.
MODULE 3: FINGERPRINT SCANNER MODULE
 It senses the fingerprint of a person.

 The specification of this module is 3.3-6V,1mA.
MODULE 4: RTC MODULE

 It is a real-time clock.
 The specification is 3.3-5.5V, 300µA.
CHAPTER 05
MODULE-1
POWER SUPPLY
CONTENTS
 5.1 Introduction
 5.2 Description
 5.3 Circuit diagram
 5.4 Bill of materials
5.1 Introduction
A power supply is an electrical device that supplies electric

power to an electric load. The primary function of a power supply is to
convert electric current from a source to the correct voltage, current,
and frequency to power the load. As a result, power supplies are
sometimes referred to as electric power converters. Some power
supplies are separate standalone pieces of equipment, while others
are built into the load appliances that they power. Examples of the
latter include power supplies found in desktop computers and

consumer electronics devices. Other functions that power supplies
may perform include limiting the current drawn by the load to safe
levels, shutting off the current in the event of an electrical fault,
power conditioning to prevent electronic noise or voltage surges on
the input from reaching the load, power-factor correction, and storing
energy so it can continue to power the load in the event of a
temporary interruption in the source power (uninterruptible power
supply).
All power supplies have a power input connection, which

receives energy in the form of electric current from a source, and one
or more power output connections that deliver current to the load.
The source power may come from the electric power grid, such as an
electrical outlet, energy storage devices such as batteries or fuel
cells, generators or alternators, solar power converters, or another
power supply. The input and output are usually hardwired circuit
connections, though some power supplies employ wireless energy
transfer to power their loads without wired connections. Some power
supplies have other types of inputs and outputs as well, for functions
such as external monitoring and control.
5.2 DESCRIPTION
 Step down transformer gives 12V/2A.

 AC to the bridge rectifier formed by diodes.
 Rectifier will convert AC to DC.
 Capacitor is introduced to filter the ripples of converted DC, so

it used as filter as well as backup capacitor.
CIRCUIT DIAGRAM
 Most of the logic and digital circuit will work only at a

voltage less than 230V.
 That is why we are using a step-down transformer in a
power supply.
12V
VVV
VVV
BRIDGE RECTIFIER:
 To convert an AC signal into a DC signal we are using
rectifier circuit.
 Which is build-up of diodes and the circuit may contain
ripples.
FILTER CIRCUIT:
 To remove the ripples, we are using filter circuit which is
built up of capacitors.
REGULATOR:
 We are using regulator ICs to maintain a constant output
voltage in a power supply circuit.
 We use regulator IC 7805 for getting 5V output.
IC 7805 voltage regulator
 The IC7805 is simple to use.

 Connect the positive lead from unregulated DC power
supply to the input pin, connect the negative lead to the
common pin and then turn on the power, a 5-volt supply
from the output pin will be obtained.
OUTPUT:
 The output of power supply is 5V DC/1A.
5.2 BILL OF MATERIALS (POWER SUPPLY)
SL.NO CONPONENTS SPECIFICATION QUANTITY PRICE(Rs)

1 DC JACK 1 12
2 STEP DOWN 12V,2A 1 270
TRANSFORMER
3 DIODE IN4007 4 8
4 REGULATOR LM7805 1 9
6 CAPACITOR 470µF,25V 1 10
7 LED RED,5mm 1 1
8 RESISTOR 100Ω 1 1
9 JUMPER Male-Female 12 88
WIRES
10 BATTERY LEAD 1 400
ACID,12V,1.3Ah
TOTAL PRICE=799
CHAPTER 7
MODULE 2:
CONTROLLER AND WI-FI UNIT
(NODE MCU-ESP8266)
CONTENTS
 7.1 DESCRIPTION
 7.2 PIN DIAGRAM
 7.3 SCHEMATIC DIAGRAM
 7.4 BILL OF MATERIALS
IMAGE
7.1 DESCRIPTION
 ESP8266 is one of the most popular Wi-Fi module available in
the market, allowing makers to develop IoT products with
ease.
 However, a lot of projects require hard coding the Wi-Fi

credentials into the device module, which is fine for
prototyping but if your devices are sent to remote locations
then the Wi-Fi credentials will have to be changed resulting in
reprogramming the device.
 This issue is further increased if you are developing a

commercial product for the open market of IoT.
 WIFI Manager has since been designed to resolve these
issues.
 Initially when you power up your ESP8266 module you will

see it as an access point, which you can then connect to it
using wither your smart phone or computer device.
 Then you can configure the WIFI credentials and connect it
to your local WIFI network using the web interface.
 This method is not uncommon on IoT devices but it is one
which hasn’t featured on the ESP8266 module before.
FEATURES
• 802.11 b/g/n
• Integrated low power 32-bit MCU
• Integrated 10-bit ADC
• Integrated TCP/IP protocol stack
• Integrated TR switch, balun, LNA, power amplifier and
matching network
• Integrated PLL, regulators, and power management units
• Supports antenna diversity
• WIFI 2.4 GHz, support WPA/WPA2
• Support STA/AP/STA+AP operation modes
• Support Smart Link Function for both Android and iOS
devices
• SDIO 2.0, (H) SPI, UART, I2C, I2S, IR Remote Control, PWM,
GPIO
• STBC, 1x1 MIMO, 2x1 MIMO
• A-MPDU & A-MSDU aggregation & 0.4s guard interval
• Deep sleep power <10uA, Power down leakage current <
5uA
• Wake up and transmit packets in < 2ms

• Standby power consumption of < 1.0mW (DTIM3)
• Operating temperature range -40C ~ 125C
FCC, CE, TELEC, WIFI Alliance, and SRRC certified
WORKING
 When your ESP starts up, it sets it up in Station mode and
tries to connect to a previously saved Access Point
 If this is unsuccessful (or no previous network saved) it
moves the ESP into Access Point mode and spins up a DNS
and Webserver (default ip 192.168.4.1)
 Using any Wi-Fi enabled device with a browser (computer,
phone, tablet) connect to the newly created Access Point
 Because of the Captive Portal and the DNS server you will
either get a 'Join to network' type of popup or get any domain
you try to access redirected to the configuration portal
 Choose one of the access points scanned, enter password,
click save
 ESP will try to connect. If successful, it relinquishes control
back to your app. If not, reconnect to AP and reconfigure.
MAJOR APPLICATIONS
• Home Appliances
• Home Automation
• Smart Plug and lights

• Mesh Network
• Industrial Wireless Control
• Baby Monitors
• IP Cameras
• Sensor Networks
• Wearable Electronics
• WIFI Location-aware Devices
• Security ID Tags
• WIFI Position System Beacons
MCU
 ESP8266EX is embedded with Ten silica L106 32-bit micro
controller (MCU), which features extra low power consumption
and 16-bit RSIC.
 The CPU clock speed is 80MHz. It can also reach a maximum
value of 160MHz.
 Real Time Operation System (RTOS) is enabled. Currently, only
20% of MIPS has been occupied by the WIFI stack, the rest can
all be used for user application programming and development.
 The following interfaces can be used to connect to the MCU
embedded in ESP8266EX:
1. Programmable RAM/ROM interfaces (bus), which can be
connected with memory controller, and can also be used to
visit external flash;
2. Data RAM interface (dBus), which can connected with
memory controller;
3. AHB interface, can be used to visit the register.
PIN CONFIGURATION EXPLANATION
Symb Min Max Unit

Variables ol
Input Low Voltage VIL -0.3 0.25× V
VIO
Input High Voltage VIH 0.75× 3.3 V
VIO
Input Leakage Current IIL 50 nA
Output Low Voltage VOL 0.1×VI V
O
Output High Voltage VOH 0.8×VI V

O
Input Pin Resistance Cpad 2 pF

Value
VDDI VIO 1.8 3.3 V
O
Maximum Driving IMAX 12 mA
Power
Temperature Tamb -40 125 °C
 All digital IO pins are protected from over-voltage with a snap-

back circuit connected between the pad and ground.
 The snap back voltage is typically about 6V, and the holding
voltage is 5.8V. This provides protection from over-voltages and
ESD.
 The output devices are also protected from reversed voltages
with diodes.
7.2 PIN DIAGRAM
7.3 SCHEMATIC DIAGRAM
7.4 BILL OF MATERIALS:

NODE MCU
1 NODE MCU ESP 1 340

8266,5V/1A
WIFI MODULE
3.6-5V,12Ma
2 LED RED, GREEN 1 each 2
5mm
3 RESISTOR 10kΩ, 2 10
220Ω 2
TOTAL PRICE=352
MODULE 3:
FINGERPRINT SCANNER
CONTENTS
 6.1 DESCRIPTION
 6.2 SCHEMATIC DIAGRAM
 6.3 PIN DIAGRAM
IMAGE
6.1 DESCRIPTION
 As we enter the new millennium, identification is used for
almost everything nowadays.
 With technology on a rapid pace of improvement, the need
for accurate identification is very necessary, especially with
the increased use of automated transactions.
 Fingerprint scanners are security systems of biometrics.
 They are used to unlock doors and in other security
applications.
 During the 2010s fingerprint scanners became
commonplace on mobile phones.
 Humans have certain unique properties to them.
 The study of these properties is called biometrics.
 Biometrics is the ability to automatically recognize a person
using distinguishing traits such as fingerprints, face, retina
or iris from the eye, voice, and hand geometry.
 Attributes such as cost, size, reliability, operating

environment, speed and accuracy help determine the
suitability for different applications.
 The use of fingerprint recognition has existed as a means
of identification for many years.
 Not only fingerprints are more accessible, but also
fingerprint recognition systems generally have lower costs,
faster speed, and more reliability compare to other
biometric recognition methods.
 Each person has a different pattern of fingerprint, and
these patterns are made of ridges, which make loops and
whirls that are unique to each person.
Figure 1 Different types of prints: arch, loop, whirl
 Fingerprints are commonly classified as 5 different types: whorl,

left loop, right loop, arch, and tented arch.
 For most recognition systems, difficulties arise in distinguishing
between fingerprints of the same type.
IMAGE ORIENTATION
 A major obstacle in fingerprint recognition is that the images

obtained are not usually perfectly aligned.
 Usually rotation and displacement of some sort is evident.
 Attempting to compare two fingerprints with different

orientations will affect the result significantly.
 To adjust for this, rotation of the input image is performed.
Types
Optical reflexive
 They are based on the oldest technique, that consists of placing

your finger on a glass surface or a prism that is illuminated by a
led diode.
 When the ridges of fingerprints touch the surface, the light is

absorbed, while between these crests a total reflection occurs.
 The resulting light and dark areas are recorded in an image

sensor.
 The unit has a considerable size, impractical and expensive.
 This system is easy to cheat and if the skin is damaged, the

fingerprint is not recognized correctly. The recognition of the
fingerprint of older people is also difficult to do because the skin
is not elastic enough.
 In some circumstances, this may result in false recognition. If

the stored fingerprint was taken with less pressure, false
acceptances may occur.
Capacitive
 The sensor is a silicon integrated circuit with a surface that is

covered by a large number of transducer elements (or pixels),
with a typical resolution of 500 dpi.
 Each e0lement contains two adjacent metal electrodes.
 The capacity between the electrodes, which forms a feedback

path for an inverting amplifier, is reduced when the finger is
applied to said surface: it is further reduced when it detects
ridges and less reduced when it detects the space between
them.
 The sensor is susceptible to electrostatic discharge.
 These sensors only work with normal healthy skins, they are
not operative being used on skins with hard areas, calluses or
scars. Moisture, grease or dust can also affect its operation.
Mechanical
 It consists of tens of thousands of tiny pressure transducers

that are mounted on the surface of the sensor.
 An alternative design uses switches that are closed when

pressed by a ridge, but that stay open when they are under a
valley.
 This only provides one bit of information per pixel, instead of

working with a gray scale.
Thermal
 In this case the heat driven by the finger is detected, which is

greater when there is a ridge than when there is a valley.
 A silicon component has been developed with a matrix of pixels

called "Finger Chip", that is, "finger integrated circuit", each of
which is covered with a layer of pyroelectric material in which a
change in temperature translates into a change in the load
distribution of its surface.
 The image is in the gray scale that has the right quality even
with the finger worn, with dirt, with grease or with humidity.
 The sensor has a robust protective layer and can provide a

dynamic output.
Dynamic output
 Most of the sensors described have been altered in the past.
 To avoid this, a new operating mode has been added. Instead

of simply placing your finger statically on the sensor, the finger
moves slowly along it.
 The sensor only has a narrow sensitive area, and generates a

complete sequence of images, which can be reassembled, by
means of a processor, in a complete image.
 The benefits are improved appreciably and the elimination of

any residual grease is guaranteed.
Use
 The most important use area is in access control for computers.
 This is especially important for laptops and PDAs.
 Thanks to the price falling, more and more devices are

equipped with sensors. Other devices with built-in fingerprint
sensors include USB hard drives, USB memory modules and
card readers. They are also available in mice and keyboards.
 Sensors are increasingly used to secure financial transactions

and change machines for "online" banking.
 In the future, the owner's fingerprint will be stored securely on

identity cards and credit cards and may also be used for
authentication of emails using digital signatures.
 Direct physical access to rooms and devices can also be

ensured by coupling fingerprint sensors with door opening
systems.
6.2 SCHEMATIC DIAGRAM
6.3 PIN DIAGRAM:
PIN CONFIGURATION
Pin Description
Name
VCC Power Supply Input
GND Power Supply Ground
OUT Active High Output
FEATURES
 5VDC Operating voltage
 I/O pins are 5V and 3.3V compliant
 Range: Up to 20cm
 Adjustable Sensing range
 Built-in Ambient Light Sensor
 1mA supply current
 Mounting hole
BILL OF MATERIALS
1 Fingerprint 3.3V-6V DC 1 1125

scanner 120Ma
module
TOTAL PRICE=1125
CHAPTER-8
MODULE:4
RTC MODULE
CONTENTS
 8.1 DESCRIPTION
 8.2 PIN DIAGRAM
IMAGE
8.1 DESCRIPTION
 The DS3231 is a low-cost, extremely accurate I2C real-time
clock (RTC) with an integrated temperature compensated
crystal oscillator (TCXO) and crystal.
 The device incorporates a battery input, and maintains
accurate timekeeping when main power to the device is
interrupted.
 The integration of the crystal resonator enhances the long-

term accuracy of the device as well as reduces the piece-part
count in a manufacturing line.
 The DS3231 is available in commercial and industrial
temperature ranges, and is offered in a 16-pin, 300-mil SO

package.
 The RTC maintains seconds, minutes, hours, day, date, month,
and year information.
 The date at the end of the month is automatically adjusted for
months with fewer than 31 days, including corrections for leap
year.
 The clock operates in either the 24-hour or 12-hour format with
an AM/PM indicator.
 Two programmable time-of-day alarms and a programmable
square-wave output are provided.
 Address and data are transferred serially through an I2C

bidirectional bus.
 A precision temperature-compensated voltage reference
and comparator circuit monitors the status of VCC to detect
power failures, to provide a reset output, and to automatically
switch to the backup supply when necessary. Additionally, the
RST pin is monitored as a pushbutton input for generating a μP
reset.
SCHEMATIC DIAGRAM
8.2 PIN DIAGRAM:
8.3 BILL OF MATERIALS

1 DS3231 RTC 3.3-5.5V 1 250
MODULE 12 300µA-0.5A
CRTC
AT24C32
TOTAL PRICE=250
CHAPTER-9
MECHANICAL DESIGN
ISOMETRIC VIEW
FRONT VIEW
SIDE VIEW
BACK VIEW
CHAPTER
SOFTWARES USED
 BLYNK - IOT FOR ARDUINO, ESP8266/32

 ARDUINO IDE 1.8.7
 AUTODESK FUSION 360
 PROTEUS 8 PROFESSIONAL
BLYNK - IOT FOR ARDUINO, ESP8266/32
Control Arduino, ESP8266, ESP32, NodeMCU, Particle Photon,

Raspberry Pi and other microcomputers with the smartphone over the
Internet. Bluetooth and BLE supported too.
Create beautiful interfaces with widgets like buttons, knobs, graphs,

displays and many more!
Start in 5 minutes:
https://www.blynk.cc/getting-started
If you have any questions, ask on our forum:

https://community.blynk.cc
You can even share your project with friends and other makers by
simply sending them the link.
Use our Blynk Cloud or deploy your own Blynk Server in a minute and
have full privacy and control in your hands.
Supported boards and shields:

• ESP8266
• ESP32
• Node MCU
• Arduino Uno
• Arduino Mega
• Arduino Nano
• Arduino Mini
• Arduino YÚN (Bridge)
• Arduino Due
• Arduino 101
• Raspberry Pi
• Particle Core (ex-Spark Core)
• Particle Photon
• Spark Fun Blynk Board
• Tiny duino (CC3000)
• Wicked Wild-Fire (CC3000)
Shields and connections:

• USB, connected to your laptop or desktop computer (no shield
required!)
• Ethernet shield (W5100)
• Adafruit CC3000 Wi-Fi
• Official Arduino Wi-Fi shield
• ENC28J60
• HC-05, HC-06, HC-08, HM-10, etc.
And much more...
ARDUINO IDE 1.8.7
Download the Arduino Software (IDE)

Get the latest version from the download page. You can choose
between the Installer (.exe) and the Zip packages. We suggest you
use the first one that installs directly everything you need to use the
Arduino Software (IDE), including the drivers. With the Zip package
you need to install the drivers manually. The Zip file is also useful if
you want to create a portable installation.
When the download finishes, proceed with the installation and please
allow the driver installation process when you get a warning from the
operating system.
Choose the components to install
Choose the installation directory (we suggest to keep the default one)
The process will extract and install all the required files to execute
properly the Arduino Software (IDE)
Proceed with board specific instructions

When the Arduino Software (IDE) is properly installed you can go
back to the Getting Started Home and choose your board from the list
on the right of the page.
PROTEUS 8 PROFESSIONAL
Introduction
Proteus 8 is a single application with many service modules
offering different functionality (schematic capture, PCB layout,
etc.). The wrapper that enables all of the various tools to communicate
with each other consists of three main parts.
Application Framework
Proteus 8 consists of a single application (PDS.EXE). This is the

framework or container which hosts all of the functionality of Proteus.
ISIS, ARES, 3DV all open as tabbed windows within this framework and
therefore all have access to the common database.
Common Database
The common database contains information about parts used in

the project. A part can contain both a schematic component and a PCB
footprint as well both user and system properties. Shared access to
this database by all application modules makes possible a huge number
of new features, many of which will evolve over the course of the
Version 8 lifecycle.
Live Netlist
Together with the common database the maintenance of a live

netlist allows all open modules to automatically reflect changes. The
most obvious example of this is wiring in ISIS producing ratsnest
connections in ARES but it goes much further than that. The new Bill
of Materials module contains a live viewer and the 3D Viewer and
Design Explorer are also linked into the live netlist.
This document covers the Proteus 8 application framework and other

functionality related to the software suite as a whole. The various
application modules (e.g. ISIS, ARES) each have their own reference
manuals and tutorial documentation.
TUTORIAL
You can find tutorial guides and an update guide from Proteus 7 near
the top of the home page on the left-hand side. Alternatively, the
tutorial for a particular module of Proteus can be found on the Help
Menu when tha t module is open.
Reference
Manual
Similarly, you can open Reference Manuals either from the Proteus 8
home page or from the Help Menu on the application module itself.
Hitting the F1 key will also launch the reference manual for the
application module you are currently working in.
Videos
Several getting started videos can be watched directly from the

home page in Proteus 8. These cover the basics of importing and
creating new projects as well as some more detailed information on
new features in the V8 release.
Context Sensitive Help
Dialogue level help is available within the software via the small
question mark at the top right of the dialog form. Left click on the
question mark and then click on the dialogue form to launch.
Installation
As a result of changes in Windows policies and access rights, the

installation of Proteus 8 differs significantly from previous versions.
Both the file structure and the registry entries have changed as detailed
below:
Installed Files
Much like previous versions of Proteus several folder groups are

installed with the software, including:
 BIN Directory (Read only)

 Models Directory (Read only)
 Library Directory (Read/Write)
 Templates Directory (Read/Write)
 Updates Directory (Read/Write)
 Help Directory (Read only)
 Samples Directory (Read/Write)

 VSM Studio Directory (Read only)
 Datasheets Directory (Read/Write)
Directories to which a user may require read/write access are now

installed in the ProgramData (Application Data in Windows XP) folder
while those requiring read only access are installed in the Program Files
directory. For example:
Network Installation
Advanced users only. This topic is intended for System Administrators.
The Proteus 8 installer is an MSI installer and system administrators

can make use of this to help with large deployments.
Command line silent installation involves two steps.
1) Extract the MSI on Server
From the command prompt you type something like :
setup_pro8.0.15299.0.exe /exenoui /a // /passive /qn

TARGETDIR="C:\PROJECTS\PROBUILD\Installers\English\netimg"
where setup_pro8.0.15299.0.exe is the Proteus installer and the

TARGETDIR path is the path to extract to. Typically executed on the
server.
2) Silent Install on the Client
From the command prompt on the client you type something like :
Msiexec /i "\\networkshare\setup_pro8.0.15299.0.msi"/qn
DATA_DIR="E:\Proteus\v8data" APPDIR="E:\Proteus\v8"
where we have path to msi that was extracted by step 1 (other files
also extracted), the target program data directory and the target
program directory.
The order of the command line arguments is important. To install a

language pack with the installation the LANG_PACK="full path to
language pack" can be appended. To prevent the re-installation of a
language pack the NO_LANG_PACK=1 option can be appended.
Where a server license and dongle are installed the KEY_SERVER

property can be set on the command line to point to the licence key
server. If set this will set the environment variable, if not set the
variable will be cleared.
Batch files on the client side can help with automation of this step.
Update Control
In large corporations or institutions you may want to control the

deployment of updates on client machines. This can be done by setting
registry keys on the clients as follows:
HKLM\SOFTWARE\ [Wow6432Node\]. Lab Center Electronics\Proteus 8

[Professional Lite Demo]\Update Manager
UpdateSchedule is a dword value in days between 2 and 30. This is the

checking period for the client.
IgnoreBetas is an optional string which can be added and set to either

"true" or "false"
Disable Update Installation is an optional string with change can be

added and set to either "true" or "false"
The latter key will prevent any client machines from installing available
updates independently.
Migrating Libraries and Files from Proteus V7.xx
Since Proteus 8 installs directories requiring write access in a different

directory structure there may be some work required in moving
existing libraries and data from your existing Proteus 7.xx installation.
In general this can be fully automated but the process may vary
depending on your Proteus 7 configuration.
Default V7.xx Installation
This is the normal situation in which your Proteus 7 was installed with
a single library directory and you have not since changed, moved or
added library paths.
After installation of Proteus 8 the Legacy Importer utility will launch

and offer to copy your user libraries, styles and templates to the new
Proteus 8 locations.
No user action is normally required for this type of installation.
If you did not make use of the Legacy Importer utility during
installation you can launch it separately from the BIN directory of your
Proteus 8 installation (LegacySettingsImporter.exe).
Custom V7.xx Installation
In this case you have more than one library directory specified for your
Proteus 7.xx installation.
Since we don't know why libraries have been separated or moved you
may need to work manually by copying files between your Proteus 7.xx
directories and your Proteus 8.xx directories.
The legacy importer utility will launch after installation and point to a
library path. Depending on how you have set up your system this may
or may not be your primary Library path. If it is, then run the tool as
normal - if it isn't then browse to your primary Library path and then
run the tool.
Organising your secondary Library paths is up to you. Typically

however the secondary library path from Proteus 7.xx can simply be
added as a secondary path in Proteus 8 via the Set Paths command on
the System Menu.
Do not change the primary Proteus 8 library path to the old Proteus
7 library path. This will cause problems throughout the software.
If all else fails, you may need to get a couple of copies of Windows
explorer open and copy files manually between your Proteus 7 Library
directory and your Proteus 8 Library directory.
Relevant Files
The following is a list of files that may be relevant for copying or moving
between Proteus 7 and Proteus 8.
Library Directory
PROPDEFS.INI : This file must not be copied from Proteus 7 as it is

completely different in Proteus 8.
SYSTEM.LIB : This file must not be copied from Proteus 7 as it is

completely different in Proteus 8.
DEFAULT.STY : This file contains custom pad and trace styles and can
be copied from Proteus 7 into Proteus 8. However, we recommend
using the migration tool in the installer as this will merge rather than
overwrite the V7 and V8 versions of the file.
Read Only Libraries: These will typically be libraries supplied by

Labcenter. You should not copy these across to Proteus 8 as we may
have added parts or corrected errors.
VML Files: These are combined 3D model files supplied by

Labcenter. You should not copy these across to Proteus 8 as we may
have added parts or corrected errors.
3DS Files: Typically these will be user generated 3D model files and
should therefore be copied across to the Proteus 8 Library directory.
User Libraries: These will contain user generated library parts and
should therefore be copied across to the Proteus 8 Library Directory.
Three such libraries are supplied as standard (USERDVC.LIB,
USERPKG.LIB & USERSYM.LIB) although users can create as many as
they need.
IDX Files: These are temporary files generated when Proteus is

launched and should not be copied between Proteus 7 and Proteus 8
directories.
Models Directory
Models that have been created or downloaded (e.g. SPICE models) by

the user can be copied from the Proteus 7 models directory to the
Proteus 8 Models directory. You should not copy any other files as these
may have changed in Proteus 8.
Template Directory
Template Files in the Proteus 7 template directory can be copied into

the Proteus 8 template directory.
Datasheets Directory
Datasheets from the Proteus 7 directory can be copied into the Proteus
8 datasheets directory.
Bill of Materials
Bill of Materials configurations can be migrated from within the

software by opening the Bill of Materials application module. You can
re-launch the tool at any time from the Import Templates command on
the Template Menu inside the BOM Module.
Filing
Proteus 8 makes use of a single compound file with extension pdsprj.

All application modules will store data inside the pdsprj file but in
general you will be prompted to save data for external use elsewhere
on disk.
Schematic and PCB
 The schematic data is stored in the pdsprj file.

 The PCB data is stored in the pdsprj file.
 Bill of Materials generation will prompt you to save to disk.
 Output for manufacture from the PCB module will prompt you to
save to disk.
 PDF and general graphics output from both schematic and PCB
modules will prompt you to save to disk.
Schematic and VSM
 The schematic data is stored in the pdsprj file.

 The source code files are (by default) stored in the pdsprj file.
 In debug configuration the object files are stored in the pdsprj
file for VSM Simulation.
 In release configuration the hex file is copied outside of the
pdsprj file for programming physical hardware.
You can choose to keep your source files outside of the pdsprj file
by upchucking the 'attach files' checkbox in the VSM Studio project
settings.
The main objective is to keep anything internal to Proteus development

in a single compounds file while anything used by another application
or device is saved externally.
In addition to the pdsprj file Proteus 8 also writes a per user workspace
file for each project. This basically remembers the state of the project
when closed including:
 Number of open frames.

 Number of open tabs and which tabs belong with which frame.
 Size and position of frame(s) on the users monitor(s).
Path Configuration
Do not set your primary Proteus 8 Path to your primary Proteus 7 Path.
This will not work and may cause serious issues throughout the
software. Refer to Migrating Files for more information.
For most users the standard paths will be sufficient. However, if you
do wish to move folders post installation you can do so from the System
Settings command on the System Menu.
Be aware that moving a read/write directory to a location where it

cannot be written by all users will cause serious problems. On a
network drive, remember that group policies may be in place which will
take precedence over local admin settings - you should not attempt
this unless you are confident that you understand the implications.
Terminology
(Application) Module
In Proteus 8 an application module encompasses functionality that

opens as a top level tab inside the Proteus application. These include
:
 Proteus Home Page

 ISIS Schematic Capture.
 ARES PCB Layout.
 3D PCB Viewer.
 Bill of Materials.
 Design Explorer
 Gerber Viewer.
 VSM Studio IDE
Frame
A frame is essentially a window in Proteus 8 and can contain several

tabs. By default you have one frame, although you can drag tabs to
create new frames or to close frames.
Tab
A tab is a small placeholder at the top of a frame that - when clicked

- will bring an application module to the foreground. You can also
drag and drop tabs onto other monitors (or an area of free space) to
open them in a separate frame.
Menus and Icons
The Proteus application framework contains a small set of menu's and

icons which are present regardless of which module or modules you
are working on. Typically, these are used to open other application
modules and to handle filing and configuration options.
File I/O Toolbar
This is a standard toolbar for creating new projects, opening and

saving projects and closing the current project.
Application Module Toolbar
Each icon on this toolbar represents an application module. Clicking

on an icon will open the application module in the current frame.
Application Toolbars and Menus
When you open an application module (e.g. ISIS) both the menus
and the toolbars will change to include the various options available.
Similarly, if you have two modules open (e.g. ISIS and ARES) in
different tabs then the menus and icons will switch as you switch
tabs.
The system commands and the application module toolbar are

available regardless of which application module you are working in.
Global Settings
The System Settings dialogue on the System Menu allows you to

configure paths for writeable directories used in Proteus. It also
enables configuration of crash dump reporting, the number of undo

levels in the software and also the locale used for library parts.
The locale setting basically determines what your resistor and

capacitor symbols look like on the schematic as there are different
conventions in Europe and the USA.
Tabs and Frames
Each top level application module will open in a new tab inside the
current frame.
If you prefer (and particularly if you work with two monitors) you can
drag and drop a tab into free space to create a new frame. This
allows you to see both modules simultaneously which, together with
the common database and live netlisting, is a common method of
working.
To open a new tab
Normally, you would do this simply by clicking on the icon on the

application module toolbar.
The exception to this paradigm is graphs which will open in a new tab
when maximised. Graphs are not represented in the application
module toolbar as they are entirely dependant on being placed in the
schematic capture module.
Design explorer can also be opened from the context menu of

components in ISIS or footprints in ARES.
To close a tab
Close a tab by clicking on the cross at the right hand side of the tab.
Alternatively, closing a frame will close all tabs inside the frame.
To open an additional frame
Assuming you have both the ISIS and the ARES tabs open and you
want to view them at the same time:
Drag the ARES tab either onto a separate monitor on into free space.
OR
Double click on the ARES tab to automatically separate into two

frames on the same monitor
To re-join two frames
To re-join one frame to another simply drag either the tab or the
window from the second frame over the first. There is a subtle
difference where the second frame has more than one tab open in
that dragging the window will re-join all of the tabs in the window
whereas dragging a tab will re-join only that tab
To close a frame
Use the cross at the top of the window to close it. If you have more
than one frame open you will be prompted to close either the current
frame or the complete application.
9.1 BILL OF MATERIALS (MECHANICAL PART)

1 COMBINATION 1000mm 1 400
OF MILD X1000mm
STEEL AND
ALUMINIUM
SHEET
TOTAL PRICE=400
2D VIEWS
CHAPTER-10
CIRCUIT DIAGRAM
A B C D E F G H J K
7805
U1
1 3
R1
VI VO
0 100e 0
TR1 BR1
GND
J3
1
2
C1 2
J2 V1 470uf
VSINE CONN-SIL2
2 D1
1 LED
1 CONN-SIL2 BRIDGE 1
TRAN-2P2S
2 2
FINGER PRINT
3 3
J1
1
1
2
3
J6 4 J7
CONN-SIL1 1 1
CONN-SIL1 CONN-SIL1
4 4
R3
10k
6
5
1 4
R2 2 3
5 10k 3 NODE MCU 2 5
4 1
R4 R5 RTC
10k 10k
1 J5
2 2 1
3 1 2
CONN-SIL2
6 6
D4
LED D5
LED
7 7
1
J4
CONN-SIL1
8 8
CRICUT DIAGRAM FOR PORTABLE CLASSROOM ATTENDENCE

FILE NAME: SYSTEM
DATE:
finger print scanner CRICUT DIAGRAM.pdsprj
PORTABLE CLASSROOM ATTENDENCE SYSTEM
15-05-2019
DESIGN TITLE: TITLE:
9 finger print scanner CRICUT DIAGRAM.pdsprj9
PAGE:
APPROVED BY
PATH: C:\Users\USER\Desktop\MSD
CHECKED BY PROJECT\PROTEUS\finger print scanner CRICUT DIAGRAM.pdsprj
DRAWING BY 1 of 1
SU 15 TEAM 1
BY: @AUTHOR REV: @REV TIME: 14:18:10
A B C D E F G H J K
71
INTERCONNECTION DIAGRAM
A B C D E F G H J K
0 0
J3
J2 3
1 2
1 2
5V 2A 1 1
3
CONN-SIL3
CONN-SIL3
2 2
FINGER PRINT
3 3
1
2
3
4
4 4
R3 6
10k 5
1 4
2 3
5 3 NODE MCU 2 5
4 1 RTC
1
2 2
R2 3 1
10k
R4 R5
10k 10k
6 6
D4
LED D5
SCHEMATIC DIAGRAM
LED
7 7
8 8
FILE NAME: ATTENDENCE SYSTEM

INTERCONNECTION DIAGRAM FOR PORTABLE CLASSROOM DATE:
finger print scanner INTERCONNECTION.pdsprj
09-05-2019
finger print scanner INTERCONNECTION.pdsprj
9 9
PAGE:
APPROVED BY
PATH: CHECKED BY PROJECT\PROTEUS\finger
C:\Users\USER\Desktop\MSD print scanner INTERCONNECTION.pdsprj
DRAWING BY 1 of 1
SU 15 TEAM 1
A B C D E F G H J K
73
A B C D E F G H J K
7805
U1
1 3
R1
VI VO
0 100e 0
TR1 BR1
GND
J3
1
2
C1 2
470uf
J2 CONN-SIL2
2 D1
1 LED
1 CONN-SIL2 BRIDGE 1
TRAN-2P2S
2 2
FINGER PRINT
3 3
J1
1
1
2
3
4
CONN-SIL1 J6 J7
1 1
CONN-SIL1 CONN-SIL1
4 R3 2
4
1
10k
J9
1
2
3 CONN-SIL2 J11 J10
4 6 1
J8 CONN-SIL2
5 2
CONN-H4 4 1 4
R2 3 2 3
5 10k 2 3 NODE MCU 2 5
1 4 1 RTC
R4 R5 J13
10k 10k CONN-H4 3 1 CONN-SIL2 J5
2 2 2 1
J12 1 3 1 2
1
2 CONN-SIL3
3
4
6 D4 6
LED D5 CONN-H4
LED
7 7
1
J4
CONN-SIL1
8 8
SCHEMATICDIAGRAM FOR PORTABLE CLASSROOM ATTENDENCE

FILE NAME: finger print scanner SCHEMATIC.pdsprj DATE:SYSTEM

09-05-2019
finger print scanner SCHEMATIC.pdsprj
9 9
PAGE:
APPROVED BY
PATH: CHECKED BY PROJECT\PROTEUS\finger
C:\Users\USER\Desktop\MSD print scanner SCHEMATIC.pdsprj
DRAWING BY 1 of 1
SU 15 TEAM 1
A B C D E F G H J K
74
CHAPTER 10
ADVANTAGES AND LIMITATIONS
ADVANTAGES
 Security and portability.

 Rechargeable with independent energy source.
 Reduces queuing and preserves data integrity.
LIMITATIONS
 There is a chance of misusing the technology by placing a fake
fingerprint.
 Modules are sensitive and they need to be handed carefully.
PROGRAM
FINAL PROGRAM
#include <Adafruit_Fingerprint.h>
#include <Wire.h>
#include <ESP8266WiFi.h>
#include <BlynkSimpleEsp8266.h>
#include "RTClib.h"
#define BLYNK_PRINT Serial
RTC_DS1307 RTC;
SoftwareSerial mySerial(13, 15); //rx, tx
Adafruit_Fingerprint finger = Adafruit_Fingerprint(&mySerial);

int
years=0,months=0,days=0,hours=0,minitues=0,seconds=0,fing_id=
0;
/////////////////////// blynk //////////////////
char ssid[] = "hello";

char pass[] = "howareyou";
char auth[] = "11a951d8b14c467abf28fed55900d085";
WidgetTerminal terminal(V1);
const int analogInPin = A0; // Analog input pin ADC

const int Battery_low = 2; // digital output pin ADC
int sensorValue = 0; // ADC value
int outputValue = 0; // mapped ADC
void setup()
{
//////////////////////// ADC //////////////////////////
pinMode(Battery_low, OUTPUT); // battery status low D4
pinMode(analogInPin, INPUT); // analog read A0
//////////////////////////////////////////////////////
pinMode(16, OUTPUT); // finger print indication failure D0
pinMode(0, OUTPUT); // finger print indication success D3
digitalWrite(16, LOW);
digitalWrite(Battery_low, LOW);
Serial.begin(9600);
/////////////////////// blynk //////////////////

Blynk.begin(auth, ssid, pass);
// terminal.println("setup") ;
// terminal.flush();
//////////////////////////RTC/////////////////////////////////
Wire.begin();
RTC.begin();
if (! RTC.isrunning()) {
Serial.println("RTC is NOT running!");
// following line sets the RTC to the date & time this sketch was
compiled
RTC.adjust(DateTime(__DATE__, __TIME__));
}
/////////////////////////FINGER///////////////////////////////////////
while (!Serial); // For Yun/Leo/Micro/Zero/...
delay(100);
Serial.println("\n\n finger detect test");
// set the data rate for the sensor serial port

finger.begin(57600);
if (finger.verifyPassword()) {
Serial.println("Found fingerprint sensor!");
} else {
Serial.println("Did not find fingerprint sensor :(");
while (1) { delay(1); }
}
finger.getTemplateCount();
Serial.print("Sensor contains "); Serial.print(finger.templateCount);
Serial.println(" templates");
Serial.println("Waiting for valid finger...");
}
void loop() // run over and over again

{
///////////////////ADC//////////////////////////////////////
// read the analog in value:
sensorValue = analogRead(analogInPin);
// map it to the range of the analog out:
outputValue = map(sensorValue, 0, 1023, 0, 255);

// change the analog out value:
if (outputValue<100)
{
digitalWrite(Battery_low,HIGH);
}
else
{
digitalWrite(Battery_low,LOW);
}
//////////////////////////RTC/////////////////////////////////
DateTime now = RTC.now();

years=now.year();
months=now.month();
days=now.day();
hours=now.hour();
minitues=now.minute();
seconds=now.second();
Serial.println(years);
Serial.println(months);
Serial.println(days);
Serial.println(hours);
Serial.println(minitues);
Serial.println(seconds);
Serial.println();
delay(100);
/////////////////////////FINGER///////////////////////////////////////
getFingerprintIDez();
delay(100);
Blynk.run();
delay(100); //don't ned to run this at full speed.

}
// returns -1 if failed, otherwise returns ID #

int getFingerprintIDez() {
uint8_t p = finger.getImage();
if (p != FINGERPRINT_OK) return -1;
p = finger.image2Tz();
if (p != FINGERPRINT_OK) return -1;
p = finger.fingerFastSearch();
if (p != FINGERPRINT_OK)
{
digitalWrite(16, HIGH);
delay(2000);
return -1;
}
// found a match!
Serial.print("Found ID #"); Serial.print(finger.fingerID);
fing_id=finger.fingerID;
Serial.print(" with confidence of "); Serial.println(finger.confidence);
digitalWrite(0, HIGH);
delay(2000);
if(fing_id==1||fing_id==2||fing_id==3)
{
if(hours==10 && minitues<10)
{
terminal.println("SU1516003 IS PRESENT AT 10 AM") ;
terminal.flush();
}
else if(hours==11 && minitues<10)
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.println("SU1516003 IS PRESENT AT 1 PM") ;
terminal.flush();
}

{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
}
{
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
}
{
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
}
{
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{
terminal.flush();
}
{

terminal.flush();
}
}
return finger.fingerID;
}
ADD DATA PROGRAM
#include <Adafruit_Fingerprint.h>
SoftwareSerial mySerial(13, 15);
Adafruit_Fingerprint finger = Adafruit_Fingerprint(&mySerial);
uint8_t id;
void setup()
{
Serial.begin(9600);
while (!Serial); // For Yun/Leo/Micro/Zero/...
delay(100);
Serial.println("\n\n Fingerprint sensor enrollment");
// set the data rate for the sensor serial port

finger.begin(57600);
if (finger.verifyPassword()) {
Serial.println("Found fingerprint sensor!");
} else {
Serial.println("Did not find fingerprint sensor :(");
while (1) { delay(1); }
}
}
uint8_t readnumber(void) {
uint8_t num = 0;
while (num == 0) {
while (! Serial.available());
num = Serial.parseInt();
}
return num;
}
void loop() // run over and over again

{
Serial.println("Ready to enroll a fingerprint!");
Serial.println("Please type in the ID # (from 1 to 127) you want to
save this finger as...");
id = readnumber();
if (id == 0) {// ID #0 not allowed, try again!
return;
}
Serial.print("Enrolling ID #");
Serial.println(id);
while (! getFingerprintEnroll() );
}
uint8_t getFingerprintEnroll() {
int p = -1;
Serial.print("Waiting for valid finger to enroll as #");
Serial.println(id);
while (p != FINGERPRINT_OK) {
p = finger.getImage();
switch (p) {
case FINGERPRINT_OK:
Serial.println("Image taken");
break;
case FINGERPRINT_NOFINGER:
Serial.println(".");
break;
case FINGERPRINT_PACKETRECIEVEERR:
Serial.println("Communication error");
break;
case FINGERPRINT_IMAGEFAIL:
Serial.println("Imaging error");
break;
default:
Serial.println("Unknown error");
break;
}
}
// OK success!
p = finger.image2Tz(1);
switch (p) {
Serial.println("Image converted");
break;
case FINGERPRINT_IMAGEMESS:
Serial.println("Image too messy");
return p;
return p;
case FINGERPRINT_FEATUREFAIL:
Serial.println("Could not find fingerprint features");
return p;
case FINGERPRINT_INVALIDIMAGE:
return p;
default:
return p;
}
Serial.println("Remove finger");
delay(2000);
p = 0;
while (p != FINGERPRINT_NOFINGER) {
}
Serial.print("ID "); Serial.println(id);
p = -1;
Serial.println("Place same finger again");
while (p != FINGERPRINT_OK) {
switch (p) {
Serial.println("Image taken");
break;
case FINGERPRINT_NOFINGER:
Serial.print(".");
break;
break;
case FINGERPRINT_IMAGEFAIL:
Serial.println("Imaging error");
break;
default:
break;
}
}
// OK success!
p = finger.image2Tz(2);
switch (p) {
Serial.println("Image converted");
break;
case FINGERPRINT_IMAGEMESS:
Serial.println("Image too messy");
return p;
return p;
case FINGERPRINT_FEATUREFAIL:
return p;
case FINGERPRINT_INVALIDIMAGE:
return p;
default:
return p;
}
// OK converted!
Serial.print("Creating model for #"); Serial.println(id);
p = finger.createModel();
if (p == FINGERPRINT_OK) {
Serial.println("Prints matched!");
} else if (p == FINGERPRINT_PACKETRECIEVEERR) {
return p;
} else if (p == FINGERPRINT_ENROLLMISMATCH) {
Serial.println("Fingerprints did not match");
return p;
} else {
return p;
}
Serial.print("ID "); Serial.println(id);

p = finger.storeModel(id);
if (p == FINGERPRINT_OK) {
Serial.println("Stored!");
} else if (p == FINGERPRINT_PACKETRECIEVEERR) {
return p;
} else if (p == FINGERPRINT_BADLOCATION) {
Serial.println("Could not store in that location");
return p;
} else if (p == FINGERPRINT_FLASHERR) {
Serial.println("Error writing to flash");
return p;
} else {
return p;
}
}
OVERALL BILL OF MATERIAL
BILL OF MATERIAL(MECHANICAL)
S.NO COMPONENT QUANTITY COST
DESCRIPTION
1 GI SHEET 1 200
2 SCREW AND NUT 10 30
TOTAL PRICE 230
BILL OF MATERIAL(ELECTRICAL&ELECTRONICS)
S.NO COMPONENT QUANTITY COST
DESCRIPTION
1 MODULE 1: POWER 1 799
SUPPLY DESIGN
2 MODULE 2: RTC MODULE 1 250
3 MODULE 3: ESP8266 1 352
NODEMCU
4 MODULE 4: FINGERPRINT 1 1125
SCANNER MODULE
TOTAL PRICE 2526
GRAND TOTAL 2926
COMPARISON OF EXISTING WITH PROPOSAL

MODEL
EXISTING MODEL PROPOSAL MODEL

 It is fixed in a  It is a portable
particular place. device which can be
 External adapter is carried anywhere.
used for providing  It has battery as an
working voltage. independent energy
 Long queue will be source.
formed.  We can punch by
 Data integrity is carrying the device,
preserved. so there is no queue.
 Data integrity is
preserved.
CHAPTER-11
CONCLUSION
 This is a handheld device which can be carried to the classroom.
 The device can be handed over to students and they can mark
their attendance.

Portable Fingerprint Attendence System

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Portable Fingerprint Attendence System

Caricato da

Copyright:

Formati disponibili

PORTABLE CLASSROOM ATTENDANCE SYSTEM

AN ISO 9001:2015 CERTIFIED TRAINING INSTITUTION

NETTUR TECHNICAL TRAINING FOUNDATION

PORTABLE CLASSROOM ATTENDANCE

GAUTAM RAJ R SU 15 16 013

AN ISO 9001:2015 CERTIFIED TRAINING INSTITUTION

NETTUR TECHNICAL TRAINING FOUNDATION

is a bonafide report of Project done by

GAUTAM RAJ R SU 15 16 013

IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR THE AWARD OF BE.

PROJECT INCHARGE COURSE INCHARGE

PRINCIPAL EXTERNAL EXAMINER

We would like to take this opportunity to mention a few names, without

Biometric student attendance system increases the efficiency of

Attendance plays a major role in educational institutions. The

The aim of the project is design and development of a portable classroom

2.2 PROJECT OBJECTIVE

 Record attendance for academic purposes.

2.3 PROJECT TARGET

To reduce queuing and preserve data integrity.

POWER SUPPLY CIRCUIT MODULE

CONTROL CIRCUIT MODULE:

BLOCK DIAGRAM DESCRIPTION

MODULE1: POWER SUPPLY DESIGN

 It consists of a 12V / 1.3Ah battery.

MODULE 2: ESP8266 NODEMCU

 It is the controller and wi-fi module.

MODULE 3: FINGERPRINT SCANNER MODULE

 It senses the fingerprint of a person.

MODULE 4: RTC MODULE

A power supply is an electrical device that supplies electric

latter include power supplies found in desktop computers and

All power supplies have a power input connection, which

 Step down transformer gives 12V/2A.

 Capacitor is introduced to filter the ripples of converted DC, so

 Most of the logic and digital circuit will work only at a

IC 7805 voltage regulator

 The IC7805 is simple to use.

5.2 BILL OF MATERIALS (POWER SUPPLY)

SL.NO CONPONENTS SPECIFICATION QUANTITY PRICE(Rs)

CONTROLLER AND WI-FI UNIT

 However, a lot of projects require hard coding the Wi-Fi

 This issue is further increased if you are developing a

 Initially when you power up your ESP8266 module you will

• Wake up and transmit packets in < 2ms

• Smart Plug and lights

3. AHB interface, can be used to visit the register.

PIN CONFIGURATION EXPLANATION

Symb Min Max Unit

Output High Voltage VOH 0.8×VI V

Input Pin Resistance Cpad 2 pF

 All digital IO pins are protected from over-voltage with a snap-

7.2 PIN DIAGRAM

7.3 SCHEMATIC DIAGRAM

7.4 BILL OF MATERIALS:

1 NODE MCU ESP 1 340

 Attributes such as cost, size, reliability, operating

Figure 1 Different types of prints: arch, loop, whirl

 Fingerprints are commonly classified as 5 different types: whorl,

 A major obstacle in fingerprint recognition is that the images

 Usually rotation and displacement of some sort is evident.

 Attempting to compare two fingerprints with different

 To adjust for this, rotation of the input image is performed.