Thanks Ken.
Do you mean that you are examining the LCD "Human Interface Module" on the 1336 Plus II drive itself ?
Yes, I meant HIM
Typically, of course, when a drive loses comms with the PLC it will generate a fault code on the display.
No Fault code is generated
So yours is either stopping because it's been told to, or because it's been configured to stop and not fault, or because it's being automatically reset.
I believe it has been programmed that way.
Do you have a 1203-CN1 external ControlNet to SCANPort module on the drive ?
Yes, there is a 1203-CN1 module and a scanport splitter installed.
Those devices can be set up to react differently to a ControlNet connection loss than to the PLC going into PROG mode.
The default is to cause a fault on the drive, just like if you had unplugged the SCANPort cable. But they can also be set up to go to "Comms Fault Action" and simply stop the drive without causing a SCANPort fault. I once programmed an application where the 1336 Plus II would react to a network fault by turning on in reverse direction and 10% speed until it hit a hardwired limit switch !
In my case, it just says Stopped on the HIM.
Your system isn't easy for a novice to use: you have a 1747-SCN15 scanner in the SLC-500 chassis, which has its scanlist and ControlNet schedule set up with RSNetworx for ControlNet software. You might also have a serial/ControlNet module (1747-KFC15, I think) or another ControlNet interface (1784-PCC card, or 1784-U2CN).
Yes, it’s a bit involved.
How often does the SLC-500 program command starts and stops on these drives ? Is the 30 minute runtime precisely 30 minutes, or does it vary ? How often does the "failed to start" alarm occur ?
Its roughly 30 minutes. It always happen when run in AUTO mode.
The 1336 Plus II has a simple "fault queue" that will show you the last four faults that occurred on the drive. It's described in Chapter 3 of the user manual.
I will find out that parameter. But last fault when checked was not listed. It stops and doesn’t log it as a fault. So probably won’t be in the list of faults.
https://literature.rockwellautomatio...m002_-en-p.pdf
A serial fault (F 10) means a disconnection of the SCANPort cable between the drive main control board and the ControlNet interface module. If my memory is correct, Fault 10 also happens if the 1203-CN1 is configured to fault the drive when the ControlNet connection fails or goes to PROG/IDLE mode.
There is no F10 or any other fault. It just stops on its own after running for 30 minutes or so.