samuraiza / jzebra

Automatically exported from code.google.com/p/jzebra
0 stars 0 forks source link

Does not print to DYMO LabelWriter 4XL #180

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install DYMO LabelWriter 4XL
2. Open Sample.html
3. click print EPL or ZPL

What is the expected output? What do you see instead?
Expect to have example label printed and the printer light just blinks and then 
does nothing.

What version of the product are you using? On what operating system?
vers. 1.7.6 on windows 8

Please provide any additional information below.
here is the log from the example print attempt:

INFO: ===== SENDING DATA TO THE PRINTER =====
Nov 13, 2013 12:07:01 PM qz.LogIt log
INFO: 

N
q609
Q203,26
B5,26,0,1A,3,7,152,B,"1234"
A310,26,0,3,1,1,N,"SKU 00000 MFG 0000"
A310,56,0,3,1,1,N,"QZ-PRINT APPLET"
A310,86,0,3,1,1,N,"TEST PRINT SUCCESSFUL"
A310,116,0,3,1,1,N,"FROM SAMPLE.HTML"
A310,146,0,3,1,1,N,"EDIT EPL_SAMPLE.TXT"
P1,1

Nov 13, 2013 12:07:01 PM qz.LogIt log
INFO: Sending print job to printer: "DYMO LabelWriter 4XL"
Nov 13, 2013 12:07:01 PM qz.LogIt log
INFO: Print job data transfer complete.
Nov 13, 2013 12:07:01 PM qz.LogIt log
INFO: Print job has no more events.
Nov 13, 2013 12:07:01 PM qz.LogIt log
INFO: Print job received by printer: "DYMO LabelWriter 4XL"
Nov 13, 2013 12:07:01 PM qz.LogIt log
INFO: Print buffer has been cleared.
Nov 13, 2013 12:07:01 PM qz.LogIt log
INFO: Succesfully called JavaScript function "qzDonePrinting(...)"...
Nov 13, 2013 12:07:01 PM qz.LogIt log
INFO: Print buffer has been cleared.

Original issue reported on code.google.com by zig...@gmail.com on 13 Nov 2013 at 8:10

GoogleCodeExporter commented 9 years ago
The DYMO LabelWriter 4XL is not listed on the DYMO product page as supporting 
EPL or ZPL languages.

Please provide more details as to the specific language you would like support 
with, as  there are literally thousands of printers that won't work when you 
click the Raw buttons.

Closing, marking as invalid.  Please reopen if you believe this bug was closed 
in error.

-Tres

Original comment by tres.fin...@gmail.com on 13 Nov 2013 at 8:17