Does anyone have a reference manual for what the error codes mean in the Kuka Log Files?
Messages like M_68, or M_12016, M_3186 aren't the most descriptive when trying to troubleshoot problems.
Does anyone have a reference manual for what the error codes mean in the Kuka Log Files?
Messages like M_68, or M_12016, M_3186 aren't the most descriptive when trying to troubleshoot problems.
Is there any other network traffic? Are they connected to the facilities ethernet?
I've seen one instance where having the robots on the plant network would cause the controller to sporadically drop ethernet connection with the PLC. Disconnecting from the office network solved the problem. My theory at the time was that there was some packet filtering or high network traffic that was causing the ethernetIP to timeout. I didn't really put too much further thought into it after disconnecting it from their office network.
-Tyler
Can you just assign 32 bits for your variable? KRL assumes that any signal is a 32 bit signed integer, but if you have less than 32 bits assigned to that signal, the front of the integer, including the sign bit gets truncated. If you only have positive numbers, it works perfectly fine, but as soon as you try to send a negative number, you will just get garbage values.
If you assign 32 bits at your plc, and KRL signal, you should get the correct data transfer for both positive and negative numbers.
-Tyler