Industry Online Support
Technical Forum
1/14/2010 4:19 PM | |
Joined: 9/27/2006 Last visit: 5/30/2023 Posts: 12025 Rating:
|
Hello mhkocak; When you configure a slave's module addresses over Profibus-DP, you are placing these addresses on a cyclic request from the DP-master, which proceeds independantly of the main CPU scan. Since there is no reply from the disconnected slave, the slave's diagnostics are being requested by the master, and the module addresses show I/O access errors because you must not use the present values (either the last one accessed, or zero) to make decisions in your program. The way to say to the CPU (actually, the DP-master interface)do notpoll this node anymore until I tell you to is to use SFC12, as shown in the following FAQ (see the downloadable project included): http://support.automation.siemens.com/WW/view/en/15014658 Hope this helps, Daniel Chartier |
1/22/2010 10:23 AM | |
Joined: 7/2/2008 Last visit: 3/14/2023 Posts: 928 Rating:
|
Hello mhkocak, The I/O access error is a synchronous error. There's SFC36 "MSK_FLT" for masking synchronous errors which means that the CPU will not trigger OB122 or OB121in a certain priority class. You can filter which error to be masked and which to be not. For unmasking errors you will have to use SFC37 "DMSK_FLT". You didn't mentionwhether you have S7-300 or S7-400 but be careful and read the help of SFC36 (If you are going to use it)carefullybecausethe behavior of S7-300 differs to behavior of S7400. You can try it as it's there but honestly I never used it and will never do. I always prefer that all errorsget registered in diagnostic buffer and always have the SF LED to remind the maintenance guys ''You have a problem - Solve it''. Best regards. H-H |
Follow us on