Add to doc, sometimes custom port must be blank

[RyanPaulMcKenna]

In my experience getting the driver working I followed all the instructions including leave the custom port number untouched. However when I attempting to start communication between ROS on my PC and the UR5 robot the connection always failed.

I attempted to use (for the custom port) the port number that ROS was starting local host on, on my PC that I assume acts as the client interface to issue requests to the UR5 however this resulted in a more serious warning/exception that also immediately ended the communication from the UR5 side.

Then I was certain that the custom port number was the problem, removing the custom port completely. Setting it to blank. Immediately solved the problem and the driver worked perfectly. I am not able to run the move_python example that commands the robot to perform a manoeuvrer.

This solution may not work in all cases but I thought that it should be in the docs since I found nothing about this on any of the forums or the docs. It should help others get up and running more easily in the future.

[urrsk]

Hi @RyanPaulMcKenna Thanks for the info. Though it sounds more like a bug that should be fixed. I would appreciate if you wrote a detail step by step of how to reproduce it, so we can get it fixed.