Second Competition Chassis - August 30, 2023

Define Problem

In the previous entry, we described how we designed, built, and tested our first competition chassis. However, after testing the chassis we made there was one small problem:

Our current chassis is too fast; it has too little torque to accelerate and decelerate as needed. Prolonged use of our current chassis will cause the motors to heat up, and thermal throttle.

Generate Concepts

We had already come up with a decent list of potential drivetrain configurations in the previous entry. Here is that list:

Wheel Configurations -

  1. A drivetrain with 6 4” wheels.
  2. A drivetrain with 4 4” wheels and small flex wheels in the middle.
  3. A drivetrain with 4 3.25” wheels and small flex wheels in the middle.

Chassis Widths & Lengths -

  1. A large chassis. (35 holes in each dimension)
  2. A skinny chassis. (25 holes wide, 35 holes long)
  3. A wide chassis. (25 holes long, 28 holes wide)

Chassis Speeds -

  1. A very fast chassis (~62 inches per second)
    • 200 Rpm Motors -> 72 Tooth Gear -> 48** Tooth Gear -> 4.0” Wheels
  2. A fast chassis (~61 inches per second)
    • 600 Rpm Motors -> 36 Tooth Gear -> 60 Tooth Gear -> 3.25” Wheels
  3. An average speed chassis (~56 inches per second)
    • 200 Rpm Motors -> 60 Tooth Gear -> 36 Tooth Gear -> 3.25” Wheels
  4. A slower chassis (~51 inches per second)
    • 600 Rpm Motors -> 36 Tooth Gear -> 72 Tooth Gear -> 3.25”

Our Decision

Wheel Configuration -

The wheel configuration of our previous chassis worked very well and was able to complete all the tasks we threw at it. As such, we will keep our current wheel configuration.

Chassis Width & Length -

Again, we thought that the size of our previous chassis (25 holes long, 28 holes wide) was good. As such, we will keep our current chassis width and length.

Chassis Speed -

As we have decided not to use 4” wheels, we don’t have to consider idea #1. We previously acted under the assumption that “The faster your robot is the better!”, however, we now realize that this is not the case. We still want to have a decent-speed chassis, but we don’t want to be too fast. idea #4 fits this description; while it is the slowest chassis speed we brainstormed, it is still fairly fast (compared to, say, 4” wheels at 200 Rpm).

Here is a summary of the decisions we made:

  • Idea #3. A drivetrain with 4 3.25” wheels and small flex wheels in the middle.
  • Idea #3. A wide chassis. (25 holes long, 28 holes wide)
  • Idea #2. A slower chassis (~51 inches per second)

Develop Solution

Now that we know what we are going to build for our chassis, we can start to figure out exactly how we are going to build it. To do this we use CAD.

The first step was to make a CAD of the gear layout for our drivetrain. Below you can see the initial layout we made:

FirstGearLayout FirstGearAndWheelLayout

However, at this point, we noticed a problem with our current CAD.

Define Problem

There are large gaps between the flex wheels and omni wheels. These gaps will make it much more difficult for us to drive over the barrier:

FirstGearAndWheelLayoutProblem

The problem is this:

  • Our current CAD design will likely become stuck on the barrier.

Generate Concepts

Here are a few options we came up with to fix our problem:

  1. Research to find a different gear ratio that would allow us to reduce the gaps in our drivetrain.
  2. Move the gears (not attached to the c-channel) vertically down, below the axles of our wheels.
  3. Move everything vertically down relative to the obstructive c-channel.

Our Decision

We discussed each potential solution as a team to identify which one would work best for us.

Concept #1 would likely work; however, we feel like there should be a way to modify the layout of our current gear ratio to achieve the same effect.

Concept #3 would also likely work; however, this would force us to attach our motors horizontally instead of vertically. This is a problem because the motors would then be taking up space where we may build an intake for our robot in the future.

This leaves concept #2 as our last remaining option.

We will use idea #2:

  • Move the gears (not attached to the c-channel) vertically down, below the axles of our wheels.

Develop Solution

Below you can see a CAD screenshot of the gears after we moved them down. Specifically, we moved the inner gears between the large outer gears down exactly 0.5 inches. Additionally, you can see the supporting framework structure of the drivetrain in the second picture.

SecondGearLayout SecondGearLayoutWithSupports

Once we had one half of the chassis in CAD, we simply mirrored the part, and joined the two halves together with the rest of our robot’s structure:

FirstDrivetrainTop FirstDrivetrainTop FirstDrivetrainTop FirstDrivetrainTop

Construct

Now that we have a CAD of our robot, we should be able to construct each half of our drivetrain easily.

One thing that we emphasize a lot during our builds is ensuring we have as little friction as possible in our builds. Below you can see a video showing the amount of resistance in our drivetrain:

After we had constructed each half of our drivetrain, we connected them:

Second Competition Chassis Top View

Test

To test this chassis, we ran the same tests as we did for our drivetrain prototypes; each test was run 10 times, and the results were recorded as a percentage. Below, you can see our results:

Momentum Jump Contact Jump High-Centered Jump
100% 100% 100%

From this testing data, we can see that these conclusions we had drawn from our test drivetrain prototype testing previously have proven accurate. The use of flex wheels in between the drivetrain’s main wheels allows the chassis to drive over the barrier much easier.

Evaluate Solution

According to our testing, this drivetrain should be a great starting point for our robot; by using more watts of power in our drivetrain (66W compared to 55W) and less speed, we should not have to worry about overheating.


Entry Signatures -


Ayla Clark
Caleb Carlson
Tucker Nielson
Thomas Reid