Hi,

My suggestions:

1 - Check if your CPU has a up to date firmware.

2 - Make sure that the HMI or other controller doesn't write in standard variables used in safety programa (in doubt, as test propouse, changes the safety ob priority to 17).

In FB35025, can you handle errors within the block?  If so, try that.  Then you can store the error details, and also, decide whether it is appropriate to halt the process, or control stop it, or E-Stop it.  But stopping the program is usually not the right answer in my experience.

Look up handling errors within a block in the F1-Help within portal.   

Ben@Work

Hey all,

I'm experiencing a CPU error on my 1516F-3. Very sporadically the CPU went to stop (about 3 times in the last year or so).

This is in the diagnostics:

 

16 of 3200; Event ID: 16# 02:4010
CPU info: System initiated request: STOP
Pending startup inhibit(s):
- No startup inhibit set

CPU changes from RUN to STOP mode

PLC_Master

Incoming event
2/5/2017 5:08:41.143 AM


17 of 3200; Event ID: 16# 02:2505
Temporary CPU error: User programmed STOP request in FB 35025
affecting OB 30000 execution

PLC_Master_013002
Internal address details: Caddr=16#000000EE

Incoming event
2/5/2017 5:08:41.112 AM


18 of 3200; Event ID: 16# 0D:75D1
Error: Safety program: Internal CPU error
F-runtime group   1
Internal error information:   2:  0

PLC_Master / PLC_Master.CpuFExecUnit_1

Incoming event
2/5/2017 5:08:41.111 AM

FB 35025 is a safety generated block called: F_CTRL_2 from my understanding this processes the outputs of the safety program. So it's not like I programmed something in it.

I've been looking at the error 0:75D1 but no real answer has come from the help.

It's a check everything event help. I went over all the points but nothing stood out that could be the cause.

Anybody that can help or had similar problems? If so how did you fix it?
 

Thank you!

Ben

From the manual, maybe one of these F-Stop related topics help?

5.15 STOP mode in the event of F errors

In the following cases, the STOP mode is triggered for F-CPUs:



● In the "System blocks" folder you must not add, change or delete any blocks.

● There must not be any access to instance DBs of F-FBs which are not called in the safety program.

● The "Maximum cycle time of the F-runtime group" must not be exceeded. Select the maximal permitted time for "Maximum cycle time der F run-time group" which can elapse between two calls of this F runtime group (maximum 20000 ms).

● If tags are read from a DB for F runtime group communication whose runtime group is not processed (main safety block of the F runtime group is not called).

● Editing the start values in instance DBs of F-FBs is not permitted online and offline and can lead to STOP of the F-CPU.

● The main safety block must not contain any parameters since they cannot be supplied.

● Outputs of F-FCs must always be initialized.

What was in your diagnostics buffer?

Ben@Work

Huggy,

No this is not possible, as I said before this is a compiler block for the safety system.

This is read & write protected so there is nothing I can do with it.

It is called F_CTRL_2
Title: F_: Test Block and Programme Run Control

thank you.