Quote:
Originally Posted by lethc
Just a heads up, we tried running TowerTracker on a TK1 at Greater Kansas City and spent literally all of Thursday trying to get it to communicate over ethernet. We got the calibration images we needed from the field about 30 seconds before we had to leave. The competition router image disables DHCP, and we hadn't planned for this. To fix it we had to set all of our devices' (Driver station, TK1, RoboRIO) IPs to static which took awhile because we hadn't planned for it.
Basically if you're planning on communication with the Jetson over ethernet make sure you account for the fact that the router competition image is different from the 'home use' image. I really don't want anybody to go through what we went through on Thursday  |
We ran into the same problem at our event. The competition bridge configuration doesn't disable DHCP, it just doesn't have a DHCP server (because it expects to use the one on the field). This causes the driver station and robot to get an autoconfigured IPv4 address (169.254.x.x), but the Jetson does not.
We fixed this at the competition by using static IPs, but it could likely also be fixed using avahi-autoipd (see:
https://wiki.ubuntu.com/ZeroConfNetworking) to assign an IP without DHCP, but I have not tried this yet.