Commander Occasionally Sends Labels With Incorrect Format Commands
Hi,
We are running Commander Automation 9.3 SR2 with 40 printers attached. The build version is 2725 on a windows server 2008 R2 x64 virtual platform.
The problem occurs infrequently and is easily resolved by stopping and starting commander. Usually the problem is reported by my user as "the printing is slow".
I investigated the problem by pausing the printer and analyzing the spooled document. There I discovered that although the label format (btw) file is designed to send the necessary printer operation settings that these were different to the btw file.
The biggest headache was that the operation mode had been changed to "peel off" instead of the design parameter "tear off". This resulted in the printer pausing between labels. I noticed that the heat setting had also been changed from a "20" to a "17".
As stated these parameters are defined in the saved btw file. Where is Commander sourcing this data? And why is it operating fine for a few months and then changing it's behaviour.
This particular VM is not scheduled for a nightly reboot because it is servicing a 3 shift 24/7 operation.
Kind Regards,
Rupert Bodisch
We are running Commander Automation 9.3 SR2 with 40 printers attached. The build version is 2725 on a windows server 2008 R2 x64 virtual platform.
The problem occurs infrequently and is easily resolved by stopping and starting commander. Usually the problem is reported by my user as "the printing is slow".
I investigated the problem by pausing the printer and analyzing the spooled document. There I discovered that although the label format (btw) file is designed to send the necessary printer operation settings that these were different to the btw file.
The biggest headache was that the operation mode had been changed to "peel off" instead of the design parameter "tear off". This resulted in the printer pausing between labels. I noticed that the heat setting had also been changed from a "20" to a "17".
As stated these parameters are defined in the saved btw file. Where is Commander sourcing this data? And why is it operating fine for a few months and then changing it's behaviour.
This particular VM is not scheduled for a nightly reboot because it is servicing a 3 shift 24/7 operation.
Kind Regards,
Rupert Bodisch
0
-
Printing preferences, in addition to the selected printer, are embedded in the label format itself, and are loaded into BarTender as the label is loaded. These setting could get lost if the label format held in memory of the Commander controlled BarTender process, is switched to a totally different printer somewhere along the line so that when it then switches back to the original it just takes on the general default options of the printer driver.
One workaround is to have separate BarTender label formats for each distinct printer brand, so that important, specific print settings are not lost when switching between printers for individual print jobs.0 -
You can test this behaviour in BarTender when switching between printer drivers of different types manually, and then checking to see if the original setting is returned when going back to the original printer. 0 -
[quote name='Ian C - Seagull Support' timestamp='1337329935' post='2460']
You can test this behaviour in BarTender when switching between printer drivers of different types manually, and then checking to see if the original setting is returned when going back to the original printer.
[/quote]
Thanks for the Response Ian.
In our environment we are only dealing with one model printer (ZM400) for the specific format file. We also use I4208's but never for that label format file.
Here's the content of a sample file that the commander is looking for:
[quote]
%BTW% /AF="E:\bartender\new_status.btw"/PRN="plzp200" /P /R=3 /D="%Trigger File
Name%" /DD
%END%
ITEM|BARCODE_ITEM_DESC|STORAGE_CONDITION|LOT|CONTAINER|RECEIPT_DATE|REVISION|SUP
PLIER_LOT|SITE|VALIDATION|QAURANTINE_STATUS|PUR_ORDER|CONT_QTY|CONTYN|ITEM_DESCR
IPTION|CONT_X_OF_Y
.148110 |Methyldopa (Reg Mrkts)(AG) |SUNLIT|.B02
3446 |0|5-JAN-2012|0 |MEB-20110808-1M |Aspen Port Eliz
abeth 442|VALIDATION LABEL|QUARANTINED|900600|0||Methyldopa (Reg Mrkts
)(AG)|0 of 36|
148110 |Methyldopa (Reg Mrkts)(AG)|SUNLIT|B023446 |1|5-JAN-2012
|0 |MEB-20110808-1M |Aspen Port Elizabeth 442||QUARA
NTINED|900600| 25.0000 kg||Methyldopa (Reg Mrkts)(AG)|1 of 36
[/quote]0 -
On a separate note I see you have a record header in the trigger, therefore you should specify the follow command option too:
/DbTextHeader=3
Is the printer driver for the ZM400 a Seagull printer driver, and if so of what version?
For the user account profile which the BarTender process runs under; what is the Windows default printer?0 -
[quote name='Ian C - Seagull Support' timestamp='1337343478' post='2466']
On a separate note I see you have a record header in the trigger, therefore you should specify the follow command option too:
/DbTextHeader=3
Is the printer driver for the ZM400 a Seagull printer driver, and if so of what version?
For the user account profile which the BarTender process runs under; what is the Windows default printer?
[/quote]
The printer driver is from "NiceDriver", version 4.6.48 build 2660 - If I recall correctly we could not find a Seagull x64 driver for the ZM400.
The default printer for that user is another printer, however it is also a ZM400 with exactly the same driver.0
Please sign in to leave a comment.
Comments
5 comments