DooRFID project VB2008

Post your VB2008 source files

I'm at a conference until the middle of next week, but I'll take a look at it then.

What version of Phidgets do you have? The damn people over there keep changing the hardware around just like they do the software library. It might be something as simple as you have the wrong library for your hardware version.

Basically, I don't know of any good way to tell hardware version just looking at it. But, you can tell at least what version family it is by describing it. Is it dark with a hole in the middle or is it light colored with the word PhidgetRFID silkscreened in the middle?

The software version that spits out the tag ID 20 times is the working model. This is a major change in the firmware's functionality that Phidgets put forward with one of many hardware changes. It's up to you to decide what to do with each event (dump duplicates, log, etc.).

Create a static or global variable that holds the last read tag ID. This variable could be called strLastTag or something similar. When the next read event fires, check first to see if the ID matches the last one read. If so, dump out of the event routine without doing anything.

If you want to get fancy, you can create a sort of timer so the old tag ID will be cleared out after a certain amount of time... say 5 seconds? To do this, create another static/global variable that holds the date and time the tag ID was put into the strLastTag variable. This variable could be called datLastTagTime and should be populated with the date and time, like so;

datLastTagTime = Date & " " &  Time

Then the next time the tag ID even fires, check the date and time stored in the datLastTagTime variable against the current date and time using DateDiff. If the difference is over 5 seconds, clear the datLastTagTime and strLastTag variables and process the tag ID event as normal.

You might be asking "Why put the date in as well as the time if I'm only looking for a 5 second difference?", well the reason for that is the midnight factor. It's just good habit to get into to put both date and time into your time differencing checks because if an event were to occur within 5 seconds of midnight, the time differencing routine may not account for the fact it's midnight and the time clock just flipped to the next day. You would either end up waiting for 24 hours for the differencing check to clear, or in some cases it will never clear because the same thing would happen on the next round. By including the date, the time differencing routine knows that 11:59:59 PM and 00:00:00 AM are only one second apart. Without the date it would assume those two times are 86399 seconds apart.