|
|
|
 As in life, the more restrictive the rules, the more creative the 'best' solution will be. - DonRotolo [more] |
 |
|
|||||||
|
||||||||
kiwi vex robot
here it is my true kiwi vex robot
what do you think?
Discussion
view entire thread
14-04-2006 14:50
Arkorobotics
Re: pic: kiwi vex robot
Woah, this is a smart design! It's small, and the structure doesn't look flimsy. How does it run?
Can you upload a video? I would like to show my friends the kiwi drive in action 
14-04-2006 14:52
Greg Perkins
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by TheNotoriousKid
how does it move forward
|
14-04-2006 15:36
Greg Needel
Re: pic: kiwi vex robot
colin,
does this mean you are going to enter the vex comp at the Ra Cha Cha this year?
Greg
14-04-2006 15:57
colin340
Re: pic: kiwi vex robot
it works like a champ with some code from Tom Bottiglieri it should be allot easier to control as for computation I will problem not but team 340 is working on starting a 9th grade team
thank you tom Bottiglieri and Greg Perkins for advise
14-04-2006 16:12
billbo911
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by colin340
it works like a champ with some code from Tom Bottiglieri it should be allot easier to control as for computation I will problem not but team 340 is working on starting a 9th grade team
thank you tom Bottiglieri and Greg Perkins for advise |
14-04-2006 16:24
Tom Bottiglieri
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by billbo911
With Tom's permission, could you possibly post the section of code that makes the magic work? PLEASE!!!!
|
Anyway, here's what you need to do to make it work:
PHP Code:
//Make sure variables are unsigned ints... rollovers WILL occur with signed ints
unsigned int trans_x, trans_y, rot;
//Grab inputs (x,y coords in rectangular coordinates and rotation rate)
trans_x = 254 - PWM_in1;
trans_y = 254 - PWM_in2;
rot = 254 - PWM_in4;
//Limit vector length to 127
trans_x = (unsigned int)(37+(254*trans_x)/359);
trans_y = (unsigned int)(37+(254*trans_y)/359);
//Assign and limit wheel outputs
wheel_1 = (unsigned char)limit( (((2*trans_x) + rot) / 3), 0, 254);
wheel_2 = (unsigned char)limit( ((601 + rot - trans_x - (168*trans_y/97)) / 3), 0, 254);
wheel_3 = (unsigned char)limit( ((161 + rot - trans_x + (168*trans_y/97)) / 3) , 0, 254);
PHP Code:
signed int limit(signed int value, signed int min, signed int max)
{
if (value < min)
{
value = min;
} else if (value > max)
{
value = max;
}
return value;
}
)
14-04-2006 16:50
billbo911
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by Tom Bottiglieri
Well credit needs to be given where it's deserved. I got the equations for my kiwi code from the living genious, Joel Johnson.
Anyway, here's what you need to do to make it work: PHP Code:
PHP Code:
) |
) so much!!The problem is, now I have to go buy some omni wheels for this weekends project
BTW. Do you know how the constant values were determined (ie. 37, 359, 601, 168, 97, 161)? Also, I see you are using PWM_in4 for the rotation value. I assume this is off the left stick X-axis. Knowing these can help me modify this stuff for future projects.
Thanks again!!!!
14-04-2006 16:54
s_forbes
Re: pic: kiwi vex robot
I like that design! It's so compact and sturdy, good job!
14-04-2006 16:58
colin340
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by s_forbes
I like that design! It's so compact and sturdy, good job!
|
15-04-2006 14:10
billbo911
Re: pic: kiwi vex robot
I just got this working this morning. I tried for hours last night to code it with EasyC. Apparently doing the math wasn't so easy with EasyC. 
I'll figure it out later today. What you see it the video is coded with MPLAB in about 20 minutes.
Vex Kiwi Drive
15-04-2006 15:39
Steve0100
Re: pic: kiwi vex robot
Very nice design!
There seem to be many variations of Vex holomic robots out there, probably because they are so fun to drive. Here's the beginnings of my first Vex bot, thanks to the RS sale:
Here's the underside:
My goal was to design a robot as clean and symmetrical as I could. It took one Starter kit and an additional hardware kit. The orange spacers in the motor mount bracket are the only non-vex parts, from an Erector set. They are conveniently in-between sizes of the vex plastic spacers.
To avoid having to support the axles on the outer sides of the wheels, I set back the motor with these spacers to allow a collar to hold in and support the axle on the motor side inside the bracket.
I've added sensors and have devised a scheme (still in the process of Implementation ) to have the robot detect walls and "bounce" off them before hitting with an angle of reflection equal to that of the angle of incidence. I'd like to put it inside a boxed-in area and have it bounce around like an billiard ball for robotics demos.
15-04-2006 16:09
billbo911
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by Steve0100
Very nice design!
I've added sensors and have devised a scheme (still in the process of Implementation ) to have the robot detect walls and "bounce" off them before hitting with an angle of reflection equal to that of the angle of incidence. I'd like to put it inside a boxed-in area and have it bounce around like an billiard ball for robotics demos. |
I really like how clean your assembly looks!
On sensors.... from my experience with the the Vex Ultrasonics.
They do a good job of sensing objects directly in front as long as object has a surface that is perpendicular to the sensor. In other words, when approaching a wall at an angle, the sensor wont pick it up very well at all.
Additionally, if you do put your bot in a box, the walls will bounce the 40KHz signal pulses quite a bit, causing misreadings from the controller.
Here's a thought. Try using the light sensors from the Line Following kit. With a little experimentation, you should be able to fine tune an algorithm to detect the relative distance from the wall based on the amount of light being reflected off of it. The biggest problem you will face with that is consistent light levels, and that may render this option useless. (Remember the difficulties with the CMU cam. and reflected light in 2005?)
15-04-2006 16:31
Joel J
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by billbo911
Now I know why I like Tom (oh yeah, and Joe too
) so much!!The problem is, now I have to go buy some omni wheels for this weekends project BTW. Do you know how the constant values were determined (ie. 37, 359, 601, 168, 97, 161)? Also, I see you are using PWM_in4 for the rotation value. I assume this is off the left stick X-axis. Knowing these can help me modify this stuff for future projects. Thanks again!!!! |
Code:
'KIWI Code Overview '------------------ ' 'Vx, Vy, and w are on the interval [-127, 127], but the inputs p2_x, p2_y, p1_x are on the interval [0, 254], 'so we compensate by setting Vx, Vy, and w to the shifted version of the input: ' ' trans_x = p2_x ' trans_y = p2_y ' rot = p1_x ' ' Vx = trans_x - 127 ' Vy = trans_y - 127 ' w = rot - 127 ' 'The kiwi system is characterized by the equation: ' ' [ Vx ] [ 1 -1/2 -1/2 ] [ V1 ] ' [ Vy ] = [ 0 -sqrt(3)/2 sqrt(3)/2 ] [ V2 ] ' [ w ] [ 1 1 1 ] [ V3 ] ' ' [1x3 matrx] = [3x3 matrix] * [1x3 matrix] ' 'where L is a length constant, Vx, Vy, and w are the system translation velocity components, and the system 'angular velocity, and V1 is the wheel velocity vector at angle 0 degrees, V2 the wheel velocity vector at 'angle -120 degrees, and V3 the wheel velocity vector at 120 degrees. ' 'Solving this system for V1, V2, and V3 yields the following equations of motion: ' ' V1 = (2Vx + w) / 3 ' V2 = (-Vx - SQR(3)*Vy + w) / 3 ' V3 = (-Vx + SQR(3)*Vy + w) / 3 ' '(NOTE: These equations operate on the assumption that the magnitude of the desired velocity vector can be 'no greater than 127. That is, the hypotenuse of the triangle formed by the trans_x and trans_y variable 'cannot exceed 127. To ensure that this condition is met, one has to convert the rectangular 'coordinates (trans_x, trans_y) into polar coordinates (V_desired, theta), limit V_desired to 127, then 'back-calculate the new values of trans_x and trans_y based on the new value of V_desired and the already 'existent theta. The code that does this has been placed exactly before this large block of text.) ' '(NOTE: UPDATE! The Basic Stamp doesn't like the math required to make the previous note a reality, so I 'am using a crude solution: I scale down all input values by 127*SQR(2) to ensure that the largest vector 'magnitude doesn't exceed 127.) ' 'The output from each equation (V1, V2, V3) is on the interval [-127, 127], but the desired outputs, 'drill_1, drill_2, drill_3 are all on the interval [0, 254], so we compensate by setting drill_1, drill_2, 'and drill_3 to the shifted version of V1, V2, and V3: ' ' drill_1 = V1 + 127 ' drill_2 = V2 + 127 ' drill_3 = V3 + 127 ' 'And that's it! Plug in all the variables, and we end up with the equations of motion that follow '(note: fractions were expanded out to compensate for the integer based calculation done by the stamp): 'Motion equations
15-04-2006 17:05
Steve0100
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by billbo911
Thanks.
I really like how clean your assembly looks! On sensors.... from my experience with the the Vex Ultrasonics. They do a good job of sensing objects directly in front as long as object has a surface that is perpendicular to the sensor. In other words, when approaching a wall at an angle, the sensor wont pick it up very well at all. Additionally, if you do put your bot in a box, the walls will bounce the 40KHz signal pulses quite a bit, causing misreadings from the controller. Here's a thought. Try using the light sensors from the Line Following kit. With a little experimentation, you should be able to fine tune an algorithm to detect the relative distance from the wall based on the amount of light being reflected off of it. The biggest problem you will face with that is consistent light levels, and that may render this option useless. (Remember the difficulties with the CMU cam. and reflected light in 2005?) |
Thanks, and thanks for the sensor feedback. I did consider Ultasonics, but couldn't hit on a scheme I thought would be reliable. Your info on the ultrasonics and performance at oblique angle confirms that I would have had a lot of problems. So- I'm using IR, very close proximity sensors, and a timing algorithm to detect differences in IR triggering in relation to angle of approach. I also have a mechanical switch backup plan- but I'd rather keep it clean with no real contact with the walls.
Thanks again for your reply. Billbo and Colin, your designs are both inspirational. Colin- I'll put your method of joining chassis parts with bearing blocks in my mental toolkit- I'm new to vex so I appreciate seeing new uses for the parts. It's amazing what can be done with, and learned from from, common creative constraints.
I'm glad I'm contending with 4-wheel math for holonomics rather than 3 though- much simpler. Thanks, trig.
15-04-2006 18:51
billbo911
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by billbo911
I just got this working this morning.
I tried for hours last night to code it with EasyC. Apparently doing the math wasn't so easy with EasyC. I'll figure it out later today. What you see it the video is coded with MPLAB in about 20 minutes.Vex Kiwi Drive |
16-04-2006 00:50
Francis-134
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by billbo911
As I mentioned earlier, I was working on getting this coded using EasyC v2.0. Well I finally got it working. The math is the same, the process is a little different, but it works. Oddly, the bot works smoother with the code done in MPLAB than it does with the code from EasyC. Anyway, I'm attaching the .hex, .bds and .ecp files from EasyC in the hopes someone else can use them. They are in a .zip file, so download and do what you will with them.
|
16-04-2006 02:54
billbo911
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by Francis-134
I noticed that your code uses a lot of custom c blocks to do the math. May I suggest using the "assignment" block, located in program flow in order to cut down on the labor. Perhaps it will work better as well.
|
Logically speaking, the code should run the same whether I code it in MPLAB or EasyC. Realistically, I just need to figure out how to do it correctly in EacyC.
Thanks again!!
BTW, do you know if there are any detailed tutorials for EasyC 2.0? I found the programing guide for 1.1 quite helpful, but a little short on covering all options.
16-04-2006 09:03
Francis-134
Re: pic: kiwi vex robot
Indeed there is a very nice tutorial. Unlike most programs, the help file of easyC has been worked on quite a bit and is an excellent resource for any questions regarding the software. The file explains what every block and more. Whats real nice is if you have a problem with a specific block while you are trying to program with it, simply drag it into the program and hit "help".
Oh, and there are some tutorials in the help file, but I believe the first few are the same as what came with your programming guide.
19-04-2006 00:32
billbo911
Re: pic: kiwi vex robot
Quote:
|
Originally Posted by Francis-134
Indeed there is a very nice tutorial. Unlike most programs, the help file of easyC has been worked on quite a bit and is an excellent resource for any questions regarding the software. The file explains what every block and more. Whats real nice is if you have a problem with a specific block while you are trying to program with it, simply drag it into the program and hit "help".
Oh, and there are some tutorials in the help file, but I believe the first few are the same as what came with your programming guide. |
Quote:
|
Originally Posted by Francis-134
I noticed that your code uses a lot of custom c blocks to do the math. May I suggest using the "assignment" block, located in program flow in order to cut down on the labor. Perhaps it will work better as well.
|
EDIT: I just double checked this file. It appears that I didn't save my changes, so, these files are the old version.
My BAD!!!! I will correct this as soon as I re-create the files correctly. Please stay tuned.EDIT2: OK, I've replaced the files with the corrected versions. Sorry to anyone who tried the previous ones. These new files were updated to CD on 4/19/06 at 4:25pm PDST
19-04-2006 13:45
jgarbers
Re: pic: kiwi vex robot (slightly OT)
Quote:
|
Originally Posted by billbo911
What you see in the video is coded with MPLAB in about 20 minutes.
|
Thanks!
19-04-2006 14:48
billbo911
Re: pic: kiwi vex robot (slightly OT)
Quote:
|
Originally Posted by jgarbers
If I may ask - are you using the "Student Version" of the C18 compiler with MPLAB? If not, what compiler are you using? I'm trying to figure out what's appropriate to buy above and beyond what comes with the stock Vex Programming Kit... I've already bought the easyC v2 upgrade, but I'd like to be able to just edit source code.
Thanks! |
I am one of the more impatient people in this world. I couldn't wait for the programming kit to be released through Radio Shack. So, when I found out that there was a possibility to purchase a prototype programming module directly from IFI , I jumped at it. It came with the cables, circuit board (unhoused) and a C-BOT CD which included MPLAB 7.0, C18 and IFI loader. These are all licensed to me and not part of my FRC teams programs. I have since then upgraded all three applications to the most current versions that work with FRC, and they still work with Vex. This allows me to use my laptop with the team to help them in programming and fiddle around with my Vex system as well.
I added EasyC when I bought the kit on sale, then later purchased the 2.0 upgrade. Now I can program in either environment. Honestly, I really like EasyC, it is amazingly powerful for a module based programming environment and is extremely easy to teach noobs the basics of robot programming. I can quite literally have a complete novice programming a Vex bot to work autonomously in less that ten minutes. On the other hand, MPLAB offers a lot more flexibility and advanced programming ability. I am not versed well enough in C to use MPLAB exclusively, but I have to admit, I can do some things in MPLAB much faster than I can with EasyC.
So, what do I recommend? Definitely keep EasyC. Only add MPLAB/C18/IFI Loader when you have mastered the use of EasyC and started running into limitations that require you to program directly in C. I know others will have different opinions, and listen to what they say as well. I base mine on my experience and knowledge level in programming. Weigh others opinions on their experience and ability as well. That will give you the truest measure of "What you should do".
19-04-2006 15:00
jgarbers
Re: pic: kiwi vex robot (slightly OT)
Quote:
|
Originally Posted by billbo911
Excellent question...
|
I suspect it's possible to compile and download "manually-edited" C code using everything that comes with easyC -- it seems to be running an external compiler during its build step -- but I have a little more experimenting to do. I've been coding for over 25 years and the drag-the-block approach seems to get in my way, although my kids seem quite comfortable with it. Maybe they'll just use easyC the way it's intended and I can try messing around under the hood in my "copious free time".... then I'll figure out if I can justify MPLAB (which looks very nice, by the way... the free IDE is quite the "gateway drug" for the rest of the product line).
01-10-2012 18:57
adam the great
Re: pic: kiwi vex robot
This code helps a lot. Me and Casey Godzyk (current 229 members) have been resurrecting the old Kiwi bot and updating the hardware and we happened to find this code...Then later realized that we were basing our new code off of the actual original code from this robot. Can't wait to be able to post pics and video of it all updated and rebuilt (hopefully with underglow).
view entire thread
previous
next
Tags
loading ...
All times are GMT -5. The time now is 10:36.
The Chief Delphi Forums are sponsored by Innovation First International, Inc.