Cookie Consent by Free Privacy Policy Generator Update cookies preferences

Card Readers

Overview

A USB card reader lets operators log in to Tascus by tapping their existing site ID badge, instead of typing a username and password. It works with no extra software or drivers in Tascus, because the reader behaves like a keyboard and simply "types" the card number into the login screen.

This article covers why a card reader is worth using, the reader we have proven in a live Tascus deployment, and how it works on a Windows PC.

Why use a card reader

Tapping a badge takes about a second and removes the most common reasons operators share logins or stay logged in.

  • Faster changeovers. Operators log in and out in one tap, so shift and station changes don't hold up production.

  • Accurate traceability. Every step, sign-off and test result in Tascus is recorded against the operator who actually did it, not whoever logged in first.

  • No shared or written-down passwords. Operators stop sharing a generic login or sticking passwords to the screen.

  • Works with gloves and on touchscreens. No typing on small on-screen keyboards in a production environment.

  • Uses badges you already have. Most sites already issue access-control cards; the same card can log in to Tascus.

Supported devices

The HID OMNIKEY 5427 CK is proven in a live Tascus deployment and is our recommended reader.

Reader

Connection

Card types read

HID OMNIKEY 5427 CK

USB, keyboard wedge

125 kHz proximity (e.g. HID Prox) and 13.56 MHz contactless (e.g. iCLASS, MIFARE)

The 5427 CK reads both low-frequency (125 kHz) and high-frequency (13.56 MHz) cards, so it works with most site access badges without changing cards. Check your badge type with your site security team before buying.

Other readers that support USB keyboard wedge mode should also work, but have not yet been proven. Contact Tascus support before rolling out a different model.

How it works on a PC

The reader presents itself to Windows as a standard USB keyboard, so any application, including Tascus, receives the card number as ordinary typed text. This is called keyboard wedge mode.

  1. The operator holds their badge near the reader.

  2. The reader's antenna powers the card's chip by radio and reads its unique card number (125 kHz or 13.56 MHz, depending on the card).

  3. The reader converts that number into keystrokes, usually followed by an Enter key.

  4. Windows passes the keystrokes to whichever field has focus, exactly as if they were typed.

  5. Tascus receives the number in its login field and matches it to the operator.

Because Windows already has a built-in keyboard driver, there is nothing to install on the PC and nothing to configure inside Tascus to talk to the reader. The same approach is used by barcode scanners, which most Tascus stations already use.

The reader also supports PC/SC (smart-card) mode, used for secure Windows logon and encrypted cards. Tascus does not need this mode; keyboard wedge is the one to use.

Setting it up with Tascus

Setup takes about 10 minutes per station once each operator's card number is recorded.

  1. Plug the reader into a USB port on the Tascus PC. Windows installs it automatically as a keyboard.

  2. Open Notepad and tap a badge. You should see the card number appear, followed by a new line. If nothing appears, see Troubleshooting.

  3. In Tascus, go to Settings > Users and select the operator, set their password to the card ID number.

  4. Click into the password field and tap the operator's badge to enter its number. Save.

  5. Repeat for each operator.

  6. On the Tascus login screen, tap the badge to confirm the operator logs in.

Tip: enrolling by tapping the card into the field (step 4) avoids typing errors and guarantees the format matches what the reader sends at login.

Troubleshooting

Symptom

Likely cause

Fix

Nothing appears in Notepad when a card is tapped

Reader is in PC/SC mode, or the card type isn't enabled

Set the reader to keyboard wedge mode using HID's configuration utility, and enable your card type

Number appears but Tascus doesn't log in

The number enrolled differs from the one sent at login

Re-enrol the operator by tapping the card into the field, rather than typing it

Number appears in the wrong place

Another field or window had focus

Click into the Tascus login field before tapping

Number appears in an unexpected format (e.g. hex vs decimal)

Reader output format differs from the badge's printed number

Keep the reader's output format consistent across all stations and enrol by tapping

If a reader still doesn't work, contact Tascus support with the reader model and the card type your site uses.

Was this article helpful?

Thanks for your feedback!