SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Scalance PNIO IO alarm remains after CPU restart

Created by: JohanBarten at: 6/26/2014 11:37 AM (4 Replies)

Rating (0)

Thanks 1

5 Entries

6/26/2014 11:37 AM	Rate (0)
JohanBarten Posts: 3 Rating: (0)	Hi all, I am using the following configuration: - Redundant CPU 416-5H - 13 Scalance X212-2 switches in a ring configuration. Using HW config all switches are configured and are all in a ProfiNet sync/MRP domain. Also a network topology is created and is currenty up to date. When the whole setup is running, the switches receive their configuration from the PLC. (checking the event log in the switches show that the switches are receiving a configuration via Profinet). But a problem arises when the PLC loses power. (powerloss / manually switching off). When the PLC is powered off, on all switches the "F" LED is lit and Fault status is: "PNIO IO Alarm". This behaviour is understandable because of the loss of their "Profinet Master". When the PLC is powered up and fully restarted, the switches keep their fault state. It appears the switches do not receive a configuration via Profinet or detect the return of their Profinet Master after the PLC is complety restarted after powerloss. Only when switching off the two switches connected to the CPU 416-5H the fault state of all 13 switches is reset and returns to normal. Also disconnecting the network cables between the two switches and the CPU 416-5H, resets the fault state of all 13 switches in the network. It seems only by forcing a topology change the switches and CPU 416-5H reconnect, and the PNIO status is reset on all switches. Is there any solution to reset the fault state of all switches after the PLC is restarted? or force the reconfiguration of all switches after a restart?
JohanBarten Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

6/27/2014 1:00 PM	Rate (0)
Pittiplatsch Posts: 1368 Rating: (128)	Hello, which Switch is MRP-Manager? Is the H-CPU a part of the ring or connected via a switch to the ring? Do you consider the watch dog time in MRP ring? http://support.automation.siemens.com/WW/view/de/46636225
Pittiplatsch Posts: 1368 Rating: (128)
Suggestion To thank Quote Answer

6/27/2014 3:33 PM	Rate (0)
JohanBarten Posts: 3 Rating: (0)	The H-PLC is not a node in the ring and is connected using two ethernet cables to the ring. One switch is RM master and is the "furthest" away from the PLC (of the 13 switches the PLC is connected to switch 1 and 2, making switch 6 RM). The weird thing is all remote IO racks and drives work fine. only the switches keep the Profinet IO alarm. Thanks for the link, i will give it a shot
JohanBarten Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

7/2/2014 5:07 PM	Rate (0)
JohanBarten Posts: 3 Rating: (0)	Found the problem... It was a double IP adres, the same adres as the configured PNIO port of the H-PLC.
JohanBarten Posts: 3 Rating: (0)	Last edited by: JohanBarten at: 7/2/2014 5:07 PM
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Fafner

7/2/2014 5:32 PM	Rate (0)
Fafner Silver Member Joined: 3/20/2013 Last visit: 3/18/2025 Posts: 676 Rating: (44)	thanks for the answer!
	Best Regards, Fafner
Suggestion To thank Quote Answer

Share this page:

Share this page on...

SiePortal

Scalance PNIO IO alarm remains after CPU restart

Created by: JohanBarten at: 6/26/2014 11:37 AM (4 Replies)

Rating (0) Thanks 1

5 Entries

JohanBarten

Pittiplatsch

JohanBarten

JohanBarten

Last edited by: JohanBarten at: 7/2/2014 5:07 PM

This contribution was helpful to

Fafner

5 Entries

Follow us on

Rating (0)

Thanks 1