Industry Online Support
Technical Forum
Navigation
Rating 
Thanks 1
4 Entries
| 9/10/2012 5:00 PM | |
Joined: 8/31/2005 Last visit: 8/20/2024 Posts: 2198 Rating:
|
Did you activate the diagnostics? (I don't know if it's required for SFC 13) see https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=41664412171&TopicId=32840846219 |
Last edited by: miami at: 9/10/2012 5:01 PM |
|
This contribution was helpful to
|
|
| 9/10/2012 5:15 PM | |
|
Posts: 26 Rating:
|
Hi Miami, Thanks for your response. The way i would normally do it is to use OB82 then look at the failed slave that has called OB82 using SFC13. Similar to this example https://support.automation.siemens.com/WW/llisapi.dll?query=sfc13+and+et200s&func=cslib.cssearch&content=adsearch%2Fadsearch.aspx%3Ftab%3D2&lang=en&siteid=csius&objaction=cssearch&searchinprim=_searchinprim_&nodeid=99&x=16&y=8&cssearchengine=NEW The drive is on profibus and i dont have the options you sugest. Regards Jon |
| 9/10/2012 6:33 PM | |
|
Joined: 8/31/2005 Last visit: 8/20/2024 Posts: 2198 Rating:
|
Hello Jon your link shows me search results from the forum, so I don't know which example you mean. I found this FAQ: http://support.automation.siemens.com/WW/view/en/2190197 Generally I check the fault bit in the status word. And if it's set you can read out the parameters of the fault memory. Or you use the telegram 352, this gives you allways the actual fault (and other valies) look here: http://support.automation.siemens.com/WW/view/en/60733299 Look for G120 examples on this page too, in the G120C islike aG120 with CU240E-2. And I don't know, if the G120C-DP gives any diagnostic informations. |
|
|
|
Follow us on