[jtrv]

Originally Posted by PAR_WIG1350

This would actually be a good one to try to tackle, but perhaps not to the extent that you are hoping for. Currently, the programming for FRC is largely done by implementing the predefined abstract functions/methods/VIs(?). The same main code runs on every robot, more or less, and only the implementations of these functions vary from team to team. If there were a handful of such abstract functions that teams could use to provide the field with a standard set of parameters, combined with some additional (non-abstract) functions that allow the robots to query these parameters as reported by their alliance partners, basic information sharing would become possible. Additionally, since it would just be more of the same type of programming that teams are already used to, the added burden to the teams would be reduced compared to more complex cooperative schemes.

For example, If robots were to report when they lacked/desired more game pieces, a game-piece-harvesting robot could hold onto its collected game pieces while periodically polling how interested its alliance partners were in receiving them. The other alliance partners would independently write their own code for when to activate this signal based on their own strategies. While other game-piece-harvesters would likely never signal a need for game pieces, an exceptionally rapid scorer might always indicate a need for more. Other teams might tie this signal to a sensor in the robot or control it manually from the driver's station. Regardless of what the method of controlling the signal is, the response of the harvester would be the same. Perhaps the harvesting robot has an automatic turret that auto-aims towards the scoring side of the field, and launches game pieces towards the scoring robots without human interference, allowing the harvester's driver to continue to concentrate on harvesting.

It would work best if the game was designed to encourage the use of such a system, but it could definitely be done.

One thing that immediately comes to mind is 148's 2015 robot. That might be the greatest potential for teamwork that was never fully utilized.

In regards to code, I'm not sure. Wireless communications are very strictly locked down while on the field to prevent field signal interference, which I understand, but I think is quite harmful to the growth of control systems within FRC, and I can only dream of the day teams are more free to implement their own wireless communication systems (provided it doesn't flop as hard as the Kinect idea ).