Quote:
Originally Posted by cpapplefamily
We could ping the Kangaroo and even better Remote into it, we could also get a simple camera Viewer on our smart dash board. THE ISSUE was Roborio coms. This was tethered and in the pits never tested on the field.
Now the for the
MOST FRUSTRATING PART OF ROBOTICS
we are home wired as stated above and everything is working. Radio still flashed for FMS, Roborio unaltered. we just plugged the cables in turn on the bot and in record time it seemed connected to the driverstation ready to run.
|
I've made comments about this before on Reddit or maybe on CD I think... FMS is a black box and is POORLY documented (Yes Virginia, I'm aware of the outdated FMS white paper). mDNS is unstable at best with FMS and on top of that no one seems to know how to correctly setup multiple devices on the team network as far as subnets and routing go.
I agree with you that this is frustrating. I worked with a couple of our students and we did our best to detail our competition setup from 2016 with a box and wire diagram in this paper:
https://www.chiefdelphi.com/media/papers/3267
We gave up with mDNS very early in our testing and moved straight to hardcoded static IPs. Honestly, I'm not sure I would trust FMS with mDNS at this point even if it were thoroughly documented.
EDIT: Looking at our paper, I think one of our subnet masks is wrong. Will get that checked at some point. Like you I'm 90% certain we had to use different masks on different devices for some strange reason despite everything being in the same class C...