[hackerspaces] RFID access was Re: WordPress websites - what features/plugins and configurations do your spaces use?

[Russell Fair]

I have a log of WordPress plugin development experience and would very much
like to be involved if you want help. Integrating with Woocommerce sounds
great, but I think having an api for the pi / rfid backend that "could" be
extended to work with any ecommerce plugin would be a good idea. We use
Restrict Content Pro because it has a membership component tied in. if you
convert the plugin to WC only it becomes a way edge case to use. Just
sayin...



On Tue, Dec 1, 2015 at 11:53 PM, Arclight <arclight at gmail.com> wrote:

> For the RFID hardware, we're using off-the-shelf Wiegand-format
> readers (available in 125Khz open-standard formats like EM4100 as well
> as Mifare/NFC) and the custom board we've been making/selling:
>
> http://accxproducts.com/wiki/index.php?title=Open_Access_4.0
>
> The server side can be a Pi bolted directly on or a USB connection to a
> server.
>
> It's a bit of work to roll a custom board with proper input protection
> and the like on every input.  This is one of our more successful
> open-source hardware projects to date.
>
> Arclight
> 23b Shop
>
> On Tue, Dec 1, 2015 at 6:24 PM, Russell Fair <rfair404 at gmail.com> wrote:
> > Bob, I'd love to see if we can use your plugin at our space. Any chance
> > you'd consider open sourcing it?
> >
> > Russell
> >
> > On Tue, Dec 1, 2015 at 6:40 PM, Shirley Hicks <
> shirley at velochicdesign.com>
> > wrote:
> >>
> >>
> >> On Nov 5, 2015, at 11:31 AM, sheila miguez <shekay at pobox.com> wrote:
> >>
> >>
> >> On Sun, Nov 1, 2015 at 10:48 AM, Bob Baddeley
> >> <hackerspace-discuss at bobbaddeley.com> wrote:
> >>>
> >>> Then it gets cool. We built another plugin on top of all these that
> >>> manages 'machines' in the space and their usage. We have RFID keys for
> door
> >>> access, and Raspberry Pi's at the doors. When an RFID is swiped, the pi
> >>> makes a web service request to our plugin to check the membership and
> >>> permission level of that user and allows them access. We have some
> caching
> >>> in place in case the web goes down, but essentially we have a web
> interface
> >>> that controls who has access to what physical things. We've also tied
> this
> >>> system in to our laser cutter, where we not only enable/disable the
> laser
> >>> based on whether the person has been trained, but we track the length
> of the
> >>> job and charge against their account funds for how many seconds of
> laser
> >>> time (since the laser tube is a consumable). We have a scale next to
> our 3D
> >>> printer area with a pi that lets you pay for plastic parts using
> account
> >>> funds as well.
> >>
> >>
> >>
> >> This is really interesting and I would like more details!
> >>
> >> So would I. And thanks for sharing the details! I’m finally compiling
> the
> >> list.
> >>
> >> — Shirley
> >>
> >> At PS1 we have a similar door control system that makes service requests
> >> to our member site. We use it to manage member information rather than a
> >> wiki plugin.
> >>
> >>
> >> I would like to know how you have tied your system in to the laser
> cutter
> >> and other tools.
> >>
> >> --
> >> shekay at pobox.com
> >> _______________________________________________
> >> Discuss mailing list
> >> Discuss at lists.hackerspaces.org
> >> http://lists.hackerspaces.org/mailman/listinfo/discuss
> >>
> >>
> >>
> >> _______________________________________________
> >> Discuss mailing list
> >> Discuss at lists.hackerspaces.org
> >> http://lists.hackerspaces.org/mailman/listinfo/discuss
> >>
> >
> >
> >
> > --
> > Thanks,
> >
> > Russell Fair
> > 770.401.9039
> >
> > _______________________________________________
> > Discuss mailing list
> > Discuss at lists.hackerspaces.org
> > http://lists.hackerspaces.org/mailman/listinfo/discuss
> >
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
>



-- 
Thanks,

Russell Fair
770.401.9039
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20151202/9621994d/attachment-0001.html>