[Rack] doorport - do you know how the door opener works?
jake at spaz.org
Wed Dec 7 18:50:06 PST 2011
jake at pony:~$ cat opendoor
echo -n 'OPEN!' | socat stdio udp4:minotaur.noisebridge.net:30012
jake at pony:~$ ./opendoor
Acknowledged. Buzzing it open.
jake at pony:~$
On Wed, 7 Dec 2011, Danny O'Brien wrote:
> echo -n 'OPEN!' | socat stdio udp4:minotaur.noisebridge.net:30012
> should do it for now
> On Wed, Dec 7, 2011 at 5:29 PM, Jake <jake at spaz.org> wrote:
> so, is there a way to open the door from my computer yet?
> On Wed, 7 Dec 2011, Danny O'Brien wrote:
> On Tue, Dec 6, 2011 at 10:35 PM, Jake <jake at spaz.org> wrote:
> Jake, what is the difference between https://www.noisebridge.net/wiki/User:Jake and
> i don't know, i guess they are both me. I made the jerkey one to edit wiki pages, and i made the jake
> one so that
> i could be given ssh access to pony.
> Do you want your SSH key for "jake" pushed to minotaur?
> yes, that would be great. so, what's that machine "for" and what is running on it?
> I'm happy to help facilitate making anything related work with the hardware/software, since I feel
> I know it well. However, from my perspective, it was already working. Coming onto the list and
> "Help! Make the door work!" doesn't make it clear what you're looking for, or how anyone can help
> I did the hardware, since there was nothing to plug the door wiring into anymore (the Wise box was gone
> and i heard
> they are bunk anyway) but I had nowhere to begin to try to get it to work with the new setup.
> It turns out that the hardware was working when i sent that message, except that a wire had come loose
> on the
> dooropener circuitboard, which I fixed with Danny. But hardware is nothing without software, and there
> was no
> software on the Minotaur to activate it. It's fixed now, says Danny.
> I just tried out the software jof put on it, but it seems to work (the daemon is running now too, but I
> didn't put in an
> init script to restart it on boot). The webscript is also not fixed to work with it yet.
> rock on!
> I put the two most-helpful tools for dealing with the hardware on minotaur:
> - /usr/local/sbin/open-door (a setuid root binary that "buzzes" open the door with the
> port hardware)
> - /usr/local/sbin/parport_daemon (a setuid binary that takes control of the parallel port,
> starts listening on UDP
> 0.0.0.0:30012, and talks a simple protocol to query the state of the ringer and open the
> Personally, I'd like to use the parport_daemon program going forward, though most of the
> others use are not setup
> to use it just yet. The protocol is dead simple. Ask it "Sup?" and it will respond with
> "Nothing." (nobody's ringing) or
> "RING!" (someone is or just rang the gate buzzer). If you send it "OPEN!" it will respond
> "Acknowledged. Buzzing it
> open." (buzzes open the door) or "Already opened recently." (if someone beat you to it --
> a timeout to avoid
> wailing on the solenoid).
> So, to open the gate from pony, one could do something like: echo -n 'OPEN!' | socat stdio
> I should probably make a wrapper script or controller around that next.
> I'm also thinking it would be cute to have the computer hosting the daemon to also announce
> Zeroconf/Avahi service
> records for the door. Maybe _door._udp?
> Rack mailing list
> Rack at lists.noisebridge.net
More information about the Rack