Scott,
we had our own problems (added a second camera, but had trouble seeing it on the field).
But as to the Field radio configuration, our own ad-hoc solution was to have two new radios, one for "Field" configuration, one configured for use just as back home for "Pit / Build". We would just switch out the radio in the pit (and use the same test radio on the practice field).
Thanks,
Martin Haeberli
(de-)mentor, FRC 3045 Gear Gremlins (formerly SWAT).
----
Quote:
Originally Posted by tr6scott
Another observation from this, and also having major pain in the a$$ with mdns in our setup, still to be "working" but no root cause of why Aaron spent two hours in our pit on Thursday at Waterford.. I feel for you Chris.
Please note that once your radio is programmed at the event, the DHCP server is turn off on your robot radio. The field is the only DHCP server while at the event.
So when you are in your pit, and testing there is no DHCP server to hand out IP addresses, so everything kind of defaults back to the 169. address space. For others this seems to work... For us, not so much...
When we were in the pit at Waterford, I used an old dlink configured to our home settings, when I needed to test and program. (which was all the time)
Thanks for the info on the static IP's
|