Commander Occasionally Sends Labels With Incorrect Format Commands S’abonner
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.
Vous devez vous connecter pour laisser un commentaire.