5/16/2019 10:07 PM | |
Posts: 1 Rating: (0) |
Hello, I am also experiencing a similar problem.... I have an assembly line with several Lumberg 0980 ESL 801 16 DI Profinet I/O Modules among many other Profinet devices. I find when I Open Siemens Starter Application and choose the Accessible Nodes function to "Scan the Profinet Network" to locate a Siemens Drive which i do not have a project file for, eventually the Lumberg I/O modules will stop sending updated I/O Status information to the PLC until power is cycled to the I/O Block, the Status LED's on these Lumberg blocks look normal, no red lights and no Profinet errors in my project. The situation does not cause any fault (the node is still view-able on the network, just no updated i/o data is transmitting any longer) on the machine and i can start the machine in auto cycle and the machine will run until it expected the Inputs from the Lumberg block to change when they don't! I fear this situation could cause our machines to crash and damaged extremely expensive equipment/robots! I have also setup in our offline Lab one of these Lumberg I/O blocks along with a Murr and Siemens I/O block on the same Profinet network/PLC. When i run the accessible nodes function the Lumberg block eventually stops sending the i/o information yet the two i/o blocks from the other manufactures continue working just fine until the end of the accessible nodes searching process (which could take who knows how long depending on the size of your network) and at that point all three of the tested I/O modules will do a reset that last about 10 seconds and the Red BF LED lights up during this reset. Again the process is... (as examined in my offline test lab) 1 Open Starter 2 Choose Accessible Nodes Function 3 Two Dialog boxes appear, one is an un-populated list box in the background the other in the foreground is titled "Find Accessible Nodes" and includes a moving progress bar. 4 "Find Accessible Nodes" dialog disappears and the list box in the background dialog is populated with all the nodes that were found, Simultaneously a new dialog with moving progress bar appears in the foreground titled "Accessible nodes" with a description stating "Contact found nodes via access point .......", there is also a cancel button on this dialog. You cannot do anything but press the cancel button until this "Contacting Nodes Function" Completes! 5 While the "Contacting Nodes Function" is doing whatever it does (i'm assuming its contacting all available IP addresses in the sub net) at some point (i assume when it contacts the IP address of the Lumberg I/O block) the Lumberg I/O status data in the PLC will freeze and stop getting updated and hold whatever value was there at the time of the freeze up. At the same time the status LED's on the Lumberg I/O block (Link/Act, BF, DIA, ect.) all function normal blinking or steady green and if the inputs are turned on or off the corresponding LED indicator for the input on the Lumberg I/O Block itself functions on or off as normal, however that changing I/O status is never sent to the PLC, the PLC has no idea the I/O is changing on the Lumberg Block and there are no Profinet Faults occurring. 6A If the "Contacting Nodes Function" is abruptly stopped (ex unplug Profinet from laptop, or force close starter application before function completes) then the Lumberg I/O blocks will stay in the frozen state with good status LED indicators until the power is disconnected from the block and reapplied. The other two I/O blocks from other vendors appear not to be affected. 6B If the "Contacting Nodes Function" is allowed to complete (takes 10 minutes on my test lab setup with 6 or so total Profinet nodes, could not afford the time to allow it to finish on my assembly line with maybe 100 nodes in the sub net) on its own then shortly before it completes and the progress bar dialog disappears at this point all three Profinet I/O modules I have on my small test lab equipment will flash the red BF LED for about 10 seconds and i assume it is doing a reset process. If i allow this to occur then the Lumberg I/O block also appears to reset itself and when it comes back up it will function fine. It seems quiet scary that simply allowing the Starter software to do an accessible nodes search on a Profinet network also has the side effect of disrupting the communication on all other Profinet devices in the same sub net and even causing some vendors hardware to fail in a state that indicates no failure present! I shall advise anyone using the Starter Application to not allow the Accessible nodes function to be ran on any equipment, or any Profinet Network that might have other equipment connected to it that is in an operating state!!!! Product: Drive ES - Starter Release: V4.4.0.0 P.S. I also have some Atlas Copco Power Focus Units on my assembly line and they faulted with a Profinet Communication Error seemingly as described in step 5 above. Atlas Copco did trigger a Profinet error while the Lumberg blocks just stopped sending their I/O status data and never triggered a Profinet error. Please Help! ------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 05/17/2019 11:40:07New subject after splitting |
|
Follow us on