Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   NI LabVIEW (http://www.chiefdelphi.com/forums/forumdisplay.php?f=182)
-   -   Encoders getting different rates (http://www.chiefdelphi.com/forums/showthread.php?t=103391)

jhellr13 20-02-2012 16:29

Re: Encoders getting different rates
 
Quote:

Originally Posted by tilky (Post 1131066)
ok so since they both work, but at different rates, the method i gave above will work.

Exactly. In my code right now I just have the distance per count set at 1 for both and they are both at 1X. I'm just going to lay out 10ft, push the robot, get the readouts for both, divide 10ft * 12 inches by the count for each side. Then I will have the distance per count for both. If that goes the way I think, both encoders will be in sync with each other afterwards. What do you think?

tilky 20-02-2012 16:31

Re: Encoders getting different rates
 
it sounds perfect. and this test will kill 2 birds with one stone; you will be able to find the counts per foot at the same time

jhellr13 20-02-2012 16:33

Re: Encoders getting different rates
 
Quote:

Originally Posted by tilky (Post 1131074)
it sounds perfect. and this test will kill 2 birds with one stone; you will be able to find the counts per foot at the same time

Great! Thanks for the help. See you guys next month at Hofstra

tilky 20-02-2012 16:36

Re: Encoders getting different rates
 
what school are you from?

Alan Anderson 20-02-2012 16:36

Re: Encoders getting different rates
 
Quote:

Originally Posted by jhellr13 (Post 1130938)
I'm not exactly sure of the entire model number as I don't have them in front of me, but I definitely know one is all Ds and the other has Ds and a H.

The letters don't tell you how many counts per revolution the encoder provides. That's in the numbers. The E4P encoders used on AndyMark gearboxes have a "250" in the part number that refers to the 1/4" shaft they go on, but they have another three-digit number that's the important one here. The KOP encoders have been 250 or 360 counts per revolution.

Find out what the full part numbers are and you'll probably see why one of them is reporting much smaller values.

jhellr13 20-02-2012 16:41

Re: Encoders getting different rates
 
Quote:

Originally Posted by tilky (Post 1131079)
what school are you from?

Comsewogue

tilky 20-02-2012 16:41

Re: Encoders getting different rates
 
ummm....where is that?

jhellr13 20-02-2012 16:42

Re: Encoders getting different rates
 
Quote:

Originally Posted by Alan Anderson (Post 1131081)
The letters don't tell you how many counts per revolution the encoder provides. That's in the numbers. The E4P encoders used on AndyMark gearboxes have a "250" in the part number that refers to the 1/4" shaft they go on, but they have another three-digit number that's the important one here. The KOP encoders have been 250 or 360 counts per revolution.

Find out what the full part numbers are and you'll probably see why one of them is reporting much smaller values.

That could be it. I'll look into it

jhellr13 20-02-2012 16:51

Re: Encoders getting different rates
 
Quote:

Originally Posted by tilky (Post 1131084)
ummm....where is that?

Suffolk county...

tilky 20-02-2012 16:52

Re: Encoders getting different rates
 
ok. i'm guessing you know where connetquot is, so see you there

Brandon_L 20-02-2012 17:46

Re: Encoders getting different rates
 
We had the same problem with ours. One side was giving reliable readings everytime, the other would give us some random garbage. We figured it out by manually rotating the axis the encoder was on by 1 revolution, and looking at the output, several times. They were very consistent, compared to the other side that would give us garbage. We looked at our wiring and found that the plastic clip the wires plug into was cracked and one of the signal wires was pretty much not connected. Pull it out and just check on it. After we replaced it, its been working fine.

If you rotate them one revolution and both sides are giving similar readings every time, then you can go ahead and scale them. For example if side A was giving you 140 and B was 360, you know that 140X=360. 360/140=~2.6. So you multiply the one side by ~2.6 to get them equal.


All times are GMT -5. The time now is 22:12.

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