Hi Ken: Firast, thanks for your answer.
I will try to quote your questions...
I have never heard of a PowerFlex drive failing to obey a STOP command.
STOP commands always override all other drive commands, and have done so for every A-B drive I have worked with for almost three decades. To my knowledge, STOP commands cannot be masked or disabled from any SCANPort or DPI adapter on any A-B drive.
Same to me, first time thast I see this very rare issue. In all networks that I have worked, stop bit from command word override any other commands.
Does this happen every time your logic attempts to stop the VFD ?
Yes, every time. Then I have to go to MCC and stop via Enable input
Are there other ways to successfully stop the drive, other than Emergency Stop ?
No, just Emergency Stop and ControlNet
How long does the condition persist ? Is the VFD configured for "coast to stop", or "Ramp to Stop" ? What is the Decel Time ?
Coast to Stop, but I am not 100% sure, I am not in plant now
Where do you see the "Stop Asserted" indication ?
In the blinking led, the HIM and the status in Drive Executive
Are you 100% certain that you are monitoring the correct VFD and motor ?
Yes, because of what I have explained before, that I shut down Enable bit and the VDF with motor stops
Are you 100% certain that the STOP command bit is staying on constantly ?
Yes, I mantain latched the stop command until running status is off. So, as the running status remains in 1, I never unlatch the stop command
Again, this is a very unusual condition to report, so I want to be sure that you very carefully check your evidence and assumptions.
I have another machine with the same logic and the same VDF and don't have that problem. So, mi hope was that an specific "hidden magic" parameter, owner or mask is bothering, but as now, cheking most common configuration, both VDF have the same programming.
Thanks