31-05-2006, 13:25
|
 |
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
|
|
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,943
|
|
|
Re: VEX inputs
Quote:
|
Originally Posted by Damien1247
I would post them but i have been unable to write the code so it registered the encoders. Also, you seemed to be using easyC and i am using MPLAB. Using the sensor test code provided by vexlabs i was unable to make the encoders work. I put his down to the fact that i was attempting to use a grayhill op encoder. I am currently lookin into purchasing a pair of encoders from vex.
|
Damien,
The algorithm should be fairly independent of the encoder used (especially for straight-line motion). I am still interested....
Blake
PS: Private email works for me, if you want to avoid a public posting of incomplete results.
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|
Blasphemy! This is FRC we must over analyze everything! - Ginger Power [more] 
Similar Threads
Threaded Mode