Closed adnanmunawar closed 6 years ago
I am suspecting that this issue might have to do with us using multiple machines on the local network (one connected to dvrk and another where we are using python api) and not updating the host in /etc/hosts file. I shall keep an eye on it to see if it pops up again if we set up the hosts correctly
This is not strictly ROS related. For a distributed ROS master to work on Linux I found that if you can ping your host without the complete domain (e.g. ping lcsr-qla
vs lcsr-qla.jhu.edu
) then ROS works fine. You can create an entry in your /etc/hosts
for each computer you might use but this is not always the best solution (specially if your computers are using DHCP). You can instead set a domain search path in your network configuration. On Ubuntu, edit your network configuration, then pick IPv4 Settings and enter "jhu.edu" in "Additional search domains".
Ahh that's a much better way of handling the dynamic allocation of host ips by the DHCP. Luckily all my workstations are connected via ethernet and the lease doesn't expire for a long time but that's not the case with the wifi machines. I shall try to adopt these changes
I think after a recent update, (I am guessing the update for broadcast of current state of robot) the python interface is not working as expected. The dmove commands block and fail to move the robot.