There are many things that are locked or disabled based on the state of the Setup Lockout, also known as the Key Switch input.

This was all being done with a global variable that was used everywhere. We have plans to make available other means of locking or unlocking things based on other factors. The global variable was removed, and it was replaced with object method function calls. This allows the locking to be changed or overridden based on any number of things, in the future.

The Setup Lockout Key Switch input, if used, provides two levels of access to settings and other options, Full and Restricted.

A new project requires the need for Eclipse to be able to override the Key Switch input and control the same two levels of access.

Two new UART commands allow Eclipse to Lock and Unlock as if the Setup Lockout input were locked or unlocked. The are active starting with UART version 3.63.

To handle cases where Eclipse might be down and Key Switch control is required, the Key Switch input can still be used. The controller will keep track of the last source of lock/unlock activity and use the state of that source for the lock state.

If Eclipse wants to be in control of the lock state, Eclipse should set the desired state every time a controller comes online. This will take back control from the Key Switch if it was used while the controller was offline.

The Rts_Sync_Acknowledge, and related functions, implement a special type of sleep that is not present in other operating systems. When we move to Linux in the next generation controller we will either have to develop an equivalent or eliminate its use.

This change eliminates its use in places where it is known not to be necessary.

The upper limit of the Shear to Scrap Detect Distance setup is increased from 1000" to 119999", which is 9999 Feet 11 inch.

By request, an "Are you sure?" prompt has been added to the Change Product Code window dialog window. The operator must acknowledge the request with a Yes before the Product Code change will be initiated.