November-2nd-2020, 04:01 PM
(November-2nd-2020, 02:39 PM)Armin@netPI Wrote: Hello again,
one question related to the "profinet controller to stop" issue. I have seen several Siemens S7 PLCs of type 1500 or 1200 in my live but non of these are stopping the PROFINET network just because one single PROFINET device like netPI has a problem. They just switch on a red status LED and continue to communicate to the rest of the PROFINET network while trying to get a communication running again to the missing device.
So has someone configured the PLC to go into forced stop mode in case one device is missing?
What do you or the end customer have exactly to do to get the system running again. Restart of netPI or just a container restart? Or a reset on PLC side?
Is it always the same device that is showing the problem?
The Industrial Network Controller netX51 PROFINET device firmware is of version V3.12.0.2 from year 2017. Of course we have newer versions of software for this controller available, but before we change anything in the software we should focus more on the hardware first. When the problem occurs is there a special activity on PROFINET side active that is activated maybe the same time? Or it is a 24/7 machine that is not observed and no human is onsite?
Thank you for your quick response!
Please see answers below:
Yes, it might be possible to configure the PLC that it does not go into forced stop. I would then have the netPi beeing able to recoved itself.
Up to now the customer restarted only the netPI to recover from the Profinet failure (no need to reset the PLC).
Yes, it is so far only the same device.
The error occured while machining (no human intervention nor profinet activation/configuration)