Go back to list

Introduction

This article will help you if the card reader connected to the POSweb has stopped working. Here you will find instructions on how to deal with the most common cases.

The instruction is made for the following card reader models:

  • GAT Writer 6000F / GAT Writer 5250B - Gantner USB readers
  • Unicard reader - card readers that emulate COM port connection
  • AccessServerCardReader - network reader that works as a POS reader 
  • NFC reader - ACS card readers
  • GAT net writer 7000 - Gantner network reader for reception desks

Instruction 

GAT Writer 6000F / GAT Writer 5250B

  • Check if card reader is visible in the Device manager. 
  • Check if GAT Direct Connect has been installed. It so, restart it, and then restart DeviceIntegrator.
  • If you use GAT Relaxx, check if the address in the FID card reader is correct. 
  • Check the logs. If you see a message that the date can't be saved on the card, check if the FID card reader has been set up correctly. 

 Unicard reader

  • Check if the reader has been set up correctly on POSweb
  • Check if card reader is visible in the Device manager and if the port set up on POSweb is correct. 
  • Check if the baud rate is right. 
  • If the card has been read but the wrong number is displayed and no user is found, check if the correct value has been set in the Unicard mode. 
  • If the card number is too short or too long, it means that wrong card number length has been set in the UnicardLength and UnicardLengthDecoded options. 
  • If the set up has been done correctly, but the reader doesn't read the card, stop the DeviceIntegrator service, download Putty program and open the port to see if the card scans: 

    • select the COM port option,
    • enter the correct COM port and baud rate,
    • try scanning the card.  

-> If the card has been read, but the wrong number is displayed and no user is found, check if the correct baud rate has been set.

-> If the card scans correctly, enter the same settings into the POSweb and restart DeviceIntegrator. After that, the reader should work correctly.

-> If the card doesn't scan in Putty, it means a reader failure or a problem with the reader connectivity. It may concern the reader itself, the port, cable or drivers, or the wrong COM port selection. Check it one-by-one. 

NFC reader

  • Check if the reader is visible in the Device manager in correct tab, and if the reader name matches the one in the POSweb.
  • If the card has been read, but the wrong number is displayed and no user is found, check if the correct value has been set in NfcCardNumberFormat

AccessServerCardReader

  • Check if Access server works on the computer where it has been installed. 
  • Check Access server logs to see if the reader is initializing and working.
  • Check if there is a connection to the computer with Access server installed. You can ping the IP address set for the Access server. 
  • Check if it is possible to connect to the computer with Access server installed after a port. Use the Telnet option in CMD, where you enter the IP address with the port. You may need as well to add an exception for this port in firewall or antivirus program.

GAT net writer 7000

  • Check if GAT Direct Connect has been installed. It so, restart it. Next, restart DeviceIntegrator.
  • Check if the correct IP address and port have been set and if there is any communication via this address and port
  • Check if the correct GAT Relaxx port has been set and if it is unlocked. 

 

Help us improve the Knowledge Base experience and rate this article!
0.0
No votes have been submitted yet.
Loading...