browse

Step by Step Instructions

Printer is not printing anything.

  • First go into Utilities > Restart Printer inside the POS to restart your print services and test after about 30 seconds.

    print_tshoot_1.png
  • Next check where the printer is plugging into, it should either plug into the station directly or into the wall (it could also plug directly into a network switch)

  • If it plugs into the station directly it is a “Serial” printer, if it plugs into the wall or a network switch with an ethernet cable it is a “Network” printer.

 

Serial Connection:                                                                      

print_tshoot_2.png

Ethernet/Network Connection:

print_tshoot_3.png
  • Whichever it is plugging into, first step is to “re-seat” the connection, so you’ll unplug the connector for about 10 seconds and then plug back in and make sure it is secure. You’ll need to do this on both sides, so into the computer/wall and also into the printer.

  • If it is a network printer, make sure you have an active internet connection in your store.

  • While doing this step go ahead and turn the printer off and wait about 30 seconds and then turn it back on.

  • Check and make sure that there are no error lights on the printer, and that there is paper and the paper is set in the correct direction. Also make sure you have the correct type of paper for your printer loaded.

  • Next try a self test to see if the printer will print; on most printers to do this you turn the printer off > hold the feed button > continue holding feed while turning the printer back on > continue holding feed until something prints (about 5 seconds). If the test page will not print go ahead and call HungerRush tech support.

**If you are getting an error when printing an order that says, “Print CC Merchant Error: Object not set to an instance of an object.” Please exit out of Revention and relaunch the software. If that does not work, go to Utilities > Restart Printer and try again. If still receiving the error please restart the computer and that should fix this error.**

 

Previous
Next

Comments

0 comments

Please sign in to leave a comment.

Was this article helpful?

0 out of 0 found this helpful
Powered by Zendesk