KOP Gear Tooth Encoder Trouble

[Sykan]

I don't think it's my printf statement because I'm using kevin printf. and it's a con. zero.

The printf statment I made was to read the rc dig itself so I see if the variable is changing and since it's a dig input it can only change 0 to 1 and back again.

the pwm connected is connected correctly.

Any other guesses?

[Joe Ross]

Originally Posted by Sykan

I don't think it's my printf statement because I'm using kevin printf. and it's a con. zero.

The printf statment I made was to read the rc dig itself so I see if the variable is changing and since it's a dig input it can only change 0 to 1 and back again.

the pwm connected is connected correctly.

Any other guesses?

It takes longer to print a single character then the time the gear tooth sensor's output is 1. The chances that you would actually catch the output high is very low.

If you follow Alan's post about how to print a long, you should see it counting up.

Make sure you aren't using the bad board too. Read this post: http://www.chiefdelphi.com/forums/sh...ad.php?t=62856

[RyanN]

It could also be the problem that teams have been experiencing with the KOP gear tooth sensors. We connected both of ours up (one good, one bad) the good one worked fine, the bad one gave us a value of 1 after moving it for a while.

[fabalafae]

The printf works now; it wasn't the long int problem, it was something else. But anyway...

The encoder printf is now remaining stable at 2560 and fluctuating to 768 every few times.

And also it's the good encoder, not the bad one.

We have a big code problem: it's putting out 2560 and 768 and 0 and 5 (and other miscellaneous random values) WITHOUT as well as WITH the encoder connected...uhm...

Any ideas? Please?

[RyanN]

What version of Kevin's code are you using? We've had no problems with his code so far except stuff we did wrong. Make sure you have read the README's, as there are more steps to getting the sensors to work than you would think. We're using the version made for 3.0, and I really like it. Some things are simpler than I thought, like the Get_Analog_Value() function, all you have to do is put a number in... very simple. I would recommend using 3.0 if you're not using it already.

[fabalafae]

We're using the latest version of Kevin's code- and we downloaded it again, just to be sure. Yeah, the encoders still don't work.

I don't know what else we can try, but I guess we'll still be working on finding the problem this afternoon after school.