Epson Printer Issues - Receipt.
-
I'm racking my brain here and everything I'm coming up with doesn't work.
I'm not exactly sure if you guys will be able to help out, but it's worth a shot.We're using POS Bank Terminals - Windows 10. (not supports by our vendor)
We're using Epson Tmt 88 thermal printers for receipts-
What I'm trying to figure out is - Why are the printers printing??????????????????????????????
On top of the receipts and reports it is printing at the terminals.That usually means that there's a connection issue, I've already swapped all patch cables, adapters, turned off Fifo Buffering on Com ports, Tried a different Dip switch layout as directed by POSBank Support, updated drivers, even tried changing the buffering size on the printer through dip switches as well.
When I google the issue I get Paperwork telling me to change settings and do everything i've already done.
Do you guys have any ideas as to what could cause this - or how to resolve it?
It's a non-issue, in a relativity. However the sites we have these issues with are asking us to fix it because it's an annoyance and causing people to ask questions. -
@WrCombs It could possibly be a driver issue. I have seen weird stuff happening and printers just refusing to work after a Windows 10 update. After I reinstalled driver it worked normal again.
-
@jmoore said in Epson Printer Issues - Receipt.:
@WrCombs It could possibly be a driver issue. I have seen weird stuff happening and printers just refusing to work after a Windows 10 update. After I reinstalled driver it worked normal again.
Thanks @jmoore I have tried reinstalling drivers.
I should be more specific.
This is happening only with A third party Hardware - not from the vendor. -
@WrCombs If you're using serial / RS232, I'm guessing that your driver might be outputting in ASCII and might need to be set to ANSI or from 8 bit to 7 bit. Check these against other sites and see what you come up with. The repeated characters are representations of solid lines or simple graphics via the various protocols.
At least I've run into this before with a telnet app that we use here.