5358
5226; Adjusted Load for Backstop Only Worked on Load Step
Pathfinder

Changes made for Pathfinder 5226 controllers.

The problem: Starting a program on a regular bend step (instead of a load step) with a gripper-backstop offset — the backstops would retract after gripping, then the backgauge never moved and the cycle hung.

Root cause: In RunDoubleBend.c, the special backstop-load block in LoadSheetWithGripper (both the _Original and _SM versions) waited in while (!TestInputBit(I_112_GRIPPER_BACKSTOP_2_RETRACTED_LIMIT)) with no check that I_112 is actually assigned. TestInputBit returns FALSE forever for an unassigned input, so machines without that limit switch spun in the loop indefinitely. The load-step path never consults I_112 at all, which is why starting on an actual load step worked fine.

The fix: Guarded both wait loops (line 1816 and line 2499) with IsInputFunctionDefine(I_112_...) — same pattern the E377 conflict checks in MoveToPosition.c already use. Machines with the switch wired behave exactly as before; machines without it skip the wait and move the backgauge immediately.

Status: Edit applied byte-safely (Win-1252/CRLF verified intact). The file was already a pending TFS edit from the state-machine work — nothing checked in. Still to do on your end: build in KDS and re-test starting on a regular step where programmed position + backstop offset < 5.0.

Model Version Released
5226BB Rev F. 4.04.28 8/11/2026
5226BB Rev G. 5.00.27 8/11/2026
5226BB Rev H. 5.01.03 8/11/2026