RFID door using strike plate + Wiegand interface

Hmm, as you can see the first 24 bits of your two tags are the same, so the reader must be picking up on the last 26 bits of each tag, which means your site codes should be the same for both tags, but they aren't. The Phidgets spits out hexadecimal data for each tag, and the 3rd byte in is C4, which is 196 in decimal format, which your first tag is reporting on the Wiegand interface. From there it gets odd because the next 8 bits of tag 1 is BD, which should be 189 in decimal.

I'm not that familiar with arduino coding but it looks like the bits from pin 2 and 3 (data 0 and data 1) are getting mixed together in the reader1 variable... not that it matters for your application. I went ahead and bought one of these readers just to play with, but you should know the mathematical limitations of Wiegand26 make it much more likely that you'll see code duplication from tags with different IDs. For example, if you have two tags with IDs 01c8a50511 and A0B0a50511, I'm pretty sure the Wiegand reader will spit out the same ID code for both tags.

Now I'm both curious and impatient :) if you have a spare minute, could post the two separate Wiegand data outputs from the DATA 0 and DATA 1 lines for tags 1 and 2?

bolsontanker wrote: I would, but it's installed in a project box, in the wall, and the wall putty is drying.

Coolio. My reader is on the way already so I'll have something to play with soon enough.

bolsontanker wrote: As far as duplicate tags go, as I'm sure you know, I'm about as worried about that as I am about someone using a "bump key" method of opening my door, if they want in, they'll get in.

True ;)