FreeAtLast
Member
Hi all. First post here, but thanks for a great site full of helpful threads.
I'm using the STO function on my Kinetix 350, and energizing those STO inputs via delayed output contacts on my safety relay. Is it bad practice to disable the "EnableInputChecking"? I want to stop the servo right before the STO disconnects power to it, but I'd rather not have to hard wire that input (IOD-29) back to my PLC. I'm not planning to use any of the drive's I/O, and I'm hoping I can do all communication over ethernet.
What is the common practice here? Do people just send stop/MSF commands, in lieu of dropping the enable bit?
I'm using the STO function on my Kinetix 350, and energizing those STO inputs via delayed output contacts on my safety relay. Is it bad practice to disable the "EnableInputChecking"? I want to stop the servo right before the STO disconnects power to it, but I'd rather not have to hard wire that input (IOD-29) back to my PLC. I'm not planning to use any of the drive's I/O, and I'm hoping I can do all communication over ethernet.
What is the common practice here? Do people just send stop/MSF commands, in lieu of dropping the enable bit?