Hi,

We have a crane hoist that is using a 6SL32101SE260AA0 power module that keeps overheating it's braking resistor.  We keep getting an external fault F07860 on the drive. It is an external fault coming in via binector p2106, but I am unsure how to trace the source of this in PLC? I assume it is coming from the thermostatic switch in the resistor but I need to trace the fault code to be certain.

Could anyone give me some tips on how to trace this fault?

Thank you in advance.

Which binector is connected in p2106?

For example if it is an digitalinput (for example r723.0), I would trace r723 and after trace you can show this in bit tracks.

You can use this binector as trigger event too.

zako_

Which binector is connected in p2106?

For example if it is an digitalinput (for example r723.0), I would trace r723 and after trace you can show this in bit tracks.

You can use this binector as trigger event too.

 Thanks for the reply, but I think I phrased my question incorrectly. I am not trying to run a diagnostic trace, I am simply looking for any reference of this bit to an input/output in the PLC. I am new to the STARTER program, and I am possibly looking in the wrong place. I've attached a screenshot.

Thanks

I suppose the screen shot is not from the correct drive, because there is p2106 = 1.

So it is always true and you won´t get F7860.

Ok, so I checked again with the drive connected and can see the fault comes from r2197.7 'speed setp - act value deviation in tolerance t_off)

I managed to catch the fault occurring during a trace and can see that when I drive the hoist up, fully loaded and in full speed, the speed deviation goes up to 320 rpm and then faults.

What parameter should I look at to mitigate this? Speed deviation tolerance? Deviation over time?

Hi,

I think there is a good reason, why someone parameterized this warning with the speed deviation. So I would rather look why the actual speed deviates now from the speed setpoint. As you have a crane, I think this solution was done to avoid the load is dropping down uncontrolled.

You say that the error is coming when the load is pulled up. So it seems that there is not enough torque available to follow the speed setpoint.

Hi, I know this thread is old now but I thought I'd share my findings. We found that the drive was set to 'encoderless operation', as there was a wiring problem with the encoder and it was never fixed during commissioning. I fixed the wiring issue and enabled the encoder, as I wanted more accurate diagnostic of speed and position. I then enabled 'speed control via encoder' and it improved the speed tracking drastically. We are now no where near our speed deviation setpoint.

Thank you for your help