There were several bugs with the same root cause in the Multi-Axis Jog Screen related to the touch screen or mouse processing of the jog buttons.

1. Clicking on the jog button and dragging the mouse out of the button area left the Axis jogging.

2. Dragging the mouse from outside of the button to inside of the button and then releasing could cause an Axis not Enabled error when technically the button had not been clicked nor had any attempt to jog the axis been made.

3. Selecting the Yes button in the Reference, Are You Sure window could sometimes erroneously result in the Axis not Enabled error window being displayed.

The root cause of these problems was a bug in how the jog buttons generated the PSF_RELEASE signals. The problem was actually in all buttons but the jog buttons are the only buttons that use these special signals created specifically for jogging.

For problem 1 the PSF_RELEASE signal was not being sent when it should have been. Problems 2 and 3 were caused because the mouse was released over the button and the PSF_RELEASED was being generated even though the button had never actually been pressed. For problem 3 the when the mouse was released the pointer was within the area of the Jog Button and it generated a PSF_RELEASED signal that it should not have.

These issues have been fixed.

SCN 4586 allowed the Velocity Scaling (Number of Implied Decimal Places) between the XL and the Drive to be configured in the drive. This required the XL to read the scaling format out of the drive and then calculate some scaling multipliers to scale back and forth between the XL and the Drive.

There was a bug that could cause the Fast and Jog velocity values sent to the drive to be incorrect if the scaling in the drive was changed after the initial power-up of the system.

This bug was discovered through code review when looking for an explanation for how the velocities could become zero. No means for them to be zero were found.

Invalid use of the Spacing Limit reference for operations in patterns can lead to unexpected results if specific rules are not followed.

In order to be effective or evaluated a Spacing Limit operation must follow an Even Space operation that uses the same Tool Id and Id Type. Id Type is used on SGF controllers for shape programming.

This change adds a test for Spacing Limit operations. If they don't directly follow an Even Space operation that uses the same Tool Id and Id Type an error message will be generated and the line halted.

The Error message states "Invalid Spacing Limit operation in Pattern %3w. Spacing Limit operations must directly follow an Even Space operation programmed with the same Tool Id and Id Type, if present."

A customer found a bug in the Tile Machine software when using Manual Punch operations and configured for dual forming presses. The Minimum Forming Tool Distance parameter was not being honored and would raise the Lower Forming Tools early under very specific conditions.

In order to manage the dual Forming tools the controller needs to know the distance between them, it needs to know how wide they are and where the forming presses fired last.

This bug would occur if the forming presses were fired using the Manual Punch input(s) prior to running any parts. The only time the distance between the presses was being calculated and saved was when calculating and running parts in automatic. If the distance had not been calculated, both forming tools would raise up early.

The solution to this problem was to do the same calculations at the start of a Manual Punch operation so that the software could calculate properly where to raise the forming tools.