We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Here's the rough method we figured out for resetting the VI sensor reliably if not working:
ps aux | grep dhclient
sudo kill -9 <process number>
ssh [email protected]
reboot
ping 10.0.0.1
sudo dhclient enx<tab complete here>
The main problem is that the VI sensor is DHCP master so the PC needs to request an IP from the sensor.
The text was updated successfully, but these errors were encountered:
our new awesome launch file. new_awesome_launch_file.launch.txt
Sorry, something went wrong.
Thanks a lot @dwisth We added this in #27, but it needs to be tested on the robot.
No branches or pull requests
Here's the rough method we figured out for resetting the VI sensor reliably if not working:
ps aux | grep dhclient
sudo kill -9 <process number>
as many times as required.ssh [email protected]
reboot
wait approx 20 seconds. Check it has rebooted with
ping 10.0.0.1
.sudo dhclient enx<tab complete here>
. This takes time.The main problem is that the VI sensor is DHCP master so the PC needs to request an IP from the sensor.
The text was updated successfully, but these errors were encountered: