Design Sprint Goals

This design sprint is intended to be a good starting point for new team members to learn about engineering concepts and how to develop a design from (nearly) the ground up. Other goals include:

• Making Self-Driven Decisions

Finding flaws in your design on your own and determining ways to fix them.

• Documenting Design Decisions

Keeping track of what changes you made and why you made them to your design.

• Working Independently in a Team

Being apart of a bigger project while taking on the responsibility of an aspect of it.

Topics Covered

• Design Concepting

• Computer-Aided Design

• Design for Manufacturing (DFM)

• *Design for Assembly (DFA)

• Finite Element Analysis (FEA)

*Not guaranteed, but the opportunity is there!

Background Information

Let’s start at the basics, what is a trailing arm suspension? It’s commonly seen in the rear suspension of bikes as seen below.

The above example uses a bellcrank to change the direction of the force, which we won’t be using due to added complexity and weight. There’s an explanation for what a bellcrank is and how it works below, but it’s not necessary for the design sprint.

 Explanation of the Bellcrank

As mentioned above, a bellcrank is used when force needs to be redirected. A bellcrank can be described by 3 points/nodes. An “input”, “output”, and rotation point.

The rotation point is fixed, and will not move, but the input and output points can rotate around the rotation point.

For example, let’s say a force is applied on the vertical linkage going downwards. to solve for a reaction on the horizontal linkage you’d use the sum of moments about the rotation point. This means that the force on the output linkage may not be the same as the input linkage because mechanical advantage can be designed into a bellcrank by adjusting the distance of the other two points from the rotation points.

The key thing to note about a trailing suspension are:

• There is a point where the trailing arm pivots around

• There is a point where the wheel is attached

• There is a point where the shock is attached

The point where the wheel is attached is where the all the forces “enter” the system, and the shock and pivot points will counteract those forces.

INSERT SKETCH ONE

The blue circle represents the wheel which isn’t to scale, but gets the idea across (hopefully).

However, the sketch above is only a side view of the wheel.

INSERT SKETCH TWO

In the top view show above the system becomes a bit more complex. We can see an additional branch/arm the connects to the pivot axis. This is to help distribute forces which you’ll see soon enough.

At this point, start thinking about what can be changed in the concept. For instance:

• How far does the wheel need to be from the pivot point?

• How far does the shock mount need to be from the pivot point?

• Do all the points need to lie in the same line? (Can the shock be moved vertically?)

• Does trailing arm need to be horizontal? (At what angle is it optimized?)

If you’re getting a bit overwhelmed, that’s normal! This is likely you’re approaching a design problem in this way, so it takes some time to get used to, and also feel free to ask questions! Don’t think you’re bothering us, when you ask questions, you show you’re interested and we want to help build that interest!

Now, back to the technical stuff. To answer a lot of these questions we need to set some design constraint.

Design Constraints

You’ll probably learn some different terminology on this, but I’m using it as the values we know that we should design around. A big part of designing parts is finding number that you need to work around, but it’s very time consuming, so I’ve done the tedious stuff so you don’t! So, I’ll list them out here, and I’ll add in sections that show how I determined these values. You don’t need to know it, but I want to feed people’s curiosity where I can, and it stands to show a good example of documenting your design decisions.

Maximum Vertical Displacement for the Wheel: +/- 9 cm

Maximum Angular Displacement for the Trailing Arm: 10 degrees from the rest position

Angle between the Pivot and the Wheel Mount: Greater than Zero

Loading From the Wheel

 Reasoning

The regulations define the loading condition in terms of acceleration; 1G Steering, 1G Braking, 2G Bump. We can see how load transfer effects the loading conditions on the wheels. Since the trailing arms are used on the rear of the car we’ll specifically look at those values.

The above screenshot is from a spreadsheet I developed that will calculate the the load distribution under a 1G brake and 1G steer. In a braking scenario there is more weight loaded to the front however. So I made some adjustments to the calculator and we can see that the rear should expect around 111 kg of mass.

So by the 2G bump case, we should expect an upward of force of around 2177.82 N

How the steering and braking cases impact our loading conditions are through the friction between the tire and the ground. If the car was turning with a centripetal acceleration of 1g, it would require a force equal to it’s weight. This force would be supplied by the friction from the tire, which is calculated by the coefficient of static friction and the normal force. Based on generally accepted values, the coefficient has a value less than 1, which means it cannot produce a force equal to the the weight of the car.

So now we need to make a decision. The car needs to be safe, but we don’t want unrealistic loading conditions either.

NEEDS A DECISION

Timeline

Week 1 - Concepting

Sept 11 - Sept 17

The idea’s pretty simple, come up with ideas! In concepting we want to come up with as many possible solutions as possible that can solve the problem we have. In our case, the problem is how do we support the wheel given all the information in INSERT SECTION HERE.

What also might be useful to consider is how to make the part. If you take the best design possible that can’t be manufactured to a machinist, they still can’t make it. We won’t have the training/info session on manufacturing methods until later in the sprint, so only consider it at this stage if you have the time.

Deliverables

2 - 3 Concepts with Sketches (Digital or on Paper)

Week 2 - Computer-Aided Design (CAD)

Sept 18 - Sept 24

Now that we have some ideas on how to solve our problem, we need to pick one to develop further. Developing multiple ideas in parallel is very time consuming and not advised, but we won’t judge if you want the extra practice.

With a concept selected, we need to digitize it! This is where CAD comes into play, by this point we’ve done the training session on how to CAD a part and I want you to do that with your part, but the part needs to be fully defined. In case it isn’t mentioned in the training session, having a fully defined part means that all dimensions needed to define a part are present. In SolidWorks at the bottom right corner you can see if you part is fully defined.

An extension to this part of the design sprint would be to make your design parametric. A parametric design means that the dimensions of the part are defined “externally” from the feature so it can automatically update if something needs to be changed. In essence, it makes it easier to tweak your design by not needing to dig through your feature tree to change a dimension.

Deliverables

1 Concept in SolidWorks Fully Defined

Week 3 - Manufacturing Design (DFM)

Sept 26 - Oct 1

With a design digitized, it time to start thinking about how it’s going to be made. Like I mentioned before, a great design is actually pretty bad if it can’t be made. Now that you’ve learned about different manufacturing techniques, it’s time to start specifying material and manufacturing techniques.

I hope at this stage you are looking at your design to make changes to make it easier to manufacture. We can purely rely on “if there’s a will, there’s a way” when we want to make something, and this means something need to give, either our bank account, or our design. We rather our design whenever possible.

A hint/idea I’ll throw out there is to see if your design can be made using multiple parts. I’ll try to bring example trailing arms during the presentation, but hopefully you can consider your design not as a single, solid piece of metal, but smaller more manageable chunks. Notices how this reduces costs as well, smaller blocks of metal are cheaper per unit volume than larger pieces of metal.

Deliverables

Bill of Materials with a manufacturing plan along with any changes to your design in CAD.

Week 4 - Static Structural Simulations (FEA)

Oct 2 - Oct 8

We have a design we can make, but will it hold up to the forces we need it to? Again, the idea is simple, but the execution is a lot harder. Hopefully you’ll understand the basics of SolidWorks FEA to run the simulation, but if you’re having any trouble with it, feel free to reach out!

Maybe after running your simulation, your part fails, but does the stress distribution make sense? Maybe it passes, but does the stress distribution make sense? I really want to reinforce the fact that we can’t accept whatever we get from the computer blindly. If they make sense, and your part is failing, then your design needs to be tweaked.

Some common changes that might help:

If there’s a very high stress concentration in a sharp corner, add a filet to get rid of the stress singularity.

If through a thickness the part is failing, make the section thicker to increase the cross-sectional area.

Deliverables

A passing simulation with a stress distribution that makes sense along with any changes to CAD.

Final Review - Oct 22nd

This is where we get to put all your work together and see what others came up with! Everyone’s solution to the problem will be different, and their approach is something you can learn from. What we’ll do for the final review is combine the small groups on each time slot to see more solutions!

The date is not a typo, but it’s considering reading week and midterms for most of you. Which also means that you don’t need to finish the FEA for the 8th. But, I imagine during reading week and midterm week you have better things to do than figure out why a simulation isn’t working, but I let that be up to you to figure out.

Info Session Schedule

*Won’t be recorded, but training materials will be uploaded to Confluence.

All will be happening from after Mech General (~1:15pm) to 2:30pm (hopefully). After the training session we’ll start doing reviews!

Review Schedule

We’ll be making small groups of around 3 people in which you will be paired up with either myself or Shangheethan. We’ll try to spend about 15 minutes on each of your designs, but we’re hoping it becomes a bit of a discussion on what the strengths were of designs and where there’s room for improvement.

We’ll keep the same time for each group, but we’ll change the lead you review with each week so you can get a different perspective on each design.

If you have a preference on who you’re paired up with for your group be sure to let us know! We’ll probably create a form or a Lettuce Meet link to schedule the sessions. TBA.

Credits

This design sprint was heavily inspired by the one created by Aidan Lehal, Min Qian Lu, Kevin Bui, and Emily Guo! Big shoutout to them for the hard work they put in!

W22 Design Sprint