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

UR robot connected but no On-/Offline programming

#1
Hello, brand new user of RoboDK (v. 5.9.4) here. Attempting to do on-/offline programming of UR-3 robot with the software. 

Here is my configuration: UR-3, CB3.1, Polyscope 3.15.8-build10.6.339, URCaps: only Robotiq_Grippers, version UCG-1.8.9.14887 

I can connect to the robot, but only with the driver “DriverUR” (the legacy apiur driver will not connect). I can select a target position and ask Move Joints to have the real robot moving to the requested position. I have read the help instructions Run a Program on the UR controller.

When I attempt to do Online Programming (Run on robot), nothing happens. No error message in RoboDK, just the status message “Sending command” (see attached picture), no error message on the UR-3 log.

When I attempt to do Offline Programming (Send program to robot), nothing happens either. The transfer is successful, I do see new entries in the UR-3 log (see attached picture), but the robot doesn’t move.

I have searched this forum for help with this problem and read Universal Robots connection issue and Connect to UR5. But this has not helped me to solve my problem.
I am also sharing my station file for more details.

I hope someone can share some light here… I’ve already being fussing around for a few hours!


Attached Files Thumbnail(s)
RoboDK-OfflineProgramming-URlog.jpg    RoboDK-OnlineProgramming.png   

.rdk   UR3-TP_P5_Rob.rdk (Size: 1.19 MB / Downloads: 13)
#2
Hello, anyone here who might help ?
#3
Can you try generating a script file and/or a URP file and load it on your robot controller? You may need to use a USB drive to transfer the URP file, or create a new program to load the script file. Youc an find more information here:
https://robodk.com/doc/en/Robots-Univers...tml#UR-URP
If you use the Univeral Robots URP post processor it will generate a program that can be loaded in the controller and you should properly see the instructions in the tree on the teach pendant of the robot.

Does the gripper work properly? It is strange to not see any error messages in the log window and for nothing to happen as if the connection was successful.
#4
Hi Albert, thanks for reaching out to me.
Yes indeed, the generation of script and URP file is working properly and I can transfer them to the robot controller via FileZila (which I lunch from the Connect Robot > Explore button in RoboDK).

I can not operate at all the gripper from RoboDK. This will be my next hurdle. The gripper is working fine with the RobotiQ URCap in the robot controller. I’ll start a new thread in this forum about resolving the operation of the gripper once we figure out what is going wrong with the Off-/online Programming, since I am suspecting it might also affect the gripper control.
#5
(12-16-2025, 07:58 PM)Jerome_HEI Wrote: Hello, anyone here who might help ?

(Yesterday, 12:00 AM)Albert Wrote: Can you try generating a script file and/or a URP file and load it on your robot controller? You may need to use a USB drive to transfer the URP file, or create a new program to load the script file. Youc an find more information here:
https://robodk.com/doc/en/Robots-Univers...tml#UR-URP FNAF Free
If you use the Univeral Robots URP post processor it will generate a program that can be loaded in the controller and you should properly see the instructions in the tree on the teach pendant of the robot.
Does the gripper work properly? It is strange to not see any error messages in the log window and for nothing to happen as if the connection was successful.

If the robot shows as connected but you can’t switch to Online programming, this is usually related to the controller mode or remote control settings. Please make sure the UR controller is in Remote Control mode and that no other application (e.g. Polyscope, another PC, or a running program) is holding the connection. Also verify that the robot is powered on, not in protective stop, and that the correct IP and driver are selected in RoboDK. Restarting both RoboDK and the controller often resolves this.
  




Users browsing this thread:
1 Guest(s)