Maker Barn Organizer Creates Makerspace Access Control System

The MakerBarn is a new makerspace between The Woodlands and Tomball, TX (north of Houston). [George Carlson], one of the founders and a retired design engineer, wanted to make sure only members certified on a machine could use it. He worked with [Kolja Windeler] to create the MACS or Makerspace Access Control System. He has one video explaining MACS and, after the break, another explaining the browser based user interface for the system.

20151205_181615A control box, [George] calls them stations, controls the power to a machine. Member badges have an RFID tag that is read when inserted into the station’s reader. If the member is authorized to use the machine, the power is enabled. For safety, the member’s badge must remain in the reader to maintain power. The reader uses a Photon board from Particle with a WiFi link to a Raspberry Pi server.

[Kolja] developed a Pi system to maintain a database of member numbers and the machines they can use. The list is sent to the stations periodically or when updates occur. The user interface is browser based on the MakerBarn’s LAN so it can be maintained by a computer or smartphone in the space. Presently 21 MACS modules have been built with some going to Hanover University in Germany for their auto hobby shop.

Not only did [George] lead the effort on creating MACS but has been key to getting the construction done inside a pole barn to make the MakerBarn a reality.

13 thoughts on “Maker Barn Organizer Creates Makerspace Access Control System

  1. I had a similar idea once, but I was just going to use it to keep track of who used a machine last, so there would be no finger-pointing when the machine ends up damaged from misuse. By adding the authorization system, this incarnation helps prevent the misuse from occurring in the first place.

      1. I visited their space last year and saw it in operation. unfortunately it is not well implemented and documented. The github documentation is inaccurate as they have changed their firmware/hardware without documenting it.

    1. Put me down for thirding the motion. Tx/Rx in central Houston has been talking about doing something like this for at least two or three years. Having a codebase and recommended hardware to work from would probably allow them to get the project (further) off the ground.

      1. Fourthed?

        This is nifty – I like the “card has to stay in place” solution, as we were trying to figure out how to do it safely with timers.

        We’re looking to build a similar system that ties into our membership database on an external service. That way we’ll have updated data when we run training classes (from the class registry) as well as automatically integrating the access control system with our payment processor. Another integration we’re working towards is showing a public calendar on the site to indicate that the machine is in use. This type of system also enables per-hour machine rates easily enough.

        There’s a lot of benefits here.

    1. You are correct. For a few dollars you can purchase a devices that is capable of coping the cards. So I certainly would not use standard EM4100 type RFID cards for building access. In the shop they work fine, the MACS log would quickly show duplicate badge usage.

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.