Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

1) Printing process stops in the middle

Symptom

Tickets are printed, but sometimes stops and there's a popup with a printing problem. That's because the Windows driver is "eating" status that SecuTix needs.

Context

The latest versions of the Boca driver can cause disturbances during SecuTix printings. Removing the driver's two-way support helps solve these problems.

Printer Identification

To identify whether your printer is using the latest version, you must open the Control Panel and go to the "Printers" menu.

 

If the name of your Boca printer contains the following BIDI, this means that the new version of the Boca driver is used. So you have to do the following setup.

Setting up the printer driver

Follow the steps below to disable bi-directional communication.

1) Open Printer properties

 

2) Configures the printer port and uncheck the checkbox to remove the two-way communication (as shown in the image below).

 

2) Printing does not work at all

Start by ensuring you don't have a communication issue with the device driver: SecuTix : Device Manager & Sophos

Then, look at the device drivers' logs. If they are very big, look for these kind of lines:

<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:readPrinter: Send the non blocking read command : <S1>
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:writePrinter: Only one packet,. no split
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:writePrinterInternal: Asynchronous write, timeout (ms) on the read is : 500
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:writePrinterInternal: Write event signaled !
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:writePrinterInternal: Number of byte written 4/ buffer size : 4
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:readPrinter: Asynchronous read, timeout (ms) on the read is : 500
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:readPrinter: Read event signaled !
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:readPrinter: Number of byte read 1/ buffer size : 1024
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.u.Win32UsbPrinterConnector> - pp20 [PTaskRunner] TnPD:readPrinter: read bytes: 65
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.BocaInlinedFglUsbPrintJnaDriver> - pp20 [PTaskRunner] TnPD:readFromPort: Loaded in read buffer: 65,
<2019-04-19 14:39:19,464> <DEBUG> <c.s.p.p.d.w.b.BocaInlinedFglUsbPrintJnaDriver> - pp20 [PTaskRunner] TnPD:readPort: readPort: [A]; in bytes: 65,

This means the Boca itself is configured in a legacy mode, where it returns letters ('A') instead of status bytes ( < ASCII 32). In this case, you have to reconfigure the Boca using the attached Boca application. The legacy mode (do not use it) is set with command <s6>. Use command <cs> (clear permament status commands) to reset it. Then restart the printer and try again. Using the app, you can also issue a <S1> command (status request) that should answer ACK (and not the 'A' character).

FGL reference documentation: 

App to reconfigure the boca: 


  • No labels