Quote:
Originally Posted by Lord_Jeremy
For two days at our regional the robot didn't move on the field. It worked just fine in the pit, tethered and it worked fine at school on wireless. Eventually I solved the problem by reimaging the cRIO, but that was after the mentors had ordered me to remove the Java code I wrote and replace it with the default LabView code. (There was a lot of fighting about this. Apparently someone from another team that used Java but switched to LabView came over and said that the Java code was the problem.)
|
Interesting, because something similar happened, except by willingness of I. I have the robot coded in not just java, but in Labview as backup (boredom produces somewhat valuable things sometimes). Since I never had time to test either code before the robot was shipped, I scrapped the java code and perfected the Labview code. It was sad to see 4 days of hard work go to waste and STILL nothing worked (NOTE: it was not a code error that killed our robot, someone just wired all pwms backwards).
As for the actual question, hands down our parallel kicker. It wasn't the code itself, but the implementation and lag prevention that was very difficult.