[hackpgh-discuss] Re: RFID timeclock

  • From: Matt Stultz <matt@xxxxxxxxxxxxxxxxxx>
  • To: hackpgh-discuss <hackpgh-discuss@xxxxxxxxxxxxx>
  • Date: Tue, 3 Mar 2015 18:17:32 -0500

Okay, Eli just pointed out that my post sounded dickish. It was not
supposed to be that way at all. I was just typing the email out quick to
try to be helpful and since I was, halfway through the email, I did the
search and that's what I found, the "oh wait, quick google search" was
literally "type type type 'wait I wonder if I can provide a link that would
help... oh here is one but I don't have time to vet and see if there is a
better one'". So again, I'm sorry if this came across like a dick, it was
not intended on being that way.

Thanks,
Matt

On Tue, Mar 3, 2015 at 5:18 PM, Matt Stultz <matt@xxxxxxxxxxxxxxxxxx> wrote:

> I would find it hard to believe that there is no "kiosk" mode for android
> where you tell it to start an app on startup and not lock the screen. Oh
> wait, quick google search provides this:
> http://sdgsystems.com/blog/implementing-kiosk-mode-android-part-1/
>
> Thanks,
> Matt
>
> On Tue, Mar 3, 2015 at 5:04 PM, Joseph Ates <joey@xxxxxxxxxxxxxx> wrote:
>
>> Hi Anthony!
>>
>> Yeah. I think scanning NFC from android apps is a no go situation under
>> lock screen conditions. That being said, there's a developer option to keep
>> the screen awake when connected to usb (or usb power sources) which would
>> be ideal for the "clock" tablet.
>>
>> USB would of course be cool as well. As an aside, I also think it would
>> be cool if one could leverage the android accessory USB protocol/interface
>> as a NFC reader to a tablet as the accessory in the standard can double as
>> a 500mA power source. [1] I think there's even an arduino mega[2] designed
>> for use as an android accessory, so all it'd need is an NFC reader shield.
>>
>>
>> [1] https://source.android.com/accessories/protocol.html
>>
>> [2] http://developer.android.com/tools/adk/adk.html
>>
>>
>> On Tue, Mar 3, 2015 at 4:00 PM, Anthony Cascone <ajc317@xxxxxxxxx> wrote:
>>
>>> Dude, you're alive.
>>>
>>> NFC makes sense for the reasons you pointed out.
>>>
>>> Personally, I'm not an app developer and would rather avoid it, but
>>> could make sense. At tablet would be cool because of the built in display,
>>> but there would be details like would the app have to be active to receive
>>> the NFC. If you had to wakeup the tablet every time to wanted to punch
>>> in/out you might as well drop the NFC aspect. All that said, there may be
>>> an app for that... again, I'd look before you build something.
>>>
>>> There are USB NFC interfaces too. Just saying.
>>>
>>> On Tue, Mar 3, 2015 at 3:49 PM, Joseph Ates <joey@xxxxxxxxxxxxxx> wrote:
>>>
>>>> To be honest, I think NFC is a bit more accessible to do this kind of
>>>> application considering it's in the back of most android/windows smart
>>>> phones. You could use a Nexus tablet as the "clock" and have employees use
>>>> their smartphones to scan past it. You could also issue small cards with
>>>> embedded NFC tags for those employees who don't have smartphones.
>>>>
>>>> On Tue, Mar 3, 2015 at 2:03 PM, Anthony Cascone <ajc317@xxxxxxxxx>
>>>> wrote:
>>>>
>>>>> I'm not aware of any projects that currently exist that you could just
>>>>> copy and past, but I'll be honest, I didn't bother searching at all. I'll
>>>>> leave that to you.
>>>>>
>>>>> In its most basic form, you'll need an RFID reader, tags, and some
>>>>> sort of computer. Depending on how you want it set up, you could use your
>>>>> own computer, or get a dedicated system. A RaspberryPi would be more than
>>>>> sufficient if you want a dedicated, low power, portable system. 
>>>>> Regardless,
>>>>> of the computer, for ease of integration, I would recommend a USB enabled
>>>>> RFID reader. That can be fairly cheap if only need it to operate indoors.
>>>>> Parallax has one I think. If you needed it our doors, you'll have to pay
>>>>> more or you a mixture of parts to get it to play nice with a computer.
>>>>>
>>>>> Once you have the reader, you'll need something to listen to the
>>>>> reader on the computer, and then log the time/date that the tag was read.
>>>>> From there, it's up to you on how the data is displayed.
>>>>>
>>>>> I have a feeling that such a project might already exist, but it
>>>>> shouldn't be too hard to whip something up.
>>>>>
>>>>> On Fri, Feb 27, 2015 at 5:37 PM, Chris Williams <cwilliams2@xxxxxxxxx>
>>>>> wrote:
>>>>>
>>>>>> Please forgive my lack of clarity.
>>>>>>
>>>>>> Anthony's explanation most accurately described the goal. The RFID
>>>>>> tag will be the timecard for the timeclock. The tag will initiate when a
>>>>>> person has clocked in and out. In addition, I want to create a log with
>>>>>> timestamps.
>>>>>>
>>>>>> -Chris
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Friday, February 27, 2015, Anthony Cascone <ajc317@xxxxxxxxx>
>>>>>> wrote:
>>>>>>
>>>>>>> While we are playing the guessing game. I suspect he means a time
>>>>>>> tracking system using RFID tags to "punch in" and out.
>>>>>>>
>>>>>>> A device that generated tag IDs that corresponded to the current
>>>>>>> time would be an interesting project though.
>>>>>>>
>>>>>>> Regardless, additional details would help to understand the scope.
>>>>>>>
>>>>>>> On Fri, Feb 27, 2015 at 10:07 AM, Yevgeniy Soroka <
>>>>>>> ukranians2@xxxxxxxxx> wrote:
>>>>>>>
>>>>>>>> I suspect he means an RFID chip which transmits the time when you
>>>>>>>> scan it?
>>>>>>>> -Geno
>>>>>>>>
>>>>>>>> On Fri, Feb 27, 2015 at 10:00 AM, Tim Cannon <timmycninja@xxxxxxxxx
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> start by explaining what you mean, RFID is usually passive and
>>>>>>>>> simply transmits an ID over low frequency radio.
>>>>>>>>>
>>>>>>>>> On Fri, Feb 27, 2015 at 9:33 AM Chris Williams <
>>>>>>>>> cwilliams2@xxxxxxxxx> wrote:
>>>>>>>>>
>>>>>>>>>> Dear Hack Pittsburgh,
>>>>>>>>>>
>>>>>>>>>> I am interested in learning how to develop an RFID timeclock.
>>>>>>>>>> Chad suggested that I ask the group.
>>>>>>>>>>
>>>>>>>>>> Where is a good place to start?
>>>>>>>>>>
>>>>>>>>>> Thanks!
>>>>>>>>>>
>>>>>>>>>> -Chris
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>
>

Other related posts: