|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Encoders Module?
Is there an "encoders module" that we may use to use an encoder in our robot?
By the way, thank you very much for the python scripts. We found it very useful so far. |
|
#2
|
|||
|
|||
|
Re: Encoders Module?
Quote:
|
|
#3
|
|||
|
|||
|
Re: Adams Coprocessor Solution
Sorry for the confusion... as soon as I get a chance I will get Bazaar and check it out.
|
|
#4
|
|||||
|
|||||
|
Re: Adams Coprocessor Solution
I plan to get working with this some starting tomorrow. I'm hoping that with the great boost that 245 is offering I will have some nice modules completed and available for later usage. Good luck everyone.
If anyone is wondering here's what we are using this year for a coproccessor: http://www.jkmicro.com/products/omniflash.html |
|
#5
|
||||
|
||||
|
Re: Adams Coprocessor Solution
Impressive, cuog!
For reference, soon some changes will be made to the code to protect some intellectual property. We're all in this together, after all. Once I make these changes, I will alert you all. There should be no significant changes in functionality. Thank you all for being so patient. (Note: The encoder modules are very old, and I haven't looked at them in a while. Use at your own risk, although I'd be more than willing to give you some support!) |
|
#6
|
|||
|
|||
|
PWM to velocity?
One more question about the encoder module..
I couldn't find the actual python code anywhere online... We have been able to set up the PID module for the power to each motor. The joysticks decide the value to be reached and the pwm values change until that value is reached. Our next task is how to use a velocity target value and connect that to the motor output (based on the error velocity value). We plan on doing this using potentiometers to determine the velocity...can anyone help us on somehow reaching the target velocity by altering the pwm output on the motors? |
|
#7
|
||||
|
||||
|
Re: Adams Coprocessor Solution
I'll scour around for some of the old encoder modules, although I don't recommend you use them just yet.
You intend to use potentiometers to figure out velocity? I would recommend that you use encoders to control velocity, as potentiometers deal more with position. However, if you would still like to use potentiometers, Post again and I can walk you through code to do so. Also, for reference, that application of PID is not terribly useful in any real application, although it is fine to test that PID functions. This is because to use a PID loop here is to match joystick output to voltage, which is already perfectly responsive. To add a PID loop only lowers this responsiveness. A more appropriate use of PID would be to match joystick input to velocity output on the motors given by encoders. In this way, you could move the joystick to a position to attain a given velocity, meaning even if there is some resistance against your robot, the PID loop would compensate for it (less driver control). |
|
#8
|
|||
|
|||
|
Re: Adams Coprocessor Solution
Thank you for the tip about the encoders.
We decided to match the joystick to the voltage only temporarily to test the PID loop, and until we had a way of measuring the velocity of the wheels. Our main problem is this: Once we have a set velocity based on the joystick, by how much do we increment the pwm to each motor to reach this velocity? The PID loop will tell us the error in the velocity and the correction value in terms of velocity right? How do we translate this in terms of change in pwm to each motor? |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Using Vex Brain as FRC Coprocessor | Tom Bottiglieri | General Forum | 25 | 18-04-2006 22:36 |
| VEX + Coprocessor? | ForgottenSalad | FIRST Tech Challenge | 4 | 13-04-2006 17:45 |
| Offboard coprocessor! | Ben Englert | Programming | 19 | 28-03-2006 18:34 |