Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Connection to KUKA using C3 bridge

#1
Hello all, 

I tried to connect my KUKA robot (KR-3-R540) to RoboDK, I reviewed the documentation and also the following threads. To the best of my knowledge, I followed every step and unfortunately, I couldn't get the connection. the only thing that I haven't tried is changing the port number. I would appreciate any assistance on this issue. I have attached the errors for reference.


1.  Question about connection between RoboDK and KUKA robot
2.  KUKA robots - RoboDK Documentation
3.  RoboDK connection with KR C5

Thank you, 
Mohamad


Attached Files
.pdf   C3 bridge.pdf (Size: 432.67 KB / Downloads: 204)
#2
Could you please try my instructions from this thread:
https://robodk.com/forum/Thread-Real-Tim...KR10-Robot

First of all, you need to make sure that the physical connection between the PC and the robot is working.
For example, use WorkVisual to check availability.
Then you need to check the Port Forwarding settings in the robot's control system.
The port 7000 may be busy on newer systems and it's worth trying other options. For example, 6999 or 7002.
#3
(07-18-2024, 10:11 AM)Dmitry Wrote: Could you please try my instructions from this thread:
https://robodk.com/forum/Thread-Real-Tim...KR10-Robot

First of all, you need to make sure that the physical connection between the PC and the robot is working.
For example, use WorkVisual to check availability.
Then you need to check the Port Forwarding settings in the robot's control system.
The port 7000 may be busy on newer systems and it's worth trying other options. For example, 6999 or 7002.

Dear Dmitry,

It worked! Thank you. 
I followed every instruction in the post you shared and by changing the port number to 7002 I could get the connection. If I may ask another question, when I try to move joints or run on the robot, I receive a "working" message (attached images). I think some settings on SmartPad are not right. Do you mind if I ask your opinion?


Attached Files Thumbnail(s)
photo_2024-07-18_15-57-14.jpg    working.jpg   
#4
Great, but your system isn't fully configured yet.
I would recommend changing the apikuka driver to the kukabridge:
[Image: img14.png]
The you can use the auto-configuration script: https://robodk.com/doc/en/Robots-KUKA-Au...nfigScript
In case of any problems, you can perform an automatic configuration interactive: https://robodk.com/doc/en/Robots-KUKA-Au...iverConfig
Or even make the configuration by yourself in manual mode: https://robodk.com/doc/en/Robots-KUKA-Ma...iverConfig
#5
Dear Dmitry, 
Thank you so much for your response. 

I followed your instructions, but the automatic configuration didn't work as it couldn't replace $config.dat. I manually added the lines to the $config file and ran the RoboDKsync570.src file. However, I still get a "working" message when I press "move joints."

When I move TCS manually, the robot moves as expected in the software, but I cannot run the robot from RoboDK. Do you think there might still be a configuration issue?

Thank you in advance for your time. ( I added some images for better clarification)


Attached Files Thumbnail(s)
Log.jpg   
#6
Make sure the KRL program RoboDKsync570.src is running and not just selected.
Also I noticed in your screenshot that you are still using apikuka instead of kukabridge.
#7
Thank you so much Dmitry, it worked. I appreciate your time.
  




Users browsing this thread:
1 Guest(s)