Posts by reneklaris
-
-
You could try to change your IOSYS file from
DEVNET=2,dnInit,dndrv.o
to
DEVNET=2,dnInit,dn2drv.oI have seen with a kss reinstall that the default is DEVNET=2,dnInit,dndrv.o but that configuration not always work with some I/O modules.
-
Here is just a little update, the robot is up and running again it was necessary to replace the MFC card as we talked about. Luckily that was the only thing to replace except for some terminating resistors. But as mentioned I did not find any cause for this to happened, I measured a lot yesterday and did not find any short circuits even when the robot was running.
So it’s hard to draw any conclusions from this, I do not know if the MFC card itself could cause a short circuit to 24VDC at the Can lines?
-
Thank you for the answers. I have yesterday ordered a new MFC card, I will check the resistance once more tomorrow. I sounds like the exactly same like Skyefire has experienced, since all of the other functions work but not the Devicenet communication.
Could this have happened in the past of the robot and then first later on show up like a problem? It should be said it’s an old robot installed in a new location.
-
Hello all in this great forum
I have a serious problem with a kuka robot, it has on the robot tool 3 Beckhoff IO modules connected with the KRC 2 controller via. Devicenet on the MFC card. I did commissioned the cell last week when everything worked fine, however on Tuesday the customer call me and says it has a devicenet problem.
I did some faulty finding thinking it was a lost connection somewhere but everything looks fine, have even measured all the wires/cables from the cabinet to the tool and no broken wires. I did notice the terminating resistor at the MFC card has got some sort of discoloration and replaced it with a fresh resistor. But no luck either. I have also used the telenet to see if it can find any modules, but if I use dnWho command it does not find them. As far as I can see from the beckhoff manual the modules are up fine but can’t find a master.
What I do not understand is how can the terminating resistor get burnt and get a reading of 137 ohm, has anyone experienced something familiar? And it has been working so I think it is very unlikely it is a configuration error, I also did a full backup of the hard drive when I did the handover to the customer, also to copy this to the hard drive suspecting a driver error but no luck.
If I measure between can low and can high I can’t get a reading only a few millivolts. So has anyone any good ideas to what can be wrong, maybe a broken MFC?
Best regards
reneklaris