Go to Post Backstabbing your opponents at the last second will not help you win friends and word will get around pretty quick. Your team will be shunned and distrusted for years. People have long memories, and some of us mentors have been playing this game since you kids were playing with blocks. - ChrisH [more]
Home
Go Back   Chief Delphi > Other > FIRST Tech Challenge
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
View Poll Results: Do you use Encoders on your DC motors?
Yes 7 58.33%
No 5 41.67%
What is an encoder? 0 0%
Voters: 12. You may not vote on this poll

Reply
Thread Tools Rating: Thread Rating: 5 votes, 5.00 average. Display Modes
  #1   Spotlight this post!  
Unread 04-11-2013, 20:22
DocMartin DocMartin is offline
Registered User
FTC #6285
 
Join Date: Nov 2012
Location: St. Louis
Posts: 9
DocMartin is an unknown quantity at this point
[FTC]: Motor encoders Love'em? or leave'em?

My fellow Mentor and I are at odds on using encoders or not.

I want to hear from you.

Does your team use them or not? and why?

Go!
Reply With Quote
  #2   Spotlight this post!  
Unread 04-11-2013, 20:57
MattRain MattRain is offline
AZ FTC AF, FTC #2844 and FTC #8640
FRC #1492 (Team Caution)
Team Role: RoboCoach
 
Join Date: Sep 2012
Rookie Year: 2008
Location: Chandler, Arizona
Posts: 322
MattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant future
Re: [FTC]: Motor encoders Love'em? or leave'em?

We love them. With the right code, they work wonders. We have code that allows us to move all the way up to a .001 of an inch, not that we need.. haha.
Reply With Quote
  #3   Spotlight this post!  
Unread 04-11-2013, 21:46
DocMartin DocMartin is offline
Registered User
FTC #6285
 
Join Date: Nov 2012
Location: St. Louis
Posts: 9
DocMartin is an unknown quantity at this point
Re: [FTC]: Motor encoders Love'em? or leave'em?

Can you provide some examples of what scenario you had the need to use them and what problem it solved?
Reply With Quote
  #4   Spotlight this post!  
Unread 05-11-2013, 22:35
ksafin's Avatar
ksafin ksafin is offline
Registered User
AKA: Kirill Safin
FRC #3992 (Eagles Robotics Xperience)
Team Role: Leadership
 
Join Date: Jan 2012
Rookie Year: 2012
Location: Delray Beach, FL
Posts: 498
ksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant futureksafin has a brilliant future
Re: [FTC]: Motor encoders Love'em? or leave'em?

I don't think this question can be asked so broadly.

They're hugely necessary in some instances, useless and redundant in others.

You should analyze your situations and decide what's best for it.
__________________
FTC Teams 5257, 6568 & FRC Team 3992
Eagles Robotics Xperience
2014 FTC WORLD CHAMPIONS
14 Trophies in 3 Years
Reply With Quote
  #5   Spotlight this post!  
Unread 06-11-2013, 07:00
Nemo's Avatar
Nemo Nemo is offline
Team 967 Mentor
AKA: Dan Niemitalo
FRC #0967 (Iron Lions)
Team Role: Coach
 
Join Date: Nov 2009
Rookie Year: 2009
Location: Iowa
Posts: 805
Nemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond repute
Re: [FTC]: Motor encoders Love'em? or leave'em?

I just wish the things weren't so insanely expensive and fragile.
Reply With Quote
  #6   Spotlight this post!  
Unread 06-11-2013, 14:35
ftcTeam6389 ftcTeam6389 is offline
Registered User
FTC #6389
 
Join Date: Oct 2013
Location: Eden Prairie MN
Posts: 39
ftcTeam6389 is on a distinguished road
Re: [FTC]: Motor encoders Love'em? or leave'em?

We've never had good luck with them, they are not accurate. Program it to go to the same spot every time, but it rarely does. I also agree they are too delicate. I just don't understand why Tetrix can't come out with a DC motor with a good encoder built in.
Reply With Quote
  #7   Spotlight this post!  
Unread 06-11-2013, 14:50
Madison's Avatar
Madison Madison is offline
Dancing through life...
FRC #0488 (Xbot)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1999
Location: Seattle, WA
Posts: 5,244
Madison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond repute
Re: [FTC]: Motor encoders Love'em? or leave'em?

Quote:
Originally Posted by MattRain View Post
We love them. With the right code, they work wonders. We have code that allows us to move all the way up to a .001 of an inch, not that we need.. haha.
How did you verify that your positioning was accurate to within .001"?
__________________
--Madison--

...down at the Ozdust!

Like a grand and miraculous spaceship, our planet has sailed through the universe of time. And for a brief moment, we have been among its many passengers.
Reply With Quote
  #8   Spotlight this post!  
Unread 06-11-2013, 15:42
aklego aklego is offline
Registered User
FTC #3595 (Schrödinger's Hat)
Team Role: Mentor
 
Join Date: Oct 2009
Rookie Year: 2004
Location: Alaska
Posts: 89
aklego is just really niceaklego is just really niceaklego is just really niceaklego is just really nice
Re: [FTC]: Motor encoders Love'em? or leave'em?

We avoid them for navigation and positioning of mechanisms. They are delicate, readings are unreliable, and they are bulky enough that they move the applied load out to the end of the motor shaft. That said, we used one with great success a few years ago. We had an arm that needed to move at a constant slow speed regardless of load or position. Adding an encoder changed that arm from unwieldy to elegant.
__________________
let tau = 2pi
Reply With Quote
  #9   Spotlight this post!  
Unread 06-11-2013, 15:44
ftcTeam6389 ftcTeam6389 is offline
Registered User
FTC #6389
 
Join Date: Oct 2013
Location: Eden Prairie MN
Posts: 39
ftcTeam6389 is on a distinguished road
Re: [FTC]: Motor encoders Love'em? or leave'em?

Quote:
Originally Posted by aklego View Post
We avoid them for navigation and positioning of mechanisms. They are delicate, readings are unreliable, and they are bulky enough that they move the applied load out to the end of the motor shaft. That said, we used one with great success a few years ago. We had an arm that needed to move at a constant slow speed regardless of load or position. Adding an encoder changed that arm from unwieldy to elegant.

I agree, there are times when you need them to control speed when under load. Another way to accomplish the same thing is to gear the arm down to 1:9 or some such.
Reply With Quote
  #10   Spotlight this post!  
Unread 08-11-2013, 02:43
RRLedford RRLedford is offline
FTC 3507 Robo Theosis -- FRC 3135
AKA: Dick Ledford
FRC #3135 (Robotic Colonels)
Team Role: Mentor
 
Join Date: Jan 2010
Rookie Year: 2009
Location: Chicago, IL USA
Posts: 286
RRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond repute
Re: [FTC]: Motor encoders Love'em? or leave'em?

We are doing a Mechanum drive for Block Party this year, using the very affordable VEX mechanum plastic hub wheels. We need the encoders to allow the mechanum drive controling S/W to function properly. BTW, for their price, these wheels work very well, if you can come up with a hub scheme for them that eliminates the tiny square shaft in favor of a sturdier one.

I agree that the Tetrix scheme for externally adding encoders is horrible, and exposes them to far too much stress and damage, usually in a very short amount of time. It forces gears & sprockets to be mounted further away from the motor gearbox, where they will tend to more easily & quickly damage it, or where they will cause the motor to shift position in the not-so-solid of a design TETRIX motor mount clamp.

Even when the encoders themselves are not internally damaged, the lack of a strain relief at the point where their wire assembly enters their micro-connector causes early failures of the wiring assembly there too.

When you combine the other TETRIX scheme for a motor with an eccentric output shaft as a way for adjusting gear & sprocket spacing, this adds even more problems for preventing the encoder wires from breaking at the connector, as the moter gets twisted in the mount clamp.

We have used urethane and silicone glue to make strain reliefs and to glue wires to side of motor case. we also use lots of ties to keep encoder wires out of harms way as much as possible.

The VEX motors with internal encoders are so much more appealing, but just too weak for most of our needs.

-Dick Ledford
__________________
FTC 3507 RoboTheosis
FRC 3135 Robotic Colonels

Last edited by RRLedford : 08-11-2013 at 09:17.
Reply With Quote
  #11   Spotlight this post!  
Unread 09-11-2013, 19:06
MattRain MattRain is offline
AZ FTC AF, FTC #2844 and FTC #8640
FRC #1492 (Team Caution)
Team Role: RoboCoach
 
Join Date: Sep 2012
Rookie Year: 2008
Location: Chandler, Arizona
Posts: 322
MattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant future
Re: [FTC]: Motor encoders Love'em? or leave'em?

Quote:
Originally Posted by DocMartin View Post
Can you provide some examples of what scenario you had the need to use them and what problem it solved?
For example for last years FTC. The robot sits in the corner of the field. Autonomous starts. IR turns on, finds out which column the IR is on, then picks out of three programs, which one to run to make it to the IR. Ok, say its the left column, robot makes a left 45 degree turn, goes 15 inches, right 45 degree turn, 20 or so inches forward, stops, lift goes up, which also has an encoder to tell it how many turns, to make it to that height, then 5 inches in, placing the ring on the peg, lift goes down a few inches, robot backs up 10 inches, does a 135 degree turn to face the ring dispenser. Ready for teleop.

With our code as well, I could move the robot to tile, carpet, concrete, asphalt, etc. And it would still do the same exact thing the program tells it to. Other than a few teams that I have seen with advanced code, most teams run off time, which with time, just with the wear and tear of some foam tiles, or brand new tiles, along with battery powered, wither fully charged, or somewhat charged, can change the autonomous sooooooo much.

If you write your code right, it works. With what we have written, it takes us less than a few minutes to write a code, or 30 minutes to write a very precise code. (and extremely easy once written. One of our new programmers, never seen code before, is writing the autonomous this year,(one day of teaching the basics) only having to list down how many inches,degrees turned,and lifting height)

Quote:
How did you verify that your positioning was accurate to within .001"?
The code is written in such a way, that it tells me on the NXT brick and computer screen, how far its traveled for each step it does, granted, there is no reason for that precision, especially this year, so we changed only go to the .1 of an inch really.

Last edited by MattRain : 09-11-2013 at 19:10.
Reply With Quote
  #12   Spotlight this post!  
Unread 09-11-2013, 19:23
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,124
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: [FTC]: Motor encoders Love'em? or leave'em?

Quote:
Originally Posted by MattRain View Post
The code is written in such a way, that it tells me on the NXT brick and computer screen, how far its traveled for each step it does
I don't think that answered the question Madison was asking.

There's a difference between what the sensor on your robot says and how far the vehicle actually moved.


Reply With Quote
  #13   Spotlight this post!  
Unread 09-11-2013, 19:50
MattRain MattRain is offline
AZ FTC AF, FTC #2844 and FTC #8640
FRC #1492 (Team Caution)
Team Role: RoboCoach
 
Join Date: Sep 2012
Rookie Year: 2008
Location: Chandler, Arizona
Posts: 322
MattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant future
Re: [FTC]: Motor encoders Love'em? or leave'em?

Quote:
Originally Posted by Ether View Post
I don't think that answered the question Madison was asking.

There's a difference between what the sensor on your robot says and how far the vehicle actually moved.


Ok, yes there is that fact of that robot could have gone a little under or over that number. Again, there really is no reason for programming that far, and hard to even get that measurement in real time, without looking at the computer. I was just stating the fact that the program could do it if it really wanted to. Right now in our programming, we do give a tolerance area for the code to decided if its in the right place without it getting stuck on a certain step. Its just stupid not to have your program run through all the steps because of a small.1 of an inch. I think right now, our programmer has it to a .1 or .15 of a tolerance, as there is really no need for huge precision this year, unlike last year with the pegs and such.
Reply With Quote
  #14   Spotlight this post!  
Unread 14-11-2013, 17:13
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,124
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: [FTC]: Motor encoders Love'em? or leave'em?

Quote:
Originally Posted by MattRain View Post
Ok, yes there is that fact of that robot could have gone a little under or over that number [ed: 0.001 inch]
As a pre-kickoff project, you might want to try this:

1) Command your robot to move exactly 20 feet forward and stop.

2) Using a tape measure, determine how far it actually traveled.

3) I think you may find the results surprising.


Reply With Quote
  #15   Spotlight this post!  
Unread 15-11-2013, 11:00
MattRain MattRain is offline
AZ FTC AF, FTC #2844 and FTC #8640
FRC #1492 (Team Caution)
Team Role: RoboCoach
 
Join Date: Sep 2012
Rookie Year: 2008
Location: Chandler, Arizona
Posts: 322
MattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant future
Re: [FTC]: Motor encoders Love'em? or leave'em?

I will have to students try that out today. I shall post the results tonight.
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 07:56.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi