How / where do I see what is causing the stop

Please also see the attached screenshots.

We have a turntable that is turned by two DC drives in master-slave configuration (I have been told that the masters current is used as a setpoint for the slave so that the 2 drives should end up sharing the load by using the same effect.

In the current running mode we have chosen to only run on one drive (luckily they are powerful enough to run in single mode) since the slave drive for some reason stops by itself and generates alarms after running a few hours as slave. But drives have done this while running in slave mode.

When it is running with a single drive it does not stop.

Once they have stopped the can be reset right away and restarted - but we don't want to have to do this all the time so we want to find out why it is stopping and correct it.

Hi,

from your screenshots we cannot see any actual faulty state of the drive. You should show/write which alarms / faults are present in the event of stopping. 

Hi Christoph and Robert,

Thank you for answering.

I have not seen the alarms - I have not been called when it happened (nice since it was in the middle of the night) but the duty electrician told me it was various PLC alarms because the drive was stopped. On the BOP display the drive just showed the it was ready to be started.

I am aware that you cannot see alarms in the screenshots - they were made from the Starter program without being connected to the drive (it is not easy to connect to the drive while running production). I was just hoping some information could be found in the SW even when offline.

Is the a way to open the right menu on the BOP panel and see what caused the stop. Preferably an explanation "for dummies".

ChristophD

hi,

and generates alarms after running a few hours

which alarms?

Regards

Christoph

Hi,

the PLC alarms from the HMI will probably not really help I guess.

We would need the real alarms from the drive. Best thing would be to go online with the engineering tool (TIA or Starter) and read the actual alarms or the alarm history. Reading the alarm history makes sense in case the PLC automatically acknowledges faults from the user program. 

Hi again Robert,

Thanks again.

OK - if I can't see it on the BOP panel (which is a shame) - it is naturally also possible to log on with Starter.

Can you tell me (perhaps from the screenshots) what / where I can open in starter and see what caused the stop. Preferably an explanation "for dummies".

RB91

Hi,

the PLC alarms from the HMI will probably not really help I guess.

We would need the real alarms from the drive. Best thing would be to go online with the engineering tool (TIA or Starter) and read the actual alarms or the alarm history. Reading the alarm history makes sense in case the PLC automatically acknowledges faults from the user program. 

Hi again Christoph,

Thanks - now I understand - and thank you Robert for explaining it also.

So the best way is with Starter - not easy with the BOP?

ChristophD

Hllo,

if you are only a additional detailwindows Alarms is open, here you can see the Alarms/Faults.

Regards

Christoph

Hi,

Christoph meant that you will automatically find a new window in the bottom of STARTER software when you go online with the drive. The tab/window is called "Alarms" and marked red. You will see it if you are online. 

If you want to see the alarm history go online and open the drive on the left side in the project navigator. Here you find diagnostics -> alarm history.