[labnetwork] Fw: Card Readers for equipment interlocks

Khanna, Rohit r.khanna at ucl.ac.uk
Fri May 5 05:59:15 EDT 2017


Daer Members,

                           Hope you are doing good. A brief introduction, I am an Electronics engineer

working with UCL (University college London). We have a Clean room facility at London Center for NANO Tech.

Incidentally I was directed to this mailing list by my manager Steve Etienne as we were also exploring option for

card access for clean room equipment.


We had also developed a custom solution for cleanroom equipment control. The hardware prototypes have been developed by me

and has been under trial for a few months with few simple equipment we have. So far the hardware seems to be working

reasonably well. The system is based on wired ethernet  or WiFi (there have been two separate version of the hardware).

The current firmware supports usage logging only as I didn't have the requisite support/expertise for developing the PC side

application/middle ware which would accept UDP/TCP requests from multiple control units and run verification requests

with the data base and send back confirmation UDP/TCP packets to the hardware units to unlock equipment.


Here is a youtube link for the system demo: https://www.youtube.com/watch?v=S9hz3KTrfno&t=30s

If this seems interesting we could discuss possibility of developing the system further and share designs for mutual benefit.


Also, I am attaching the system overview block diagram for the same.


Warm Regards
Rohit Khanna
Electronic Test & Measurement Engineer
London Center for NANO Technology, UCL
Ph:+44-020-7679984
Int Ext: 39984
Mob: +44 7456265557


________________________________
From: Etienne, Steve
Sent: 24 April 2017 10:55
To: Khanna, Rohit
Subject: FW: [labnetwork] Card Readers for equipment interlocks


Rohit,



Are you subscribed to this mailing list?  It has some information about access systems from time to time.  You could also contribute if you wish.



Steve



From: labnetwork-bounces at mtl.mit.edu [mailto:labnetwork-bounces at mtl.mit.edu] On Behalf Of Price, Aimee
Sent: 18 April 2017 18:30
To: Klomparens, Dylan L. (Fed) <dylan.klomparens at nist.gov>; Mike Young <mike.young at nd.edu>; Ferraguto, Thomas <Thomas_Ferraguto at uml.edu>; labnetwork at mtl.mit.edu
Subject: Re: [labnetwork] Card Readers for equipment interlocks



We have a home built system that utilizes Raspberry Pi.  Users fob in and out of the equipment and it talks to our database to ensure they are certified to use that equipment.  We use it for billing as well.



Our engineer who designed it is out this week and much of next, but if you contact me I can put you in touch with him.  I’m not sure if he’s on this list or not.  He and our IT engineer worked through a lot of the issues and bugs.  We are happy with it for the most part.



Aimee



From: labnetwork-bounces at mtl.mit.edu [mailto:labnetwork-bounces at mtl.mit.edu] On Behalf Of Klomparens, Dylan L. (Fed)
Sent: Tuesday, April 18, 2017 10:33 AM
To: Mike Young; Ferraguto, Thomas; labnetwork at mtl.mit.edu
Subject: Re: [labnetwork] Card Readers for equipment interlocks



Hi Tom,



CNST has “tap in/out” system to control physical access to the cleanroom and tool interlocks. We use wall mounted Windows tablets that communicate with our lab management software, NEMO. I’ve attached a picture and parts list of one of the entryway tablets. I have received many positive comments about this system, the users really enjoy the convenience and speed of logging in. It’s been working well for over a year now.



I enjoyed reading Mike Young’s response, since we’re also working on improved interlocks using the Raspberry Pi. We have a working prototype (read: kludge) for a single tool. The eventual goal will be to polish it to product level quality. What’s nice about the Raspberry Pi is that it has the potential to enable us to collect data from sensors, or create a small embedded systems controller for tools. While prototyping, I’ve successfully programmed a Raspberry Pi to read an ID number from my government badge. I’d be interested in continuing a conversation about this off-list if anyone is interested in collaborating on Raspberry Pi interlocks.



-- Dylan Klomparens



From: labnetwork-bounces at mtl.mit.edu<mailto:labnetwork-bounces at mtl.mit.edu> [mailto:labnetwork-bounces at mtl.mit.edu] On Behalf Of Mike Young
Sent: Friday, April 14, 2017 10:10 AM
To: Ferraguto, Thomas <Thomas_Ferraguto at uml.edu<mailto:Thomas_Ferraguto at uml.edu>>; labnetwork at mtl.mit.edu<mailto:labnetwork at mtl.mit.edu>
Subject: Re: [labnetwork] Card Readers for equipment interlocks



Hi Tom. We use Coral, along with a mix of internet-based interlocks. We also use RFID cleanroom badges. I have made a first-cut implementation of this for one of our resist spinners, using a Raspberry Pi and an RFID reader. It's a bit of a kludge, I think I can do better, but it is functional. I'd extend the implementation to other tools also, if the darn readers weren't so expensive (~$100 each)!

What I have not addressed, is how to do this for equipment which collects run data at disable. I suppose if coral could download the run data from the tool at disable, via SECS or some other interface... That's how the Big Boys do it...

Good luck, and contact me offline if you'd like more of the gory details.

--Mike



On 4/13/2017 1:47 PM, Ferraguto, Thomas wrote:



Colleagues,



Has anyone integrated RFID card readers to their equipment interlocks. I’d like to set up a system where the “Tap in” & “Tap Out” ID the user on opens the interlock on the tool.



Thanks in advance….



Best Regards…



Tom Ferraguto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20170505/4e68e2d5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Smart access system.pdf
Type: application/pdf
Size: 645169 bytes
Desc: Smart access system.pdf
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20170505/4e68e2d5/attachment.pdf>


More information about the labnetwork mailing list