Limits and Delays

From Knowledge Base
Revision as of 14:16, 31 August 2022 by Jordan (talk | contribs)

Back to TMAC Categories Page

Overview

Every limit and delay programmed for an operation is stored in the job. Limits and delays can be edited at any time. The available limits for an operation depend on the channel class being monitored and if adaptive control is enabled.

Note: The limits and delays described in this chapter are not applicable to Millivolt operations.  

Limits and Delays Per Channel Class

Work (HP/s, kW/s) Limits

TMAC has the capability of using a work value for undercut and wear limits. Work limits (also known as "area under the curve") use signal value over time instead of peak values learned during an operation. Spikes in signal can satisfy undercut limits or trigger wear alarms unnecessarily. This can be prevented by using work limits.

For example: If a power spike reaches a value over the undercut limit but immediately comes back down under the limit, the undercut limit is satisfied, and the process continues. If the power stays below the undercut limit after the spike, the desired output is an alarm condition.

Work limits can only be applied to primary channel operations.

Extreme Limit

The Extreme Limit signals a catastrophic event (e.g., a severely worn or broken tool). When the signal value exceeds the extreme alarm for the amount of time specified in the Extreme Alarm Delay, TMAC halts monitoring and triggers an Extreme Alarm. The extreme limit is set at a percentage above the learned value for a given operation.

Setting the Extreme Limit

To set an Extreme Limit use the following steps:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the Extreme Limit % field
  3. Enter the percentage above the learned value that will trigger an extreme alarm condition.
    1. Allowable values range from 1% to 999%
    2. Entering a value of 0 disables the Extreme Limit
  4. Click SAVE

Note: Although the above step list specifies entering a percentage for the limit, a direct value may be entered in the other field outlined in step 3 in the figure above. When a limit is set in either field, the other field is automatically populated.

Extreme Alarm Delay

The extreme alarm delay specifies a time period during which the signal value exceeds the extreme limit without triggering an alarm. This allows for brief spikes without unnecessary alarms.

Setting an Extreme Alarm Delay

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Extreme Limit section of the Job Editor, click the Delay field
  3. Enter the duration of the extreme delay
    1. Allowable values range from 0.1 to 320 seconds in 0.1 second increments
    2. Entering a value of 0 disables the Extreme alarm delay
  4. Click SAVE

Wear Limit

The Wear Limit alerts the operator that a tool has reached its optimum wear point and should be changed. An alarm activates immediately when signal value exceeds the Wear Limit, unless a Wear Alarm Delay is set. The Wear Limit is a percentage value above the learned value for an operation.

The user may need to experiment with different tools and parts to arrive at the best Wear Limit for a given set of conditions. Once appropriate limits are determined for all the machining processes, a direct and repeatable relationship to tool condition will be noticeable.

Setting the Wear Limit

To set a Wear Limit:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the Wear Limit % field
  3. Enter the percentage above the learned value that will trigger a wear alarm condition.
    1. Allowable values range from 1% to 999%
    2. Entering a value of 0 disables the Wear Limit
  4. Click SAVE

Note: Although the above step list specifies entering a percentage for the limit, a direct value may be entered in the other field outlined in step 3 in the figure above. When a limit is set in either field, the other field is automatically populated.

Wear Alarm Delay

The Wear Alarm Delay specifies a time period during which the signal value for an operation may exceed the wear limit without triggering an alarm. This allows for brief signal spikes without unnecessary alarms.

Setting a Wear Alarm Delay

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Wear Limit section of the Job Editor, click the Delay field
  3. Enter the duration of the wear delay
    1. Allowable values range from 0.1 to 320 seconds in 0.1 second increments
    2. Entering a value of 0 disables the Wear Alarm Delay
  4. Click SAVE

Setting a Work Wear Limit

To set a work wear limit use the following steps:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the Work toggle switch
  3. Enter the percentage above the Learned Work value that will trigger an alarm.
    1. Allowable values range from 1% to 999%
    2. Entering a value of 0 disables the Wear Limit
  4. Click SAVE

Undercut Limit

The Undercut Limit alerts the user to an incomplete machining process (e.g., a broken or missing tool).

The Undercut Limit is programmed as a percentage below the learned value for an operation. If the signal value fails to exceed the undercut limit for the amount of time specified in the Time Above Undercut field, TMAC generates an under-cut alarm when it receives a stop command.

Note: If using time increments, the undercut alarm is generated at the end of the time increment instead of the next stop monitor command.

Setting the Undercut Limit

To set an Undercut Limit:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the undercut Limit % field
  3. Enter the percentage below the learned value that will trigger an undercut alarm condition.
    1. Allowable values range from 1% to 99%
    2. Entering a value of 0 disables the Undercut Limit
  4. Click SAVE

Note: Although the above step list specifies entering a percentage for the limit, a direct value may be entered in the other field outlined in step 3 in the figure above. When a limit is set in either field, the other field is automatically populated.

Time Above Undercut

The Time Above Undercut feature is a timer that adds an additional requirement to trigger an undercut alarm. When using Time Above Undercut, an undercut alarm is triggered when the signal value fails to exceed the undercut limit for a specified duration. The Time Above Undercut limit is cumulative. TMAC accumulates the time while the signal value exceeds the undercut limit.

If the time is equal to or greater than the limit, no alarm is triggered. An alarm is generated only when the total time the signal value exceeds the undercut limit is less than the programmed time above undercut. The best way to arrive at an undercut time is to use the Data Viewer and measure the duration that the signal value exceeds the undercut limit.

Setting a Time Above Undercut

In the Job Editor

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Undercut Limit section of the Job Editor, click the Time Above Undercut field
  3. Enter the desired Time Above Undercut time
    1. Allowable values range from 0.1 to 320 seconds in 0.1 second increments
    2. Entering a value of 0 disables the Time Above Undercut Feature
  4. Click SAVE

Setting a Work Undercut Limit

To set a work undercut limit use the following steps:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the Work toggle switch
  3. Enter the percentage below the learned work value that will trigger an alarm.
    1. Allowable values range from 1% to 99%
      1. Entering a value of 0 disables the Undercut Limit
  4. Click Save

Spindle Speed Limits

Spindle Speed monitoring tests the measured spindle speed of the machine against an upper and lower limit. TMAC checks the spindle speed between every Start and Stop monitor command. If the speed exceeds the upper limit or falls below the lower limit by the specified percentage:

  • An alarm is triggered
  • Tool monitoring is halted

Note: If a start delay is used, the spindle speed threshold does not take effect until the start delay has timed out.

Setting an Upper Spindle Limit

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the parameters section of the Job editor, click the Spindle Speed field
  3. Enter a target spindle speed for the operation. Typically this matches the spindle speed set in the part program
    1. Valid values are 0-99999
  4. In the Limits section of the Job Editor, click the Upper Limit % field
  5. Enter the percentage above target spindle speed that will trigger an Upper alarm condition.
    1. Allowable values range from 0% to 99%
    2. Entering a value of 0 disables the Upper Spindle Limit
  6. Click Save

Setting an Upper Limit Delay

An Upper Limit Delay allows the spindle speed to surpass the upper limit for a specified amount of time before an alarm is triggered. To set an Upper Limit Delay use the following steps:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click Upper Delay field
  3. Enter the amount of time the spindle speed is allowed to exceed the upper limit
  4. Click SAVE

Setting a Lower Spindle Limit

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the parameters section of the Job editor, click the Spindle Speed field
  3. Enter a target spindle speed for the operation. Typically this matches the spindle speed set in the part program
    1. Valid values are 0-99999
  4. In the Limits section of the Job Editor, click the Lower Limit % field
  5. Enter the percentage below the target spindle speed that will trigger a Lower alarm condition.
    1. Allowable values range from 0% to 99%
    2. Entering a value of 0 disables the Lower Spindle Limit
  6. Click SAVE

Setting a Lower Limit Delay

A Lower Limit Delay allows the spindle speed to fall below the lower limit for a specified amount of time before an alarm is triggered. To set a Lower Limit Delay use the following steps:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the Lower Delay field
  3. Enter the amount of time the spindle speed is allowed to fall below the lower limit
  4. Click SAVE

Coolant Limits

Coolant monitoring measures either coolant flow or coolant pressure against programmed limits. Alarms are triggered when the coolant flow/pressure deviates outside of the programmed limits. The available limits are as follows:

  • High: When coolant flow or pressure exceeds the limit, TMAC halts monitoring and issues a High Coolant Alarm
  • Low Warning: When coolant flow or pressure falls below the limit, TMAC issues an alarm and continues to monitor the operation
  • Low: When coolant flow or pressure falls below the limit, TMAC halts monitoring and issues a Low Coolant Alarm

Note: The learned value that coolant limits are based on, is the lowest value recorded during the learn operation.

Setting a High Coolant Limit

To set a High Coolant Limit use the following steps:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the High Limit % field
  3. Enter the percentage above the learned coolant flow/pressure that will trigger a High alarm condition.
  4. Click Save

Setting a Low Warning Coolant Limit

To set a Low Warning Coolant limit, use the following steps:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the Low Warning Limit % field
  3. Enter the percentage below the Learned Coolant Flow/Pressure that will trigger a Low Warning alarm condition.
  4. Click Save

Setting a Low Coolant Limit

To set a low coolant limit use the following steps:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, click the Low Limit % field
  3. Enter the percentage below the Learned Coolant Flow/Pressure that will trigger a Low alarm condition.
  4. Click SAVE.

Coolant Alarm Delay

The Coolant Alarm Delay specifies a period of time which the measured coolant flow/pressure may exceed (High) or fall below (Low Warning and Low) the programmed limits before triggering an alarm condition.

Setting Coolant Alarm Delay

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Limits section of the Job Editor, Click the Delay field for the desired limit
  3. Enter the time in seconds for the alarm delay
    1. Allowable values range from 0.1 to 320 seconds in 0.1 second increments
    2. Enter 0.0 to disable the coolant alarm delay Click Save
  4. Repeat steps 2-4 for each limit that requires a delay

Extreme Feedrate Limit

The Extreme Feedrate limit is used to monitor excessive tool wear or breakage in adaptive control. In an adaptive operation, the commanded feedrate is inversely proportional to the signal value. As the signal value increases, TMAC reduces the feedrate to maintain a constant target signal value. When the feedrate over- ride falls below the programmed Extreme Feedrate Limit for the time specified by the Extreme Feedrate Alarm Delay, TMAC triggers an extreme feedrate alarm. The Extreme Feedrate Limit function cannot be disabled. The default value is 20%.

Setting the Extreme Feedrate Limit

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the segment features section click the Adaptive check-box
  3. In the Limits section of the Job Editor, click the Feedrate Extreme % field
  4. Enter the percentage feedrate that will trigger an Extreme Feedrate Alarm condition.
    1. Allowable values range from 1% to the max feedrate of the machine
    2. Must be less than Wear Feedrate % Limit
  5. Click Save

Extreme Feedrate Alarm Delay

The Extreme Feedrate Delay specifies a time period during which the feedrate can fall below the Extreme Feedrate Limit without triggering an alarm.

Setting an Extreme Feedrate Alarm Delay

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Feedrate Extreme Limit section of the Job Editor, click the Delay field
  3. Enter the duration of the feedrate extreme delay
    1. Allowable values range from 0.1 to 320 seconds in 0.1 second increments
    2. Entering a value of 0 disables the Feedrate Extreme alarm delay
  4. Click SAVE

Wear Feedrate Limit

The Wear Feedrate Limit is used to monitor tool wear in adaptive control. Adapt- ive control determines tool wear by controlling the feedrate override. In an adapt- ive operation, the commanded feedrate is inversely proportional to the signal value. As the signal value increases, TMAC reduces the feedrate to maintain a constant target signal value. When the feedrate override falls below the wear feedrate limit for the time specified by the Wear Feedrate Alarm Delay, TMAC triggers a wear feedrate alarm.

Setting a Wear Feedrate Limit

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the features section click the Adaptive check-box
  3. In the Limits section of the Job Editor, click the Feedrate Wear Limit % field
  4. Enter the percentage feedrate that will trigger a Wear Feedrate alarm condition.
    1. Allowable values range from 1% to the max feedrate of the machine
    2. Must be greater than Extreme feedrate limit
  5. Click SAVE

Note: Use trial and error to determine the best setting. Remember, the lower the programmed wear feedrate, the longer the tool will cut before generating a wear feedrate alarm.

Wear Feedrate Alarm Delay

The Wear Feedrate Alarm Delay can prevent an instantaneous signal spike and associated feedrate drop from triggering the wear feedrate alarm. These spikes may occur if the tool encounters a hard spot in the material and may not necessarily indicate tool wear. This delay allows the feedrate to drop below the wear feedrate without generating an alarm for the time specified . The Data Viewer can help determine the duration of the spike, and the appropriate value for this delay.

Setting a Wear Feedrate Alarm Delay

In the Job Editor:

  1. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. In the Feedrate Wear Limit section of the Job Editor, click the Delay field Enter the duration of the Feedrate Wear delay
    1. Allowable values range from 0.1 to 320 seconds in 0.1 second increments
    2. Entering a value of 0 disables the feedrate Wear alarm delay
  3. Click SA VE

Slope Limit

Slope limits are available for operations that employ time increments. Some complex machining operations, such as constant surface speed lathe operations, can be monitored more accurately with slope limits. An operation where the load increases or decreases from start to finish is not accurately monitored with horizontal limits. Slope limits that parallel the slope of the signal value permit more accurate and sensitive monitoring. The following is true when implementing slope limits:

  • The operation must employ time increments
  • The last time increment in an operation cannot have a slope limit
  • Slope parameters define the learned slope value for the operation
  • Slope limits are calculated as a percentage above or below the learned slope

Setting Slope Limits

Use the following steps to set slope limits for an operation:

  1. If the operation does not employ time increments, use the Time Increment Editor to add time increments to the associated operation.
  2. Specify the operation by selecting the tool, section, and channel from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  3. Select the time increment that requires slope limits
  4. Select the Slope monitor type
  5. Enter the Slope parameters:
    1. Slope Start: Defines the learn value at the start of the time increment
    2. Slope End: Defines the learn value at the end of the time increment
    3. Limit Sensitivity: Determines the slope of the slope limits; Increasing the value of this setting makes less parallel to the learned slope, allowing the user to fine tune slope limits
  6. Set desired limits
    1. Slope Extreme: Set as a percentage above the learned slope; An alarm is triggered when the signal value exceeds the limit.
    2. Slope Wear: Set as a percentage above the learned slope; An alarm is triggered when the signal value exceeds the limit.
    3. Slope Undercut: Set as a percentage below the learned slope; An alarm is triggered if the signal value fails to exceed the limit.
  7. Set any desired alarm delays
    1. If an alarm delay is set for slope extreme or wear, an alarm is triggered when the signal value exceeds the limit for the amount of time set in the delay.
    2. If the Time Above Undercut is set, the signal value must exceed the undercut limit for the amount of time set.
    3. If the Immediate switch is toggled, the functionality of the Undercut limit changes; An alarm is triggered when the signal value falls below the undercut limit.

Slope Sensitivity Examples

Slope Sensitivity allows the user to fine-tune the behavior of slope limits. Slope limits without limit sensitivity set run parallel to the learned slope value. Increasing the sensitivity causes the limit to be calculated from learned load data samples across the entire time increment. This makes the limits proportional to the learned slope, so that at lower load values in the slope the limits are closer to the learned load limit. Slope limit sensitivity impacts wear and extreme slope limits. If the Immediate switch is toggled for the undercut slope limit, the limit sensitivity will also impact the undercut limit. This is displayed in the following examples:

Comparison Examples of Slope Limit Sensitivity

Signature Limits

Signature limits offer an alternative to standard monitoring limits. When using standard monitoring limits, the sensor signal is measured against a set value as a percentage above or below the learned peak value. Signature limits are based on a learned signature profile. TMAC accesses the learned profile to build limits that mirror the monitored operation. Alarms are triggered when the sensor signal deviates from the learned profile by the value set for the limit. The following signature limits are available:

  • Upper Extreme: When the sensor signal exceeds the learned profile by the value set for the limit, a critical alarm is triggered.
  • Upper Warning: When the sensor signal exceeds the learned profile by the value set for the limit, a warning alarm is triggered.
  • Lower Warning: When the sensor signal falls below the learned profile by the value set for the limit, a warning alarm is triggered.
  • Lower Extreme: When the sensor signal falls below the learned profile by the value set for the limit, a critical alarm is triggered.

Setting Signature Limits

Use the following steps to set signature limits for an operation:

  1. Specify the operation by selecting the tool, section, channel and time increment (optional) from the lists on the left side of the Job Editor. The selected operation is displayed at the top of the Job Editor.
  2. Select the signature monitor type.
    1. Note: When selecting the signature monitor type, the operation should be re-learned using the Learn Once feature
  3. Set desired limits:
    1. Upper Extreme: Set as a value above the learned profile; A critical alarm is triggered when the signal value exceeds the limit.
    2. Upper Warning: Set as a value above the learned profile; A warning alarm is triggered when the signal value exceeds the limit.
    3. Lower Warning: Set as a value below the learned profile; A warning alarm is triggered when the signal value falls below the limit.
    4. Lower Extreme: Set as a value below the learned profile; A critical alarm is triggered when the signal value falls below the limit.
  4. Set any desired alarm delays
    1. If an alarm delay is set for the upper extreme or upper warning lim- its, an alarm is triggered when the signal value exceeds the limit for the amount of time set in the delay
    2. If an alarm delay is set for the lower extreme or lower warning lim- its, an alarm is triggered when the signal value falls below the limit for the amount of time set in the delay
Retrieved from "https://kb.wolframmfg.com/index.php?title=Limits_and_Delays&oldid=183"