Skip to main content
Question

Time clock reader and tag recommendations and limitations

  • Oct 22, 2026 10:27 AM UTC
  • 2 replies
  • 17 views

Forum|alt.badge.img+2

Is anyone aware of any device limitations, compatibility requirements, or recommendations regarding card readers and tags used with IFS Time Clock?

We have tested the reader and tags currently used by our client, but they do not appear to work with IFS Time Clock. The reader is connected through a serial COM port (COM5). 

It would be valuable information to have some quidance which devices are compatible with IFS Time Clock and which are not.

2 replies

ADDMARIAE
Superhero (Partner)
Forum|alt.badge.img+14
  • Superhero (Partner)
  • Oct 22, 2026 1:20 PM UTC

Hi,

I would say any reader is compatible as long as it works on the device you use for Time Clock. The reader should just be as an alternative to a keyboard… 

If you start notepad (or any editor) and connect the reader - can you capture what’s on the tag?

And if you open a dialogue on Time Clock(not card driven) and present your tag - doesn’t it show any data?

If you just get that to work it should work. 

 

There are some “limitations”:

  • All card numbers must be unique
  • Card number stored on employee in IFS is max 10 characters
  • You have to define Employee Card Parameters for each Time Clock and if the tag / card reads more than 10 characters you have to define what positions to actually read.

Regards,

Maria

 


Forum|alt.badge.img+2
  • Author
  • Sidekick (Partner)
  • Oct 22, 2026 2:23 PM UTC

Thank you Addmariae,

I tested the devices (reader and tag) on my laptop with a PuTTY program and the reader gave me the data.

When I tried the notepad it didn´t give any data and same with IFS Time Clock. In Time Clock it should give the error message if the tag id is not recognised but it doesn´t give anything so my assumption is that the reader is not compatible with Time Clock.

I guess the problem is the reader type which is COM port and recognized by my computer Device Manager as a Port, not as a Keyboard, could this be core issue?