July 2013 8.6 DCM – Dynamic Collision Monitoring 1485
CMO In the tool-carrier kinematics, you need to define additional CMOs to describe
the collision-monitored objects. These collision monitored objects must exists
as files. The files for CMOs of the tool-carrier kinematics may also be in *.CFT
format. Upon a TOOL CALL, the control automatically converts these files of
the respective tool to the necessary *.TAB format.
In the definition of a CMO, shifts and rotations of subsequent collision objects
can be entered via the keyword TRANS. This functions like entering the
description of a kinematics configuration. However, the coordinate
transformations in a CMO definition file are only effective within the
respective object-description file.
Input possibilities for CMOs:
Example Here is an example of how a simple tool-carrier kinematics description (*.cft
template) is created with KinematicsDesign:
Start the KinematicsDesign PC tool.
Under File / New..., select Tool-Carrier Template.
Assign any file name (the extension .cft is added automatically).
You can then create your variable tool-carrier template or a tool-carrier
kinematics description. In the example, first four variables are defined for
the height and radius of the two cylinders. This means that the appearance
of the tool carriers is variable. The height and radius of the two cylinders will
later be specified with the FixtureWizard.
Entry Input Description
Description
(DOC)
Any text Object designation that is used in the tool-
carrier description.
File
(FILE)
Path and file
name
Path and file name of the CMO that is to be
used at this spot in the tool-carrier
kinematics.
Help graphic
(PICTURE)
Numerical value Path to the help-graphic file for a variable or
a variable tool-carrier part.
Label text
(LABELID)
Any text Entry of a plain-language name or text ID.
You can use the PLCtext software tool to
create the texts as BMX texts. The texts
must be located in a Text subdirectory of
the respective fixture.
To Next Page
Loading...
