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:
Re: Improving reliability and repeatability
From:
Daniel Pedersen <[log in to unmask]>
Reply To:
Daniel Pedersen <[log in to unmask]>
Date:
Sun, 10 Nov 2019 10:10:50 -0500
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (2956 bytes) , text/html (4 kB) 
The most reliable way for the robot to perform tasks on the mat is to use sensor feedback, using color, light, touch and gyro sensors. 
It’s more complicated but a good combination of mechanical and programming solutions will give the most reliable solutions

Sent from my iPhone

> On Nov 10, 2019, at 10:03 AM, Skip Morrow <[log in to unmask]> wrote:
> 
> 
> The most reliable and repeatable way to move from point to point is to use mechanics wherever you can. Wall following is a great example. This year wall following is difficult, but it is possible. 
> 
> Also, try looking for things on the mission model itself that lends itself to helping the robot. We like to make funnels for our attachments to help align the robot to a mission model. See the high-resolution photograph I have a attached :)
> 
> Remember, the most reliable solution will almost always be a mechanical solution. Look for the very best possible mechanical solution and then start programming.
> 
>> On Sat, Nov 9, 2019 at 10:13 PM Leyla Nazhand-Ali <[log in to unmask]> wrote:
>> Good evening,
>> 
>> As a rookie coach, I have a general question for the community: what is the most reliable and repeatable way to go from point A to point B using Ev3 (FLL robot)?
>> 
>> I know there is a method to use actual motor rotation counts. I also know we can use a gyro sensor. Any advantages or disadvantages for each of these methods?
>> 
>> We have two related problems: 1) our navigation program doesn’t behave similarly a few days later or on a different table. 2) a backup robot we built doesn’t run the same programs in a similar way to our original robot even on the same table and almost the same time. In other words, our solutions are not robust. 
>> 
>> I know this is a very broad question that probably touches upon various topics. However, I appreciate if the other coaches point me to good resources or share their wisdom with me. 
>> 
>> Thanks,
>> Leyla
>> 
>> -- 
>> Sent from my iPhone
>> 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.
> <RobotFunnel.png>

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