Cash drawers - abcsoftware/abc-docs GitHub Wiki

We recommend using a cash drawer in conjunction with a receipt printer. Recommended model (10/31/2023) Star Micronics CD-4 https://starmicronics.com/product/choice-cash-drawer-cd4/

Configuration

With a Direct Printer for Receipts

Enter the cash drawer setup info on the Terminal Setup screen. Access the Terminal Setup screen with F10 'T. In the User Number or Code field enter ! followed by the 2-digit user number. Enter the cash drawer device number in the CashDrwrDev field. This will be a 2-digit "printer number," usually the same as the POS printer number. Enter the OpenCashDr code as 007027080068. Remember to save with F9. You will need to restart the ABC Server (or use 8-25 to restart the user) to apply the new settings.

With a WIN2 Printer for Receipts

You can use an M8 or M10 printer for the receipt printer. To run a cash drawer on this printer you need to also setup a direct printer just for the cash drawer. You can use a Generic Text printer on the same Windows printer port as the receipt printer. If you use a Star printer driver on the direct printer port you must be sure to disable print job monitoring in the port configuration page of the Star printer driver.

With Star MCP30 printer

A common fix for mC-Print3 (MCP30) print jobs that do not close automatically is to disable the "Monitor Job End" setting in the printer's driver properties . This issue often occurs when the printer's status monitoring gets stuck, which keeps the job active in the queue. Solution for Windows computers Open Printer Properties: On your computer, go to "Printers & scanners" via the Start Menu. Find and select your Star mC-Print3 printer, then click Manage > Printer Properties. Access the Star/Help tab: Navigate to the Star/Help tab in the properties window. Configure the port: Click the Configure Port button. Set "Monitor Job End" to "Not Monitor": In the port settings, change the "Monitor Job End" state to "Not Monitor". Save your changes: Click OK to apply the new setting. This should prevent jobs from getting stuck in the print queue.