Good morning,

I am having a nightmare with the following error related to communication between 2 F-Runtimes:

Temporary CPU error: User programmed STOP request in FB 2008
affecting OB 123 execution

Internal address details: Caddr=16#00002186

Error: Safety program:DatacorruptionpriortosendingtopartnerF-CPU/other F-runtime group
F-runtime group   1
Detected by: Sender UUID beginning with 16#77E4
Offset of faulty byte:  4

Checking FB2008 it is a protected compiler block named "F_PS_COMM_DEVICE" with the following description inside:

F_: Protocol Driver Block Send PROFIsafe V2 + Protocolextension up to 100 Bytes

Checking this link https://support.industry.siemens.com/cs/ec/en/view/19183712 gives some info about how to find the origin, in my case just shows and offset of faulty byte but not the starting address.

Does anybody have an idea how to find the problem?  Any help would be great.

Thanks you all in advance

 More info. I have the following OBs:

OB30: 5ms priority 16

F-RTG 1: 20ms priority 15

F-RTG 2 : 80ms priority 15

I was doing some test and looks like when I assign to F-RTG 1 and F-RTG 2 same priority as OB30 problem dissapear, but I can not do it as OB30 execution time get unstable. Do you think problem is produced by OB30 interruptions over F-RTGs?

If somebody has any idea please let me know 

Best regards

AutoGen_4612448

Good morning,

I am having a nightmare with the following error related to communication between 2 F-Runtimes:

Temporary CPU error: User programmed STOP request in FB 2008
affecting OB 123 execution

Internal address details: Caddr=16#00002186

Error: Safety program:DatacorruptionpriortosendingtopartnerF-CPU/other F-runtime group
F-runtime group   1
Detected by: Sender UUID beginning with 16#77E4
Offset of faulty byte:  4

Checking FB2008 it is a protected compiler block named "F_PS_COMM_DEVICE" with the following description inside:

F_: Protocol Driver Block Send PROFIsafe V2 + Protocolextension up to 100 Bytes

Checking this link https://support.industry.siemens.com/cs/ec/en/view/19183712 gives some info about how to find the origin, in my case just shows and offset of faulty byte but not the starting address.

Does anybody have an idea how to find the problem?  Any help would be great.

Thanks you all in advance