[foxobot]

Hello.
I have RoboDK (x32 architecture) and taked the latest driver for Doosan by link from RoboDK Support. Unfortunately the issue with the connection remained.



The robot M1013 has M2.4.1 system.
Can you help me?

[Albert]

I recommend you to try connecting to your Doosan robot with the latest version available here:
http://robodk.com/downloads/DoosanDriver.zip
You can uzip the files here:
C:/RoboDK/api/robot

This should work with any version of RoboDK on Windows.

Let us know if you have issues (I believe there was a problem when you uploaded your images).

[foxobot]

I recommend you to try connecting to your Doosan robot with the latest version available here:
http://robodk.com/downloads/DoosanDriver.zip
You can uzip the files here:
C:/RoboDK/api/robot

This should work with any version of RoboDK on Windows.

Let us know if you have issues (I believe there was a problem when you uploaded your images).

With a virtual controller i have connection, but with a real robot the situation is the opposite.
   
There is connection has state is "Working..." long time, but if I disconnect by double click on "Disconnect" and then push the "Stop", the state is "Ready". But at the same time I can't control the robot.
   
   

[Phillip]

Thank you for your feedback, I've attached an improved version of the driver you can download here, the version number should 2.0.4

http://robodk.com/downloads/DoosanDriver.zip

If you have any further issues please get back to us, the log will provide more details of errors now.

[foxobot]

Thank you for your feedback, I've attached an improved version of the driver you can download here, the version number should 2.0.4

http://robodk.com/downloads/DoosanDriver.zip

If you have any further issues please get back to us, the log will provide more details of errors now.

Dear Phillip.

I downloaded this driver and the connection was astablished! Thank you for your help.

   

P.S. Some instructions of RoboDK aren't work correctly on the robot. More precisely, they are not recognized by the robot. For example, "Rounding".

   

But after reconnecting the program work is correctly and the robot is moving, but not always: sometimes in this case the robot is jerk and stopping with message "5 (CODE 7061) or 2 (CODE 9012) TCP (Tool Center Point) overstepped the workspace limit.