Our application is for a Zebra TC72 (Android Oreo) and Zebra ZQ510.
At the start of the session, we connect to the printer and then, at intermittent intervals, we print a ticket.
Most times, the printer responds but often it drops the connection and/or goes to sleep and takes a long time to wake up.
When fails to print (ie the library throws an exception), we attempt to connect and print. If that fails, we disconnect, connect and then print (this sometimes works and sometimes requires the printer to be rebooted).
Other times, no exception is thrown when printed but nothing is printed.
On connection, we send the following zpl:
"! U1 setvar \"wlan.enable\" \"off\"\r\n"
+ "! U1 setvar \"bluetooth.enable\" \"on\"\r\n"
+ "! U1 setvar \"bluetooth.enable_reconnect\" \"on\"\r\n"
+ "! U1 setvar \"power.inactivity_timeout\" \"0\"\r\n"
+ "! U1 setvar \"power.sleep.enable\" \"off\"\r\n"
+ "! U1 setvar \"device.languages\" \"zpl\"\r\n";
-
Are we using the library correctly? Or should we connect, print, disconnect on every job?
-
Is there a way to keep the bluetooth connection alive? And/or check if it's been dropped so we can reconnect?
-
Any thoughts as to how/why the library silently fail sometimes when printing?
Mostly interested in others experiences and/or how they managed to get a reliable and responsive connection from what is an excellent library! Thank you.
Our application is for a Zebra TC72 (Android Oreo) and Zebra ZQ510.
At the start of the session, we connect to the printer and then, at intermittent intervals, we print a ticket.
Most times, the printer responds but often it drops the connection and/or goes to sleep and takes a long time to wake up.
When fails to print (ie the library throws an exception), we attempt to connect and print. If that fails, we disconnect, connect and then print (this sometimes works and sometimes requires the printer to be rebooted).
Other times, no exception is thrown when printed but nothing is printed.
On connection, we send the following zpl:
Are we using the library correctly? Or should we connect, print, disconnect on every job?
Is there a way to keep the bluetooth connection alive? And/or check if it's been dropped so we can reconnect?
Any thoughts as to how/why the library silently fail sometimes when printing?
Mostly interested in others experiences and/or how they managed to get a reliable and responsive connection from what is an excellent library! Thank you.