[ajit]

We are having an issue with TCP connection to Dobot CR5, the IP the CR5 unit is at IP 10.168.111.88 but when the commands are being sent they go to 192.168.5.1. 

There are some commands that seems to work we can get robot position correctly and it seems Accl() command is accepted.

We can't send a command, it just disconnects.

Here is the log for the connection:

Code:

Starting robot driver: C:/RoboDK/api/robot/DobotCRDriver.py
Using RoboDK RoboDK v5.7.4
Starting...
Using Python version: sys.version_info(major=3, minor=10, micro=10, releaselevel='final', serial=0)
RoboDK Driver: C:/RoboDK/api/robot
RoboDK Driver v2.0 for Dobot CR Controller..
Command c PowerOn(): Poser On
Command c EnableRobot(): Enable robot
Command c ClearError(): Clear errors
Command c ResetRobot(): Reset errors
Command c User(0): Set User frame 0
Command c User(1): Set User frame 1
Command c User(2): Set 2
Command c Tool(0): Set tool 0
Command c Tool(1): Set tool 1
Command c Tool(2): Set tool 2
RoboDK Driver for Dobot CR5 v2.0.1
Disconnected
Sending command...
Connecting to robot 10.168.111.88:29999
Working...
Ready
Sending command...
Working...
Set tool not supported. Command ingored. Make sure you define the same tool on the controller.
Ready
Sending command...
Working...
Send to 192.168.5.1:29999: AccL(500)
Receive from 192.168.5.1:29999: AccL(500)
Ready
Sending command...
Working...
Enabling Robot..
Send to 192.168.5.1:29999: EnableRobot()
Receive from 192.168.5.1:29999: EnableRobot()
Unable to enable the robot. Is the robot already connected?
Stopped

[Phillip]

Thanks for the feedback, looking into this in more detail now

[ajit]

This got resolved by firmware update.

[Albert]

Thank you for letting us know!

[Tooz]

We are having an issue with TCP connection to Dobot CR12, the IP the CR12 unit is at IP 10.168.10.1 but when the commands are being sent they go to 192.168.5.1. 


Please refer the log information below:

Code:

Driver for RoboDK 5.8.0.24806
Disconnected
Stopped
Starting robot driver: C:/RoboDK/api/robot/DobotCRDriver.py
Using RoboDK RoboDK v5.8.0
Starting...
Not started
Sending command...
Using Python version: sys.version_info(major=3, minor=10, micro=10, releaselevel='final', serial=0)
RoboDK Driver: C:/RoboDK/api/robot
RoboDK Driver v2.0 for Dobot CR Controller..
Command c PowerOn(): Poser On
Command c EnableRobot(): Enable robot
Command c ClearError(): Clear errors
Command c ResetRobot(): Reset errors
Command c User(0): Set User frame 0
Command c User(1): Set User frame 1
Command c User(2): Set  2
Command c Tool(0): Set tool 0
Command c Tool(1): Set tool 1
Command c Tool(2): Set tool 2
RoboDK Driver for Dobot CR5 v2.0.1
Disconnected
Connecting to robot 192.168.10.1:29999
Working...
Ready
Sending command...
Send to 192.168.5.1:29999: MovL(629.400000,-191.000000,858.000000,-90.000000,-0.000000,-90.000000)
Receive from 192.168.5.1:29999: -2,{not tcp mode or system is starting},MovL(629.400000,-191.000000,858.000000,-90.000000,-0.000000,-90.000000);
Ready
Sending command...
Working...
Enabling Robot..
Send to 192.168.5.1:29999: EnableRobot()
Receive from 192.168.5.1:29999: -2,{not tcp mode or system is starting},EnableRobot();
Start to MoveJoint..
Send to 192.168.5.1:29999: JointMovJ(0.000000,0.000000,-90.000000,90.000000,90.000000,10.000000)
Receive from 192.168.5.1:29999: -2,{not tcp mode or system is starting},JointMovJ(0.000000,0.000000,-90.000000,90.000000,90.000000,10.000000);
Moveing..
Send to 192.168.5.1:29999: Sync()
Receive from 192.168.5.1:29999: -2,{not tcp mode or system is starting},Sync();
Ready
Sending command...
Working...
Enabling Robot..
Send to 192.168.5.1:29999: EnableRobot()
Receive from 192.168.5.1:29999: -2,{not tcp mode or system is starting},EnableRobot();
Start to MoveJoint..
Send to 192.168.5.1:29999: JointMovJ(0.000000,0.000000,-90.000000,90.000000,90.000000,0.000000)
Receive from 192.168.5.1:29999: -2,{not tcp mode or system is starting},JointMovJ(0.000000,0.000000,-90.000000,90.000000,90.000000,0.000000);
Moveing..
Send to 192.168.5.1:29999: Sync()
Receive from 192.168.5.1:29999: -2,{not tcp mode or system is starting},Sync();
Ready

[Albert]

Did you update the IP of the robot in the robot connection panel?

If you can provide your RoboDK project file we can take a better look.