Hi All,

I am experiencieng this, not very ofter, but at least it has happened two times in the las 48 hrs.

This PLC goes to stop, after some fault ocurring in the OB123 (main safeties program)

The following description can be found in the online and diagnistics status.

89 of 3200; Event ID: 16# 0D:75D6
Error: Safety program: Data corruption prior to sending to F-I/O
F-runtime group   1
Start address of the F-I/O:        230
Offset of the output:   0
JNAP / JNAP.

.

.

.

Any Idea of how to solve this?

LuisBeta17

 Yes, I've tried to look for that but it doesnt show a lot of infotmation

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

JNAP / JNAP


Internal address details: Caddr=16#00001E01

As this is an autogenerated safety block, I cant really see anything helpful in the Open editor option...

huggy_d1

What is going on in FB 32770? 

Some value out of range is being assigned, division by 0 (without verifying it is not about to div by 0 before doing it).

It says to open TIA Portal and search for the Event ID.

If I were you, I would be keenly interested in diagnostics buffer entry # 90 to see what FB 32770 had to say in the Details / Description and Help below.

LuisBeta17

Hi All,

I am experiencieng this, not very ofter, but at least it has happened two times in the las 48 hrs.

This PLC goes to stop, after some fault ocurring in the OB123 (main safeties program)

The following description can be found in the online and diagnistics status.

89 of 3200; Event ID: 16# 0D:75D6
Error: Safety program: Data corruption prior to sending to F-I/O
F-runtime group   1
Start address of the F-I/O:        230
Offset of the output:   0
JNAP / JNAP.

.

.

.

Any Idea of how to solve this?

LuisBeta17

 

It is probably the first of possibilities from link above.

- either you are using some tags directly from HMI in safety program, or even a problem with system clock bits, as Huggy says.

I have had similar case, when I wrote my first F program... and the failure was, that I have connected some bits (for ACK!) directly with HMI tag....

Have fun!

Uel123.

Quote from link:

Possible causes

This can happen in the following cases:

• The standard user program or an external device (HMI, for example) writes data that is read in the safety program while the safety program is being processed, for example:

  • Write access to standard data through higher-priority interrupts

  • Write access to standard data through HMI/communication

  • Use of clock markers

  • Update of a partial PII through higher-priority interrupts

Thank you all for you support,

I was overwritting in the safety outputs.

Hi All,

Have been getting similar issues but on a ProfiSafe front, I think:

Had this second time in a short time interval, using a SunaTIg902control with the address 27, how can one investigate it without access to the "LDrvSafe_SinaTlg902Control" ?

Cheers