Difference between revisions of "Door control system"

From London Hackspace Wiki
Jump to navigation Jump to search
(→‎Doorbot sounds: updated mountpoint info.)
(5 intermediate revisions by the same user not shown)
Line 8: Line 8:
 
=== Front doorbot ===
 
=== Front doorbot ===
  
[[Equipment/Wilkes]], is on the red lobby interior door into the main space (NOT the roller shutter or the glass door inside the lobby). We have a [http://www.touchatag.com/ Tikitag] RFID reader, embedded in the panel by the door, which we use to read member cards and then trigger the Asec something-or-other electric strike plate that opens the lock. Control of the strike plate is done by a USB relay, since the Arduino died. The doorbell currently is connected to an AC psu so the bell rings, but button pushes are not detected by the rpi.
+
[[File:New-doorbot.jpg|400px|thumb|right|The new front doorbot.]]
 +
The new front doorbot is based on the ACNode infrastructure, specifically a [http://www.ti.com/ww/en/launchpad/launchpads-connected-ek-tm4c1294xl.html#tabs TI Connected Launchpad], a [http://www.elechouse.com/elechouse/index.php?main_page=product_info&cPath=90_93&products_id=2242 PN532 NFC shield] with a generic Arduino relay board. The bell is a 24VAC-powered generic doorbell, and currently bell presses are not detected by the doorbot.
  
<graphviz border='frame' format='png' >
+
The front doorbot sends out notifications about starting up and scanned cards via UDP to the global broadcast address 255.255.255.255 on port 50002. Any network device can listen in to these messages and set up their own bot/reporting infrastructure, etc.
digraph rfboard{
 
  rankdir=LR;
 
  size="12,5!";
 
  node [style=rounded];
 
 
 
  x86 [label="RPi",shape=box];
 
  rfid [label="RFID reader",shape=box];
 
  psu [label="12V AC PSU",shape=box];
 
  psu2 [label="Powered USB Hub",shape=box];
 
  relay [label="KMTronic Relay",shape=box];
 
  release [label="Release",shape=box];
 
 
 
  subgraph cluster_0 {
 
                relay -> release;
 
label = "Door control";
 
}
 
 
 
  psu -> relay;
 
  psu2 -> x86;
 
  x86 -> relay;
 
  rfid -> x86;
 
 
 
 
 
}
 
 
 
</graphviz>
 
  
 
=== Back Doorbot ===
 
=== Back Doorbot ===
  
[[Perlman]] is in a wooden box on the inside of the back door. We use a [http://www.touchatag.com/ Tikitag] RFID reader, in a black project box mounted on the wall outside the space by the backdoor. We use a KMtronic usb relay board to trigger the Cisa 11610 lock to open the door when authenticated.
+
The back doorbot is the same as the front - with two differences: there's no bell, and the relay is activated by setting the pin state to HIGH. This instance sends notifications to port 50000.
 
 
The backdoor has no speaker(s) or buzzers, doorbell, or indicator led's.
 
  
 
==Software==
 
==Software==
The software runs on [[Equipment/Wilkes]] and [[perlman]], and its code is on [http://github.com/londonhackspace/doorbot Github].  Both are currently Raspberry Pis.
+
The source code for the software is on [https://github.com/londonhackspace/acnode-cl Github].
  
 
All the logs go over the network to /var/log/network/ on [[boole]].
 
All the logs go over the network to /var/log/network/ on [[boole]].
  
The access list is JSON [http://github.com/londonhackspace/hackspace-foundation-sites/blob/master/london.hackspace.org.uk/carddb.php file]. The machines have cron set up to download the card database every minute from [[Turing]] (the machine that runs the website).
+
The access list is JSON [http://github.com/londonhackspace/hackspace-foundation-sites/blob/master/london.hackspace.org.uk/carddb.php file]. The acserver downloads a new version of the carddb file every 5 minutes from [[Turing]] (the machine that runs the website).
  
 
The door opener broadcasts on the network whenever the door is opened by a member using their card <s>, or if the front doorbell is pushed</s>. The back door broadcasts on 50000, and the front uses 50002, so we can tell the difference between them in the various listeners.  This is a stop-gap until we add the door ID to the messages.
 
The door opener broadcasts on the network whenever the door is opened by a member using their card <s>, or if the front doorbell is pushed</s>. The back door broadcasts on 50000, and the front uses 50002, so we can tell the difference between them in the various listeners.  This is a stop-gap until we add the door ID to the messages.
Line 55: Line 28:
 
=== Doorbot listener scripts ===
 
=== Doorbot listener scripts ===
  
There are [http://github.com/londonhackspace/Doorbot/tree/master/listeners listeners] on [[Lamarr#Chomsky| the VM 'chomsky']] that connect to '''robonaut''' to announce on IRC, and <s>flash the lights using '''Lighted'''</s>. By default, this will include your full real name. If you wish to change this behaviour, you can set up a nickname [https://london.hackspace.org.uk/members/cards.php in the cards section] of the member area.
+
There are [http://github.com/londonhackspace/Doorbot/tree/master/listeners listeners] on [[hamming]] that connect to '''robonaut''' to announce on IRC, and <s>flash the lights using '''Lighted'''</s>. By default, this will include your full real name. If you wish to change this behaviour, you can set up a nickname [https://london.hackspace.org.uk/members/cards.php in the cards section] of the member area.
  
 
<s>[[hamming]] also runs listeners for the scrolling led board and the audio announcements.</s>
 
<s>[[hamming]] also runs listeners for the scrolling led board and the audio announcements.</s>
Line 95: Line 68:
 
If you make changes or discover a problem with doorbot, please add it to '''[[Door control system/Logbook|the logbook]]'''.
 
If you make changes or discover a problem with doorbot, please add it to '''[[Door control system/Logbook|the logbook]]'''.
  
* Issues are tracked [https://github.com/londonhackspace/Doorbot/issues/ on Github]
+
On [[hamming]], the listeners are at /root/Doorbot/listeners
* The main script is rundoorbot, which announces to irccat on Babbage if the python script dies.
 
* The python script (doorbot.py) announces on successful initialisation.
 
 
 
Note that killing the python script will be announced and emailed by Monit. To start or stop doorbot, use:
 
 
 
/etc/init.d/doorbot start
 
/etc/init.d/doorbot stop
 
 
 
 
 
On babbage, the listeners are at /usr/local/bin/Doorbot/listeners
 
 
 
sudo service doorbot-listeners restart
 
  
 +
sudo supervisorctl restart all
  
 
[[Category:Systems]]
 
[[Category:Systems]]
 
[[Category:Infrastructure]]
 
[[Category:Infrastructure]]

Revision as of 16:19, 1 July 2016

Preface

The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.

- Douglas Adams, 'Mostly Harmless'

Hardware

Front doorbot

The new front doorbot.

The new front doorbot is based on the ACNode infrastructure, specifically a TI Connected Launchpad, a PN532 NFC shield with a generic Arduino relay board. The bell is a 24VAC-powered generic doorbell, and currently bell presses are not detected by the doorbot.

The front doorbot sends out notifications about starting up and scanned cards via UDP to the global broadcast address 255.255.255.255 on port 50002. Any network device can listen in to these messages and set up their own bot/reporting infrastructure, etc.

Back Doorbot

The back doorbot is the same as the front - with two differences: there's no bell, and the relay is activated by setting the pin state to HIGH. This instance sends notifications to port 50000.

Software

The source code for the software is on Github.

All the logs go over the network to /var/log/network/ on boole.

The access list is JSON file. The acserver downloads a new version of the carddb file every 5 minutes from Turing (the machine that runs the website).

The door opener broadcasts on the network whenever the door is opened by a member using their card , or if the front doorbell is pushed. The back door broadcasts on 50000, and the front uses 50002, so we can tell the difference between them in the various listeners. This is a stop-gap until we add the door ID to the messages.

Doorbot listener scripts

There are listeners on hamming that connect to robonaut to announce on IRC, and flash the lights using Lighted. By default, this will include your full real name. If you wish to change this behaviour, you can set up a nickname in the cards section of the member area.

hamming also runs listeners for the scrolling led board and the audio announcements.

The announcement listener uses the GLaDOS voice. You can generate and use your own file as a greeting.

The code that runs the bandwidth meter on tesla also listens for doorbell and member entry messages.

Adding a card

Access is based on the RFID UID - it is not the number written on the back of your Oyster card. There are three ways to add a card:

  1. Use the Membership_Kiosk which is next to the book shelves.
  2. Run the "Add card to Doorbot" script on Tesla (hint: it's on desktop) and follow the instructions (basically, swipe your card and then enter your hackspace website login details).
  3. If you have a card reader get the code at Github and run addcard.sh. If you have another reader that can give you the UID, log in to the website and add it at the secret page. Note that doorbot is case sensitive; enter the (hex encoded) ID using upper case letters only.
  4. If you have an Android phone that supports NFC List of NFC-enabled mobile devices you can use this App (More details). Do remember to activate NFC connections on Config>wireless and network connections. Also, remember the app works with LHS membership Usernames and Passwords, not TFL's. and not the logins to this wiki... - Broken by new website changes, will differ fixing it until we get an API (and i get a new laptop) -- Jasper

Doorbot sounds

Doorbot audio files are stored in /mnt/doorbot-sounds/wavefiles/members. (Mounted on systems from colin:/doorbot-sounds) Set your wave file (in wav or mp3 format) on the members site. You may copy the files into the directory via chomsky.

Many early members enjoyed doorbot audio greetings in the style of GLaDOS - an artificial-intelligence sounding voice used in the Portal series of video games and in the movie Pacific Rim. Want to fit in with the 'classical' spirit of the Hackspace? Generate your own GLaDOS voice file on this site here.

Old GLaDOS Voice Generation Guide

There is a guide on Youtube made to show the process as its hard to describe simply in text: http://www.youtube.com/watch?v=OE8S9knXcW0

The original GLaDOS voices were generated by oni following the method found by Tom Wyatt. To create a GLaDOS voice one must do the following:

  • Go to ATandT's Text to Speech Website (now offline). Type in your name and download the file. Alternately, use Cepstral or another online text-to-speech site allowing downloads.
  • Load up the program Melodyne
  • Select the entire Waveform
  • Using the melodic algorithm, double click on one section of the waveform. I believe this moves the form to its nearest notes.
  • Using the zig Zag looking tool, flatten the pitch.
  • Up the pitch by dragging upwards by 160 or so.
  • Save

Managing Doorbots

Logging & maintenance

If you make changes or discover a problem with doorbot, please add it to the logbook.

On hamming, the listeners are at /root/Doorbot/listeners

sudo supervisorctl restart all