Integrating Access Control System with Hackerspaces Passport and Membership Software
Wise Cricket
- If you are interested in the project, please go to the group and sign up.
- There will be opportunities to work on embedded firmware, electronics, mechanics, encryption, and the membership software application.
- You can then control whether to get each email separately or receive a digest once a day.
Wise Cricket
- Arduino Uno board
- shop.23b.org awesome shield for battery charging, door strike drivers, Weigand interface
- Arduino Ethernet board
- Adafruit NFC card reader and a selection of Mifare cards
- Some wireless router TBD
- A PC for running membership software (hopefully Nadine from Office Nomads)
- Duct tape / Perl scripts / beer as appropriate
ITechGeek
Nexus S.
On Sep 12, 2:50 am, Wise Cricket <celestialproph...@gmail.com> wrote:
> We have ordered the parts
>
> After some discussions with our landlord we are starting the project with
> just a single door to Jigsaw's space within the large Inscape building.
> Hopefully we will expand to the 5 external doors and the parking lot at some
> point a little later but we need to do a proof of concept first.
>
> So our design will be:
>
> - shop.23b.org awesome shield for battery charging, door strike drivers,
> Weigand interface
> - Arduino Ethernet board
> - Adafruit NFC card reader and a selection of Mifare cards
> - Some wireless router TBD
> - A PC for running membership software (hopefully Nadine from Office
> Nomads)
> - Duct tape / Perl scripts / beer as appropriate
ken larson
I mention this because the 23b board expects a Wiegand (data0/data1) input using 2 pins, but the Adafruit NFC reader integrates at a lower level, with more pins.
http://www.ladyada.net/products/rfidnfc/wiring.html
A couple of ideas come to mind:
- one is to connect the NFC board in like in the Adafruit sample, and modify the 23b sketch to include some of the Adafruit code. I'm not sure whether the optocoupler on pins 2&3 would mess things up, whether there is some way to either bypass it, or add the capacitors on like you do if using a higher-speed Wiegand reader.
- another would be to use a second Arduino for the NFC board, and modify the Adafruit sample to add code to output a Wiegand signal, and then connect the Wiegand output to the Wiegand input on the 23b shield. I've done some things like this in the past for testing one Arduino using another.
One disadvantage of both of these options is that the only thing being read is the unencrypted ID number from the NFC tag (or phone). I'm not yet experienced enough with NFC to be able to say how you might perform, say, a challenge/response to a key on the NFC tag (or phone).
Ken
Scott Bailey
Scott Bailey
Will Bradley
I have a high frequency reader that uses wiegand for signaling. Haven't tested it yet tho. Remember that nfc is not a wire protocol (and, wirelessly, is a bunch of disparate HF protocols) so the conversion really happens in the reader itself.
Attempts to do challenge-response with open protocols have been sparse from what I've seen. The industry could use some open innovation.
Arclight
I took a look at the NFC tutorial, and it looks like it attaches via SPI. You can use the SPI pins on the Open Access that are left open accessories. The only problem is that you can't extend SPI very far, so the NFC reader would need to pretty much sit on top as a shield.
The best option would probably be to design a board with its own micro and RS232, RS485, Wiegand, or whatever you needed as outputs to the panel/controller. While you're at it, get a 3.3V version and eliminate the buffer chip.
Arclight
ken larson
Which means that you are unlikely to be able to build a system to get in the door using a phone, where the reader is a normal NFC/RFID reader.
An interesting alternative to explore is the peer-to-peer NFC mode. A reader on the door capable of this could support an NFC phone such as the Nexus S, peer-to-peer mode is working today.
See this link:
ITechGeek
tag and it sounds like w/ the peer-to-peer model since it allows for
2-way communication, you might even get a basic level of encryption in
there so that you don't have to worry about someone maybe picking up
the transaction and duplicating it.
The problem w/ even RFID credit cards is that even though there is
encryption, my understanding is there is no system in there for
authentication of who the card is talking to and will therefore talk
to any reader near it. I always thought it was an interesting idea of
when you hand your card to a waiter, they could have a reader in their
sleeve that would read the data on the card on the way to being
swiped. Just the waiter holding the card for a few seconds and they
would have all the information needed to reproduce the card, then
clone the RFID itself (not even the face of the card) w/ reusable RFID
chips and blow through dozens of people's credit cards w/ a laptop, a
reader, and an RFID chip.
Might have to go a little more powerful then an Arduino (Maybe a
Sheevaplug which would then send the unlock command to the Arduino?)
but then have some sort of asymmetric encryption based on x.509 or PGP
based certificates (I would say x.509 since it is the most widely
used).
Arclight
phone in peer mode might be the way to go.
On another note, the guys from the Raspberry Pi Linux server project
are coming to Los Angeles next month, and I'm going to try get them to
come by and talk to us about their system.
A $25 board that runs a real Linux OS might be just the thing for the
"Level 2 management server" tasks we all seem to need for a secure
system.
This device really seems to bridge the gap between "roll your own
software in C after designing a 32-bit embedded system" and "hook up
to a full-size PC" and comes in at a cheap enough price point that one
of these could be on every 1-4 doors, with access to any type of Linux
software or library you might want to use.
Arclight
ITechGeek
Pi would be all you'd need for management. Although if you could make
this interact w/ cell phones w/ a small app on the cell using NFC
peer-peer (Or how about Bluetooth?) and actually secure the coms, you
might have the basis to unseat RFID as a primary form of electronic
access control (hey, can we file a patent for unlocking doors via
bluetooth???) (=
Use Bluetooth between the phone and a reader to connect to the
Raspberry Pi, use a handshake similar to https to create a secure
connection then send the tag info to unlock the door.
Might even be able to extend the system to a Level 3 management server
(a standard desktop computer) for like whole building (multi-zone)
implementations.
Any Android devs on this list???????
Arclight
good dev platform for this:
http://wiki.032.la/nsl/RFiddle
Arclight
Alan Widmer
Arclight
Alan,
It sounds like you made progress. For extended range, you could also consider attaching an Arduino or other micro to the NFC device via SPI, then doing RS232 or RS485 out to the panel. The software serial or newsoftserial libaryy can give you more ports.
Emulating Wiegand output is also possible.
Oh, and you can use the analog pins as D15..D19 if you need to. Just don'y use the I2C pins, as the real-time clock uses those.
Arclight
ken larson
Anyway, it does look like the NXP PN532 chip on that board does fully support peer-to-peer, so in theory it should be possible to communicate with a phone that way.
Ken
Alan Widmer
Alan Widmer
Wise Cricket
rrix
On Wednesday, August 31, 2011 9:58:01 AM UTC-7, Wise Cricket wrote:
rrix
Ryan Rix
*switches back to email*
On Tue 17 April 2012 22:04:50 rrix wrote:
> Uhm, google groups's new ui just pooped all over me and posted that to the
> wrong thread, haha. :(
>
> On Tuesday, April 17, 2012 10:03:41 PM UTC-7, rrix wrote:
> > Does space federation not realise we've solved this problem?
> >
> > r
> >
> > On Wednesday, August 31, 2011 9:58:01 AM UTC-7, Wise Cricket wrote:
> >> Jigsaw Renaissance <http://www.jigsawrenaissance.org/> are looking into
> >> integrating
> >> Nadine<http://wiki.coworking.info/w/page/31359618/NadineProject>>>
> >> and Hackerspaces
> >> Passport<http://hackerspaces.org/wiki/Hackerspaces_Passport> with>>
> >> our door locks <http://wiki.jigren.org/Inscape_Access_Control_System>.
> >>
> >> If you are able to commit time to help us designing or building, please
> >> post to:Inscape Access Control
> >> System<https://groups.google.com/forum/#!topic/inscape-access-control-sy
> >> stem/ijn9H9XR_90>>>
> >> - If you are interested in the project, please go to the group and
> >> sign
> >> up<https://groups.google.com/group/inscape-access-control-system/subsc
> >> ribe>
> >> .
> >> - There will be opportunities to work on embedded firmware,
> >> electronics, mechanics, encryption, and the membership software
> >> application.
> >> - You can then control whether to get each email separately or
--
Ryan Rix -- http://rix.si
== OpenSource.com: Where Open Source Happens! ==
_
\/"/_ All Hail the Beefy Miracle!
/_/
\ \
Arclight
Heh, that's just what you wanted, right? :)
So yes, I'm signed up for the "unconference." At this point, we have a typical open-source project, where it's been developed to working reliably but that's about it.
Since I'm just about sold out of the original Open Access board at this point, I figure this is a good opportunity to finish up the new version of the board this week.
Of note is:
-Increased stand-alone user count by way of a 128K eeprom
-Full support of all of the lines on the Wiegand readers (blinky LED and beeper)
-Optional built-in Arduino on board
-No more glass fuses (all self-resttting PTCs)
-Better expansion (extra I/o and 2 types of Ethernet boards supported)
Arclight
David M. N. Bryan
-David
Of note is:
*switches back to email*
> >> For more information about JR ( www.jigsawrenaissance.org ), please visit
Arclight
David,
The new system has a 1Mb eeprom chip that will support about 12,000 users. Since SSD devices only work on 3.3V, I am putting the SSD and ethernet on a separate daughter board. You can also buy the Arduino Wiznet board with SSD and plug it in.
Here is what the new board will look like:
http://23.org/~arclight/pic/access_v31.png
Arclight
David M. N. Bryan
--