<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext">Hi Tom,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">-- Dylan Klomparens<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> labnetwork-bounces@mtl.mit.edu [mailto:labnetwork-bounces@mtl.mit.edu]
<b>On Behalf Of </b>Mike Young<br>
<b>Sent:</b> Friday, April 14, 2017 10:10 AM<br>
<b>To:</b> Ferraguto, Thomas <Thomas_Ferraguto@uml.edu>; labnetwork@mtl.mit.edu<br>
<b>Subject:</b> Re: [labnetwork] Card Readers for equipment interlocks<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>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)!<span style="font-size:12.0pt"><o:p></o:p></span></p>
<p>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...<o:p></o:p></p>
<p>Good luck, and contact me offline if you'd like more of the gory details.<o:p></o:p></p>
<p>--Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 4/13/2017 1:47 PM, Ferraguto, Thomas wrote:<span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext">Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext">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.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext">Thanks in advance….<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext">Best Regards…<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:windowtext">Tom Ferraguto<o:p></o:p></span></p>
</div>
</div>
</body>
</html>