Dimensions: 17.9" x 22.25" x 4.6"
Also I had to shrink the image from its original to get it to upload to CD, So here is the link to the original file. Original Res: 3840x2160
http://polynomic3d.com/user/smith/Andrew%20Swerve.png
Render Credit: Cody Smith
As always Questions, Comments, Concerns are always welcome
This makes it all click. Very nice design (and render)
Everytime I see a new swerve drive design on CD I just wanna build one even more so…
One of these days…
There’s your problem. Use JPG, not PNG, for renders.
I cropped the 45MegaByte PNG pic and converted to JPG and reduced the filesize by a factor of 200 with no perceptible loss of quality.
Yep. They are quite complicated, but pay off in the end, especially if you can get them light enough. By the way, Great design.
Now, for me:
Design and build a swerve drive vex robot to take to competitions! I’d like to see how that would work out 
I think it’d be helpful to see an exploded view of one of the modules so that it’s clearer how they’re designed and assembled. Any chance of that happening?
I can work on one yes, no guarantees on the time it’ll take to get to it though.
Design and build a swerve drive vex robot to take to competitions! I’d like to see how that would work out
Who’s to say I haven’t already done so? 
No, no, in actuality The amount of motor resources I’d like to dedicate to drive is far from optimal so as far as the rules remain the way they are I will not be building a swerve in VEX.
Ya. That would indeed be a bad idea, especially after I just finished a holonomic chassis that requires 4 motor ports, not 8. Also, there is a motor quota of ten, so that would be 4/5ths of my quota!
I’d like to keep some outputs for my cool scanning distance sensor and it’s moving mount!
This is awesome, I think smaller 2.5-3.5" wheels are going to start being more “common” for FRC use. I agree an exploded view would really help to understand what all is going on in there.
Also what program did you use to make this render? It’s beautiful!
If I weren’t using WiFi, I would have killed my data plan!!! That reminds me when I saved a GIMP picture as HTML and the filesize was over 250MB! Crashed my computer the first time I tried to do it!
What program was this rendered with?
SolidWorks
I’m pretty sure this is not solidworks. Andrew uses inventor so this being solidworks would make no sense. I am pretty sure this is 3ds max
This was rendered in 3ds Max by my friend and animator Cody Smith. I am slowly learning how to do something like this, but he is far more knowledgeable in this regard. Plus I am helping keeping his house warm since there are 5 (I think) i7s that crunch all the data for one render, and its 30 degrees in Colorado currently.
I also only have one i7 processor at my disposal instead of an entire render farm so it would take me a couple days to actually pull something off like this.
Maybe I’m missing something. VEX offers a swerve drive kit; one could easily be built with 5 or 6 motors.
This is incredibly well done. I hope you put the CAD up so others can see what you did. I’m trying to teach the new freshman to Cad and this is the perfect example of what I hope they can do someday.
Yes I am aware of this fact but the level of dexterity and flexibility required by NARs robot designs needs something far more space efficient. We have yet to find a decent acceptable way of doing a swerve without adding lots of interestingly complex mechanisms to allow us to get the same performance out of a swerve compared to one of our x holo drives or tank drives.
I’ve been wanting to build a vex swerve for a while and I’m sure it will be done eventually just so far we haven’t been happy with our solutions to the problem yet.
Sorry, my comment wasn’t meant toward the OP. It was directed toward the people who were asking about swerve use in VRC.
Any idea what the weight would look like for this?
This set up here is roughly 37 lbs (including some left electronics left out of the render) Those electronics consisted of enough talon motor controllers to power the machine. They were removed because polygon counts were through the roof.
