|
Re: The perfect dashboard
Battery level is always handy, as would the sensor readings of anything drastically important (say, current draw on my drive motors, if I had them wired to say as such).
CMUcam information would be ridiculously awesome for aiming purposes; I remember seeing 16's system at Palmetto, and I wish we'd thought of it.
Important alerts (say, loss of the backup battery) should be easily seen (think big red boxes with clear text), but also not block the other data. (Call it the I-know-the-backup-battery-is-on-the-floor-you-stupid-dolt! principle.)
Orientation of attachments I'm not so sure of. For a game like Aim High or Triple Play, it wasn't exactly important--your operator could most likely see what was happening better than he or she could deduce them from a Dashboard. That said, a game with less visibility from the drivers' station like Stack Attack (or perhaps FIRST Frenzy, if you were trying to climb from the other end of the field) might find this useful.
Speed....eh, not really. From my experience behind the glass, you want as few distractions as possible before and during a match--that includes extraneous information on a Dashboard, opposing robots chucking balls right at you, your mother trying to talk to you, and having your cell phone start ringing. Of course, if you wanted to have speed information on there, you could always have a bells-and-whistles dashboard for testing and a streamlined one for on the field.
__________________
William "Billfred" Leverette - Gamecock/ Jessica Boucher victim/ Marketing & Sales Specialist at AndyMark
2004-2006: FRC 1293 (D5 Robotics) - Student, Mentor, Coach
2007-2009: FRC 1618 (Capital Robotics) - Mentor, Coach
2009-2013: FRC 2815 (Los Pollos Locos) - Mentor, Coach - Palmetto '09, Peachtree '11, Palmetto '11, Palmetto '12
2010: FRC 1398 (Keenan Robo-Raiders) - Mentor - Palmetto '10
2014-2016: FRC 4901 (Garnet Squadron) - Co-Founder and Head Bot Coach - Orlando '14, SCRIW '16
2017-: FRC 5402 (Iron Kings) - Mentor
|