Skip to main content

Benefit card reader - Troubleshooting

Updated

Introduction

This troubleshooting article will help you in solving the most common problems with the Benefit card reader.

Benefit card reader is used in Poland only. 

  • This article will be helpful if you are experiencing issues with the Benefit card reader.
  • It is dedicated to Administrator, PG Champion and Perfect Gym Technical Support Agents.

Before you start

  1. In the search bar, toolbar, or file explorer, type %programdata% - ścieżka to C:\ProgramData.
  2. Go to Creadhoc -> Perfect Gym -> Logs -> DeviceIntegrator.log  - C:\ProgramData\Creadhoc\PerfectGym\Logs
  3. In logs, at the bottom of the page, search for the causes responsible for the card reader malfunction. Usually, these are issues connected with COM port or the DeviceIntegrator (DI).

Instruction

What should I do if my Benefit card reader is not working?

  • DI Restart:
  1. In the search box, type Services, or right-click on the Toolbar -> Task Menager -> Services
  2. Right-click on the DeviceIntegratorService and restart the DI application. 
  • Issues connected with COM port:
  1. Unplug the device from the computer, wait for about 5 seconds and plug the device in again. 
  2. Repeat the steps from the instruction above - DI Restart. 
  • Issues connected with COM port (other port):

If the device still does not work after the previous instructions, the next step is to check whether it has a good COM port assigned. 

  1. Type Task Manager in the search bar, or right-click on the Windows icon, and go to Task Manager.
  2. Open the Ports tab (COM and LPT).
  3. Unplug the device and see which one disappears from the list.
  4. Plug the device in again, paying attention to the COM assigned next to the device name.
  5. Go to the PosWeb of the appropriate Front Desk.
  6. In the bottom-right corner of the screen, go to Settings.
  7. In the options, search for BenefitCardReader - check the COM Port Number assigned to the device.
  8. Change it to the one assigned in the Device Manager. 

Hints

These two articles may be useful if this is a recurring problem:

Related articles