Atlas Copco PowerMACS 4000, Руководство пользователя

Страница: 371 / 668

Tightening
9836 3521 01 371
an alternative method that does not use the monitoring buffer. See description of the Angle monitoring
check in chapter: Monitoring Check
– Angle .
If the bolt runs forward again the recording is started from the current position.
Steps of the following types are handled specially:

D - Diagnostic Step. Is always considered running backward.

E1 - Run Engage method 1. Is always considered running backward.

GS - Run Gear Shift. Is always considered running backward.

SR
– Socket Release. Nothing is recorded for this step, neither in the forward, nor backward
direction.
When monitoring ends two things are done. First, the "Cycle End Torque", used by the Monitoring Check
–
Monitoring Yield point torque and angle check, is stored. It is normally set to the torque measured at the
shut off point of the last step, or if this step is a SR
– Socket Release, the step prior to it. However, if the
shut off point (target) is not reached for the last step executed, or if it did run in reverse direction and
thereby deleted values from the buffer, then the last torque value stored in the buffer is used as "Cycle
End Torque".
Secondly, the complete buffer is filtered for maximum torque for increasing angle, i.e. the following
algorithm is applied on the buffer
Torque(k) = MAX(Torque(k), Torque(k
– 1)), where k = [2..8192]
It is the filtered buffer that is used for all monitoring checks.
The monitoring checks are added as regular checks on any CE step. The checks are described in detail in
the following sub chapters.
If the parameter Ignore monitoring errors when step ends NOK (located under Monitoring on the CE
step) is checked then the active checks will not cause any events or set any error bits, only calculate and
report the corresponding result variables, when the cycle is already NOK. It is wise to check this setting to
avoid resulting events and error bits caused by the original error.
Note! All limits of the checks are optional. A check having no limit defined will always generate an OK result.
This might be useful if its only purpose is to produce a result variable to be reported.
All Monitoring checks can be configured as Fatal or Repairable. This controls which RM action that will be
taken.
Note! If the conditions required for evaluation of a check for some reason are not fulfilled an event saying
so is generated. Should the check have one or more limits defined then the corresponding error bits
are set as well and the status of the checks is set to
Fatal independent of the configuration.
Examples of such conditions are that the buffer is empty, that T start, T stop or threshold torques was
not reached, that no yield point was found, etc.
When a monitoring error is found the error is reported as RM Errors in cycle data and if not repaired by
Cycle RM also as Errors . See Cycle RM for details on reject management for monitoring checks.