pic: #NotSwerve

[ClockworkGold]

Originally Posted by audietron

Nice Job! Are you still planning on improving the swerve drive throughout the next couple seasons?

Heck no

[llamadon]

Originally Posted by ClockworkGold

Heck no

What he meant to say is "No most likely not, swerve was a challenge that we did not have the proper planning or knowhow to accomplish. Though it was a valuable lesson."
After analysing which drivetrains made it to einstein, and the kind or drivetrains our team has built in the past we decided to give this a try. It will be implemented in a west coast fashion, and is currently being CADed

What spreads and speeds are you using on the transmissions, alongside what wheels? Also, will you have any active way of measuring your total current draw with the 6 CIMs?

[llamadon]

Originally Posted by Andrew Lawrence

What spreads and speeds are you using on the transmissions, alongside what wheels? Also, will you have any active way of measuring your total current draw with the 6 CIMs?

We plan to use 4" hex bore Andymark performance wheels on live axles with blue nitrile tread. We will be testing a 2.92 spread ratio, set to roughly 7fps/18fps, a 3.64 spread at 5.5fps/18fps, and finally a 2.06 spread geared to 7fps/13.5fps. The 2.06 spread is being tested specifically to see what kinds of acceleration we will see with a lower top speed, but more torque. As for the current draw, we have not thought of any ways to measure that yet.

Originally Posted by llamadon

We plan to use 4" hex bore Andymark performance wheels on live axles with blue nitrile tread. We will be testing a 2.92 spread ratio, set to roughly 7fps/18fps, a 3.64 spread at 5.5fps/18fps, and finally a 2.06 spread geared to 7fps/13.5fps. The 2.06 spread is being tested specifically to see what kinds of acceleration we will see with a lower top speed, but more torque. As for the current draw, we have not thought of any ways to measure that yet.

Excellent idea of testing the different speeds and spreads. I'm not entirely certain what method they used, but Team Spectrum 3847 had a method of measuring their current draw on their robot this year. While you are testing spreads, I think it would be interesting to add this current meter to see how many amps you're pulling in certain situations. It could help you better assess what main breaker limitations you may have in the future.

[llamadon]

Originally Posted by Andrew Lawrence

Excellent idea of testing the different speeds and spreads. I'm not entirely certain what method they used, but Team Spectrum 3847 had a method of measuring their current draw on their robot this year. While you are testing spreads, I think it would be interesting to add this current meter to see how many amps you're pulling in certain situations. It could help you better assess what main breaker limitations you may have in the future.

Thanks! I will definitely inquire of this testing methods. I have read up a small amount on the effects of this number of CIMs on the breaker and have heard of a few blow outs. These blow outs tend to happen in an immediate change in voltage. IE. driving the robot forward and then immediately going backwards. Teams have implemented a part in the code that does not allow this immediate jump from 0 to 100 percent, and instead ramps it up steadily.

[AKSoapy29]

Originally Posted by llamadon

Thanks! I will definitely inquire of this testing methods. I have read up a small amount on the effects of this number of CIMs on the breaker and have heard of a few blow outs. These blow outs tend to happen in an immediate change in voltage. IE. driving the robot forward and then immediately going backwards. Teams have implemented a part in the code that does not allow this immediate jump from 0 to 100 percent, and instead ramps it up steadily.

Well we only tripped the breakers a few times on our shooter, lol. Load testing would be neat. I think we have a load tester in the cave actually, I saw it the other day.

[Arpan]

We used these gearboxes on our robot this year. They were fantastic, esp. considering how we abused them. A few notes :

1. LOCKTITE like the instructions say. We did not do this and it caused several screw failures throughout the season, resulting in worn teeth on some of our gears. The gears themselves are overbuilt - they survived the extreme chipping a CIM coming unmounted caused.

2. The 22 fps calculated speed is too fast to drive without proper code, and will blow your breakers whenever you hit anything. For FRC applications , I don't recommend going faster than 16 FPS.

I'd be very interested in seeing the results of your tests of different ratios.

[nathannfm]

Originally Posted by ClockworkGold

Heck no

It looks like I missed the back story here. If it's not too painful would someone from 2169 mind recounting their season of swerve and what problems you had with it for other teams who are dead set on at least trying swerve as an off season project so they may learn from your season?

[llamadon]

Originally Posted by nathannfm

It looks like I missed the back story here. If it's not too painful would someone from 2169 mind recounting their season of swerve and what problems you had with it for other teams who are dead set on at least trying swerve as an off season project so they may learn from your season?

We used the "Wild Swerve" modules from Team 221 robotics parts. We did not order them prior to build season. I think they were ordered by the end of week 1. Arriving mid week 2, we assembled them and attached them to our drive base. Our programers were coding prior to receiving the modules, confident in their code. We implement the code, not up to snuff. We keep editing and revising, problems arise left and right (using 3D printed encoder mounts was one of said issues.) We focused so much on our swerve that other mechanisms suffered. We over complicated the code, and the start up routine for each match (we had a "hard zero" button to "reset" the encoder values to 0) and in the end we didn't move for half our regionals. My advice is do your trouble shooting and learning before the build season, and only implement swerve for the build season if you already have a polished code for it, and have designed and planned the mechanical implementation of the drive before kick-off.