Sap Glm With Zebra Printer: Seagull Drivers
Hi All,
We have integration with SAP GLM- we use WWI functionality meaning windows word which will create a final label based on xml generated per print job. The input is then sent to ZEBRA printer to print. We have ZEBRA 170xi4 (300 dpi)
Zebra 170xiIII Plus (300 dpi) being used with Seagull 64 bit drivers.
The seaguall drivers are upgraded from 32 bit to 64 bit and word from 2003 to 2010.
Issue: When we send more than 1 copy to printer for e.g. 4 or 100 then its expected that printer will produce those number of copies and display 1 of 100, 2 of 100 and so..on the printer display screen. But this is not happening. The printer shows 1 of 1 always and repeats this 100 times, till we get all prints. Meaning instead of making 100 copies from 1, each time its taking 1 as a copy. This is causing printer pause, and counter display on printer is also incorrect.
When we manually selected the 'Un-collated' option in word everything worked fine. But we can not do the manually and it has to happen automatically when every print goes from SAP to the printer. This was working before with collated option but it was word 2003 and 32 bit drivers.
I cant find any option on ZEBRA something like mopier mode off. I suspect the printer drivers are not interpreting the inputs properly. PFB expamples
with collate option:
-
The copies quantity value on the printer reflects the amount specified in the issue (^PQ) command. You have 100 of these for one copy thus the result you see.
Is the entire print run of 100 labels supposed to be absolutely identical? If yes then the problem lies in Word. Try the same using BarTender and our driver and you'll see a single issue command for 100 labels. In fact, do this with Windows Notepad, collate disabled, and you'll get the same 100 label issue command.
0 -
Thanks,
Your are right, its the word issue but can this be solved alone with the upgraded or any other driver version. This was working before with Segull drivers 32 bit, but now OS is on 64 bit and new seagull drivers with 64 bit is not considering this.
Can we have any solution alone on driver?
Regards,
Sachin0 -
This has been reported elsewhere and diagnosed by development, but unfortunately for you this is a Word 2010 issue, you'll need to chase Microsoft. Might I suggest you consider using BarTender instead for the generation of highly optimized printer code.
0 -
Hello Sachin, Did you solve this issue in your WWI server. We are also having this issue after Server OS & WWI SP upgrade. Kindly advice if you have found a resolution for this issue. Thanks.
0
請登入寫評論。
評論
4 條評論