Go to Post I've learned that the measure of success isn't the money you make, the education you get, or the car you drive. Your success can only be measured in the amount of people in whose lives you've made a difference and the size of your heart. - Amanda Morrison [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

 
Reply
 
Thread Tools Rating: Thread Rating: 4 votes, 5.00 average. Display Modes
  #1   Spotlight this post!  
Unread 19-05-2006, 12:05
Andrew Schreiber Andrew Schreiber is offline
Joining the 900 Meme Team
FRC #0079
 
Join Date: Jan 2005
Rookie Year: 2000
Location: Misplaced Michigander
Posts: 4,074
Andrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond repute
Re: VEX inputs

I am attempting to play with pots but for some reason the pot reads a constant value even when it isnt plugged it. Im going to play with it today during class and ill post a result here before i leave today.

I am just trying to show a proof of concept and this will by no means be a finished product.

Also does anyone know if I could run the grayhill op encoders on a vex robot?? I am doing this to prove out concepts for our first team next year.
Reply With Quote
  #2   Spotlight this post!  
Unread 20-05-2006, 10:34
skimoose's Avatar
skimoose skimoose is offline
Parent/Mentor/Engineer
AKA: Arthur Dutra
FRC #0228 (GUS)
Team Role: Electrical
 
Join Date: Jan 2005
Rookie Year: 2003
Location: Meriden, Connecticut
Posts: 568
skimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond reputeskimoose has a reputation beyond repute
Re: VEX inputs

Quote:
Originally Posted by Damien1247
I am attempting to play with pots but for some reason the pot reads a constant value even when it isnt plugged it. Im going to play with it today during class and ill post a result here before i leave today.
If you're getting a constant value even when the pot isn't "plugged in", you're reading the value across the coil. The analog value should be taken, and read across one side of the coil and the wiper terminal. The pot should be wired to the vex controller like this:

pot coil
+5V ____/\/\/\/\/\/\/\______ GND
|
wiper
|
SIGNAL

The pot coil leads are almost always the outside two terminals and should always read 100K ohms, or 5 volts if energized, across them. The wiper terminal is almost always the center terminal. If you measure resistance across the +5V and Signal the value will change as the pot is turned. If the pot is energized, you should be measuring a variable voltage across +5V and Signal. If you are wired correctly, and you are not getting the correct values, then the pot is failed, or you're not using a 100K pot. Correct wiring is +5V red PWM wire, signal white PWM wire, and GND black PWM wire. as the cable comes off the Vex controller's analog input.

Hope this helps.
__________________

2009 CT Regional Motorola Quality Award
2010 VRC Connecticut Championship Winners & Amaze Award
2010 VRC Championship Divisional Energy Award
2010 WPI Regional Winner
2010 WPI Regional Engineering Inspiration Award
2011 WPI Regional Chairman's Award
2012 WPI Regional Finalists
Reply With Quote
  #3   Spotlight this post!  
Unread 30-05-2006, 23:11
gblake's Avatar
gblake gblake is offline
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,940
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: VEX inputs

ChrisH & GDeaver,

I would appreciate seeing your control algorithms/equations or your code that uses shaft encoders to supply feedback for controlling your Vex bots paths.

I am dabbling with the same thing right now and mine is both wobbly and biased.

Right now I attempting to have both sides maintain 50_tick / 100_msec speeds and I am using 5:1 gearing to make the the encoder count 450 ticks for each revolution of the drive motor.

Because I am think I am getting different response characteristics from my motor(s) when I compare driving them CW vs driving them CCW (see below), I think I am ultimately up against writing some semi-complicated trig equations/approximations. Maybe I am thinking too hard...

I am adjusting the bot's speed by just incrementing/decrementing the EasyC command sent to each motor depending on whether that motor's encoder counted more or less than 50 ticks during a 100 msec EasyC "wait"; and depending on whether that motor is already slower or faster than the other motor.

The slow reads of the encoders Gdeaver hypothesized could be one problem I face.

Another problem might be that (contrary to what I read on in the VexLAbs fora) the motors react differently to commands that are identical except for direction (i.e. sending 127+70 produces a different RPM magnitude from a motor than sending 127-70). That means that starting my left and right motors at values that will produce (nearly) identical RPMs is a matter of holding your tongue in the right place; and furthermore, that incrementing the input to the CW one will produce a different change in output (for that one) than does decrementing the input to the otherwise symmetrical CCW motor on the other side of the bot.

I admit, the assertions in the paragraph above are generalizations from measurements I took on ONE motor while the bot was up on blocks.

I graphed the motor transfer function results (encoder ticks over ten consecutive 100 msec intervals) vs input value) in Excel if anyone wants to compare my results with any other measurements.

Does anyone else have any motor measurements to share? In addition to wanting to combine the fun of implementing my own ideas with not re-inventing too many wheels (see request above for sample algorithms), I am curious if I got unlucky with the one motor I measured; or if there is a pattern we should measure carefully and report in an appropriate FVC thread.

Blake
PS: Should we transfer this discussion to the Vex Shaft Encoder Kit thread???
__________________
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
Reply With Quote
  #4   Spotlight this post!  
Unread 31-05-2006, 11:45
Andrew Schreiber Andrew Schreiber is offline
Joining the 900 Meme Team
FRC #0079
 
Join Date: Jan 2005
Rookie Year: 2000
Location: Misplaced Michigander
Posts: 4,074
Andrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond repute
Re: VEX inputs

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.
Reply With Quote
  #5   Spotlight this post!  
Unread 31-05-2006, 13:25
gblake's Avatar
gblake gblake is offline
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,940
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
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
Reply With Quote
  #6   Spotlight this post!  
Unread 31-05-2006, 18:17
Andrew Schreiber Andrew Schreiber is offline
Joining the 900 Meme Team
FRC #0079
 
Join Date: Jan 2005
Rookie Year: 2000
Location: Misplaced Michigander
Posts: 4,074
Andrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond repute
Re: VEX inputs

Oh no. im always a fan of posting work, complete or incomplete. The problem is i dont have any writen. I was doing proof of concept for a class. nothing that would be usable, just to make sure it could be done.

Though to make the 'bot drive in a straight line id think youd need two encoders. each time either of them is triggered you would add one to that wheel's count. Now, to make sure that it ran in a straight line i would use a timer to determine the rate at which you are calling interupts (dont ask me how to but i have a hunch it is in the pic18 ref manual ill look into it more after i finish my report on spam)

If i get time i will most definetly write up some code. I cant garuntee it will work or will be correct but i recall we wrote something using the hall effect sensors for the FRC game this year. I will look into it and ill keep in touch with you. .
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

Similar Threads
Thread Thread Starter Forum Replies Last Post
Useful VEX Tools Joe Johnson FIRST Tech Challenge 4 26-04-2005 18:48
Vex Robotics Vex FIRST Tech Challenge 0 14-04-2005 13:48
VEX Robotics vexrobotics FIRST Tech Challenge 8 30-03-2005 23:25
VEX Kits ARRIVED!!! Joe Johnson FIRST Tech Challenge 14 28-03-2005 19:28
digital inputs not valid just after initialization? WizardOfAz Programming 2 26-01-2004 13:21


All times are GMT -5. The time now is 18:09.

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