← Back to All Weeks
Week 12

Week 12: Mechanical Design and Machine Design

Group project: a modular fabrication machine

Our group developed a Cartesian machine intended to support interchangeable fabrication tools. The shared project combines a profile frame, guided motion and electronic control. We document the concept, CAD, assembly, motion tests and presentation on our group assignment page.

My assigned mechanical role

The team allocation identifies my role as mechanical design and CAD assembly: the chassis layout, V-slot profiles, spacers and gantry alignment. The group problem log also attributes a belt-tension adjustment to me during the coordinate checks. My own CAD revisions and photographs still need to be linked here to show those contributions in detail.

For the mechanical work, the important relationships are the frame geometry, guide alignment, carriage clearance and belt path. A CAD assembly is useful for checking these relationships before making changes to the physical structure. It also gives the team a common reference when the electronics and control work affect the mechanism.

Mechanism and automation

Our shared record includes frame and assembly models, stepper-driver wiring, motor tests and browser-based G-code control. We use these stages to connect mechanical movement with commanded motion. Manual movement and alignment checks are distinct from powered axis tests, and a motion test alone does not verify every proposed fabrication tool.

The team’s source packages and presentation are linked from the shared machine page. We keep that common record together so that individual contributions can be related to the whole machine.

What the mechanical checks need to establish

For my part of the project, I need to show how the gantry is constrained and how an adjustment changes its movement. A useful check compares the same commanded move before and after a mechanical change, rather than judging alignment only from an assembly view.

The personal record will identify which components I modelled or adjusted, the original file names and the physical result. Until those records are added, the team allocation describes the scope of my role without substituting for a detailed fabrication log.

Reflection and next iteration

The machine project connects mechanical design to control in a direct way. A coordinate error can come from the frame, belt tension, drive settings or firmware, so identifying the source matters before changing a parameter. For the next iteration, I would keep each mechanical adjustment paired with a repeatable movement check and share that result with the teammates responsible for control.

How I will check the mechanical contribution

For my mechanical-design record, I need to connect each CAD or assembly change to its purpose: spacers locate the guide components, the gantry needs constrained motion without binding, and belt adjustment should remove slack without pulling the frame out of alignment. The shared machine files remain group work; I will identify my own revisions rather than present the whole machine as my individual design.

I will first compare manual travel at both ends of each axis, then repeat the same commanded movement before and after an adjustment. If the measured movement is wrong, I need to distinguish lost motion and a skewed frame from a steps-per-millimetre setting. A numerical correction cannot remove mechanical backlash. I have not added a new movement measurement or claimed an adjustment test here.

My remaining personal evidence is the actual CAD revisions, photographs identifying the parts I worked on, and the before/after result of the mechanical change. The group allocation and belt-tension attribution above remain separate from that missing detailed record.