<![CDATA[RoboDK Forum - All Forums]]>

<![CDATA[RoboDK Forum - All Forums]]> https://robodk.com/forum/ Sat, 23 May 2026 15:13:17 +0000 MyBB <![CDATA[Questions about kinematic equations in RoboDK]]> https://robodk.com/forum/Thread-Questions-about-kinematic-equations-in-RoboDK Thu, 21 May 2026 15:02:12 +0000 hanzel]]> https://robodk.com/forum/Thread-Questions-about-kinematic-equations-in-RoboDK
I have carefully measured and verified the dimensions to ensure they are consistent with the robot model specifications. I am conducting this experiment mainly for research purposes and to deepen my understanding through practical learning.The robot I am currently using is the ABB-IRB-360-1-1600.]]>
I have carefully measured and verified the dimensions to ensure they are consistent with the robot model specifications. I am conducting this experiment mainly for research purposes and to deepen my understanding through practical learning.The robot I am currently using is the ABB-IRB-360-1-1600.]]> <![CDATA[What hardware do you use for prototyping robot cells pre-deployment?]]> https://robodk.com/forum/Thread-What-hardware-do-you-use-for-prototyping-robot-cells-pre-deployment Thu, 21 May 2026 12:48:36 +0000 Danieldsouza]]> https://robodk.com/forum/Thread-What-hardware-do-you-use-for-prototyping-robot-cells-pre-deployment
I've been thinking about how differently people approach the physical prototyping side before deploying a robot cell, and I'm curious what the community is actually using.

RoboDK handles the simulation side brilliantly, but once you're ready to test I/O signals, sensor triggers, or controller logic on real hardware, the choice of components can make a big difference in how quickly you iterate.

A few questions to get discussion going:

1. What microcontroller/SBC do you use for testing signal logic before wiring to the actual robot controller?

Arduino? Raspberry Pi? Something industrial like a CLICK PLC? Each has tradeoffs in cost, GPIO availability, and how easily it maps to the real controller environment.

2. How do you handle sensor validation?

Do you test proximity sensors, encoders, or vision triggers on a benchtop first, or go straight to the simulation + real robot combo?

3. Any tips for bridging the gap between RoboDK's simulated I/O and physical test rigs?

I've seen some clever setups using Python API calls to trigger GPIO on a Pi in sync with the simulation would love to hear what others have done.

Not looking for a specific product recommendation , more interested in the workflow people follow and the lessons learned the hard way.

Happy to share what I've tried too. What's working for you?]]>
I've been thinking about how differently people approach the physical prototyping side before deploying a robot cell, and I'm curious what the community is actually using.

RoboDK handles the simulation side brilliantly, but once you're ready to test I/O signals, sensor triggers, or controller logic on real hardware, the choice of components can make a big difference in how quickly you iterate.

A few questions to get discussion going:

1. What microcontroller/SBC do you use for testing signal logic before wiring to the actual robot controller?

Arduino? Raspberry Pi? Something industrial like a CLICK PLC? Each has tradeoffs in cost, GPIO availability, and how easily it maps to the real controller environment.

2. How do you handle sensor validation?

Do you test proximity sensors, encoders, or vision triggers on a benchtop first, or go straight to the simulation + real robot combo?

3. Any tips for bridging the gap between RoboDK's simulated I/O and physical test rigs?

I've seen some clever setups using Python API calls to trigger GPIO on a Pi in sync with the simulation would love to hear what others have done.

Not looking for a specific product recommendation , more interested in the workflow people follow and the lessons learned the hard way.

Happy to share what I've tried too. What's working for you?]]> <![CDATA[UR20 Cycle time]]> https://robodk.com/forum/Thread-UR20-Cycle-time Thu, 21 May 2026 11:53:13 +0000 manan]]> https://robodk.com/forum/Thread-UR20-Cycle-time
I am trying to simulate sanding path with UR20 robot. The path motion is accurate, and I set speed and acceleration parameters similar to actual path. However, I am getting big differences between the cycle time. Simulation time is 33.1 seconds, and real time is 64 seconds. I do have some wait commands, but it is less than 3 seconds. This robot has some safety constraint which cannot be added in Robodk for example, elbow speed 350mm/s, tool speed 350mm/sec, but my speed is not even set to that high. Please see the attached Robodk study. I am not sure why there is a big discrepancy between two cycle time.

Thank you.

Manan

.rdk

robotpath.rdk (Size: 3.18 MB / Downloads: 4) ]]>
I am trying to simulate sanding path with UR20 robot. The path motion is accurate, and I set speed and acceleration parameters similar to actual path. However, I am getting big differences between the cycle time. Simulation time is 33.1 seconds, and real time is 64 seconds. I do have some wait commands, but it is less than 3 seconds. This robot has some safety constraint which cannot be added in Robodk for example, elbow speed 350mm/s, tool speed 350mm/sec, but my speed is not even set to that high. Please see the attached Robodk study. I am not sure why there is a big discrepancy between two cycle time.

Thank you.

Manan

.rdk

robotpath.rdk (Size: 3.18 MB / Downloads: 4) ]]> <![CDATA[Display Panel add-in not rendering on macOS Desktop]]> https://robodk.com/forum/Thread-Display-Panel-add-in-not-rendering-on-macOS-Desktop Sun, 17 May 2026 18:50:39 +0000 aliabdelhamid]]> https://robodk.com/forum/Thread-Display-Panel-add-in-not-rendering-on-macOS-Desktop Hello RoboDK team,

I am having an issue with the Display Panel add-in on macOS.

The Display Panel add-in installs correctly and I can create a display panel from Utilities → Create display panel. The Display Panel settings window opens correctly, and the panel appears to be attached to the selected object.

However, the content is not rendered in the 3D view. I tested simple text such as “TEST”, HTML with a red background, large display sizes, different positions and rotations, and simple objects such as a box. Nothing is visible in the 3D scene.

I also tested the official RoboDK Display Panel example stations, but the display content does not appear there either.

Things I have already tried:
- Reinstalling the Display Panel add-in.
- Installing it in Current user storage.
- Updating RoboDK to the latest macOS version.
- Testing with simple text and HTML.
- Testing with different sizes, positions and rotations.
- Testing with simple objects.
- Testing with official Display Panel example stations.
- Restarting RoboDK completely.
- Resetting the tree/window layout settings.

System:
- OS: macOS Sequoia 15.7.4
- RoboDK version: 6.0.0
- Add-in: Display Panel
- Installation location: Current user storage

Could this be a known issue with the Display Panel add-in on macOS? Is there any workaround, dependency, or setting required for the panel to render correctly?

Thank you.

.png

Captura de pantalla 2026-05-17 a las 20.50.16.png (Size: 882.91 KB / Downloads: 12) ]]> Hello RoboDK team,

I am having an issue with the Display Panel add-in on macOS.

The Display Panel add-in installs correctly and I can create a display panel from Utilities → Create display panel. The Display Panel settings window opens correctly, and the panel appears to be attached to the selected object.

However, the content is not rendered in the 3D view. I tested simple text such as “TEST”, HTML with a red background, large display sizes, different positions and rotations, and simple objects such as a box. Nothing is visible in the 3D scene.

I also tested the official RoboDK Display Panel example stations, but the display content does not appear there either.

Things I have already tried:
- Reinstalling the Display Panel add-in.
- Installing it in Current user storage.
- Updating RoboDK to the latest macOS version.
- Testing with simple text and HTML.
- Testing with different sizes, positions and rotations.
- Testing with simple objects.
- Testing with official Display Panel example stations.
- Restarting RoboDK completely.
- Resetting the tree/window layout settings.

System:
- OS: macOS Sequoia 15.7.4
- RoboDK version: 6.0.0
- Add-in: Display Panel
- Installation location: Current user storage

Could this be a known issue with the Display Panel add-in on macOS? Is there any workaround, dependency, or setting required for the panel to render correctly?

Thank you.

.png

Captura de pantalla 2026-05-17 a las 20.50.16.png (Size: 882.91 KB / Downloads: 12) ]]> <![CDATA[Question with painting spray on.py]]> https://robodk.com/forum/Thread-Question-with-painting-spray-on-py Sun, 17 May 2026 14:58:44 +0000 Meng]]> https://robodk.com/forum/Thread-Question-with-painting-spray-on-py
When I run "progmain" the result is right, but when I run "prog12 ", I can't find the painted color on obj? I have tried to change obj and tool variables in the PY file.

.rdk

multi painting520.rdk (Size: 2.65 MB / Downloads: 13) ]]>
When I run "progmain" the result is right, but when I run "prog12 ", I can't find the painted color on obj? I have tried to change obj and tool variables in the PY file.

.rdk

multi painting520.rdk (Size: 2.65 MB / Downloads: 13) ]]> <![CDATA[License problem]]> https://robodk.com/forum/Thread-License-problem Fri, 15 May 2026 19:05:56 +0000 169981]]> https://robodk.com/forum/Thread-License-problem
.png

Zrzut ekranu 2026-05-15 205203.png (Size: 27.51 KB / Downloads: 54) ]]>
.png

Zrzut ekranu 2026-05-15 205203.png (Size: 27.51 KB / Downloads: 54) ]]> <![CDATA[Motoman Dx100 connection issues]]> https://robodk.com/forum/Thread-Motoman-Dx100-connection-issues Thu, 14 May 2026 17:49:13 +0000 GeorgeLopez]]> https://robodk.com/forum/Thread-Motoman-Dx100-connection-issues <![CDATA[Inquiry Regarding Support and Configuration for Hybrid Serial-Parallel]]> https://robodk.com/forum/Thread-Inquiry-Regarding-Support-and-Configuration-for-Hybrid-Serial-Parallel Wed, 13 May 2026 09:07:02 +0000 xilijun]]> https://robodk.com/forum/Thread-Inquiry-Regarding-Support-and-Configuration-for-Hybrid-Serial-Parallel

We have an upcoming project that requires the use of a precession stepping robot, which adopts a hybrid serial-parallel mechanical structure.

At present, we have not yet obtained the 3D CAD model of this robot. We will coordinate with our client promptly and provide the model as soon as it becomes available.

We are writing to inquire whether the RoboDK software supports this type of hybrid serial-parallel precession stepping robot. If supported, kindly advise us on the detailed configuration procedure and the required documentation and materials.

Thank you for your support and prompt reply.

Best regards,

.png

X17.png (Size: 510.19 KB / Downloads: 27)
.png

X17.png (Size: 510.19 KB / Downloads: 27)

.mp4

X17.mp4 (Size: 332.5 KB / Downloads: 11) ]]>

We have an upcoming project that requires the use of a precession stepping robot, which adopts a hybrid serial-parallel mechanical structure.

At present, we have not yet obtained the 3D CAD model of this robot. We will coordinate with our client promptly and provide the model as soon as it becomes available.

Thank you for your support and prompt reply.

Best regards,

.png

X17.png (Size: 510.19 KB / Downloads: 27)
.png

X17.png (Size: 510.19 KB / Downloads: 27)

.mp4

X17.mp4 (Size: 332.5 KB / Downloads: 11) ]]> <![CDATA[Process failed to start: The system cannot find the file specified]]> https://robodk.com/forum/Thread-Process-failed-to-start-The-system-cannot-find-the-file-specified Fri, 08 May 2026 05:42:29 +0000 NMTAFE]]> https://robodk.com/forum/Thread-Process-failed-to-start-The-system-cannot-find-the-file-specified
This is a test installation from my end, the other device has the IP address set to the robot and we are both getting the same result. Our prod version is 5.9.6 and I have also tested the current version, both yielded the same result. I've also tried different drivers all with no success.

.png

Screenshot 2026-05-08 133728.png (Size: 85.35 KB / Downloads: 34) ]]>
This is a test installation from my end, the other device has the IP address set to the robot and we are both getting the same result. Our prod version is 5.9.6 and I have also tested the current version, both yielded the same result. I've also tried different drivers all with no success.

.png

Screenshot 2026-05-08 133728.png (Size: 85.35 KB / Downloads: 34) ]]> <![CDATA[Connection error with Fanuc M-710id/70 robot (RoboDK Trial Version)]]> https://robodk.com/forum/Thread-Connection-error-with-Fanuc-M-710id-70-robot-RoboDK-Trial-Version Wed, 06 May 2026 16:21:47 +0000 Trung Ho]]> https://robodk.com/forum/Thread-Connection-error-with-Fanuc-M-710id-70-robot-RoboDK-Trial-Version Even though I have turn off Window fire wall and I can also ping the robot from RoboDK, the error persisted. In the log it said: "Invalid header" and "Connection problems".
I can not find anything similar online so I would be very grateful if anyone can help me with this. Thank you in advances.

.jpg

robodk.jpg (Size: 93.38 KB / Downloads: 27) ]]> Even though I have turn off Window fire wall and I can also ping the robot from RoboDK, the error persisted. In the log it said: "Invalid header" and "Connection problems".
I can not find anything similar online so I would be very grateful if anyone can help me with this. Thank you in advances.

.jpg

robodk.jpg (Size: 93.38 KB / Downloads: 27) ]]> <![CDATA[Moving Two Robots Independently]]> https://robodk.com/forum/Thread-Moving-Two-Robots-Independently Tue, 05 May 2026 16:36:55 +0000 HenryInUtah]]> https://robodk.com/forum/Thread-Moving-Two-Robots-Independently
Skipping some steps... the self.RDK = robolink.Robolink(args=["-NEWINSTANCE", "-EXIT_LAST_COM", "-SKIPCOM_ALL"]) command provided a RoboLink instance for our program. That object could be used to move the robot or send a program to the controller. No problems so far.

The next project will use two robots - each with a seventh axis. Each robot will have a separate ABB controller running the RoboDK driver. I expect the RoboDK window to embed using the same steps as before. Each robot in the station can connect and (hopefully) the simulation will echo what is happening in real life as the two robots move. But here is where I get confused.

Consider the example where each robot needs to calibrate an end effector. Our program will move a robot to a position, signal the end effector to do something, then repeat for many positions. This should happen for each robot at the same time - but the two robots are not "synchronized", they are running independently. How do I do this?

The first idea is to start two threads and pass the main RoboLink object to them. The "self.RDK" object created above. Thread "A" will make a reference to "Robot A" using something like self.Robot = self.RDK.Item('RobotA', 2) and move it as needed. Similarly, thread "B" will move RobotB. In reality, they are both using methods in the same RoboLink object (I think). What happens if both threads tell RoboLink to move different robots at the same?

The "Synchronize 3 Robots" example in the documentation also creates a thread for each robot, but the threads then create a new RoboLink instance. How would this work if the RoboDK window (with the initial RoboLink) is embedded in our program? That "embedded RoboLink" is also talking to the drivers to update the display, correct?

I don't feel like I explained this very well - here is some pseudo-code that might help.

Code:
class ApplicationGUI(QtWidgets.QMainWindow):

    def embedRoboSK(self):

        self.RDK = robolink.Robolink(args=["-NEWINSTANCE", "-EXIT_LAST_COM", "-SKIPCOM_ALL"])

        # Stuff happens to embed the window and connect to the robots

    def startTreads(self):

        # Each thread gets a reference to the main RoboLink object and a file of instructions

        self.threadA = calibrationThreadA()

        self.threadA.rdk = self.RDK

        self.threadA.instructions = pathToListOfPositionsA

        self.threadA.start()

        self.threadB = calibrationThreadB(pathToListOfPositionsB)

        self.threadB.rdk = self.RDK

        self.threadB.instructions = pathToListOfPositionsB

        self.threadB.start()

class calibrationThreadA(QThread):

    def __init__(self, parent=None):

        QThread.__init__(self, parent)

    def run(self)

        self.robot = self.rdk.Item('RobotA', 2)

        # Read the self.instructions file and move the robot when needed.

class calibrationThreadB(QThread):

    def __init__(self, parent=None):

        QThread.__init__(self, parent)

    def run(self):

        self.robot = self.rdk.Item('RobotB', 2)

        # Read the self.instructions file and move the robot when needed.

]]>
Skipping some steps... the self.RDK = robolink.Robolink(args=["-NEWINSTANCE", "-EXIT_LAST_COM", "-SKIPCOM_ALL"]) command provided a RoboLink instance for our program. That object could be used to move the robot or send a program to the controller. No problems so far.

The next project will use two robots - each with a seventh axis. Each robot will have a separate ABB controller running the RoboDK driver. I expect the RoboDK window to embed using the same steps as before. Each robot in the station can connect and (hopefully) the simulation will echo what is happening in real life as the two robots move. But here is where I get confused.

Consider the example where each robot needs to calibrate an end effector. Our program will move a robot to a position, signal the end effector to do something, then repeat for many positions. This should happen for each robot at the same time - but the two robots are not "synchronized", they are running independently. How do I do this?

The first idea is to start two threads and pass the main RoboLink object to them. The "self.RDK" object created above. Thread "A" will make a reference to "Robot A" using something like self.Robot = self.RDK.Item('RobotA', 2) and move it as needed. Similarly, thread "B" will move RobotB. In reality, they are both using methods in the same RoboLink object (I think). What happens if both threads tell RoboLink to move different robots at the same?

The "Synchronize 3 Robots" example in the documentation also creates a thread for each robot, but the threads then create a new RoboLink instance. How would this work if the RoboDK window (with the initial RoboLink) is embedded in our program? That "embedded RoboLink" is also talking to the drivers to update the display, correct?

I don't feel like I explained this very well - here is some pseudo-code that might help.

Code:
class ApplicationGUI(QtWidgets.QMainWindow):

    def embedRoboSK(self):

        self.RDK = robolink.Robolink(args=["-NEWINSTANCE", "-EXIT_LAST_COM", "-SKIPCOM_ALL"])

        # Stuff happens to embed the window and connect to the robots

    def startTreads(self):

        # Each thread gets a reference to the main RoboLink object and a file of instructions

        self.threadA = calibrationThreadA()

        self.threadA.rdk = self.RDK

        self.threadA.instructions = pathToListOfPositionsA

        self.threadA.start()

        self.threadB = calibrationThreadB(pathToListOfPositionsB)

        self.threadB.rdk = self.RDK

        self.threadB.instructions = pathToListOfPositionsB

        self.threadB.start()

class calibrationThreadA(QThread):

    def __init__(self, parent=None):

        QThread.__init__(self, parent)

    def run(self)

        self.robot = self.rdk.Item('RobotA', 2)

        # Read the self.instructions file and move the robot when needed.

class calibrationThreadB(QThread):

    def __init__(self, parent=None):

        QThread.__init__(self, parent)

    def run(self):

        self.robot = self.rdk.Item('RobotB', 2)

        # Read the self.instructions file and move the robot when needed.

]]> <![CDATA[Robot is not moving]]> https://robodk.com/forum/Thread-Robot-is-not-moving Tue, 05 May 2026 15:56:23 +0000 weisseran]]> https://robodk.com/forum/Thread-Robot-is-not-moving When I rotate the dial to change the robot orientation, I can see the robot on my screen moving but the real robot is not moving unless I click Move Joint.
It was moving before.
What went wrong ?]]> When I rotate the dial to change the robot orientation, I can see the robot on my screen moving but the real robot is not moving unless I click Move Joint.
It was moving before.
What went wrong ?]]> <![CDATA[OMPL Integration with RoboDK for Path Planning]]> https://robodk.com/forum/Thread-OMPL-Integration-with-RoboDK-for-Path-Planning Mon, 04 May 2026 12:27:23 +0000 Lukas12]]> https://robodk.com/forum/Thread-OMPL-Integration-with-RoboDK-for-Path-Planning OMPL into RoboDK to use planners such as PRM*, RRT, and FMT*. Scene extraction from RoboDK to Python is already working (robot model, obstacles, joint limits, start/goal configurations).
My current challenge is collision checking:
OMPL runs, but some generated paths are not feasible. I suspect the issue is with the synchronization between OMPL(Python script) and RoboDK’s collision checker (currently using

Code:
return self.RDK.Collisions() == 0

).
A few questions:

Has anyone successfully integrated OMPL directly with RoboDK?
How is collision checking handled in RoboDK’s internal PRM implementation?
Is there a way to query the minimum distance between the robot and obstacles, rather than only checking for collisions?

]]> OMPL into RoboDK to use planners such as PRM*, RRT, and FMT*. Scene extraction from RoboDK to Python is already working (robot model, obstacles, joint limits, start/goal configurations).
My current challenge is collision checking:
OMPL runs, but some generated paths are not feasible. I suspect the issue is with the synchronization between OMPL(Python script) and RoboDK’s collision checker (currently using

Code:
return self.RDK.Collisions() == 0

).
A few questions:

Has anyone successfully integrated OMPL directly with RoboDK?
How is collision checking handled in RoboDK’s internal PRM implementation?
Is there a way to query the minimum distance between the robot and obstacles, rather than only checking for collisions?

]]> <![CDATA[curve follow project with point]]> https://robodk.com/forum/Thread-curve-follow-project-with-point Thu, 30 Apr 2026 13:12:54 +0000 SagarMangulkar]]> https://robodk.com/forum/Thread-curve-follow-project-with-point For polishing how to make a program in which the grinder blade tool should be parallel to each curve follow point without collision.

Please suggest I am attaching station here.

.rdk

Polishing SGP Down RH.rdk (Size: 2.51 MB / Downloads: 41) ]]> For polishing how to make a program in which the grinder blade tool should be parallel to each curve follow point without collision.

Please suggest I am attaching station here.

.rdk

Polishing SGP Down RH.rdk (Size: 2.51 MB / Downloads: 41) ]]> <![CDATA[Modifying a code instruction always changes the name]]> https://robodk.com/forum/Thread-Modifying-a-code-instruction-always-changes-the-name Wed, 29 Apr 2026 17:55:28 +0000 HenryInUtah]]> https://robodk.com/forum/Thread-Modifying-a-code-instruction-always-changes-the-name
Here is an image to help explain:

.png

RoboDK Always Renames Instruction.png (Size: 21.5 KB / Downloads: 62) ]]>
Here is an image to help explain:

.png

RoboDK Always Renames Instruction.png (Size: 21.5 KB / Downloads: 62) ]]>