I have an older 1336 Impact Drive that is setup to operate on a vector input based on torque, drive communicates via DeviceNet. When the process is finished and the start command OTE falls off the drive will continue to creep because not all the torque calculation goes to zero as the speed reference. Why would the drive continue to run without the start command? Anyone else have this issues? Process has been stable for a number of years without issue until this started happening recently.
I guess the quick fix would be to move 0 into the speed reference when the process is not running. Just thrown why this is occuring now after the process has been rock steady for years.
I guess the quick fix would be to move 0 into the speed reference when the process is not running. Just thrown why this is occuring now after the process has been rock steady for years.