Difference between revisions of "Door control system"

From London Hackspace Wiki
Jump to: navigation, search
(Replaced the outdated diagram with a graphviz generated one)
(Logging & maintenance)
Line 166: Line 166:
 
* The python script (doorbot.py) announces on successful initialisation.
 
* The python script (doorbot.py) announces on successful initialisation.
  
The service currently logs to /var/log/doorbot.log.  This will be moved to tmpfs to avoid disk sync issues. Note that killing the python script will be announced. To start or stop doorbot, use:
+
The service currently logs to /var/log/deamon.log on hamming, on perlman it sends the logs over the network to /var/log/network/perlman on boole (no local logs on perlman since it's an rpi). Note that killing the python script will be announced (really?). To start or stop doorbot, use:
  
 
  /etc/init.d/doorbot start
 
  /etc/init.d/doorbot start

Revision as of 19:50, 30 January 2014

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'

Doorbot listener scripts

on babbage /usr/local/bin/Doorbot/listeners

sudo service doorbot-listeners restart

Status

Below is quite out of date, we have 2 doorbots, one on the backdoor: Perlman, and Bell bell died, now using Hamming which will go on the red lobby interior door into the main space (NOT the roller shutter or the glass door inside the lobby). perlman broadcasts on 50000, and hamming 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.

    • Note: The sockets in the hallway which power the door release, have an inline fuse located just under the exterior light switch in the adjacent room.

Sol's Big button

  • white - common ground?
  • brown (dark) - button contact
  • yellow and black - not connected
  • red and blue: speaker
  • green and orange: either side of the bi colour led, maybe even to the green and orange sides!

Arduino pinouts

  • 13 - relay trigger?
  • 12 - led soldered on header
  • 0
  • 1
  • 2
  • 3

green & blue = wires from doorbell

button green wire A0

redLED yellow wire A2

greenLED red wire A1

Short length of phone cable from the parallel connector

  • orange -> orange
  • white with orange -> brown
  • green -> green
  • green with white -> white
  • blue - not used, speaker?
  • white with blue - not used, speaker?


Parallel Connector:

  • purple - back to door?

Overview

Front Doorbot

We have a 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 and reading the state of the doorbell is done by an arduino

<graphviz border='frame' format='png' >

digraph rfboard{
  rankdir=LR;
  size="12,5!";
  node [style=rounded];
  x86 [label="hamming",shape=box];
  usb_hub [label="USB hub - 7 port",shape=box];
  rfid [label="RFID reader",shape=box];
  x86_psu [label="12V DC PSU",shape=box];
  door_control_uc [label="Arduino",shape=box];
  transistor [label="Darlington transistor",shape=box];
  relay [label="Relay",shape=box];
  dc_dc [label="12V to 5V",shape=box];
  door_battery [label="12V Battery",shape=box];
  release [label="Release",shape=box];
  door_psu [label="14V DC PSU",shape=box];
  
  subgraph cluster_0 {
  	        door_control_uc -> transistor;
               transistor -> relay;
               relay -> release;
               dc_dc -> door_control_uc;
               door_battery -> relay;

label = "Door control"; }

  door_battery -> dc_dc;
  door_psu -> door_battery;
  x86_psu -> x86;
  x86 -> usb_hub;
  usb_hub -> door_control_uc;
  rfid -> usb_hub;


}

</graphviz>

Back Doorbot

We use a Tikitag RFID reader, in a black project box mounted on the wall outside the space by the backdoor. The reader is connected to a rPi which uses a KMtronic usb relay board to trigger the Cisa 11610 lock to open the door when authenticated.

The backdoor has no speaker(s) or buzzers, doorbell, or indicator led's.

Details

The software runs on hamming and perlman, and its code is on Github. hamming is a VIA EPIA something with 2 x 2.5in ata drives in a raid mirrir, perlman is a Rpi.

on hamming doorbot logs to /var/log/daemon.log, on perlman all the logs go over the network to /var/log/network/perlman on boole.

The access list is JSON file, downloaded from Turing.

The door opener broadcasts on the network whenever the door is opened by a member using there card, or if the front doorbell is pushed.

There are listeners on Babbage 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.

Card database

perlman and hamming download the card database every minute from Turing (the machine that runs the website).

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. Run the "Add card to Doorbot" script on Tesla and follow the instructions (basically, swipe your card and then enter your hackspace website login details).
  2. 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.
  1. 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

Glados Voice

Glados audio files are stored on Babbage at /home/glados/wavefiles/members. Set your wave file (in wav or mp3 format) on the members site. Generate your own from text using Tom's script at http://niceface.dyndns.org/glados/ (down temporarily)

Old guide

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

The 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 page. Type in your name and download the file
  • 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

Tom and I have looked for a vocoder or similar in Audacity that will do this for you. I'll make a video of this and stick it on YouTube at some point. Believe it or not, it is faster than the website as this is exactly what that website in the links is doing.

I'll see about implementing the processing algorithm in ChucK so it can be a command-line operation the next time I'm prototyping some FFT analysis stuff with it. -- Anthony

Managing Doorbots

Logging & maintenance

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

  • Issues are tracked on Github
  • 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.

The service currently logs to /var/log/deamon.log on hamming, on perlman it sends the logs over the network to /var/log/network/perlman on boole (no local logs on perlman since it's an rpi). Note that killing the python script will be announced (really?). To start or stop doorbot, use:

/etc/init.d/doorbot start
/etc/init.d/doorbot stop