Where reading errors come from
A scanner working as a keyboard sends key codes, not characters. The operating system converts those key codes into letters according to the current keyboard layout. When the gate computer uses the PL layout with Caps Lock switched on, or when the scanner is set to the AZERTY country, the characters and letter case are distorted.
The symptom is deceptive: the code appears to read correctly, but the character string does not match any token. The guard sees a refusal with a valid badge and assumes the badge is faulty.
How the system limits the risk on its own
The parser in the system converts the read text to lower case and recognises the token with one rule shared by the server and the browser. As a result, a change of letter case caused by Caps Lock does not break reading a token stored in hexadecimal.
The same rule handles two formats: old proximity cards circulate as bare digit strings, and QR badges as an address with a token. A revoked card is rejected by the gate. There is therefore no need for a separate path for cards or a separate scanner.
Good practices for IT and security
The parser helps, but it does not replace order in the configuration. The practices below reduce the number of surprises at the gate.
Set one keyboard layout for the station
The gate station should have one keyboard layout, recorded in the documentation. Changing the system language by a shift worker is a typical source of problems. Lock layout switching if the station policy allows it.
Check the country in the scanner
The factory country setting in the scanner must match the computer's layout. A new scanner with the default AZERTY setting out of the box produces distorted characters on a PL keyboard. Scan the configuration code from the manufacturer's manual and check the result in a text window.
Test on real badges and cards
A test with a test card is not enough. Scan an active badge, a revoked badge and an old proximity card. The active one should open the gate; the revoked badge and the revoked card should be rejected.
Troubleshooting in three questions
When the gate rejects a valid badge, check in order: whether Caps Lock is on, whether the scanner has the correct country set, and whether the keyboard layout in the system is PL. This order catches most cases before anyone suspects the label or the printer.
If the scan in a notepad window shows different characters than the label, the problem is in the scanner or the layout, not in the system. If the characters are correct and the gate still rejects, the cause is the state of the badge, for example a revocation.
Checklist
Video
Frequently asked questions
Why does the scanner read the code but the gate rejects it?
Most often the characters were distorted by Caps Lock, the keyboard layout or the country set in the scanner. Check the scan result in a text window.
Do I need a separate scanner for cards and QR codes?
No. The same recognition rule handles cards as digit strings and QR badges as an address with a token.
Does the letter case of the token matter?
No, because the parser converts text to lower case before recognition.
What should I do with a revoked card?
Nothing on the scanner side. The gate will reject it on recognition.
Configure the gate without distortion
We will help IT and security pass a scanner test on active and revoked badges. Book a call with InnerWeb.
Let's talk