Changes made for Pathfinder 5223 and 5225 controllers.

Axes need bi-directional parameters to account for the axis moving differently in one direction compared to the other. With separate control of the axis the user is able to get more accurate results. The problem is that the backgauge and radius adjust were not updated to have bi-directional parameters like the clamp and bending beam.

The solution was to add the reverse directional parameters for the backgauge and the radius adjust. For the backgauge that meant adding the reverse slow distance and stopping reaction time. The radius adjust needed the reverse fast and slow speed in addition to the slow distance and stopping reaction time.

Changes made for Pathfinder 5223 and 5225 controllers.

In Pathfinder V2 there was a set in stone block of delay times used for certain safety and production features. If a certain machine needed the time to be different then the time had to be changed in the machine setup and built into Pathfinder. When moving to V4 and the configuration format this block of delays were turned into parameters for the 5226. The problem is that this was not implemented for the 5223/5225's which means they were stuck with default times built into the firmware.

The solution was to convert some of these delays into usable parameters. The delays that transitioned are the one man two man, hem in position and wait for pump active. One man two man is the amount of time the second operator has to press their pedal after the first operator pressed theirs. Hem in position is the amount of time the controller will wait after a hem smash before opening the clamp. Wait for pump active is the amount of time the controller will wait for the Hydraulic Motor Status input to turn on.

Changes made for Pathfinder 5223 and 5225 controllers.

Pathfinder communicates with the 5223 and 5225 controllers through a communication protocol. One of the ways the controller checks a command is by checking how much information it got and if it gets more than what the command was supposed to send it won't proceed. When Pathfinder transitioned from V2 to V4 the communication protocol changed which meant some commands would be sending more or less information in a different way. The bug that came from this is that the power off state command was checking the wrong packet length so the controller would not reset itself when Pathfinder told it to. This problem led to the controller instead raising the clamp when the e-stop input was taken away on a power down. This ended up leading to the clamp having to be referenced on a power up because it was still moving up when the machine lost complete power.

The fix to this bug was to make sure the correct packet length is looked at for the power down command.