Hi. Yes, since it's a slow process, we increase the RPI time from 10 ms to 100 ms (Maximum). Also I noticed (using ping to all over the system) that it was normal (one time each 30 min) to have a response time of 35-45 ms between the systems, and with the RPI was default (10ms) and the timeout was default (4x RPI), it was easy to the system get this flag you lost communication. Thanks for the help.
Hi, There is already more than 3 weeks that I found this error and still not solved. I fear for the possibility of a system crash during the full production of the machine. Can someone give the an information or a way to debug this failure? Thanks.
I made the update of the EIP and all other packages that it's giving attentions flags to update. Even with this update, the error still there and the runtime reboot one time in the last days. Error in attachment.!
Hi, We are having a regular error "Error: "IODrvEthernetIP: Connection failure. (16#1)" "Extended Status: Target connection not found. (16#107)"" and last night the PLC crashed and this is the only error displayed in the log. We have 6 identical Cube67+ BN-E V2 (Murrelektronik Gmbh) connect in 1 scanner. The IOTask and ServiceTask still on factory default configuration (cyclic with 10ms and 20ms) How can we solve this error and is it this error possible to crash the system? (It was necessary to restart...
Hi, We are having a regular error "Error: "IODrvEthernetIP: Connection failure. (16#1)" "Extended Status: Target connection not found. (16#107)"" and last night the PLC crashed and this is the only error displayed in the log. We have 6 identical Cube67+ BN-E V2 (Murrelektronik Gmbh) connect in 1 scanner. The IOTask and ServiceTask still on factory default configuration (cyclic with 10ms and 20ms) How can we solve this error and is it this error possible to crash the system? (It was necessary to restart...