The "Set Next" function has been added to the list of XL Controller functions that can be disabled by Eclipse.

SCN 2274 allowed Eclipse to disable certain Order and Pattern modification features.

When SCN 2274 was implemented, no ability to override the Disable was added. Some features like "Set Next" or "Remake" are essential for expeditiously recovering from expected production events like parts that get damaged or don't meet quality expectations.

The ability for the Disable to be overridden at the controller by a manager that has a Setup Lockout Key has now been added. Each of the features that can be disabled are also capable of selectively being able to be overridden by the Setup Lockout.

The override capability is configured within Eclipse.

The "F3-Skip/Ready" function can be disabled by Eclipse.

The Advance After Cut setup had no effect on a rotary shear. The bug was caused because the Advance after Cut table was not being calculated for a rotary shear.

Start Match Smoothing used to have a range of 0% to 100%. There were several issues with the lower limit.

The Crank DA could not handle a value of zero. Zero was modified to have special functionality for the Eccentric DA. The Crank will generate a Drive Not Responding error if Zero is entered.

Very small values below 1% resulted in infinite loops during the Crank or Eccentric Cam Table creation.

1% is now the lower limit on the Start Match Smoothing parameter. The Eccentric will also accept 0% but nothing between 0% and 1%.

The Format of the parameter was modified to force all values to be in integer increments as all Mathcad simulation and testing were performed this way..

Although it has not been needed as of yet, the Crank Shear has a Continuous Mode that allows it to keep the die running continuously. To use this mode the press output needs to cut or punch the metal instead of the mechanical motion of the die. Enabling this mode was causing a Drive Not Responding error.

The original release of the Dual Line Encoder did not support Two Encoder Feed to Stop operation.

The Two Encoder Feed to Stop used and corrected the motor encoder resolution for generating Queue Targets. The Line Encoder counts were converted to Motor resolution counts. In order to implement the Dual Line Encoder feature each Line encoder needs a correction factor. This meant the code needed to be changed to correct and use the Main Encoder Resolution for generating Queue Targets. Encoder counts from the motor and the second line encoder are converted to the Main Encoder Resolution.

Although Dual Line Encoders cannot be enabled on a V3 controllers, common code was modified to allow it to be done on the V4 controllers.

The DIP switch setting to enable the second encoder has been enabled on the XL200CL.

The XL208 Crank Shear had a parameter called speed reduction that allowed the die to speed up, slow down or use the line velocity captured at the Start Match Position to finish the remainder of the die stroke.

Although the setup parameter still existed, this feature did not get implemented in the RE or MRE2 controllers.

We have added this feature to the RE and MRE2 models but we need to not impact machines that are working well and have been basically ignoring the value of the Speed Reduction parameter.

We are changing the name of the parameter to Shear Speed Adjustment to better reflect what it does. This has the added benefit of protecting a customer that has Eclipse and a potentially unwanted value for an old setup that prior to this change, did nothing.

When this parameter is set to to 0% it does nothing.

If it is non-zero, between 95% and 105%, it disables the Continuous mode operation. It captures the line velocity when the die is at the start match position and continues the die stroke all the way to home as if the material is moving at that velocity, multiplied by the Shear Speed Adjustment percentage.

The initial release of Dual Line Encoder capability calculated the ratio and Auto Corrected the Auxilliary Encoder Resolution backwards. For example, if the Auxilliary Encoder is reading half the encoder counts as the Main Encoder, over the same distance, the Auxilliary resolution should be corrected to double the resolution as the Main Encoder.

In the example above, the controller was incorrectly coming up with an Auxilliary Resolution that was half of the Main Encoder resolution