Other robots tend to do enough to randomize things. I don’t think adding more is a good thing, at least at the middle/high-school levels. Maybe VEX U.
Lol yeah. Vex should introduce some rule where the corners of the robot have like identifiable thinsg (idk something reflective or something) so that with the vision sensor we can track where our other robot is. They should also add in a way for two robots to communicate during a competition (esp during auton, then maybe alliances would actually make sense).
+1
those are pretty good ideas, and could make using the vision sensor even better.
I’d have to get @jpearman to back me up on this, and maybe it’s changed with V5, I don’t think VEXNet would support such two way communication.
Although, with Bluetooth, it may be possible. It would be interesting for VEX to allow and support some sort of standardized system to allow robots to communicate in a match. It could lead to some very interesting match play and strategy, even during driver control (Imagine getting haptic feedback based on your alliance robot, etc)
On the v5 system page it says robot to robot communication is coming for vexnet (3.0, which is what v5 uses.)
But, notably, not for Cortex. I wouldn’t imagine that the GDC would even consider allowing robot-robot communication before Cortexes are no longer allowed (even if the update comes before then)
- alliance tethers two robots together *
I cannot unsee this on my own field…
The GDC hath spoken: Parking Platforms Closer to Blue? : Robot Events
Seems like this is intentional and the field specs doc will be updated with the correct distances.
Yes, but the reasoning presented is highly suspect. As was pointed before here, holes could have been drilled differently in the tubes to allow for the platforms to be centered.
Oh I agree. Seems like no one actually checked to see if the platform would be able to be centered before they put the parts into production, and by the time they realized it was too late.