we have an 420t zebra printer, which suddenly started printing labels in a wrong way. Say one wanted to print a first name and a last-name on it, now it prints part only of the last name. The code that i send to the printer has not changed at all. When i try to reinstall the printer, i get a certificate error on windows 10, i have calibrated many times the printer, but other than that, i have no idea what else i should do...
i have also tried my code here, it prints correctly, so i guess it is an issue with my zebra printer setup:
http://labelary.com/viewer.html
Related
I'm using printer from Eurocoin called EP800 on Linux. It's similar to ep802 printer in specifications.
When printing an image, sometimes this happens:
A lot of times it prints normal image, but sometimes I get this. Does anyone have any idea why this happens sometimes ?
I didn't provide a code since I'm not looking for programming related bug but more of what could cause this ?
We have a web app that batches the ZPL for many shipping labels (UPS, USPS, FedEx) at a time. For some reason it will randomly mis-print where is just prints the barcodes, but nothing else. This usually only starts after about label 20 or so in the batch, and even then, it is not consistent in the labels after that. Sometimes it does it, sometimes it doesn't. It is consistent in that it does it to the USPS labels and not UPS or FedEx.
If we reprint just that label's zpl, it prints fine.
So I was wondering if there is some limit we're running into with batching. We send just one long zpl string for the entire batch, each label separated with ^XA....^XZ.
The printer is a GX420T.
Any ideas?
Example mis-print - I drew black lines on the barcodes to make them not readable for privacy
I use Raspberry Pi connected to a Zebra GX430t with CUPS. I use the "Local Raw Printer" driver and I send the ZPL directly to the printer using Python.
I use the termal transfert mode, but I have a problem with the printer (300dpi), because the printing of the datamatrix is quite blurry, so I can't read it.
I emailed the Zebra support, and they told me to modify the temperature of the printing head, but I have no clue on how to do it with ZPL. I also have to modify the grayscale with ZPL. Do you know how to do one of this commands please ?
Plus, could you confirm that ^MTT is the command to set the printer to Thermal Transfert and that ^PW is used to set the width of the label ? Is the configuration saved in the printer, even when turned off, until the configuration change ?
Use ^MDa command. where a is the value of the darkness level. Value is 0 to 30 in increments of 0.1.
Yes, ^MTa sets printer mode where a is the setting, T= Thermal Transfer, D= Direct
I am working on a set of ZPL validation routines which parse arbitrary ZPL files, sanitize them, edit certain key commands (label length, print speeds, etc), and extract some useful information.
Since this printer is generating labels for a free-running shipping line I really need to know how long it's going to take from the moment I send the ZPL file to the printer until I'll be ready to apply the label. It is clear that the print time is directly linked to the label length and print speeds, but the label render time (conversion of ZPL into ready to print image in printer memory) is less obvious.
Since I'm printing label contents provided by numerous third parties, I can't simply measure the time for the labels. I've asked Zebra and gotten no guidance, so I'm wondering if anyone has an idea of how to estimate the render time? Am I stuck trying to estimate the processing time of every individual ZPL command?
My experience over the last couple of years working with differnt zebra printers (Z4M, ZM400, GK420t) is, that the label that is send to the printer is printed almost instantaneously.
I have an app that prints out labels to a Zebra GK420t label printer. The ZPL sends some text and a QRCode. This works fine when the printer is first turned on, but there is another app that prints to it, and after the other app has printed, the position of the QRCode changes on our labels.
I don't have access to the source for the other program so I can't see what ZPL it is sending. I know it is sending some config to the printer (Print Width for example) but I can't figure out what it could be sending to change the positioning for just the QRCode.
This is the label from our app when the label printer is first turned on
And this is label from our app, after the other app has printed a label and changed some settings.
The QR Code moved up and to the right, but everything else stayed in the same place.
This is some example ZPL for one of our labels
^XA
^PW420
^LS0
^LH0,0
^CF0,40^FO20,25^FDUnknown Vendor^FS
^FO15,0^BQN,2,6^FD##hCsck00000000000779/221a1^FS
^CFR,15^FO55,220^FD3877^FS
^CFR,15^FO180,70^FDTue 07:30 Nov 10^FS
^FO180,100^FDU. Surgeon^FS
^FO180,130^FDTotal hip^FS
^FO180,160^FDsigma^FS
^FO180,190^FDHip tool^FS
^FO180,220^FD1 of 2^FS
^XZ
^BY (Bar Code Field Default) is the only command that can affect all barcodes. However it shouldn't affect field origin, but you may want to test this.
Your best bet is to print a config label before and after and look for the difference. Also, it's good practice to create a 'config' format and send as needed. In your case where you are sharing the printer among different applications you should send the config each time you print.
We have many Zebra printers across our manufacturing site, and we send all of the config data each time we print a label.
If you have an Ethernet enabled printer you should also be able to type the IP address into IE and view the printer config information from your web browser.
Regards,
For some more info on Brians answer, in case anyone comes up against this. The ^BY field does affect QRCodes on the GK420t printer.
The other vendor was setting the barcode defaults
^BY2,2,59
And that was moving the QR Code down by 59. I've tested it on another model which didn't have the same issue so I think it's a bug.
If you are in 600 dpi Subst ^FO15,0 with ^FO15,050
015,050 is the position of qr code inside your label.
Try putting ^LH0,0 right after ^XA. That fixed mine.