Use the OB35 with 100ms

Hi,

Got same trouble here,

already localize the block into separate OB, but the time still exceeded 

seem u right, there is problem in the block,

do u have experience what causing this? um, also delete AFP block which is generate clock, but still ob35 exceed monitoring scan time 

can consistency check locate the block problem?

------------------------------------------------------------------------------------------
Split from OB80 interrupt.

Hi Utalika,

I know two reason why you get timing error OB (OB80).

The first one is that you have to much blocks in your cyclic OB. This depends on the CPU type (a CPU 414 is slower then a CPU 416 and the CPU 416 is slower then a CPU 410), number of blocks in the cyclic OB and the time, that the CPU needs to processed the block.

The second reason is that you have a timing problem in your own block. And every time I had this problem there was an unsolved while loop. If you have a unsolved while loop the block is processed the hole time and after the next cycle interrupt you get the error, because your block has not been processed in this moment.

And if your problem with the timing error is switching if you change the cyclic OB of your block, then it is definitely your block the reason why you get the timing error.

With regards
Heisenberg

Heisenberg,

Thanks for the response and knowledge.

In my experience, my OB35 triggered OB80 was by using OB10 time_of_day in PCS7 with AFP block for clock generator.

• After deactivate the OB10, replace it with SFC1 for TOD function
• Delete AFP, replace by clock of CPU memory  option

 the cyclic of OB35 back to normal, CPU never call OB80 again.

fyi, also using CPU410H.

out of topic, I was looking the solution of this issue because of I thought the reason of "sampletime" error in PCS7 cause by this issue