VADCFLL-L Archives

November 2014

VADCFLL-L@LISTSERV.JMU.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
Content-Type:
multipart/alternative; boundary="001a113ebb0e7103d60507942046"
Sender:
First Lego League in Virginia and DC <[log in to unmask]>
Subject:
From:
Skip Morrow <[log in to unmask]>
Date:
Tue, 11 Nov 2014 07:07:44 -0500
In-Reply-To:
MIME-Version:
1.0
Reply-To:
Skip Morrow <[log in to unmask]>
Parts/Attachments:
text/plain (4 kB) , text/html (9 kB)
Wow. Add us to the list of teams with color sensor issues this past
weekend. Many of our missions relied on the sensor, and had been working
nearly perfectly in team practices.

When we got to the tournament, we did pretty good on our practice round.
But then for round 1 no missions worked. We hadn't changed anything, so we
were puzzled. Back in the pit, we troubleshot and troubleshot. We could
tell that the sensor was changing from color mode to light intensity mode
for no apparent reason. You should see a blue-ish light coming from the
sensor when it is in color mode. A reddish light indicates light intensity
mode. Depending on the settings of the wait block, the sensor should
automatically select the correct mode. Well, ours would spontaneously
switch over to light intensity mode, even though we never use light
intensity.

Round two came and went and we got lucky on one mission. We still had not
figured out what was going on. Finally, we tried our backup robot. And
everything worked perfectly. 100%. It just never occurred to us that we
could be facing a hardware issue.

For round three we went to the table and all of our missions worked.


.

On Mon, Nov 10, 2014 at 6:35 PM, Monson Gmail <[log in to unmask]>
wrote:

> Jill,
>
> We had a similar issue with color sensor, but we build a shield around the
> sensor and the issue was resolved. We researched and found this solution.
>
> Thanks,
> Monson
> Rookie coach of Future Geekbots
>
>
> On Nov 10, 2014, at 6:23 PM, Jill Hamilton <[log in to unmask]>
> wrote:
>
>  Amy, thanks for sharing.  We found this too.  Our EV3 color sensor
> wouldn’t read green.  We realized it was too close to the table.  I am
> curious what you learned during the competition that helped.
>
>
>
> Thanks
>
> Jill Hamilton
>
> Coach of Cyborg Piñata 3335
>
> Coach of the Mechanical Manatees
>
> Coach of the Electric Pineapples
>
>
>
> *From:* First Lego League in Virginia and DC [
> mailto:[log in to unmask] <[log in to unmask]>] *On
> Behalf Of *Amy Nichols
> *Sent:* Sunday, November 09, 2014 10:15 AM
> *To:* [log in to unmask]
> *Subject:* [VADCFLL-L] Thank you!
>
>
>
> I want to offer a huge thank you from The Ruling Robot Falcons to Karen
> Berger and all the organizers, judges, referees, and volunteers that helped
> put on the regional tournament in Newport News yesterday.  Our kids had
> such a fun time and I appreciate all the work that was put into it!  I
> think the referees were cheering for all the kids as much as the coaches
> were!  Thank you all!
>
>
>
> I also want to add a note about real Gracious Professionalism that
> happened for our team yesterday.  When we arrived at the school yesterday
> and our kids ran their robot on the practice boards, they discovered that
> nothing on their robot worked.  All their missions were dependent on the
> color sensor, which had was only randomly seeing certain colors.  They
> tried everything they could think of to fix it, but then got the idea to
> see if the other teams that had EV3's could help.  So they went around the
> room asking other teams if they had any ideas or knew how to calibrate a
> color sensor (one of the things they thought perhaps was wrong).   The
> other teams all stopped what they were doing to help our kids try to
> problem solve and help think of what could be wrong.  It was very apparent
> that these kids were not just there to win a tournament...but they really
> loved being there and wanted to help.  This just made me love FIRST/FLL
> even more than I already did, and realize just how great this organization
> is!
>
>
>
> Thank you all!
>   ------------------------------
>
> 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.
>

-- 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