13. Professional CAD Habits
Working in CAD is not a solo endeavor, and even solo work benefits from professional discipline. The difference between a hobbyist and a professional is not the complexity of their geometry -- it is the organization, clarity, and maintainability of their project. A well-organized CAD project can be picked up by any teammate (or by your future self six months later) and understood immediately. Poor habits lead to broken references, lost work, and costly miscommunication. This module covers the practices that separate clean, production-ready CAD work from chaotic files that only the original author can decipher.
File Organization
A consistent file structure is the foundation of every successful CAD project. When a team of five engineers is working on a robot, everyone must know exactly where to find any part, assembly, or drawing without asking.
- Consistent Naming Conventions: Use a standard format for every file:
TeamName_PartName_v01 (e.g., Atlas_DriveGear_v03). Include version numbers in the filename. Never use spaces or special characters -- use underscores or camelCase.
- Folder Structure: Organize your project into clear top-level folders:
Parts/ for individual components, Assemblies/ for assembled groups, Drawings/ for 2D manufacturing drawings, and References/ for vendor data sheets, COTS models, and imported geometry.
- Component Naming in Browser Tree: Inside your CAD tool, rename every component in the browser tree to match its real-world name. "Body1" and "Sketch7" are meaningless. "LeftDrivePlate" and "MotorMountHoles" communicate intent instantly.
- Archive Old Versions: Move superseded designs to an
_Archive/ folder rather than deleting them. You may need to reference or revert to a previous approach.
Feature Tree Hygiene
The feature tree (timeline in Fusion 360, FeatureManager in SolidWorks) is the DNA of your part. A messy feature tree is a ticking time bomb -- one edit can cascade into dozens of broken features. Keep it clean from the start.
- Rename Sketches and Features Descriptively: Change "Sketch1" to "BaseProfile" and "Extrude2" to "MotorPocket." When you return to the design in three months, you will know exactly what each feature does without clicking through them.
- Group Related Features: Use folders or groups to bundle features that belong together. For example, group all the mounting hole features under a "MountingHoles" folder. This collapses complexity and makes the tree scannable.
- Avoid Suppressed and Broken Features: Suppressed features lurk in the timeline and can reactivate unexpectedly. Broken features (yellow warnings) propagate errors downstream. If a feature is no longer needed, delete it cleanly rather than suppressing it.
- Use Construction Geometry Wisely: Construction lines, planes, and axes are powerful for building robust parametric models, but overusing them creates clutter. Keep construction geometry in clearly labeled sketches and reference it intentionally.
- Build Features in Logical Order: Model the major form first (base extrusions), then add secondary features (pockets, holes), then finishing details (fillets, chamfers). This order makes the tree intuitive and minimizes rebuild errors when parameters change.
Design Approach
There are two fundamental strategies for building an assembly. Choosing the right approach for your project can mean the difference between a smooth build and a dependency nightmare.
Top-Down Design
How it works: Design all components within a single parent assembly. Parts reference each other directly -- a bracket's hole pattern is driven by the motor mount's bolt positions.
Pros: Ensures perfect fit between mating parts. Changes to one part automatically propagate to dependent parts. Ideal for tightly integrated custom designs.
Cons: Creates complex inter-part references that can break. Difficult for large teams because one person's edits can disrupt another's work. Assembly files become heavy.
When to use: Small teams, custom one-off robots, mechanisms where parts must fit together precisely (e.g., a custom gearbox housing).
Bottom-Up Design
How it works: Design each part independently in its own file, then import and constrain them in an assembly. Parts are self-contained with no external references.
Pros: Parts are portable and reusable across projects. Easy to divide work among team members. Fewer broken references. Lighter assembly files.
Cons: No automatic propagation of changes between parts. Requires careful communication of interface dimensions (bolt patterns, mounting faces). Parts may not fit if tolerances are not managed.
When to use: Large teams, projects with standard/reusable components, competitions where parts are shared across multiple robot iterations.
Version Control
Losing a day's work to a corrupted file or an accidental overwrite is a preventable disaster. Version control gives you a safety net and a clear history of how your design evolved.
- Cloud Save vs Local: Cloud-based CAD tools (Fusion 360, Onshape) save automatically and maintain version history on the server. Local tools (SolidWorks, Inventor) require manual saves and backup strategies. If working locally, save to a synced cloud folder (Google Drive, OneDrive) as a minimum safety net.
- Branching and Forking Designs: When you want to explore an alternative approach without risking the main design, create a branch (a copy that diverges from the original). Develop the alternative, and merge it back if it works or discard it if it does not.
- Using Milestones: Mark key versions as milestones: "v5 - Pre-Competition Design Freeze," "v8 - After Weight Reduction Pass." Milestones give you reliable rollback points and document the evolution of your design intent.
- Comparing Versions: Use your CAD tool's version comparison feature to see exactly what changed between two saves. This is essential for design reviews and for diagnosing when a problem was introduced.
- Rollback Strategies: If a recent change breaks the model, roll back to the last known good version rather than trying to manually undo a chain of edits. Cloud tools make this trivial; local tools require disciplined backup habits.
Collaboration
Robotics is a team sport. Multiple engineers working on the same robot must coordinate their CAD work to avoid conflicts and ensure everything assembles correctly.
- Shared Projects: Use your CAD platform's project sharing features to give all team members access to the same files. Define clear ownership -- one person owns each part or subassembly. Avoid two people editing the same file simultaneously unless the tool supports real-time collaboration (Onshape does; Fusion 360 does not).
- Reference Components from Teammates: When your part needs to interface with a teammate's part, reference their published component rather than guessing dimensions. Insert their part into your assembly and design your geometry to match.
- Managing External References: External references (links between files) are powerful but fragile. Document which files depend on which. If a referenced file is moved or renamed, the link breaks. Keep referenced files in stable locations and communicate before reorganizing folders.
- Design Reviews: Schedule regular design reviews where the team walks through the assembly together. Check for interference, verify that fastener holes align, and confirm that manufacturing constraints are met. Catching a 2mm misalignment in CAD is cheap; catching it after machining is expensive.
Common Mistakes to Avoid:
- The "One Sketch Does Everything" Trap: Do not pack an entire part's geometry into a single complex sketch with hundreds of constraints. It becomes impossible to debug and edit. Break geometry into multiple focused sketches, each driving a specific feature.
- Not Using Components: Modeling multiple separate parts as a single body and then trying to split them later is fragile. Use components (or parts within an assembly) from the start so each piece has its own independent solid body.
- Circular References: Part A references Part B, which references Part A. This creates an infinite update loop that crashes rebuilds. Always reference in one direction: layout sketch drives parts, not the other way around.
- Ignoring Warnings: Yellow warning icons and error messages in the feature tree exist for a reason. Every ignored warning is a potential time bomb. Fix warnings immediately, even if the model "looks fine" -- it will break later at the worst possible moment.
Starting a New Project
Follow this workflow to set yourself and your team up for success from the very first file.
1
Define Requirements
Write down what the robot must do, its size constraints, weight limits, and interface requirements before opening CAD. Requirements drive design, not the other way around.
2
Create Folder Structure
Set up your Parts/, Assemblies/, Drawings/, and References/ folders. Import COTS (commercial off-the-shelf) models into References.
3
Set Up Parameters
Define key dimensions as named parameters (e.g., drivetrainWidth = 550mm, wheelDiameter = 100mm). Parametric design lets you resize the entire robot by changing a few numbers.
4
Build Skeleton / Layout Sketch
Create a master layout sketch that defines major dimensions, mounting locations, and spatial relationships. This sketch drives the placement of all downstream components.
5
Create Components
Model each part as an individual component, referencing the layout sketch for critical dimensions. Follow naming conventions and keep the feature tree clean as you go.
6
Assemble
Bring components together in the assembly. Apply joints and constraints. Check for interferences and verify motion ranges for all moving parts.
7
Review
Conduct a team design review. Walk through every subsystem. Verify fit, function, and manufacturability. Mark the version as a milestone once approved.