Cannot Connect to Robot

[Dave Kotfis]

We've attempted to connect to the Atlas hardware with the IHMCAtlasAPI. Our field computer is 10.66.171.20 and robot is 10.66.171.30 (which I believe is the default from BDI). I adjusted the value of networkProcessorIP to be 10.66.171.30 in atlas_network_config.ini as suggested, but am getting this result:

Running with torque and velocity limits disabled, do not check in !! Failed to connect KryoClient to SCS at ip: 10.66.171.20 at port: 4895. retrying... [RobotDataReceiver] TODO: Fix threading in robot model update [RobotDataReceiver] TODO: Fix threading in robot model update Failed to connect KryoClient to SCS at ip: 10.66.171.20 at port: 4895. retrying... Failed to connect KryoClient to SCS at ip: 10.66.171.20 at port: 4895. retrying... Failed to connect KryoClient to SCS at ip: 10.66.171.20 at port: 4895. retrying... Exception in thread "main" java.lang.RuntimeException: Cannot connect to 10.66.171.44 No route to host at us.ihmc.utilities.net.NetworkTools.getMyIP(NetworkTools.java:25) at us.ihmc.utilities.ros.RosTools.createNodeConfiguration(RosTools.java:73) at us.ihmc.utilities.ros.RosMainNode.execute(RosMainNode.java:204) at us.ihmc.darpaRoboticsChallenge.gfe.ThePeoplesGloriousNetworkProcessor.<init>(ThePeoplesGloriousNetworkProcessor.java:75) at us.ihmc.darpaRoboticsChallenge.gfe.ThePeoplesGloriousNetworkProcessor.<init>(ThePeoplesGloriousNetworkProcessor.java:80) at us.ihmc.atlas.AtlasROSAPINetworkProcessor.<init>(AtlasROSAPINetworkProcessor.java:32) at us.ihmc.atlas.AtlasROSAPINetworkProcessor.main(AtlasROSAPINetworkProcessor.java:66) Failed to connect KryoClient to SCS at ip: 10.66.171.20 at port: 4895. retrying... Failed to connect KryoClient to SCS at ip: 10.66.171.20 at port: 4895. retrying... Failed to connect KryoClient to SCS at ip: 10.66.171.20 at port: 4895. retrying...

IHMCAtlasAPISimulator seems to be working just fine :-). On that note, we appreciate the opportunity to use your WBC through your open source initiative.

[DouglasS]

Hey @dkotfis, thanks for the interest in the project and the kind words! I sent you a private message regarding this bug, as it is actually related to another repo we run that you currently don't have access to. I'll be closing this ticket.