LINK Systems OmniLink 5000 - Manual (Page 49)

April 17, 2000 Man ual Revisio n 1.0
5.4
It has no effect on the determination of peak tonnage (sampled at 200 microseconds). Machines with
speeds greater than about 20 strokes per minutes should be set to store at 200 microseconds. However,
slower presses that begin the working portion of the stroke (Start of Sample Window) high in the
downstroke may reach the maximum number of samples that can be stored (4735) before the end of the
stroke is reached (End of Sample Window). This would result in not being able to examine the tonnage
curve beyond the point where the storage area filled up. In this situation the storage rate should be set to
400 microseconds.
The entry can be:
Setting=000 Store sample point every 200 microseconds
Setting=001 Store sample point every 400 microseconds
Section 5.1.7 Start Sample Window Angle
This angle defines the point in the downstroke where the tonnage monitor module stops integrating
machine offsets and starts taking samples. After it is reached each sample is examined in order to
capture the peak tonnage for comparison with the limits in effect. The determination of peak tonnage
continues until the end of the working portion of the stroke (End Sample Window). Since this angle
defines the start of the working portion of the stroke, it must be set prior to the angle that tooling forces
begin. The angle can be set from 45 degrees to 120 degrees.
Section 5.1.8 End Sample Window Angle
This angle defines the point in the up portion of the stroke where the tonnage monitor stops sampling the
peak tonnage. At this point all limits that create top stops are examined and a stop signal sent to the
press control if any alarm detected. Alarm counters are also updated at this time, along with saving the
last machine offset. Since this angle defines the end of the working portion of the stroke it must be set
beyond the angle where tooling forces end. The angle can be set from 220 degrees to 250 degrees.
Section 5.1.9 Erase All Setups
The tonnage monitor module stores limits for job setups in a nonvolatile memory. If a module is ever
moved to another machine, the limits that exist are no longer applicable. This function will erase all job
setups. It requires an additional access code to initiate (see section 10).