
Lenze · Drive Solution Designer · Manual · DMS 4.2 EN · 12/2013 · TD23 237
8 Motion design
8.2 MotionDesigner
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Structure of the ASCII file
Comply with the following conditions when creating the ASCII file. Thus, errors can be prevented
during the import. Error messages during import
( 238)
Condition Description
The parameters in the ASCII file must
be arranged in columns.
Separate table columns using semicolons, tabulators or spaces.
Each table column has to contain a
heading.
• The title is the unit of the quantity to be transmitted.
• Example: "[s]" or "time [s]", "[m/s]" or "speed [m/s]", "[kg]" or "mass
[kg]".
• Indicate the quantity when being without a unit.
• Examples: [BRK], [CINH].
• Set unit/quantity in squared brackets, e.g. [t].
Arrangement, number and identity
of the parameters in the ASCII file
and in the Object area of the Mo-
tionDesigner must comply with each
other.
• DSD reads the table columns from the left to the right. The parameters in
the Object area must be arranged accordingly from the top to the button.
• The data of the motion profile must be defined in the first two table col-
umns:
• 1. table column (X axis): Time [s]
• 2. table column (Y axis): Speed [m/s] (translatory) or speed [rpm] (rota-
ry).
The data must be consistent and
have valid value ranges.
• Table lines must be complete. No values should be missing.
• Mass must not have any negative values.
• Decimal numbers must not contain any characters.
• Decimals must be written with comma or point.
• In case of digital signals, the states must be indicated with "1" (High) and
"0" (Low).
• An activated brake (BRK) or a set controller inhibit (CINH) is displayed
as "1".
• A deactivated brake (BRK) or non-set controller inhibit (CINH) is dis-
played as "0".
During the import, other programs
must not access the ASCII file.
—
Comentários a estes Manuais