Zebra cutting at end of integration not each label.
We are printing via a BT integration that reads label data from a CSV file. The CSV is multi line with each line having the data for one label.
There is a setting in the Zebra ZT230 driver for "cutting every label" or "batch". Currently it is set to the latter however it cuts every label when running the integration. The integration is set to use the Printer settings and the Label Template has the driver settings. (Note the Zebra driver is being used)
So the question is does the printer "see" each line in the CSV file as a separate print job and if so is there a setting that would allow it to treat the print output from the whole CSV file as a batch?
Of is there some other way of getting it to cut at the end of the file?
Thanks
-
The first thing I would suggest is test it with the Seagull rather than ZDesigner driver. BarTender performs far better with this and on numerous occasions (although not all) switching to Seagull from a ZDesigner driver has fixed any little issues I have come across especially where peripherals are in use, such as cutters and internal rewinds etc.
Each line may be being handled as a separate print run, however, and so this may not adjust this but you could try using the Cut After Job setting that is present in the Seagull driver and see what that does for you situation.
1 -
Good suggestion thanks Peter. I might save that one to last though as I have only just returned from my last 7 days of penance for the temerity of changing a printer driver 😂
0 -
Hello together,
I have the same problem with a csv integration. The printer cuts after every data record. Set the driver to "cut after job" does not work, cause the integration builder handels every data record as a own print job.
Is there a possibility, for example, to insert a start job and end of job sign into the csv file? Any ideas?
All ideas are welcome.
0 -
If the Cut after Job isnt working then you could add an extra Integration that prints a different label that includes the cut command in it.
You could use the rename option for what happens to your original trigger file after it is received and then use that renamed trigger to print the new end of job and cut label. The new label would need to be the same size etc as the original and could say just have a dot on it so it not blank or else "End of Job" or similar with the cut command
0 -
Tried it out and it works fine. Thanks for your suggestions. :-)
0
Iniciar sesión para dejar un comentario.
Comentarios
5 comentarios