ctrlX SAFETY "SafeMotion"
Fig. 53: Exemplary dialog: "IO mapper inputs"
The IO mapper blocks are assigned in the 16 so-called "networks”.
The maximum number of IO mapper blocks is limited and preset by so-called
"instances". If all instances of an IO mapper block are used, this IO mapper
block is not provided any more.
When an IO mapper block has been assigned to a network, the name of
the IO mapper block type is displayed in the Project Explorer; for example,
"Network 1: Safe connector".
If the predefined configuration "Safety bus communication" has been
pre-assigned to a network, the text of the corresponding branch is
grayed out and "(predefined configuration)" is added to it; for example,
"Network 2: Safe connector (predefined configuration)" (see ⮫ Safety bus com-
munication).
The "Emergency stop signal (SMES)" and the
"operation mode selection signal (MS)" always have to be assigned to a
selection signal in the I/O mapper inputs via a network. If the signals are
not used, they have to permanently deselected via the I/O mapper block
"safe constant selection" (signals are active when signals = 0 V). Otherwise,
the axis permanently is in SMES or SMST1/SMST2.
− When the IO mapper block type is changed, the allowed input/output sig-
nals change in many cases. The signals that were set are not changed, but
might possibly be displayed as invalid.
− Which input signals can be processed by an IO mapper block depends on
the IO mapper block type.
− The multiple use of inputs is possible, because source signals can be simul-
taneously assigned to several networks.
−
IO mapper blocks have at least one input at which a signal has to be
applied. It is not necessary to apply a signal at optional inputs. If no signal
has been applied to an optional input (the input is not used), S-0-0000 has
to be configured as the source signal at the optional input.
Selection and acknowledgment
To Next Page
Loading...
