Commander 9.4S3 Issues With "print Label When Detecting New Trigger File" Follow

0
Avatar
Legacy Poster

Hello,

 

We're having issues with Commander regarding the "Print Label when Detecting New Trigger File"

 

Sometimes the following issues occur: 

 

- The barcode field from the label definition is not printed on the label.

- The wrong label definition is used to print the label. (the priovious label definition is still used for the new labels)

 

Stopping & starting the commander task solves the problem

 

Any advise is welcome,

 

thanks in advance,

 

Kind regards,

Willem.

4 comments

0
Avatar
Fernando Ramos Miracle
Moderator
Comment actions Permalink

Hello Wllemm,

 

1. Could you let me know what exact information is stored in your trigger file? Is it only the data for printing? Are you using Commander script or BT XML script? Or is the information contained on a separate file?

 

2. What type of Command have you defined for the Commander task? If it's a BarTender command, what exactly have you set up under the "Text File" tab?

 

3. What do you exactly mean when saying that the "Barcode field from the label definition is not printed"? is it that the barcode doesn't contain the data from the trigger file?

 

4. And what are you referring to when saying "label definition"? Is it printing the wrong BarTender document? Is it using the wrong data?

 

5. Could you attach your Commander task list so I can take a look at it?

 

Thanks!

0
Avatar
Legacy Poster
Comment actions Permalink

Hi Fernando,

 

I am a colleague of Willemm and will answer in his place.

  1. The trigger file contains 4 fields, 3 informative and one important field on which our MSSQL database is coupled. I"ll explain: we have a "Label" table in our database in which we store all our labels. This table holds all the information needed for getting data onto the the label. So when we print a label we generate a file for commander in which each separate label id is given so that we can fill in our data in the label. The file is a simple commander script file.
  2. Our commander settings are the following : poll the folder where the text files are being placed each 100ms, When a file is detected the following command is used "%Trigger Contents". After the label has been printed the text file gets deleted (pretty basic setup)
  3. Well it occurs that the barcode that is on our label (EAN128 barcode) is not begin printed onto the label, whilst all the configuration is in place and data should be returned
  4. Yes, commander (or Bartender) is printing with the wrong label definition file. Let say we first print with labeldefinition X and then with labeldefinition Y. When printing with labeldefinition X again we sometimes get our labels printed onto the Y layout... The data is correct, the layout is not...
  5. See the following link (contains the label definitions, commander task and layout files) https://www.dropbox.com/s/lh6z3nhrux16m61/Bartender.rar

 

Thanks in advance!

0
Avatar
Fernando Ramos Miracle
Moderator
Comment actions Permalink

Taking a look at your files I see a number of things you need to modify:

 

1. Firstly I see that your documents are saved with a Datamax E-4203 printer, but the trigger file specifies it to print to an "HP" printer. Can I understand that this is an HP laser printer? If that is the case, you will certainly see "page setup" errors as the printer configuration between the Datamax printer and the HP printer are radically different (when BarTender encounters the new printer it modifies the label design doing a "Best guess" which isn't very reliable with two printers with so many differences).

 

If you wish to print to an HP printer you need to save your BarTender documents with the HP driver (open the "File>Print..." dialog in BarTender, select the HP driver, close the dialog, adapt the label if any changes arise and save it).

 

You cannot expect the same BarTender document to print perfectly to a Datamax thermal printer and to an HP laser printer. If the same document needs to print to both printers, you'll need to create a copy of the document configured and saved for each driver.

 

2. Also regarding your Commander script I've noticed that is missing the /R and the /DbTextHeader commands.

 

- Regarding the /R command you need to specify in the script where the actual data starts or it will try printing the Commander script as raw data.

 

- The /DbTextHeader command is used to indicate where the database header record is.

 

In your case, both commands should be set to "3" as that is the line in the file where the data starts, and where the headers are specified.

 

3. Regarding your BarTender document you need to modify the text file database connection. You are using a data with field headers, so you need to specify it on the database connection options. when configuring your document you should use a "dummy" text database with the same structure as the one used in production.

 

In your case, you should be using a text file with both fields and with at least two records, the first containing the name of your fields: "NumberOfTickets,TicketNumber,Barcode,labelID".

 

Make sure to save your document and restart Commander detection after the above changes.

 

Once done, are you able to print correctly?

 

*I've also noticed that you contacted our European Tech Support office with this issue, please do inform my colleague Carlos of your results too.

 

Thanks!

0
Avatar
Legacy Poster
Comment actions Permalink

Hello Fernando,

 

We think we have our issue resolved. We yesterday changed our Bartender Command Handler reset service action to “restart every print” and we haven’t had the issue for the entire day (even with polling every 100ms)

Are there any disadvantages of putting the command handler in this mode? 

 

Thanks for all the (fast) help and tips!

 

Steff

 

ps I also informed your colleague of this.

Please sign in to leave a comment.