F-DQ defective

I have issues with a F-DQ module(6ES7526-2BF00-0AB0) that keep going defective.

We have 5x of the same type module in the rack and it's only this one module that goes defective. Note that this module is in the last slot of the 5.

After the module has gone defective we can disconnect and reinsert it to make it work again, for a timeframe of about 10min to 2days, where it again will get the "defective" error.

We have attempted to replace this module with brand new module but the same error occurs.

We have also attempted to increase the f-monitoring time from 150ms to 500ms.

The module has the latest firmware version 1.0.2. The CPU has the latest firmware version 2.5.2.

Do anyone have experience with the same issues?

Attached zip file of 3 diagnostic buffers:

- Module is defective

- Safety program: Error in PROFIsafe communication with F-I/O

- Safety program: F-I/O passivated

Hi MartinDav,

We have the same problem at a PLC configuration. The last F-DQ (6ES7 526-1BH00-0AB0) card detect some times (few days/weeks) a fault (wire break detection) . 

We already exchanged a few parts:

- the F-DQ card,

- Contactor on the output channel

- wiring in the panel

We still have the problem, it is the first output channel of the last card (same as yours) 

Do you already found the issue and do you have a sollution?

Best regards,

Roel

Hi MartinDav,

Has there been a solution to this? I am also having the same problem with the same card (6ES7526-2BF00-0AB0).

I've got two panels, each with identical PLC racks. The F-DQ card of the first panel had this error a week ago. The F-DQ card of the second panel had this error two days ago. Both panels are in the same building.

The errors happen in the same order:

1. Module is defective

2. Safety program: Error in PROFIsafe communication with F-I/O

3. Safety program: F-I/O passivated

Have you sorted the issue yet?

Hello everyone,

I am dealing with same problema with some Siemens F-DQ 6ES7526-2BF00-0AB0 cards which get defective few time after starting operation. ¿Did you get any solution to this issue?

Thanks you in advance.

Hi there,

We updated the firmware to V1.0.3 which solved the problem for us. Interestingly, the V1.0.2 firmware was meant to fix an error that is very similar to this one, but we already had V1.0.2 installed on the card. Whatever it was, V1.0.3 fixed it for us.

Firmware is here:

https://support.industry.siemens.com/cs/gr/en/view/109746436 

Hope this helps!