...
Search for SetupPOS. You can also find this program in the StartMenu under Epson. NOTE: you must be an administrator to run this program. A regular user will not be able to run the troubleshooting utilities.
...
Run the setup utility. At the UAC message, click yes.
...
Q3: The PAX S300 pin pad is not working properly or shows a black screen. How do I fix it?
If the screen is completely black, then the pin pad is not getting any power. Make sure the power cable is attached and the power socket is good. Some pin pads use a smart power plug for remote power control. If the smart plug is turned off, the power socket will not work. Either power on the smart plug or move the power cable to a working socket.
Pin pads can malfunction when they are powered on for a long time. We recommend a reboot at least once a week. Unfortunately, PAX S300 pin pads can only be rebooted by performing a power cycle. Here’s how to power cycle a PAX S300 pin pad:
Follow the thick black cable of the pin pad to the fan-out hub (about 2 feet away).
At the fan-out hub, disconnect the small black power cable (the L shaped barrel connector labelled PWR in this diagram).
Make sure the right pin pad is turned off; the screen should be completely black.
Wait for 10 seconds (very important).
Then, plug the power connector back in.
...
If the scanner scans the bar code but doesn’t append a <CR><LF> to the end of each scan, then it needs to be re-configured. For Zebra (or Motorola) scanners, scan the following bar code:
...
Q5:
...
None of the cash registers are working. When I run RMH POS, it gives an error message about not being able to connect to the database. What’s going on?
The cash registers store all of their transactions in a separate database server (located in the back office near the networking gear). When that server is down, RMH POS will not work.
Sometimes the database server gets turned off accidentally. In that case it needs to be turned on.
Sometimes the database server gets stuck on a reboot or a power outage. In that case, we need to access the console (either on-site or through AMT with remote KVM) to troubleshoot the reboot issue.