Closed tgroechel closed 3 years ago
Looks like this may something specific in the included Unity dll and/or getSystemState
calls. I was able to pub/sub from a separate dotnet project with the iviz_utils
project added to the sln :) I'll post whatever I find and do a PR if there is any straightforward change to make.
Yes, sorry. The HTTP library wasn't honoring the 'connection: close' header entry sent from Kinetic, so it was surprised by the host suddenly closing the connection. The fix was already in iviz_utils, but the dlls weren't copied to Unity. I think it should work now.
Thanks!
I'm able to get iviz to connect (Win 10 Unity) to a laptop's roscore (Ubuntu 18.04/melodic).
I've been having issues with other laptops/robots, however, using 14.04/Indigo and 16.04/Kinetic. I run
roscore
on the laptops/robots and make sure to setROS_MASTER_URI
,ROS_HOSTNAME
, andROS_IP
to whichever ip they are assigned (have tried a combination of hostname/ip changes with no success).On the Unity side, in the iviz
UI AR
Scene, I get the following error:I can't seem to pin down the connection issue/don't have a great networking background. I'm guessing this is a
ros_comm
issue that has changed fromkinetic -> melodic
. I can't really upgrade my robots sadly. Any idea where to look would be greatly appreciated.