Quote:
Originally Posted by John_1102
I hate that light thing!!!! SO MUCH!!! If anything goes wrong it's like an oops oh well sort of thing.
IDK bout the code part, no one was using NXT-G last year at nationals except me when I was on 1102. Though i have to say my transition into RobotC and LabVIEW was quite easy.
Our robot at the beginning was a child, but thing is starting to grow it's wings esp. since we beat out two of our own teams 1102, and 3923 who won SC State Day 1. We got beaten by the on day 2 playing defense against 315 and burned out our right motor in the semifinals but still went on to the finals, We re geared the system to have the speed and power of ten bears. and it ended up working for us without the slightest pit stop in TN.
The best part of nationals is going to be there is a team from Maryland also called G-FORCE, and we have been talking and if we're on an alliance or against each other it's due to be a funny match. Also weirdly our robots turned our slightly similar shooter wise.
|
Yeah. The lights are annoying. >.<
You use RobotC and LabVIEW? Cool. I'm mainly RobotC, because the LabVIEW programs last year took a while to compile, and- surprisingly- quite a bit of the NXT's puny SSD. I think I was able to get 6 on there before it ran out of space. >.<
Very nice. Seeing a huge amount of progress in your robot is always a good thing.
Having multiple teams with similar names in the same match as allies or opponents is always funny.

We have 4 FTC teams, and all of them used to just be called "ILITE". So, if we were partnered up to two- or even three- in the same match, it would be "And on the red alliance, ILITE robotics, with ILITE robotics!" XD
I just finished all of the FRC coding I can do for the night (see: bugtesting all that I can with a bare cRIO), so I thinks I'm going to move on to programming our FTC autonomouses. In tallying up how many I have to make, I'm seeing numbers in the mid-teens. So, might as well get to work.
