![]() |
pic: Sparto the Waldo
|
Re: pic: Sparto the Waldo
Now it just needs a mini-rack to score on (maybe with mini-tubes?)
|
Re: pic: Sparto the Waldo
Great work!
Do you have a cad drawing or pdf drawings for your design. In addition, do you also a a schematic of the controls and wiring. This would be a great tool for any team to use for arm manipulator controls.:cool: |
Re: pic: Sparto the Waldo
Quote:
|
Re: pic: Sparto the Waldo
This makes me soooo happy. Great idea!
|
Re: pic: Sparto the Waldo
Very cool !!!
Let me guess... you also have a set of red bumpers? |
Re: pic: Sparto the Waldo
We almost did that this year. We had done something similarly in a previous year, and thought that maybe we should do it again. We used pre-set heights for each peg instead.
|
Re: pic: Sparto the Waldo
Quote:
Quote:
|
Re: pic: Sparto the Waldo
How did you code this? We use C++ on our bot and it seems like what you would have to do is set the setpoint of a PID loop to the value of the analog inputs on the model. Could you post the code that you wrote for this? And does it require any programming on the Cypress module?
|
Re: pic: Sparto the Waldo
If I were to program it, I would probably:
1. Take the inputs from the Cypress board (in Teleop.vi) and scale them to some sane units (degrees, radians, etc.), probably by taking the volts in, subtracting a known centerpoint (0 would probably be straight out or vertical, you pick but be consistent), and then multiplying the volts from center by a constant. 2. Send the scaled numbers off to another thread to be processed 3. Said other thread would take the units, and lookup the appropriate scaling on this robot (meaning, the competition or practice robot), and take the analog sensors on the robot and scale the inputs to the same units (with the same 0-point) 4. A P-controller would run in said thread, taking numbers of sane units from 1 and sensors of same sane units from 3 and determining the motor output for each joint. I have actually never used anything but P, because I have not yet found the need for any other terms. If you do a lot of trig processing (maybe for gain scheduling or elsewhere), storing the value in radians makes everything cleaner. If you want to use stored positions (say, for autonomous), you can store them in radians, so if the sensor calibration changes, it doesn't affect any other code. |
Re: pic: Sparto the Waldo
Quote:
Quote:
Code:
public class Arm { |
Re: pic: Sparto the Waldo
Hey frasnow,
Are you guys going to the Championships? |
Re: pic: Sparto the Waldo
Quote:
|
Re: pic: Sparto the Waldo
My team had discussed making a control system like this, but we found that we didn't have the time, and a simple gamepad served adequately. However, I'm really glad to see one of these actually have been made! Nice work!
|
Re: pic: Sparto the Waldo
wow this is really quite clever
|
| All times are GMT -5. The time now is 12:27. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi