Machine Setup
Contents
Install .net framework
Install .net 4.0 Full Profile.
.net 4.0 is available by default on later versions of windows, but typically only the client profile is loaded. You need to go to the Microsoft site and load the full profile.
Install your licenced version of bartender
Create your printers
Load up the proper (and most recent) Seagull Scientific drivers for your printer (SATO, DATAMAX, etc)...
Here are some standard names, but the actual queue name is defined in the configuration file as needed.
<add key="casePrinter" value="LabelPrinter" /> <add key="palletPrinter" value="PalletPrinter" />
If you are using VideoJet, you still will need to install bartender (for the pallet printer). Even if you are not printing with bartender in any form, you still need to install the application (the system requires it). However, in this case it doesn't have to be fully licensed, since it won't be used.
Create the base TEE directory
This is also defined in config.
<add key="ERPInforATFPath" value="C:\Coolearth\TEE" />
- The base directory for these files (in this example c:\Coolearth) must be writable/readable by the user which will run the catchweight.
Put your bartender labels into the label directory
You should test these labels by attempting to print them via bartender manually. You may have to get the production reporting to print the first time so that the tab-delimited-file interface file gets created (if the system is using that).
<add key="labelPath" value="C:\Coolearth\Labels" />
A new feature is available to use the bartender librarian. This gets labels from the database. If you use this, then bartender needs to be set up proper to connect to the database for the librarian. The librarian feature is not available in all versions of our Production Reporting Software, but we can easily migrate it. It does however require bartender 9.0 or beyond.
<add key="labelPath" value="lib:\\basedir" />
The tool will automatically change the '\' to a '/' needed to make the URLs for the librarian work properly. In setup, treat these like dos filenames (with backslashes) not like URLs (with forward slashes).