Hello ronald_marcos;

As Hati has pointed out, the cause(s) of the faults will be included in your diagnostic buffer.

Sometimes understanding the information on the buffer can be tough. If you need help understanding the buffer messages, use the "Save As" button in the diagnostic buffer page. This creates a diagnose.txt file containing all the buffer message information, if you post it here as an attachment we could probably help you decipher it.

Hope this helps,

Daniel Chartier

Hello ronald_marcos;

If you are not suppllying power to your modules, then you will have diagnoistic faults in your buffer and diagnostic LEDs active on your CPU.

Normally, I would expect OB122 and OB 121 calls in your diagnostic buffer when your I/O connection happens over a network, Profibus or Profinet. Is this the case? Check the HWCVonfig to determine which m,oduyles occupy addresses 256. 268, 270, 272...

OB122 is linked to a BF fault (Bus fault) and appears when your CPU does not receive a reply from the I/O module (because, possibly, it is not powered up). OB121 appears when a SF is declared (System fault) because your program is trying to read or write data from a non-responding slave module. So the messages in your buffer would be linked that way. 

Power up your I/O modules and tell us if the diagnostic LEDs turn off.

As for your CP 343-1 LEAN (6GK7343-1CX00-0XE0 or 6GK7343-1CX10-0XE0), it should be compatible with your CPU. The messages in your diagnostic buffer would be very different if there was a problem there.

Note that your buffer can contain only 10 messages for the moment, you can increase its capacity if you open the CPU properties (in HWConfig, Memory tab i believe). More messages (you can set up to 500 messages depending on your CPU) would give a braoder view of the problems you are facing.

Hope this helps,

Daniel Chartier