Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconnect triggered by zero bytes received fails #58

Open
GoogleCodeExporter opened this issue Apr 7, 2015 · 4 comments
Open

Reconnect triggered by zero bytes received fails #58

GoogleCodeExporter opened this issue Apr 7, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

This error is in the simple message library but it presents itself when used 
with the Fanuc controller.  This seems to occur because the Fanuc controller 
keeps socket connections open.

What steps will reproduce the problem?
1. Start the ROS-I software on the Fanuc controller: ldr_ros_i.tp
2. Start the ROS-I software on the PC: roslaunch fanuc_common 
robot_state_visualize_<robot>.launch robot_ip:<ip address>
3. Abort or pause the programs executed by ldr_ros_i.tp
4. Restart ldr_ros_i.tp

What is the expected output? What do you see instead?

The ROS logs will show reconnection errors (EISCONN 106 /* Transport endpoint 
is already connected).  The reconnect is triggered by receiving zero bytes, not 
an error code returned by the socket read.  The socket connection is never 
reacquired.  The socket should reconnect when ldr_ros_i.tp is executed.


Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 19 Apr 2013 at 3:29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant