10/14/2013 8:45 AM | |
Posts: 1368 Rating: (126) |
Hello @Nick, hello bruce_ooi If OB86 has not been programmed, thePLC changes to the STOP mode when the failure of a station when using distributed I/O (PROFIBUS DP or PROFINET IO) is detected. If your program contains this operating block, the system error LEDgoes on. The rack failure OB contains some variables. To analyze the cause of the start of the OB, the followingvariables are important: OB86_EV_CLASS OB86_FLT_ID In this manual http://support.automation.siemens.com/WW/view/de/44240604/0/en in chapter 1.22 you find more informationen. @Nick: Do you only use LAN or also WLAN? Did you try to increase the "Update Time" and "Watchdog Time" of the PROFINET IO Devices? This parameter you find here: [PROFINET Interface of the PN Device] ==> Properties ==> I/O cycle tab. Perhaps this could solve your problem. Good luck, Pittiplatsch |
This contribution was helpful to1 thankful Users |
6/8/2015 10:13 AM | |
Joined: 9/3/2014 Last visit: 3/13/2019 Posts: 4766 Rating: (122) |
|
3/9/2017 2:59 PM | |
Posts: 531 Rating: (34) |
Does the issue occur when a switch is used instead off routing it through all stations? Maybe the travel time is a problem. |
4/13/2017 10:40 PM | |
Joined: 7/2/2007 Last visit: 10/7/2024 Posts: 12 Rating: (1) |
Hi, this sounds like a watchdog timeout if the device goes offline then back online again quickly. How fast are the IO's set to update in the configuration? Usually the watchdog timeout means the devices or controller did not get updated fast enough and the timeout is usually by default 3 times update time. So if update time is 1ms then watchdog is 3ms. I don't know why, but many manufacturers tools always put the devices at the fastest update time (or almost) by default. And usually with a Siemens device its 1ms. Typically, most applications don't need the data that fast anyway. Usually watchdog timeouts are caused by network load issues, cabling or interference issues or resource issues (speed of processing) As a test you can increase the update time in the configuration tool to see if this helps communications. Your diagram does not show where the devices are actually located. Check cabling, is it shielded PROFINET cable or unshielded twisted pair (UTP)? Are there other devices or voltages nearby.? Make sure you have cable separation from higher voltage signals, otherwise you can get interference and frames are corrupted. Especially check if you have any drives or motors near the cabling. Also check the PROFINET installation guidelines to determine if you have grounded the system cabling properly. grounding issues can also cause voltage on the shield connection causing interference. Is this system isolated or also connected to the office / plant network(s)? You mention more than one system is affected, are they interconnected? If connected have you checked the network load? It should not be above 50% at any time to guarantee frames would not get dropped. You can measure load with a SNMP tool (PRTG or similar) connected to the PLCs (bandwidth utilization) at critical points. See the PROFINET design guideline for more information (link above). Also it should be noted you cannot have more than 7 devices in series if your update time is 1ms with PROFINET RT. Have you checked that you have the latest firmware in CPU and devices? You can use the Simatic Automation Tool to update and check this:Simatic Automation Tool |
This contribution was helpful to1 thankful Users |
Follow us on