5/10/2017 10:37 AM | |
Joined: 10/31/2005 Last visit: 8/6/2024 Posts: 366 Rating:
|
Hello guys, I'm having a problem with one FM458 module that is part of S7 414H redundant system with two AddFem modules connected with Profibus DP. So total configuration is 100% fully redundant. Two days ago I have noticed that one FM458 is in stop mode and I have just performed warm restart. It started the module and everything was fully functional. The plant was in scheduled standstill, so there was no risk at all. Next morning the fault was present again. IN the attachment you can find the diagnostic file. I need your help in determining the cause for this fault. Is it failing HW or somewhere in the field. Since all measurements are present in the system I doubt that error is caused by some faulty connection or equipment in the field. Right now the plant is running so I'm not sure whether there is a risk for performing new Warm restart of the stopped module. Can you please inspect the attached file and give me your opinion regarding the nature of the fault? The whole plant is now runing on A configuration while module FM458 B is currently in STOP mode. I don't think that there is a risk for performing the new warm restart but would like to read you recommendation. Thank you AttachmentDiagnose.txt (824 Downloads) |
Last edited by: Pandiani at: 5/10/2017 10:38:01 AM |
|
5/16/2017 7:01 PM | |
Joined: 10/31/2005 Last visit: 8/6/2024 Posts: 366 Rating:
|
Hello, I have performed Warm restart and solved the problem but only for a while. Today it happened again. I would like to understand what exactly is causing this. Is it failing hardware (FM458) or AddFem module on Profibus address 1022 or maybe communication DP cable. If anyone has any advice I would highly appreciate it. What I can conclude from the diagnostic file it seems that FM458 (which is standby) first loses its connection to AddFem module and that triggers the STOP mode on FM module. After few moments the communication is back again, but FM458 cannot restart by itself. Judging from the diagnostic file the very few events are: Event 41 of 100: Event ID 16# 430E So it seems like FM458 is causing this problem. Please have a look at the attached files. Thanks in advance. AttachmentDiagnose2.txt (772 Downloads) |
Follow us on