V90 Fault F30074 on STO activation

Hello dear experts.

On Sinamics V90 driver (6SL3210-5FE11-0UF0). When aplying +24V to STO inputs, the fault F30074 is shown. After acknowledge, F1611 appears and remains on.

I've made some research on the forum, and F1611 can be from improper wiring or the "dark tests" from fail-safe outputs. I've followed this document (https://support.industry.siemens.com/cs/ww/en/view/109740693) trying every single type of connection, and the error still occurs.

It is strange that F30074 does not appear in the V90 documentation.

This behaviour happens in only 3 units of 5 present in the cabinet. The other 2 work nicely.

Any help will be appreciated.

Thank you

Hello Technology Team.

While I was writing the answer to your questions, I came up with another setup for the fail-safe CPU. I tested it and the problem has gone.

The key factor here is that the fail-safe CPU has 4 DC PNP outputs (Sick CPU0 with XTIO module). Output O0 and O1 are wired to all STO1 and STO2 respectively. Outputs O2 and O3 control one small relay each.

When the area is safe, all four safety outputs were activated at once. And that was the problem. Now, I give the small relays a bit of delay (500ms), to supply voltage only to STO inputs and after that I can close the relays.

Thank you for your time.

Update:

At first was OK. Did a fair ammount of tests, but after a while only one of five units is still faulty. Same error F30074 and F1611 now on every STO activation. The other four always ok, no ussues.

I increased the delay to 1,5sec but error shows right after supply 24V to STO inputs. If I power-on the V90 with the safe area, some times the error occur on change to unsafe (de-energisation).

All 24V supply and ground come from the same power source. I've checked all the connections are tight, not loose.

¿Is there a way to change the timing discrepancy of the STO inputs?

In the Function: Safety Integration (starter / startdrive), enable changes and enter the passcode.  Then the advanced options for the input timing differences can be adjusted.  The default is 500ms.  If it is lower than 500ms, it could definitely cause a problem.  It's there to help make up for dual-contact device opening and closing timing differences.  500ms is very generous in most applications.

Automation_***

Update:

At first was OK. Did a fair ammount of tests, but after a while only one of five units is still faulty. Same error F30074 and F1611 now on every STO activation. The other four always ok, no ussues.

I increased the delay to 1,5sec but error shows right after supply 24V to STO inputs. If I power-on the V90 with the safe area, some times the error occur on change to unsafe (de-energisation).

All 24V supply and ground come from the same power source. I've checked all the connections are tight, not loose.

¿Is there a way to change the timing discrepancy of the STO inputs?

0_Einstein

In the Function: Safety Integration (starter / startdrive), enable changes and enter the passcode. 

Dear  0_Einstein:

That is possible with the two G120C that I also have inside the same cabinet. But for the V90 drives I cannot parametrize safety feature. Nor with the V-Assistant.

I'm using TiaPortal V16 with sinamics Upd5

Technology Team

I don`t understand what the relays have to do with the STO terminals in your setup.
Could you provide a wiring diagram to understand where the F-DO`s are connected to?

Those relays control the supply for the outputs. The Sick CPU0 has PNP outputs, I thought that the simultaneous activation of STO and the relays could cause a voltage drop.

Attached you can find my original safety wiring setup and the alternate setup isolating the STO from the other safety features. When I changed to alternate, it begun working great, but after 20 or so enable-disable cycles, the error started to appear.

24V and GND come all from a single 10 Amp power supply. All components share the same source. I also tested with 20 Amp model, with the same results. There are no sensors connected yet. Only 1511CPU (+ 32DI, 16DO), Fail-safe Sick CPU0, 5x V90, 2x G120C, 1x Sick AFS60 absolute encoder, and 1x Delta HMI (DOP-107HE42).

Faulty drives are number 1,3 and 4. I know this isn't relevant.

I've changed the wiring many times, to test the issue. What really amazes me is that the fault is still happening even wiring the STO internally in every single drive (STO+ supply to STO1 and STO2). Plus, if I shutdown the drivers overnight, the fault is not activated the first time. It takes like 10 enable-disable cycles to happen on the nº1 drive, and a couple more cycles on the other 2.

While I'm testing / debugging the PLC + HMI program, I have the STO wired on the "original setup" attached. I've set "always true" to the STO. As the V90 drivers take much more time to startup than the fail-safe CPU, they start with the STO energized. I've cycled enable-disable all drivers a houndred times with not a single issue.

Thank you.