TCP/IP Interface Stops Responding


#1

First, I am using the TCP/IP interface for a Dobot CR10. I am able to power up and enable the robot. I can even issue a MoveJ command. However, it stops responding to commands after the move. As in, I am sending the commands, but I get no data in response from the socket that is connected to the robot.

Second, is there a certain starting sequence of commands that need to be sent to bring the robot online? What is the proper startup sequence when using the TCP/IP interface? And, if my application restarts, what is the proper way to reconnect to the robot that won’t cause it to stop responding?