User manual

Tasks and Kits
ProMaster 2500 User Manual 3-33
Introduction to Kits
Kits are Tasks that have been daisy-chained together so several can be
run as one large job. The most common use for Kits is to string together
the separate Tasks used to program all the devices for a single board. In
Figure 3-23 there are four devices that must be programmed and labeled
for the sample board. Each device has one Task that controls the process
for producing that device. The Kit acts like a super-Task.
To illustrate this point, assume that 60 boards need to be built. When the
Kit for this board is run, the Task 1 pass limit is set to 60 devices. When
that count is reached, TaskLink displays a message prompting the system
operator to change over for the second Task. When ready for Task 2, the
operator presses
↵
. TaskLink starts Task 2, and 60 devices for that Task
are programmed. This process continues for Task 3 and Task 4.
The messages screens are typically used when the Tasks define devices
using different package types (Task 1 uses DIPs and Task 2 uses PLCCs).
In this case, a message screen might remind the operator about the steps
required to change over from one package type to another.
A Kit can include a maximum of 20 Tasks. All the Tasks for a Kit must be
in the same database file (called the
Source Database
in the Kit dialog
box), but the Kit can be stored in the Source Database or a different
database file. When the Kit is run, the system operator specifies the
number of Kits (equal to the number of complete boards) to be built.
Selecting Kit
Parameters
The process for creating a Kit is similar to creating a Task. From
TaskLink’s main screen, select
Add Kit...
and press
↵
(see Figure
3-22).
Figure 3-22
Selecting “Add Kit” from the
Main Screen