RMA
Member
In the course of trying to find out what was wrong with the 4MB MMC for my 317-2 DP CPU (see separate thread), I was repeatedly uploading different projects from different MMC cards to the CPU to see what happened. Somewhere along the line I noticed that I was occasionally getting the CPU into an SF fault condition. Having got the MMC problem out of the way I decided to have a closer look at what exactly was causing the fault.
Having created a completely new project in order to test my FM352-5s, as opposed to the chopped back version of my main project which I had previously been using, I was pretty sure I had a clean piece of S/W with no rubbish lying around in some hidden corner. (I suspect I might be coming back to this in another thread, but that's another story!). I uploaded the project from the Simatic manager by highlighting the "Station" directory and clicking the upload icon. I then powered off and on and everthing came up and ran cleanly.
I then repeated this with the CPU still running and got my error immediately. I then repeated this in several variations - first with the CPU in STOP, then with the CPU in STOP and the memory completely cleared (What's "Urlöschen" called in Engllish, Jesper?). It didn't matter what I did, only when I powered off and on again did I get rid of my fault.
I then tried it by highlighting the "Baustein" (Blocks?) directory and copying only the blocks without the System information - that worked OK. Repeating the action and this time, when asked, saying "Yes", also copy the System Info and now I've got my fault back again. The contents of the diagnostic buffer I've hung on the end of this post.
So the questions are:
1) What exactly am I doing when I upload from station
2) What are the contents of the system information folder - I've been assuming that when moving between my real project with its 20-odd DP stations and my test projects with no I/O, I need to update the System Information so as to avoid faults due to missing H/W. Is this correct?
3) When do I have to cycle the power after changing something.
This problem caught my eye because in my test project, I have no OB100 and no I/O (other than that contained in the FM352-5, of course). I had seen these contents in the diagnostic buffer a few times with my real project and I hate to think how many hours I've wasted trying to track down where I was addressing something wrongly in my OB100!
Final question, is this a normal set of fault messages, or is it another 317-2 DP funny?
Having created a completely new project in order to test my FM352-5s, as opposed to the chopped back version of my main project which I had previously been using, I was pretty sure I had a clean piece of S/W with no rubbish lying around in some hidden corner. (I suspect I might be coming back to this in another thread, but that's another story!). I uploaded the project from the Simatic manager by highlighting the "Station" directory and clicking the upload icon. I then powered off and on and everthing came up and ran cleanly.
I then repeated this with the CPU still running and got my error immediately. I then repeated this in several variations - first with the CPU in STOP, then with the CPU in STOP and the memory completely cleared (What's "Urlöschen" called in Engllish, Jesper?). It didn't matter what I did, only when I powered off and on again did I get rid of my fault.
I then tried it by highlighting the "Baustein" (Blocks?) directory and copying only the blocks without the System information - that worked OK. Repeating the action and this time, when asked, saying "Yes", also copy the System Info and now I've got my fault back again. The contents of the diagnostic buffer I've hung on the end of this post.
So the questions are:
1) What exactly am I doing when I upload from station
2) What are the contents of the system information folder - I've been assuming that when moving between my real project with its 20-odd DP stations and my test projects with no I/O, I need to update the System Information so as to avoid faults due to missing H/W. Is this correct?
3) When do I have to cycle the power after changing something.
This problem caught my eye because in my test project, I have no OB100 and no I/O (other than that contained in the FM352-5, of course). I had seen these contents in the diagnostic buffer a few times with my real project and I hate to think how many hours I've wasted trying to track down where I was addressing something wrongly in my OB100!
Final question, is this a normal set of fault messages, or is it another 317-2 DP funny?
Last edited: