5/31/2010 10:50 PM | |
Joined: 9/27/2006 Last visit: 9/10/2024 Posts: 12282 Rating:
|
Well since you ask so nice, let's see if we can help a bit.
If OB82 does not appear in your blocks list, and if it has not been downloaded to the CPU, then when a diagnostic error appears the PLC will go into STOP mode. At that point the diagnostic buffer will contain a mention of "going to STOP" and request OB82. Not very informative. If you create a New Block, name it OB82, and download it to the CPU (without a single line of code), then the next time the diagnostic interrupt happens, the SF LED will light but the PLC will continue in RUN mode. The diagnostic buffer (using the OB82 parameter interface) will be able to get a lot more information on the location and the cause of the error, so you can read it there.
As an example, if you program this code inside OB82: L #OB82_EV_CLASS T MB25 L #OB82_COMM_FAULT T MB26 MB26 will contain a value of 0 (no comm fault)or 1 (comm fault)once OB82 has executed, which can be verified by looking at the value contained in MB25: Hex 38 means a new starting event; Hex39 means an ending event. To see the available list of parameters for the OB82 interface, look in the System and Standard Function manual (http://support.automation.siemens.com/WW/view/en/1214574)
Well you can call SFC51 to trigger more diagnostic data naywhere in your program, inside a diagnostic OB82 also. But that is a bit more complicated. I suggest you start by studying the suggestions above first. But if you want to look further now, many threads have dealt with SFC51, look them up through the Search box at the top of this page. Hope this helps, Daniel Chartier |
This contribution was helpful to
6 thankful Users |
6/1/2010 7:41 PM | |
Posts: 35 Rating:
|
here it is what you have demanded |
6/2/2010 6:36 PM | |
Posts: 35 Rating:
|
I HAVE TRIED YOUR FIRST SUGGESTION IT IS ALWAYS RED. I HAVE CHANGED tempw in db1.dbd1258 look the picture joint. |
Follow us on