Quote:
Originally Posted by wilsonmw04
Could you elaborate on the problems you had with labview this year? We were able to use various senor applications with the brick last year without too much difficulty and after a bit of a jump start from the awesome gals from Twisted Bots we were running Auto like mad.
|
Quirky encoder feedback, where it seemed the encoder would stop responding. At UVA I heard of teams using some loop to get around this (like a heartbeat check), but why add that overhead when there seems to be an underlying problem? We had 5 sensors integrated into autonomous -- 2 encoders, 2 bump switches, and a sonic range finder. Yet the robot kept either bumping into the wall, or stopping too soon or too late. The reason we believe it's the brick and not the code is that the results would change in between tests even when the code did not change. We will program Atlanta's autonomous in RobotC sometime in the next couple of weeks, so we'll know if it's just our lack of knowledge or if it really is the brick's inability to process everything.
Quote:
Originally Posted by Rick TYler
I'm not factoring in team registration costs, by the way. This is just hardware. An FTC program using Vex parts would be a much more affordable way to deliver a mid-sized robot STEM program, even with the $275 FIRST registration fee. IMO. YMMV.
|
Aye, but first you have to believe in how your school system implements a STEM program. Around here, usually classroom-based STEM programs are put in gifted programs. To me, closing robotics off to a select few 'gifted' students is not something I believe in, so everything we do is based upon the broader scope of students in the county. That's just around this area though.