Quote:
Originally Posted by feverittm
Are their any know best practices for how to work with this type of network code.
|
Treat FMS like a black box until FIRST provides more details about what it is doing. Refer to the white papers I listed earlier in this thread for the setup that 900 ran this year for vision. We had no issues with vision communication on the robot. We did have issues with our driver station at one event, likely created by a non-constrained loop on the driver console and definitely not the result of our vision configuration.
Anecdotally, all the teams that I heard/saw having issues with cameras were not relying on static addresses but on mDNS. I'm not saying mDNS was the problem but I know that the documentation for both of these is lacking for making forward progress for integrated vision systems.
I would really like to see simple block & wire diagrams from FIRST documenting how all of the components of FMS work together and outlining ports/protocols in use along with what data is collected and when and any exposed APIs that the teams can use. I think having all of this documented would go a long way towards solving the "it works on the practice field" issues that plague a lot of teams.
Quote:
Originally Posted by frcguy
|
This is severely lacking technical details for what is going on with the FMS and is not a white paper describing FMS so much as a set of guidelines for teams to use. There is a lot of information that is not detailed here.