Quote:
Originally Posted by Ari423
423 did that in almost every eliminations match at Springside Chestnut Hill, but just barely so. During quals we always stopped before we crashed. Between quals and elims we upped the power from 50% to 85%, but forgot to change the timing. Now the robot would stop almost exactly 1/2 second after it crashed, consistently. Sadly because of quick turn-around time and LabVIEW's slow and inconsistent deploys, we weren't able (or willing to risk) reloading the code to stop a second earlier. I'd like to officially apologize to any team we may have hit and let you know that we've fixed that problem for Westtown this weekend by adding an ultrasonic rangefinder to auto-stop when we get close to the wall.
|
This is the primary reason we took a year working on implementing a simple text file system where everything is read in from text files that we FTP to the robot. Deploying labVIEW in a competitive environment is nearly impossible. Just FTPing new constant and auto text files takes a matter of a second.