Export Printer Code Template – Zpl - Driver Compatibility
Hello,
We are using Bartender 9.3 and have to migrate our Windows server to Windows 2008 R2.
Currently we use Seagull Scientific Zebra print driver version 6.6.3 to generate the printer code template.
Unfortunately this driver cannot be installed on Windows 2008 R2 and we tried to use latest Seagull Scientific Zebra print driver version 7.3.6 but we have some issues with the code generated.
When exporting PCT with the new driver, text object position is set using Zebra ZPL II command: ^FT
It there :
- a Bartender parameter to force compatibility with an old driver?
- a driver parameter to generate text object position using Zebra ZPL II command: ^FO ?
Thanks for your help,
Daniel
-
Have you tried with v7.0 drivers, which are Windows Server 2008 R2 compatible?
ftp://ftp.seagullscientific.com/Drivers/archive/7.0/7.0/
What Edition of BarTender is in use BTW?
0 -
Bartender on our proiduction machine: 9.3 SR1 Automation.
We use our own printer template for Zebra printers to update the output via a VB script.
Notes about my test environment:
- a test VM running Windows 2008 R2 to test Bartender driver compatibility,
- because I cannot move Bartender licence yet to the new Windows 2008 R2 server, Bartender is installed in Trial mode on test VM
- Print file generated via: Menu -> Print (because automation does not work in Trial mode )
I installed v7.0 drivers from your link in test VM.
Test print from the printer driver: text object position is generated using Zebra ZPL II command: ^FO.
Printing from Bartender: text object position is generated using Zebra ZPL II command: ^FT.
- when using the driver v6.6.3 printing or exporting the template generate the same file
- I don't expect that when using the new driver printing or exporting print template will generate different files
Thanks,
Daniel
0 -
Am I correct in saying that you want BarTender, with the newer drivers, to create ZPL print code that uses the ^FO command to position label objects as opposed to the ^FT command? Is that the sum total of the issue or are there other problems?
I made a quick test of printing to file and exporting a PCT, and in both cases the positioning command used was the ^FT command.
0 -
Main issue for us when using new drivers is:
- Bartender generate ZPL print code that use ^FT command to position text objects
It seems that ZPL format related commands are missing as well but this may be handled via VB script:
- ^DFR:<format-name>.ZPL - download format
- ^XFR:<format-name>.ZPL - recall format
- ^IDR:<format-name>.ZPL - delete format objectMaybe format related commands are missing because they are replaced with <xpml><page> nodes?
In this case if <xpml><page> nodes can be removed as well and generate ZPL format related command that will be great.
Thanks for your support,
Daniel
0 -
Can you tell me why is the use of an ^FT position command a problem, other than you've used ^FO in the past?
Generating a simple PCT example I not the ^DF and ^XF commands are very much present. To my mind the use of an ^ID command makes little sense as the whole point of a PCT is that it is to stay memory resident, unless of course the format and data sections of the print code are split into separate files.
0 -
The issue with ^FO is related with the way we use the template generated by Bartender:
- we parse the ZPL code generated and use position in our application
When generating the ZPL code via Printing I don't get ^DF and ^XF commands.
0 -
Hi,
Any update on this issue?
Or should I follow this on a different support channel?
Thanks,
Daniel0 -
I think you'd best be served by contacting tech-support by telephone or email at the office that serves your region.
http://www.seagullscientific.com/label-software/contact_us.aspx#usa
It should be noted that Seagull employees only contribute to the forum in their spare time. Official support cases via telephone and email, that require license registration, get priority over questions asked in the public forum. If a case is important, complex, and/or urgent then you should seek assistance via these channels instead.
Concerning your issue, I think it's the case that we just don't use the ^FO command like we've done in the past. I don't think we've ever made a commitment to always formulate printer code in the same way until the end of time, as such a commitment would be too restrictive. Our primary goal is to produce accurate and highly optimized printer code so that a BarTender user, in combination with a Seagull printer driver, can print labels to their printer in the best way possible.
0 -
Maybe I should rephrase my question about the ZPL code generated by Bartender 9.3 when using different versions of Zebra ZPL driver:
-when using Zebra ZPL print driver version 6.6.3 text positioning is generated using ^FO command
-when using Zebra ZPL print driver version 7.0 and later - compatible with Windows 64 bit - text positioning is generated using ^FT command
This means that Bartender uses a Zebra printer driver property in order to use one position command or the other one.
This is my question: is there a driver property that can be added as parameter in Printer Code Template to keep compatibility with the code generated with the old driver?
Thanks for your support,
Daniel
0 -
Note that it's the printer driver that generates the end result printer code. BarTender connects to the driver via a standard and Seagull proprietary API.
In the Printer Code Template (PCT) setup dialog under the "General" tab you can make use of the "Print Code Modifier" (with an action list or VB script) to automatically modify the printer code further to better suit your purposes.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
10 Kommentare