
PLMNL0243 REV. A, Effective Date: 03/24/16
53
FiberMINI ™ 2.0 Operation Manual
10 Appendix B
– Example of Integrating the HSU to a PLC/CNC
In general, the HSU is intended to be very
simple in design. The integration into a motion
system requires a minimal amount of hardware
wiring and I/O resources. This section provides
examples on how to integrate the HSU into a
PLC/CNC based motion system using Ladder
Logic. However, these examples are not meant
to be exact, as your actual system will have
different labeling and assignments. The
integrator is encouraged to build off of these
examples and modify them to best meet the
design criteria for the system.
There are significant advantages of having the
following logic signals generated within the
PLC/CNC rather than on the height sensor
electronics or external circuitry. These
advantages include:
The user can adjust all of these parameters
through the PLC/CNC.
The safety interlocks for the PLC/CNC are
retained because direct servo control is not
given to the HSU.
There is less opportunity for electrical noise
to cause interference because the signals
are generated within the code of the
PLC/CNC.
The system integrator builds the controls
directly into their own system, which gives
the operator one point of control.
In-Position
Typically the In-Position signal is generated by
comparing the actual standoff to the desired
standoff. Rung 1 gives an example of how to
generate the In-Position signal. See
Figure 64
Run/Hold
There are a couple of different ways of
implementing a Run/Hold request. The first
example is to simply have the Hold request tied
directly to the drive-enabled contact as shown in
Rung 2. Other conditions for a hold should also
be applied in-series to Hold in this rung. See
Figure 65
The second example is to set the drive
command to a constant value of zero (K0) as
shown in Rung 3. See
. Be careful not
to set the drive command value in another rung
as it might cancel out the effects of this one.
(Notice that Rungs 4 and 5 both require that
Hold is not active).
Figure 66