Zum Hauptinhalt gehen



Ideal Commander setup for custom labels


1 Kommentar

  • Avatar
    Jasper Wen

    I would suggest the following:

    • Confirm that you are on the latest service release of v10.1 which should be SR4 by going under help->about. If you are not on the latest SR, you can download it here: http://www.seagullscientific.com/support/service-releases-legacy-versions/v101/
    • Make sure you are using one process per each handler that you have set in Commander and command handler setup to guarantee order. Ideally, you wouldn't want to set it to restart after every command because that would essentially restart BarTender running in the background each time a trigger is sent and wouldn't be optimal. Usually, you would want to have it restart every hour or on failure only.
    • You wouldn't be able to specify multiple documents to print in a single command script trigger file. (You would need to use BTXML formatting to do that.)
    • Also, in Commander and command handler setup (under administer->command handler setup->document caching), you can control document caching and limit the number cached and open documents that Commander is using.
    • I would also suggest turn on some BarTender and Commander logging to confirm what Commander processed and BarTender actually printed. BarTender - Logging is set under administer->log setup->text file log tab->check log messages->click setup to set logging location. Commander - You can log the out window messages by going under administer->log setup->text file log tab->check log output window->click setup to set logging location.

    If you need further assistance, please contact our tech support directly to open a support ticket.


Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.