Use Bt To Print Pre-defined Zpl Label Format
Hi Everyone,
Have what should be a simple question.
Running Enterprise Automation, 9.4
We are receiving label formats from the UPS website. They send me a label format that contains all of the required Zebra ZPL programming statement required to build their shipping label. If I copy this file directly to a zebra printer, using vbscript, the label spits out exactly as it should.
Copying the label format to the printer leaves me open to all kinds of issues, such as...
other jobs getting interleaved into this job, if I am printing multiple labels, and someone else prints, too.
printer failures will not be reported back to the copying program
can't easily reprint
I am wondering if it would be possible to make use of BT Automation, passing the pre-defined label statements, and having BT manage the jobs?
I am familiar with creating label formats in BT, then using trigger files with data in them, to print labels.
tia,
ron
Have what should be a simple question.
Running Enterprise Automation, 9.4
We are receiving label formats from the UPS website. They send me a label format that contains all of the required Zebra ZPL programming statement required to build their shipping label. If I copy this file directly to a zebra printer, using vbscript, the label spits out exactly as it should.
Copying the label format to the printer leaves me open to all kinds of issues, such as...
other jobs getting interleaved into this job, if I am printing multiple labels, and someone else prints, too.
printer failures will not be reported back to the copying program
can't easily reprint
I am wondering if it would be possible to make use of BT Automation, passing the pre-defined label statements, and having BT manage the jobs?
I am familiar with creating label formats in BT, then using trigger files with data in them, to print labels.
tia,
ron
0
-
I'm pretty sure such functionality does not yet exist in BarTender and I can't come up w/ a good workaround. If you deem this as an important functionality, I would recommend contacting local Seagull support technician to file a feature request. 0 -
If you are using the ssdal.exe (found in the System32 folder) command line to send the ZPL print job to the printer, then the print job will appear in the Windows spool queue just like any regular print job. Would that still be liable to the issues you worry about?
Example command line:
ssdal.exe /p "PrinterName" send "FilePathAndName"0 -
[quote name='Ian C - Seagull Support' timestamp='1316595794' post='666']
If you are using the ssdal.exe (found in the System32 folder) command line to send the ZPL print job to the printer, then the print job will appear in the Windows spool queue just like any regular print job. Would that still be liable to the issues you worry about?
Example command line:
ssdal.exe /p "PrinterName" send "FilePathAndName"
[/quote]
Hi Ian,
Don't know anything about ssdal.exe, but I will look into it. The control issue arises because of the nature of our setup. The label printer is attached to the network. It is used by various applications, from different servers. Most of the applications are windows based, and submit the jobs to the windows spooler. For the printing of the UPS labels, we have a vbscript running, that creates a file system object for the printer using a UNC, then does a CopyFile. Bypasses the spooler. If I could run the jobs thru BT, I would eliminate the chance of stepping on, or into, the middle of another job. A future release of this app will make use of windows spooler, and the problem will go away, but, it would still be nice to continue centralizing label printing thru BT.
thanx,
ron0 -
If you send the printer code via the ssdal.exe command line then it will be a spooled job just like BarTender. There is no need to use BarTender in order to get a spooled print job. 0
Please sign in to leave a comment.
Comments
4 comments