Difference between revisions of "Door control system"
(remove this cos it dose not work)
|Line 113:||Line 113:|
== Managing Doorbots ==
== Managing Doorbots ==
=== Logging & maintenance ===
=== Logging & maintenance ===
Revision as of 20:23, 29 January 2014
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
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.
- 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!
- 13 - relay trigger?
- 12 - led soldered on header
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?
- purple - back to door?
We have a Tikitag RFID reader, embedded in the door, which we use to automatically trigger the Cisa 11610 lock to open when authenticated.
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 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.
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:
- 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).
- 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.
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 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)
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.
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
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/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:
/etc/init.d/doorbot start /etc/init.d/doorbot stop