VADCFLL-L Archives

First Lego League in Virginia and DC

VADCFLL-L@LISTSERV.JMU.EDU

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
B Bergenstock <[log in to unmask]>
Reply To:
B Bergenstock <[log in to unmask]>
Date:
Tue, 29 Oct 2013 17:40:50 -0400
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (3396 bytes) , text/html (6 kB)
For my team, it was a motor that decided to not break completely, but not
work at "regular" speed. So the advice of the painters tape to check to see
if a robot is running straight is a great tip!  For us, there was no way to
correct for it because it seemed to not have a consistent slowing down in
that motor.  After discovering it, the kids had to rebuild the robot to
make the 3rd motor the right wheel motor and move that "broken" motor up to
the 3rd motor position where it's slower speed didn't affect the driving of
the robot.   I have since outlawed hand-spinning  motors- you know when the
kids stand there with the robot and just rip away at the wheels to make
them move? Yeah. Ask them not to do that.
  Our biggest problem by far was user error, but battery power really hurts
you if you have programmed any timed missions, vs. degrees/rotations.  Not
that you want to redo any of your missions this close so game time, but you
might have time to update one section on the most critical missions if you
used the timed distance option.
Good luck! And have fun :)
Brandy


On Tue, Oct 29, 2013 at 3:48 PM, Scott Rakestraw <[log in to unmask]>wrote:

> Mandy outlined all the consistency issues.  In my team’s experience, it
> has been battery assuming the robot is not changing.   The team would start
> with a fresh battery and as the practice went on, things that were working
> would stop working.  They would make adjustments.  Once the battery was
> charged, the stuff that was working stop working.  After experiencing this
> rinse and repeat cycle, we now limit programming practices to one hour.
> ****
>
> ** **
>
> Scott Rakestraw****
>
> Coach****
>
> Capital Girls and Code Crackers****
>
> ** **
>
> *From:* First Lego League in Virginia and DC [mailto:
> [log in to unmask]] *On Behalf Of *Tonya Lapham
> *Sent:* Tuesday, October 29, 2013 12:34 PM
> *To:* [log in to unmask]
> *Subject:* [VADCFLL-L] Robot consistancy****
>
> ** **
>
> Hello,****
>
> ** **
>
> I seem to have this trouble each year.  The robot will be doing just fine.
>  Then suddenly the programs that were working fine now are not working the
> way they were programmed.  And it seem to happen about the same time during
> the tournament season, only it is with a different set of kids each time.
>  Any suggestions on how to trouble shoot these issues?
> ****
>
> ** **
>
> --
> Thank you!!****
>
> Tonya Lapham****
>
> Coach****
>
> Seismic Wave****
>
> ** **
> ------------------------------
>
> To UNSUBSCRIBE or CHANGE your settings, please visit
> https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or
> leave the list".
> VADCFLL administrative announcements are sent via VADCFLL-ANNOUNCEMENTS-L.
> Visit https://listserv.jmu.edu/archives/vadcfll-announcements-l.html to
> subscribe. ****
> ------------------------------
> To UNSUBSCRIBE or CHANGE your settings, please visit
> https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or
> leave the list".
> VADCFLL administrative announcements are sent via VADCFLL-ANNOUNCEMENTS-L.
> Visit https://listserv.jmu.edu/archives/vadcfll-announcements-l.html to
> subscribe.
>

-- To UNSUBSCRIBE or CHANGE your settings, please visit https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave the list".

-- VADCFLL administrative announcements are sent via VADCFLL-ANNOUNCEMENTS-L. Visit https://listserv.jmu.edu/archives/vadcfll-ANNOUNCEMENTS-l.html to subscribe.


ATOM RSS1 RSS2