Posts by MDFB

Thanks for your answer.

I need the axis rotating in only one direction because we need too much precision in the position of the axis, I explain it better:

We are working with Mx Automation (an interface to program the robot on a PLC), so in order to improve the precision on the axis position we have installed an encoder with an inductive sensor to count each flank when the axis is on the 'cero' position. When we rotate in one direction the flanks are precise but if we change the direction (the operator in manual or the automatic program in any movement) the flank will be executed in the other side of the inductive sensor, introducing an error in the position.

Thanks Fubini,

But changing the sign of the gear ratio RAT_MOT_AX it seems I will only change the direction of rotation (positive becomes negative and vice versa). Isn´t it?

I need the axis moves only in one direction (positive or negative but always the same direction of rotation). I need that with the robot working in AUT and also in T1 (disabling one of the movements (+/-) buttons if possible or similar).

Hi everyone,

I'm working with a KRC 4 (8.5.8) controller and an external axis Kuka External Kinematics 400V (MGU6800-235_KSP64) configured as an endless rotation axis.

I would know if there is a possibility to limit the rotation direction: I need the axis rotates clockwise all the time and not on the contrary.

I would appreciate knowing if anyone has tried it before or knows if it is possible.

Thanks in advance!

Hi there,

I'm having problems with some IRC5-RW6.08.01 Robots: only 2 robots from more than 10 identical robots connected to the same network, entered in a system failure state, APPARENTLY after a network loop (PROFINET) --> The robots restarted by themselves and a gap in the event log and the only error '20195: System data from las shutdown is lost' appeared.

Someone knows why only 2 of more than 10 robots are having this problem? We had the same problem months ago, and not in all robots, after changing network configuration (all device IPs in the network to change management parameters in a switch...). Why the robot restarts by itself when (supposedly) detecting a network loop/changes in switches?

The only difference, is that in robots with that problem, we don't have a Local_IO (EtherNet/IP Device) defined, while in robots that didn't have the system failure, we have it (DSQC1030 with IP 192.168.125.100). We don't know if this parameter could be the reason for the differences.

Someone knows what can we do to avoid this? If there are any changes we can make on the robot's configuration to protect it, I 'd like to know about it!

Thanks in advance!

Thanks! we hope no more network loops happens but it doesn´t depend on us... So, if there are any changes we can make on the robot's configuration to protect it, we 'd like to to know about it!

Hi there,

I have some problems related, i think, with yours: only two IRC5 - RW 6.08.01 from more than ten identical robots connected to the same network, entered in a system failure state, aparently after a network loop (PROFINET). The robots restarted by themselves and a gap in the event log and the only error '20195: System data from las shutdown is lost' appeared.

Someone knows why only two of more than ten robots are having this problem? We had the same problem months ago, and not in all robots, after changing network configuration (all device IPs in the network to change management parameters in a switch...).

The only difference, is that in robots with that problem, we don't have a Local_IO (EtherNet/IP Device) defined, while in robots that didn't have the system failure, we have it (DSQC1030 with IP 192.168.125.100 ).

We don't know if this parameter could be the reason for the differences. Also, we don't know why the robot restarts by itself when detecting a network loop/changes in switches.

 Someone knows what can we do to avoid this? 

Thanks in advance!