|
|
|
![]() |
|
|||||||
|
||||||||
People really like to say that you can't do 6 week swerve without the swerve turning out janky or it having a large negative impact on the rest of your robot, so naturally my team is trying it.
Just to get all the basic questions/warnings out of the way:we know that it's kinda risky so we do have hard deadlines that if we miss swerve is dead. In the past we've had one programmer who programs all robot function, this year we had a 4th year frc programmer transfer to our team. His only job this build season is to program and tune the swerve on a seperate test bed. None of our strategy revolves entiely around the swerve, if we get locked into crab drive due to full swerve being too much of a problem to program that wouldn't be a big hit on robot function. My only job this build season was to design the swerve, and get it finished mechanically, once that's all done i'll head off and help another sub-team.
soooo yea 6 week swerve it'll work or it won't but i'm excited to see what happens
21-01-2015 14:27
orangemoore
21-01-2015 14:28
lukedude43None, programmer made some swerve code for fun and I had been toying around with the idea in the offseason but everything was started fresh on everything when the season started
21-01-2015 14:35
Out of curiosity (if you don't mind me asking) - what was the thought process behind deciding to choose swerve for the first time in-season this year?
21-01-2015 14:36
AustinHI wonder if the game this year is at all conducive to taking these sorts of risks. We've been able to spare some individual team members for tackling quite a few of these "don't try this during build season" projects. For some reason, it seems like a more favorable risk/reward scenario compared to previous years in case we don't end up checking off all the boxes.
Looking forward to seeing how this turns out for you guys!
21-01-2015 14:41
Christopher149|
Out of curiosity (if you don't mind me asking) - what was the thought process behind deciding to choose swerve for the first time in-season this year?
Spoiler for I want everyone moving this season:
|
21-01-2015 14:48
lukedude43|
Out of curiosity (if you don't mind me asking) - what was the thought process behind deciding to choose swerve for the first time in-season this year?
Spoiler for I want everyone moving this season:
|
21-01-2015 14:55
Navid Shafa
21-01-2015 14:55
lukedude43
21-01-2015 15:49
asid61If that bottom is a single piece, you will want to add a radius on the inner edges on the top.
How thick is the bottom plate? It looks pretty thin right now.
How are you constrianing the bevel gears on that shaft? How are you constraining the other gears?
Your top plates are too thin. It looks like it's 1/8" at most. Make it 1/4" to be really safe.
I LOL'd at that gear on the top. I assume that's a versakey gear with 3/8" hex bore like I ised on my drill press verson.
You need some thrust bearings on the module to support the vertical loads. This year more than ever it's going to be turning under a lot of load.
All things considered I would not do a swerve drive fresh out of the box. Please consider buying something like a premade team 221 revolution module and just belting some motors to it.
21-01-2015 16:14
lukedude43|
If that bottom is a single piece, you will want to add a radius on the inner edges on the top.
How thick is the bottom plate? It looks pretty thin right now. How are you constrianing the bevel gears on that shaft? How are you constraining the other gears? Your top plates are too thin. It looks like it's 1/8" at most. Make it 1/4" to be really safe. I LOL'd at that gear on the top. I assume that's a versakey gear with 3/8" hex bore like I ised on my drill press verson. You need some thrust bearings on the module to support the vertical loads. This year more than ever it's going to be turning under a lot of load. All things considered I would not do a swerve drive fresh out of the box. Please consider buying something like a premade team 221 revolution module and just belting some motors to it. |
21-01-2015 23:29
nathannfmPut your module into the CAD of the field right at the transition between the carpet and the scoring platform. Rotate the module as it would if the steering motor was rotating it, will that low ground clearance gear run into the ramp in any orientation? Looks to me like it will.
22-01-2015 02:33
lukedude43|
Put your module into the CAD of the field right at the transition between the carpet and the scoring platform. Rotate the module as it would if the steering motor was rotating it, will that low ground clearance gear run into the ramp in any orientation? Looks to me like it will.
|
22-01-2015 02:36
asid61|
Put your module into the CAD of the field right at the transition between the carpet and the scoring platform. Rotate the module as it would if the steering motor was rotating it, will that low ground clearance gear run into the ramp in any orientation? Looks to me like it will.
|
22-01-2015 02:42
lukedude43Unless we want to do any sort of rotation on the step, that could cause the gear to hit the step and that would obviously be bad. The solution was to go from a 30:50 gear reduction to a 40:40 which increased the max fps from 11.5ish to 15ish but since pushing isn't an issue the lost torque from turning down wheel speed in programming shouldn't be an issue
22-01-2015 08:41
JamesCH95|
Unless we want to do any sort of rotation on the step, that could cause the gear to hit the step and that would obviously be bad. The solution was to go from a 30:50 gear reduction to a 40:40 which increased the max fps from 11.5ish to 15ish but since pushing isn't an issue the lost torque from turning down wheel speed in programming shouldn't be an issue
|
22-01-2015 13:28
lukedude43|
The lost torque will be manifested as a loss of low-speed control, loss of acceleration (especially when loaded with game pieces), increased current draw from your drive motors, and a general loss of 'responsiveness' from your drive.
Do not dismiss such gearing changes so flippantly. |
22-01-2015 13:37
JamesCH95|
Which is why we're playing around with last years robot in high gear with max motor speed turned down in code.
|
22-01-2015 13:40
Ether|
Which is why we're playing around with last years robot in high gear with max motor speed turned down in code.
|
22-01-2015 14:12
lukedude43|
Good.
However, the principle of limiting power-train speed in code, typically done via limiting the maximum voltage from each motor controller, is very bad. This artificially cripples the drive train, which is likely the most important sub-system on your robot. You might consider using chain, belts, or another lower-profile means of getting the gear reduction you should have inside of the envelope you're limited to. |
22-01-2015 14:23
lukedude43Will come back and edit so this makes sense
Realized I forgot to add other important info but the gist of it is 3d printed preliminary pods and having the gears for this gearing change in shop
latest post covers everything
22-01-2015 14:24
Ether|
what it does allow us to do is get 4 modules made and starting testing on 4 modules
|
22-01-2015 15:30
JamesCH95|
Just to be clear: The point James was making is that your testing will not be representative of the fine control you could get by reducing the speed via gearing.
|
|
Will come back and edit so this makes sense
Realized I forgot to add other important info but the gist of it is 3d printed preliminary pods and having the gears for this gearing change in shop |
22-01-2015 16:17
Ken Streeter
|
Just to be clear: The point James was making is that your testing will not be representative of the fine control you could get by reducing the speed via gearing.
|
22-01-2015 16:55
lukedude43I'm back on a computer and actually have some time so hopefully I can write a response that will make me seem less willfully ignorant
First of, the change in gearing is an admittedly quick and dirty fix, but what I believe to be the best fix just to get some pods printed up and working together. We are 3d printing the first iteration of the pods in the next few nights so that we can have something together and working so our programmer has the maximum amount of time to work on getting the pods working together nicely and field oriented control working nicely. The gearing change is by no means a final fix which is something I something I don't think I ever mentioned (serious mistake on my part), it is just a quick fix to get the test bed together and running.
What i'm leaning towards as a final fix is a cim face mounted to the lower plate with a cim gear going to a gear on some .5 hex shaft. That shaft will have the pulley that was previously on the cim with the same gear reduction. If I do this right that means the wheel pod reduction could actually end up being something like 50:30 (as opposed to the previous 30:50) which should leave more than enough ramp clearance for the wheel gear.
The testing we're going to do tonight is only to see if last years robot (roughly 15 fps) with motor speed limited will give us fine enough control for our collector (In my mind our robot design is split into collector and indexer, collector is the only part that needs fine control). If it is it leaves the current quick and dirty gear change fix as a semi viable option if for some reason everything goes to crap. All of the downsides (motor speed being limited as opposed to proper gearing, barely scraping by on ramp clearance, etc.) will all be taken into account in the final decision matrix that decides if our swerve is actually worth it or if we should throw in the tank drive.