Hi
I using kuka mfc2 x804 ethernet , but when windows hibrnated , after startup network is disbale ,after that i must cold booting to start network again, how can i solve this problem??
X804 mfc2
-
m.dinio -
March 8, 2025 at 5:04 PM -
Thread is Unresolved
-
I using kuka mfc2 x804 ethernet , but when windows hibrnated , after startup network is disbale ,after that i must cold booting to start network again, how can i solve this problem??
MFC2? What model controller? I assume KRC2, but pre-ed2005?
"Network is disabled" -- what does this mean? What tests have you performed?
-
Make cold boot persistent. There is a registry file in 'tools' directory somewhere under the krc directory on drive c:.
-
MFC2? What model controller? I assume KRC2, but pre-ed2005?
"Network is disabled" -- what does this mean? What tests have you performed?
Kuka krc2 before 2005.when i cold booting , i can ping it from another network,but after hibernate i can't.
I use RSI with x804 .
-
I use RSI with x804 .
That is not an approved usage. I assume you have it configured to use the KUKA.Router program for software routing in Windows? And this must be RSI-XML, as opposed to "vanilla" RSI.
Is RSI running when you hibernate the KRC? Is the RSI port open?
I assume you're trying to ping the actual NIC IP, rather than the specific RSI port? It is quite odd that the NIC would not recover after a Warm Start. Is it possible to ping or make connections outbound from the KRC?
-
RSI port is open when when i hibernate the KRC.
I have a hunch that might be part of the problem. I suggest experimenting with hibernating the KRC with the RSI port closed and see if that prevents the problem.
If that works, my first thought is to add an Interrupt or some SPS code that can detect an impending Hibernation and close the RSI port. I don't recall offhand if there's a system variable that trips when the KRC is performing a controlled shutdown, though. You might have to close the RSI on errors or on program halts, and include methods to re-open RSI on resume.
-
I have a hunch that might be part of the problem. I suggest experimenting with hibernating the KRC with the RSI port closed and see if that prevents the problem.
If that works, my first thought is to add an Interrupt or some SPS code that can detect an impending Hibernation and close the RSI port. I don't recall offhand if there's a system variable that trips when the KRC is performing a controlled shutdown, though. You might have to close the RSI on errors or on program halts, and include methods to re-open RSI on resume.
ok , i will do it ,thanks
Advertising from our partners
