omron — Process Components

Process Components Motion Information After a collection of Part Processes is defined, the Process Manager scans the collection to determine what additional configuration data is needed to properly drive the process. The following are some examples: l Each robot will need an idle position. l For each part that is picked, motion parameters describing the approach height, depart height, motion configuration, and offset at the pick location must be defined. l For each part that is to be delivered to a target, the approach height, depart height, motion con- figuration, and offset at the place location must be defined.

The Process Manager maintains a list of the required information that must be taught as part of the con- figuration of the system. The motion information is located in the Configuration Items group of the Process Manager editor. For details, see Configuration Items on page 856. Part Sources The Process Manager analyzes the configuration of Part Processes in order to determine what Sources are needed to control the hardware. A Source is an object that interacts with the hardware and discovers Part Instances and Part Target Instances. A Source is allocated for each of these conditions: l For each Static-defined Part or Part Target, a Source is created.

l For each Vision-defined Part or Part Target, one Source is created for each Virtual Camera ref- erenced. This Source will process the collection of all Part or Part Targets referenced by the Virtual Camera. l For each Belt-defined Part or Part Target, one Source is created for each Belt referenced. This Source will process the collection of all Part or Part Targets referenced by the Belt. For each Source, the Process Manager allows you to modify certain parameters associated with the Source. As an example, the Vision and Static Source objects can be configured to interface with a feeder.

Part and Part Target Instances When an individual Part is located, it is represented by a Part Instance. When an individual Part Target point is identified, it is represented by a Part Target Instance. These objects identify the transformation and Part/Part Target information so the complete location can be resolved. If an individual Part Instance must be placed at a specific Part Target Instance, the Part Instance will have a link to the appropriate Part Target Instance. Part Instance and Part Target Instance objects get allocated to a controller for processing by a robot. The Process Manager uses the Process Strategy to identify that allocation. NOTE:

The Process Manager knows if a Part/Part Target instance was processed, not processed, or if an error happened during processing because of a grip error. If a grip error occurs, that instance will not be transferred to next robot and will be counted as not processed in the statistics. ACE User's Guide, 3.6.x, 18316-000 Rev A Page 803