Broun Hall Access System Weekly Status Report Week 4 PowerPoint PPT Presentation

presentation player overlay
1 / 36
About This Presentation
Transcript and Presenter's Notes

Title: Broun Hall Access System Weekly Status Report Week 4


1
Broun Hall Access SystemFinal Presentation
Janus Security Brad Austin Cole Brown Kelly
Hall Kyle Coker Russell Biser Steve Hawkins Linda
Kirk
2
Outline
  • Introduction
  • Approach
  • Design Specifications
  • Project details
  • Budget
  • Final Design
  • Future work
  • Conclusion
  • Questions

3
Introduction
  • Existing System
  • Purpose
  • Hardware
  • Neptune donations, out of replacements
  • Z80 Obselete
  • Behavior
  • Problems
  • Logging
  • Door Propping

4
Approach
  • General Description
  • Technical Trades
  • Specific Description
  • Failure Behavior
  • Proposal
  • System Breakdown
  • Timeline
  • Parallel and Sequential Processes

5
Design Specifications
  • The access controller performs the following
    tasks
  • Read access id from keypad.
  • Sends  fixed or scrolling messages to the keypad
    display.
  • Communicates with central computer to verify
    access request (lowspeed CAN network).
  • Opens door if access is allowed (12 Volt
    solenoid HES1003 electricstrike).
  • Monitors door to make sure it is not propped open
    (Hall effect switch).
  • Sounds alarm if door is propped open (Buzzer
    and/or message tocentral computer).
  • The keypad module performs the following tasks.
  • Scan keypad (3x4 matrix Grayhill 88AB2-172  ),
    debounce key, send toaccess controller.
  • Display  fixed  or scrolled messages.
  • Reset both keypad and access controller module
    for freeze ups causedby brownouts.
  • At least one keypad will be subjected to outside
    weatherconditions so all components used in the
    keypad module have to be temperature rated  from
    atleast -5C to 50C.
  • The central computer network interface module
    handles the translation from the CAN networkto a
    standard computer interface (ex USB or serial).

6
Design Specifications
  • System Overview
  • Hardware
  • Software

7
(No Transcript)
8
(No Transcript)
9
  • Micro Controller Unit
  • CSM-12C32
  • 49.41
  • Features
  • 32K Byte Flash EEPROM
  • 2K Bytes RAM
  • 31 I/O lines
  • SCI and SPI Ports
  • BDM DEBUG Port
  • CAN 2.0 Module
  • 8 MHz Internal Bus
  • Wide input voltage range
  • 7VDC to 20VDC
  • On-board regulated 5V power supply
  • RS-232 Serial Port w/DB9 Connector
  • 8-Ch, 10-bit, Analog Comparator
  • 8-Channel, 16-bit Timer and PWM
  • 40-pin MCU I/O Connector

10
  • MC9S12C32 Microcontroller Schematic8 in
    quantity of 100

11
  • MC9S12C32 Microcontroller

  • The design team chose the MC9S12C32 because
  • Availability (short delivery time)
  • Price
  • Less than 50 per module
  • 8 per microcontroller
  • Support for C/C in software development
  • Includes the interfaces needed for this project
  • CAN, SPI, GPIO

12
  • MCU Project Board
  • 224 w/ CSM-12C32
  • Features
  • Integrated USB BDM pod
  • 60-pin MCU Interface Connector
  • 2 Banana Connectors
  • 1 BNC Connector
  • 8 DIP Switches
  • 1, 5k ohm Pot
  • 8 Green LED's
  • 8 Push Button Switches

On-board voltage regulators provide 4 different
voltage levels 5VDC _at_ 500mA 3.3VDC _at_ 500mA
15VDC _at_ 50mA -15VDC _at_ 50mA
13
  • Keypad Interface

Grayhill 88AB2-172 24.72
  • FEATURES
  • Sealed Keyboard
  • Colorful Graphic Overlay
  • Audible, Snap-Dome Contact
  • User Legendable Styles
  • 3,000,000 Operations per Button
  • Optional Panel Seal Gasket to Protect Your
    Equipment
  • Available in quantity at your local Joe-Mart

14
  • Keypad Schematic
  • Row lines are connected to 10k pull-up resistors
    5V, and also to the MCU.
  • Column lines are connected to MCU only.
  • Row Lines are READ-ONLY
  • Column Lines are WRITE-ONLY

15
  • Keypad Software
  • Scanning for Input

1. Column lines are set to 0 2 .Rows are scanned,
checking for 0. 3. If a 0 is detected, wait a
few microseconds to debounce the keys 4. All
column lines are set to 1 5. A single column is
set to 0 6. The rows are re-scanned for 0 Steps
5-6 are repeated until 0 is found on the rows, or
until all columns have been set to 0 7. If a 0 is
found, look up the key value in an array using
the row column for the index
16
Display HardwareVaritronix LCD
  • A 16 characters (5 x 8 dots) x 1 line LCD
  • Operates at temperatures between -5C to 50C
  • The display has a NOVATEK LCD controller and
    driver

17
Display Hardware
  • The enable, R/W, and register select pins are
    connected to the microcontroller.
  • Vo and Vss are tied to ground.
  • Vcc is connected to 5V.
  • Data pins are connected to the microcontroller.

18
Display Software
  • DisplayInit()
  • initializes the display
  • Dual line
  • Curser off
  • Font
  • LCDSendChar()
  • sends a character to the display
  • CheckLCDReady()
  • waits for the busy flag to clear
  • LCDClearDisplay
  • Clears the display
  • SetDDRAM()
  • 0x00 for the first line on the display
  • 0x40 for the second line on the display
  • ScrollString()
  • Display a message
  • Scrolls message if greater than 16 characters

19
Lock/Sensor/Buzzer Hardware
20
Lock/Sensor/Buzzer Software
  • Lock disabled when valid code received
  • Count for buzzer started when magnet signal low
  • Short buzz when magnet low with no keypad
    interaction

21
Serial Communication
  • Asynchronous at 19,200 baud.
  • Used to send messages between door module and
    control module.
  • Message types defined by 1 byte header.

22
Serial Communication
  • Serial messages
  • Keycode
  • Valid/Invalid/Logged In
  • Error
  • Door Opened
  • Network Status

23
Database - Tables
  • JanusDoors contains four tables
  • log
  • room_users
  • rooms
  • users

24
Database - Functions
  • Home
  • Add User
  • Add Room
  • Add User to Room
  • Search
  • List Rooms
  • List Users

25
Database Interface
26
Database Quick Guide
27
CAN Communication
  • General Network Layout
  • Star Topology, such that all microcontrollers are
    interconnected at a single point.
  • The central computer also connects to the CAN
    network via a microcontroller.
  • There are two microcontrollers per room.
  • The first of which is located inside the room,
    and is connected to the CAN network the door
    lock mechanism.
  • The second microcontroller is located outside the
    room communicates with the first one via serial
    link.
  • This is done to isolate the lock mechanism from
    the outside of the room.

28
CAN Communication
  • 1. User enters code on microcontroller outside
    room.
  • 2. Code is sent to 1st microcroller inside the
    room
  • 3. Code is sent over CAN network to the central
    computer
  • 4. Central computer verifies access to the room
    sends back either denied or granted
    response to 1st microcontroller, inside the room.
  • 5. If access was granted, 1st microcontroller
    unlocks the lock mechanism. It then sends a
    message via serial to the 2nd microcontroller
    outside the door. If access was denied, the door
    is not unlocked. It then sends a message via
    serial to the 2nd microcontroller outside the
    door.

29
(No Transcript)
30
Budget
  • Materials provided by Dr. Nelson, Joe Haggerty,
    Janus Security Team
  • Expenses covered by team
  • LCD module
  • Transceivers
  • Buzzer
  • Miscellaneous materials

31
Materials
32
Final Design
  • For display at Senior Design Fair
  • Enter ID message
  • Valid ID unlocks latch, reads Open
  • Door
  • Invalid ID, reads, Invalid ID Code
  • Buzzer sounds after 23 seconds of open door
  • Reads, Close Door
  • Door opens from inside
  • Buzzer sounds briefly times, reads Log Out
  • After logging out, reads Bye
  • Error message
  • Network Down message

33
Final Design
34
Future Work
  • CAN to be developed in the near future for
    various functions/messages
  • Error checking for Serial Communication
  • Timeout issues for Serial Communication

35
Conclusion
  • Door Access System nearly fully functional.
  • Design thoroughly tested
  • Functional aspects of the design
  • Keypad
  • Display
  • Door interface
  • Complete database
  • Serial communication
  • CAN yet to be implemented
  • Further serial communication development
  • New team can pick up project
  • Sufficient documentation left behind

36
  • Questions
  • or
  • Discussion
Write a Comment
User Comments (0)
About PowerShow.com