Dear Expert,

Please find the attached image this fault is happening every ten seconds while simulation.

While compiling there is no error.

Kindly clarify the same.

Regards,
Gowtham.S

Hi GUWS,

Did you've enought cycle time for all your program?¿

Lets start with the colours. Bright green means that block is the Predecessor for Installation block. Any block you insert into the chart will have a higher number that the Predecessor for Installation block. 

Next, all the blocks with the dull green, as you call it, are not the Predecessor for Installation. So the bright green colour does not mean the PLC is in RUN mode, or anything like that.

As for the RED connection status you see, that means something is wrong with the monitoring. When all are red, then it usually mean the PLC is in STOP mode. 

I would go look at the Diagnostic Buffer"" of the PLC. Maybe that will indicate what is going wrong.

GUWS

In this picture I can see that you renamed an OB, possibly OB38, to Cyclic_10. Also the PfI block is in Runtime Group 60, and the block is in position 2. The block before it is in Runtime Group 6, and in position 138. So it is safe to assume you have at least 60 Runtime Groups in OB38.

OB38, if I am correct (Basing my assumption on the _10 (10ms) in the name), is a very fast Cyclic OB. Is this code for a high speed bottling plant or something? Why OB38?

If it is in fact OB38, then your PC might be missing a few PLC scans or something. Again, go loog at the Diagnostic Buffer.

Again, still assuming that Cyclic)10 is OB38, it also has a higher scan priority than any other cyclic OB. If its scan is not complete, it will interrupt the next highest priority cyclic OB to complete, and so forth. Eventually one of the lowest cyclic OBs might never complete a scan, and then you could end up with a PLC STOP.

This could be sortof avoided by increasing the Scan Cycle Monitoring Time [ms] from 6000 to 12000 on the PLC. That will give the CPU 24 seconds to complete all scans before going into STOP mode. But this is only prolonging the inevitable.

With the time set to 6000, you get that times 2 two before the PLC stops, which is close to your 10 seconds you mentioned.

Thanks Mr.Martin

Actually it was cyclic OB 100ms only, in image it showing like 10  ms