The Makerspace Lockout System

Team Name

The Makerspace Lockout System
The Makerspace Lockout System

Timeline

Spring 2019 – Summer 2019

Students

  • Erick Andrup
  • Nhat Nguyen
  • Said Adem
  • Jake Lewis

Abstract

The Maker Space Lockout System correctly gives access to Machinery only to users that have
been adequately briefed on the machinery’s safety and operation. The Maker Space Lockout
System is a locking system that only gives trained users access to the machinery that they have
been trained. Purchasers of the system will be able control access for each user according to
their level of skill and expertise. Users of The Maker Space Lockout System will also become
more equipped to handle and view wear and tear on machines via the data collection purge at
the end of each job.

Background

Maker spaces and other workshops contain shop equipment that can be very dangerous untrained users and have a high risk of injury when used improperly. As a result, it is important to have a method in place to limit access to certain tools so that untrained users cannot use more dangerous and expensive equipment such a lathe or laser cutter. The current method that the The Maker Space Lockout System uses Mainly relies on controlling who has access to the room is effective but could be more optimized to allow untrained individuals to access equipment that does not require extensive training and allow them to schedule training on devices that they are currently not trained.

The current system also doesn’t have an effective way of tracking available machines such as 3D printers nor does it have an effective way of tracking who is using each machine. With Marker Space Lockout System, our team have anopportunity to streamline training requests and individual access to dangerous equipment, monitor what users are using what equipment, and add other features to allow a better experience for users and admin. Moreover, team Lockout will design web interface for validated users that provide training documentation the shop equipment.

Project Requirements

The Maker Space Lockout System has three parts :

  • The Maker Space Lockout SystemWeb Portal
  • The Maker Space Lockout System Server
  • The Maker Space Lockout System Control Module Network.

The Maker Space Lockout System will use a relational database table to store all users information in the system. The Maker Space Lockout System Web Interface will be available for users to create log in account, request training on machinery, and be assigned PIN numbers for identification from the System.

Administrators can run query reports, adding information through the The Maker Space Lockout System Web Portal. The Maker Space Lockout System Control Module Prototype, will be implemented with Raspberry PI 0 B+, a Rotary Encoder, number pad, Magnetic Card reader, and a Key Studio LCM1602 LCD Display.

System Overview

The Maker Space Lockout System is split up into three parts Web interface, server, and module design
interface. For our application we hope to use a REST API and service, such as described in the figure
above. The client application could be considered our web portal and the bottom client application our
Arduino module, while the server is where we will be hosting our website and database. We are also
looking into MQTT to use as an alternative

Results

  • Lockout System Control Hub hardware is completed and able to show data on the LCD screen.
  • Frontend system is able to show different sub-website when different authorized users login. For example : Lab administrator, manager will able to see machines ‘logs and users’ info when logging in.
  • User information is stored in system database.
  • The system has some issue connecting between frontend and backend system.
  • Communication between database and Lockout Control Hub Model has not been established.

Lockout Control Hub

Future Work

The Maker Space Lockout System Control Modules will be over-engineered to allow for the expansion of the future needs of the system. Team Lockout anticipates that the system may be deployed in commercial applications. So the need for the Control Module to be easily scaled is a necessary component of the project. The Future will need to implement wireless capability with out the use of a plug and play Rasbian device. The end final product will need to be a wireless IOT network of many machines.

Project Files

Project Charter (link)

System Requirements Specification (link)

Architectural Design Specification (link)

Detailed Design Specification (link)

Poster (Link)

References

  • Superior glove. 2018
  • Medhi Deep and Ramasam Karthik. “ip traffic engineering”. 2018.
  • Daranyi Natalie. Shop and makerspace saftey. 2018.
  • “Ponemon Instituteâs 2017 Cost of Data Breach Study: Global Overview”. Probability and cost of a
    data breach. 2017.
  • terasolunaorg. 5.1. restful web service. 2019.
  • Korniluk Woldzimierz and Dartiusz Sajewicz. “method for estimating probabilistic models of touch
    currents and impedance of human body relying on the effects of electric shock”. page 10.

chenc4