Hi Sir,

I have the same problem here but only "SYSTEM FAULT" and no "BUS FAULT" alarm recorded, I perform diagnostic buffer and the results is in the attachment. But the problem is "DB162 address" can't find in the program and also in our back up program. Can somebody help me what to do to solve the problem? Thanks 

------------------------------------------------------------------------------------------
Split from SF fault in S7-300 PLC.

Hello PaulEM,

please don't post twice for the same problem.

You have also made a own topic for your problem:

S7-300 "SYSTEM FAULT"

ixo65

Hello PaulEM,

please don't post twice for the same problem.

You have also made a own topic for your problem:

S7-300 "SYSTEM FAULT"

 My apologies. Sorry. I will delete the other one. Thanks

 Hello,

PaulEm

Hi Sir,

I have the same problem here but only "SYSTEM FAULT" and no "BUS FAULT" alarm recorded, I perform diagnostic buffer and the results is in the attachment. But the problem is "DB162 address" can't find in the program and also in our back up program. Can somebody help me what to do to solve the problem? Thanks 

 generally if some BF fault is presented, we can expect some specific network error (Profibus DP,...) or cfg error for modules depended to that network. Logically if some Slave device isn't accessible, also address for data access isn't also accessible so that message can point to this. For first check pls network with Slaves devices, cables if this network is existed actually. If network is ok, also Slaves addresses are accessible also.

Duris_I

 Hello,

PaulEm

Hi Sir,

I have the same problem here but only "SYSTEM FAULT" and no "BUS FAULT" alarm recorded, I perform diagnostic buffer and the results is in the attachment. But the problem is "DB162 address" can't find in the program and also in our back up program. Can somebody help me what to do to solve the problem? Thanks 

 generally if some BF fault is presented, we can expect some specific network error (Profibus DP,...) or cfg error for modules depended to that network. Logically if some Slave device isn't accessible, also address for data access isn't also accessible so that message can point to this. For first check pls network with Slaves devices, cables if this network is existed actually. If network is ok, also Slaves addresses are accessible also.

 Thank you for your response. I will check all network with slaves devices then I will give an update to this. 

Hello,

for next time pls do screenshots on PC (PrtScr key) and save them as JPG, use some Paint or picture manager, then ZIP them and attach zip file here. From your screenshot is hard to read informations.

Duris_I

Hello,

for next time pls do screenshots on PC (PrtScr key) and save them as JPG, use some Paint or picture manager, then ZIP them and attach zip file here. From your screenshot is hard to read informations.

 Hi,

Okay I got it. Thank you for the advice.

Unfortunately, we are done in checking of all network slave connections and all are working. But still the problem is in there. Is there a high probability that we experienced corrupted files? 

Another information is that, the version of software we used is Simatic v5.5 sp3 and the back up program they used before was v5.4 sp8. Is it okay?

We also noticed today after performing diagnostic buffer again, the pointed address to look for was changed from DB164 to DB162. And same scenario, there is no DB available in our back up program.

I hope you understand my information. 

Thank you.

Hi All,

Thank you for the support. The problem was solved by downloading again the program to the PLC. We miss some data to load to the PLC. 

Best regards,

PaulEM