This repository has been archived by the owner on Apr 29, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add the identify wings problems entry and test elevation entry
- Loading branch information
1 parent
e13b9fd
commit 05609fe
Showing
9 changed files
with
157 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,93 @@ | ||
#import "/template/template.typ": * | ||
#import "@preview/cetz:0.2.0" | ||
|
||
#show: create_entry.with( | ||
title: "Elevation #1", | ||
type: "test", | ||
start_date: datetime(year: 2024, month: 2, day: 23), | ||
attendance: "Ajibola, Jin, Ishika, Makhi, Eric, Rory", | ||
designed: "Jin", | ||
witnessed: "Rory", | ||
) | ||
|
||
With the state competition rapidly approaching, we need to ensure that our elevation mechanism is high scoring and reliable. To verify this, we conducted two sets of tests on the elevation bar hang mechanism. | ||
|
||
= Tier Test | ||
|
||
== Objective | ||
We want the elevation mechanism to reach C tier at least 60% of the time. | ||
|
||
#grid( | ||
columns: 2, | ||
rows: 1, | ||
column-gutter: 1em, | ||
|
||
[ | ||
== Materials | ||
- Robot | ||
- Controller | ||
- VRC Height Guide Stick | ||
- Notebook and pen to record data | ||
], | ||
|
||
[ | ||
== Procedures | ||
+ Position the robot directly under the elevation bar | ||
+ Grab onto the elevation bar and pull up until the robot has reached its max height | ||
+ Measure the tier of the elevation using the Height Guide Stick | ||
+ Repeat steps 1-3 for a total of 4 trials | ||
], | ||
) | ||
|
||
== Results | ||
#grid( | ||
columns: 2, | ||
column-gutter: 5pt, | ||
|
||
align(center)[ | ||
#tablex( | ||
columns: 6, | ||
align: center + horizon, | ||
|
||
cellx(fill: gray.lighten(20%))[Trial \#], [Trial 1], [Trial 2], [Trial 3], [Trial 4], [Trial 5], | ||
|
||
cellx(fill:gray.lighten(20%))[Tier], [B], [B], [B], [B], [B] | ||
) | ||
|
||
#cetz.canvas({ | ||
import cetz.draw: * | ||
import cetz.chart | ||
|
||
let data = ( | ||
([A Tier], 0), | ||
([B Tier], 5), | ||
) | ||
|
||
let colors = (red, yellow.darken(10%)) | ||
|
||
chart.piechart( | ||
data, | ||
value-key: 1, | ||
label-key: 0, | ||
radius: 2.625, | ||
slice-style: colors, | ||
inner-radius: 0.75, | ||
outset: 0, | ||
inner-label: ( | ||
content: (value, label) => [ | ||
#text(white, label) | ||
], | ||
radius: 110% | ||
), | ||
outer-label: (content: "%", radius: 120%) | ||
) | ||
}), | ||
], | ||
|
||
align(center)[ | ||
#image("./test/2.23.png", height: 18em) | ||
] | ||
) | ||
|
||
== Conclusion | ||
We are not satisfied with the elevation bar hang design. We are barely reaching B tier, which is a step down from our goal of a C tier. We are also worried that we could fall to A tier in situations when the elevation motor is slightly weakened due to overheating or other circumstances, which could potentially lower our point gain from elevation. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
#import "/template/template.typ": * | ||
|
||
#show: create_entry.with( | ||
title: "Wings #1.1 - Problems", | ||
type: "identify", | ||
start_date: datetime(year: 2024, month: 2, day: 7), | ||
attendance: "Ajibola, Jin, Ishika, Makhi, Rory, Eric", | ||
designed: "Rory", | ||
witnessed: "Jin", | ||
) | ||
|
||
#nb_todo( | ||
date: datetime(year: 2024, month: 1, day: 1), | ||
( | ||
(true, ""), | ||
) | ||
) | ||
|
||
At Gateway to the West, we spoke with team 338A about their front wing design and how we could implement it on our robot. The pros that we saw with their design was how compact and light the wings were. They used a half cut C-channel as their base, which we never thought of using. We also saw the importance of bracing our wings for better support. | ||
|
||
= Design Comparison | ||
|
||
#gridx( | ||
columns: 2, | ||
|
||
image("./identify-problems/338A-1.png", height: 14em), | ||
[338A uses a regular 2 C-channel as their pivot. There is a screw joint going through the C-channel and two half cuts bolted together for support. We believe this is to reduce friction as the boxed half cuts will make it difficult for the wings to open up.], | ||
|
||
[Another difference between their wing design and our wing design is the position of the pneumatics. When 338A's robot's wings are fully extended, the angle of their wings and the pneumatics is more parallel than ours. We observed that the more parallel the wings and pneumatics are, the easier it is for them to open. On the contrary, the more perpendicular they are, the more torque they generate and the stronger the wings are. We observed that a 135 degree angle seems to be the sweet spot.], | ||
image("./identify-problems/338A-2.jpg", height: 14em), | ||
|
||
image("./identify-problems/338A-3.jpg", height: 14em), | ||
[This picture demonstrates the screw-joint. There is a long screw coming from the chassis and the wing. There is a collar as well that acts as a triangle brace for the wing. We plan to use this feature in our design as well.], | ||
) | ||
|
||
= Design Evaluation | ||
|
||
#tablex( | ||
columns: 2, | ||
|
||
cellx(fill: red)[Old Wing Design], | ||
cellx(fill: green)[New Wing Design], | ||
|
||
image("./identify-problems/Identify problem old wing design.excalidraw.svg"), | ||
image("./identify-problems/Identify problem new wing design.excalidraw.svg"), | ||
|
||
[ | ||
Our current wing design involves using a 45 degree gusset that is attached to the side of the chassis. There is a screw joint going through a 45 degree gusset that connects the wing to the robot. | ||
|
||
When the wing is fully extended, the piston creates a 110 degree angle with the wing. The more perpdenicular it is, the more torque is produce from the piston. A drawback is that it's harder to push open. | ||
], | ||
[ | ||
With our new wing design, there will be a C-channel attached to the screw joint. The physical wing will be attached to the C-channel to reduce friction. Alongside the screw joint is a triangle brace to help secure the wing. | ||
|
||
When the wing is fully extended, the piston will create a 145 degree angle with the wing. We found that weaker wings help with pushing triballs. | ||
] | ||
) |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
10 changes: 5 additions & 5 deletions
10
...y problems new wing design.excalidraw.svg → ...fy problem new wing design.excalidraw.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
File renamed without changes