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

Using the SMB 261 VI sensor #18

Open
dwisth opened this issue Jun 30, 2019 · 2 comments
Open

Using the SMB 261 VI sensor #18

dwisth opened this issue Jun 30, 2019 · 2 comments

Comments

@dwisth
Copy link

dwisth commented Jun 30, 2019

Here's the rough method we figured out for resetting the VI sensor reliably if not working:

  1. Close all ros process running.
  2. Kill any existing DHCP clients.
    ps aux | grep dhclient
    sudo kill -9 <process number> as many times as required.
  3. Reboot the VI sensor.
    ssh [email protected]
    reboot
    wait approx 20 seconds. Check it has rebooted with ping 10.0.0.1.
  4. Restart the DHCP client: sudo dhclient enx<tab complete here>. This takes time.
  5. Start the launch files now.

The main problem is that the VI sensor is DHCP master so the PC needs to request an IP from the sensor.

@dwisth
Copy link
Author

dwisth commented Jun 30, 2019

our new awesome launch file.
new_awesome_launch_file.launch.txt

@gawela
Copy link
Contributor

gawela commented Jul 3, 2019

Thanks a lot @dwisth
We added this in #27, but it needs to be tested on the robot.

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

No branches or pull requests

2 participants