|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#16
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
|
|
#17
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
Since you have a 4 wheel drive, put 2 CIMs on modules in opposite corners, with 1 CIM in each of the other corners. The power you're supplying to your wheels should still be balanced on either side, regardless of the direction of movement which is defining said "sides" at any given time. Adding in arbitrary rotation on top of translation complicates things a bit, since now the power available to pull off the rotation will depend on how far each "unit" of power is from the center of rotation. In particular, if you're spinning about one of your modules, if it's a 1 CIM module, you have 5 CIMs available to do the maneuver, while if it's a 2 CIM module, you only have 4 across the other 3 modules. If you spin about a point away from all the modules, you have all 6 CIMs available. A 4 CIM, 4 wheel swerve also fails to have this type of symmetry, but to a lesser extent. In any case, a good speed control loop will ensure you still get the desired motion, but the max acceleration and force with which you can perform a maneuver may vary because of the loss of symmetry. Since a good swerve will require extensive off season testing anyway, I'd recommend trying this out so you don't have to try transferring power between modules, and seeing if the performance is acceptable. Or go 3 wheel ![]() |
|
#18
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
![]() where i is the index of the wheel, r is its position vector relative to robot center, v is the velocity of the robot, omega is the rotation of the robot (counterclockwise around robot center). However, by pairing up modules, you introduce further constraints on magnitudes and directions of wheel velocities. In your case, you are requiring for some pair i,j: ![]() or very close to zero (the wheels are allowed to scrub a little). But this means either you aren't turning very much at all, or your paired wheels are nearly on top of each other. For other pairings you can follow a similar process to figure out what motions are still allowed. Calculate wheel speeds and directions as you would normally, then average them for each pair output, so that the pair outputs are the same, and it should work, though some motions may not be possible. Last edited by Aren Siekmeier : 15-05-2014 at 23:58. |
|
#19
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
http://www.chiefdelphi.com/media/papers/2785 is a tremendously useful paper that outlines pretty much every possible combination of steering and powering modules, including a list of possible maneuvers by combination and notable examples.
The configuration that you're describing is the one labeled {5}. As mentioned earlier in this thread, it is basically a 4 wheeled tank that can translate, meaning that to spin in place you'll have a bit of scrub. One way to avoid this is configuration {13} which powers each side together but links steering modules on the diagonal. This retains the ability to strafe in an arbitrary direction but does a much better job at spinning in place. Check out team 1717 in 2011 for an example of this. I would tend to agree with other posters in this thread and say that if you're planning on going through with a swerve, assuming the motor rules stay as lax as they are, it wouldn't be a huge step up to just go for 4 independently powered and steered modules. I would also recommend, if you have the resources to do so (which is a decent amount of money), buying a set of revolution modules from 221 robotic systems and throwing together a chassis to give to your programmers as soon as possible. The biggest hurdle with swerve tends to be software and implementation of controls, as there are tons of resources available mechanically (221 posts cad on their website, team 1640's wiki is incredible, 973 has swerve cad on their website, etc.). Last edited by smistthegreat : 16-05-2014 at 00:01. |
|
#20
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
However, I stand by by statement that torque is limited by the breaker. |
|
#21
|
|||
|
|||
|
Re: Coaxial Swerve Derivation with Paired Modules
You can pull huge amounts of current for a short amount of time without tripping the breaker.
Source: http://www.cooperindustries.com/cont...UITBREAKER.pdf Last edited by Knufire : 16-05-2014 at 01:54. |
|
#22
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
As the speed approaches motor free speed (for the given voltage), current draw approaches zero no matter how many motors you have (due to back emf). Quote:
|
|
#23
|
|||||
|
|||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
Get back to me when you find a need for 18 motors. |
|
#24
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
Drivetrain Full-Throttle Acceleration Simulation Model with traction limiting and voltage drops: http://www.chiefdelphi.com/media/papers/2868 see these attachments: PDF Drivetrain Acceleration 2013-09-25 RevC See attached chart of accel vs speed for one set of model parameters, using data generated with attachment ready-to-run model 2013-12-18 You can change the parameters to whatever you think is appropriate for your drivetrain and run the model to see how they affect the performance. Last edited by Ether : 16-05-2014 at 13:44. |
|
#25
|
|||||
|
|||||
|
Re: Coaxial Swerve Derivation with Paired Modules
The potentially big issue with a 10 motor drive on the new control system is only having 16 slots on the odb. 6 motors might not be enough for the rest of the bot.
|
|
#26
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
Also, 3 wheel swerve only has 3 turning motors ![]() |
|
#27
|
|||||
|
|||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
Currently you need to power at least the sidecar and analog breakout, and sometimes a solenoid breakout and a compressor, so you're effecivly loosing 2 ports without pneumatics, no ports with pneumatics. See attached image. |
|
#28
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
In 2011 we did a 2 speed coaxial crab ( fronts paired, backs paired ), I'll try to find some pics/CAD.
Last edited by Richard.Varone : 16-05-2014 at 19:08. |
|
#29
|
||||
|
||||
|
Re: Coaxial Swerve Derivation with Paired Modules
Hmm. I thought I'd get some comments or questions about the shape of the 6CIM accel curve.
|
|
#30
|
|||
|
|||
|
Re: Coaxial Swerve Derivation with Paired Modules
Quote:
I wonder why there is a slight decrease in acceleration while traction-limited as the speed increases, though? Last edited by Oblarg : 17-05-2014 at 21:33. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|