LogoLogo
  • Welcome!
  • Mission Statement
  • Contributing Guidelines
    • Embed CADs in Wiki Articles
  • VEX Worlds Livestream Archive
    • VEX U
    • V5RC High School
    • V5RC Middle School
    • VIQRC Middle School
    • VIQRC Elementary School
    • JROTC
  • ⚙️Hardware
    • Design Fundamentals
      • Gear Ratios
      • Internal Forces (Stress)
      • Torque
      • RPM
      • Center of Mass
    • Introduction to VEX Parts
      • Structure
        • C-Channels and Angles
        • Fasteners
        • Retainers
        • Gussets and Brackets
        • Bearings
        • Plate Metal and Flat Bars
      • Motion
        • High Strength Components
        • Gears and Sprockets
        • Traction Wheels
        • Mecanum Wheels
        • Omnidirectional Wheels
        • Flex Wheels
    • Robot Decorations
      • Part Dyeing
      • Metal Coloring
      • License Plate Holders
    • Lifts
      • Double Reverse Four Bar (DR4B or RD4B)
      • Four Bar
      • Scissor Lift
      • Six Bar
      • Other Lifts
      • Best Practices
    • Shooting Mechanisms
      • Catapult
      • Flywheel
      • Linear Puncher
    • Drivetrains
      • Tank Drive
      • Mecanum Drive
      • Holonomic Drive
      • Designing a Drivetrain
      • Best Practices
    • Pivots & Joints
    • Pneumatics
      • Best Practices - Pneumatics
    • Intakes
    • Flip Out Mechanisms
    • Defensive Mechanisms
    • Misc. Building Techniques
    • VexU
      • Common Manufacturing Techniques
        • 3D Printing
        • Laser Cutting
      • Custom Manufactured Parts Library
      • Commercial Off The Shelf Parts Library
  • 👑Team Administration
    • New Team Resources
      • Creating The Team
      • Gaining Interest for Robotics Teams
      • Attending Competitions
        • Elimination Bracket
    • Team Dynamics
      • Organization Structure and Longevity
      • Member Allocation and Management
      • How *Not* To Run a Team
    • Team Finances
      • One-Year Team Financial Breakdown
      • Funding Your Teams
    • Hosting Competitions
      • Live Streaming
      • Tournament Manager
        • Competition Electronics
        • Creating a Tournament
        • Tools
          • Field Set Control
          • Connecting Mobile Devices
          • Connecting Raspberry Pis
        • Match Control
          • Inputting Match Scores
          • Inputting Skills Scores
          • Inputting Scores on TM Mobile
        • Displays
        • Alliance Selection
      • Additional Event Partner Resources
    • VexU Organization Management
      • Getting Started in VexU
      • Team / Personnel Management
      • Volunteering At Local Events
  • 📚The Judging Process
    • The Engineering Design Process
      • Test and Refine
    • The Engineering Notebook
      • Segments of the Notebook
      • BLRS2 '23-'24 Engineering Notebook
      • Integrating Inventor Models into Documentation
      • Engineering Notebook Rubric Breakdown
    • The Interview
      • Interview Rubric Breakdown
    • Using Notion for an Engineering Notebook
      • How to Setup a Notebook
      • How to Create Entries
      • How to Export a Notebook
      • Purdue SIGBots Notion Template
        • Game Analysis
        • Identify The Problem
        • Brainstorm Solution
        • Select Best Approach & Plan
        • Build Log
        • Programming Log
        • Testing Solution
        • Tournament Recap
        • Innovative Feature
  • 🖥️VEX CAD
    • CAD Programs
      • Inventor
      • Fusion 360
      • Solidworks
      • OnShape
      • Protobot
    • Making a Chassis
      • Inventor Chassis: The Basics
        • Installation
        • User Interface Overview
        • Dark Mode
        • Assemblies
        • Placing Parts
        • Navigating CAD
        • Changing Visual Style
        • Grounding
        • Connecting Two C-Channels
        • Modifying Existing Constraints
        • Toggling Visibility on Existing Parts
        • Completing Half of the Chassis
          • Inner Drive Channel
          • Bearing Flats
          • Motors
          • Wheels
          • Sprockets
          • Spacers, Washers and Standoffs
          • Spacers Cont.
        • Creating Mid-Plane
        • Mirroring
      • Inventor Chassis: Best Practices
        • File Structure
        • Subassemblies
        • Wheel Subassembly
        • Origin Planes
        • Cross Brace
        • Drive Channels
        • Simple Motor iMates
        • Replacing Simple Electronics
        • Completing Half of the Drive
          • Bearing Flats (Best Practice)
          • Wheels
          • Powered Gear
          • Spacer Boxing
          • Spacers, Washers and Standoffs (Best Practice)
        • Model Browser Folders
        • Mirroring (Best Practice)
        • Model Browser Folder (Right)
        • Main Assembly
      • Fusion 360 Chassis
      • Solidworks Chassis, Chain, and Custom Plastic
    • Remembering The Best
      • 62A Skyrise
      • 400X Nothing But Net
      • 2587Z Nothing But Net
      • 365X Starstruck
      • 62A In The Zone
      • 202Z In The Zone
      • 5225A In The Zone
      • 169A Turning Point
      • 929U Turning Point
      • 7K Tower Takeover
      • 5225A Tower Takeover
      • 62A Change Up
    • Scuff Controller
  • 💻Software
    • Odometry
    • Path Planning
    • Robotics Basics
      • Arcade Drive
      • Tank Drive
      • Joystick Deadzones
      • Curvature (Cheesy) Drive
      • Subsystem Toggling
    • Organizing Code
      • Code Style
      • Code Styling Guide
      • Writing Good Comments
      • Version Control
    • Control Algorithms
      • Bang Bang
      • PID Controller
      • Basic Pure Pursuit
      • Flywheel Velocity Control
      • Kalman Filter
      • Take Back Half (TBH) Controller
      • RAMSETE Controller
    • Competition Specific
      • Operator Control
      • Autonomous Control
    • C++ Basics for VEX Robotics
      • Basic Control Flow
      • Enumerations
      • Namespaces (::)
      • Multiple Files (C/C++)
    • VEX Programming Software
      • PROS
        • OkapiLib
      • vexide
      • Robot Mesh Studio (RMS)
      • EasyC
      • RobotC
      • VEXcode
      • Midnight C
    • General
      • Stall Detection
      • Register Programming
      • Sensors and Odometry in Autonomous
      • Embedded Programming Tips
      • Debugging
      • Bit Shift
      • Bit Mask
      • Autoformatting
      • Finite State Machine
      • Data Logging
    • Object Recognition
      • Red Green Buoy
      • AMS
      • OpenCV
      • OpenNI
    • 🤖AI in VRC: Pac-Man Pete
  • ⚡VEX Electronics
    • V5 ESD Protection Board
    • VEX Electronics
      • VEX V5 Brain
        • V5 Electronics Observations and Issues
      • VEX Controller
      • VEXnet and V5 Robot Radio
      • VEX Battery
      • VEX Motors
    • VEX Sensors
      • 3-Pin / ADI Sensors
        • Encoder
        • Potentiometer
        • Limit Switch
        • Bumper Switch
        • Accelerometer
        • Gyroscope
        • Ultrasonic
        • Line Tracker
        • LED Indicator
      • Smart Port Sensors
        • GPS Sensor
        • Rotation Sensor
        • Vision Sensor
        • Optical Sensor
        • Distance Sensor
        • Inertial Sensor (IMU)
        • 3-Wire Expander
    • V5 Brain Wiring Guide
    • Legacy
      • VEX Cortex
      • Power Expander
      • VEX Motor Controller
      • VEX Cortex Wiring Guide
  • General Electronics
    • General Topics
      • External Boards
        • ASUS Tinker Board S
        • Arduino
        • Beagleboard
        • Leaflabs Maple
        • LattePanda
        • Meadow F7 Micro
        • Netduino
        • ODROID-XU4
        • Pandaboard
        • Raspberry Pi
      • Analog-Digital Converter (ADC)
      • Bit-Bang
      • GPIO
      • I2C
      • Jitter
      • Line Noise
      • List of Tools
      • Output Drive
      • Power Consumption
      • Radius Array
      • Resettable Fuse (PTC)
      • SPI
      • Slew Rate
      • Stalling
      • USART
      • UART
      • 5 Volt Tolerant
      • DC Motor Basics
Powered by GitBook
LogoLogo

This work is licensed under a Attribution-ShareAlike 2.0 Generic License

On this page
  • Displaying Assemblies
  • Creating Drawings of Models
  • Teams Contributed to this Article:

Was this helpful?

Edit on GitHub
Export as PDF
  1. The Judging Process
  2. The Engineering Notebook

Integrating Inventor Models into Documentation

Creating CAD models is a crucial step in the Engineering Design Process, which is why it's important to integrate models into documentation.

PreviousBLRS2 '23-'24 Engineering NotebookNextEngineering Notebook Rubric Breakdown

Last updated 1 year ago

Was this helpful?

Displaying Assemblies

The simplest way to integrate CAD into documentation is to display the assembly file of the robot/mechanism as it appears in the software. This can be accomplished by simply screenshotting the assembly, although there are a few clever tricks that can be utilized to improve the appearance of the assembly, most of which appear in the "View" tab at the top of the window. Of course, these tips all depend on the amount of detail that a team is attempting to display in the documentation.

  1. Know when to utilize orthographic view vs. perspective view

    In most cases, it is best to opt for using the perspective view when displaying a robot assembly, as it looks more realistic since it more accurately represents the field of view of the human eye. However, orthographic view is generally better to use in more technical cases, such as a multi-view of the CAD model (although typically a team would use drawings to express this).

  2. Use the "Realistic" visual style

    While not particularly performance-friendly, the realistic visual style fleshes out the materials of the assembly to make them look significantly more polished. This is extremely useful when trying to show off a "finished product" CAD model in documentation, and it also opens the door for ray tracing to be activated in order to polish the assembly even further if necessary.

  3. Make use of shadows

    Similar to the Realistic visual style, enabling shadows is another aspect of Inventor's rendering abilities that, while also not performance-friendly, can make a design look more polished. However, in most use cases, it is best to only want to enable object shadows and ambient shadows, while ignoring ground shadows in order to make the model appear more seamless against the page in a team's documentation.

  4. Temporarily change color settings before screenshotting or rendering

    In Inventor, depending on the version, the default background being displayed behind the model usually does not coincide with the pages in of documentation very well. This could be solved by utilizing paint.NET or Adobe Photoshop to make the screenshot of the CAD model a PNG with a transparent background, but a much simpler method would just be to temporarily change the color settings in Inventor such that the background is a solid white color. To do this, go to the "Tools" tab at the top of the window, then click "Application Options". At the top of the Application Options window, navigate to "Colors", and then as the In-canvas Color Scheme, choose "Presentation". Finally, on the right, there should be a drop-down button under "Background". Instead of "Background Image" (which should be the default), change this setting to "1 Color", then click "Apply" at the very bottom of the window. This should make the background of Inventor a solid white color, making it much easier to seamlessly print out and paste onto a notebook or copy and paste into digital documentation.

Creating Drawings of Models

One valuable feature of Autodesk Inventor is being able to import assemblies and parts alike as drawings. This makes it easy to display and annotate different views of a robot, mechanism, or part, all while maintaining an industry-like multi-view sketch scheme within the drawing file.

In order to create a drawing of a part or model, a DWG file or IDW file needs to be created. Inventor's default extension for drawing files is DWG, but there are few distinguishable differences between the two file extensions.

Once the drawing file has been created, the "Default Border" and "ANSI - Large" objects from the explorer can be deleted, unless it is preferred for a school or organization to use them as part of the drawing.

To import a model, click "Base" at the top of the window (under the "Place Views" tab). Another window will open which will ask to specify the file to generate a drawing for, the style of the drawing, and the scale of the drawing.

First, select the file to display in the drawing file. Then, change the scale of the object accordingly. Usually, it is best to increase the ratio of small objects and decrease the ratio of large objects in order for them to take up a reasonable amount of space, although Inventor will try to do this automatically. Finally, the style of the drawing is dependent on what is being displayed; including hidden lines is potentially useful in the context of a small, simple part, but would make the entire drawing file look cluttered if enabled for a large, complex assembly like a robot, hence presenting a good reason to use the "Hidden Line Removed" option. Whether the drawing is shaded or not is up to preference, although it is usually good practice to leave the drawing unshaded. This option will not affect hidden lines. Clicking "OK" should close this window and generate the drawing of the base view.

When importing the model, keep in mind that the base view should always be the flat view that shows the most features on the object. In this case, the top view of this mecanum wheel would be the base view. Once the base view is placed, the multi-view layout can now be generated. To do so, click "Projected" at the top of the Inventor window under the "Place Views" tab. Then, click on the base view. Once the cursor is moved away from the base view, an image of the model will appear. Moving the mouse along different axes will display a different view. Moving the mouse directly up will create a top view of the model. Moving the mouse to the right or left will create a side view of the model. Finally, moving the mouse diagonally from the model will create an isometric view of the model. Once it is determined that the optimal position of the projected view, left-click to place the view. Repeat this until there is a top view, side view, and isometric view present. Then right-click, and drag the mouse towards "Create" and let go once it's highlighted. This will complete the multi-view drawing.

The final step of integrating these drawings into documentation is to export the drawing. Click on "File" at the very top of the window, then click "Export", and select "Image". Drawings can then be exported as a BMP, GIF, JPEG, PNG, or TIFF file.

Teams Contributed to this Article:

  • 5327U (Gael Force Robotics)

(Purdue SIGBots)

📚
BLRS
An example of an Inventor assembly representing a prototype robot that could be displayed in documentation.
A multi-view drawing generated from a full robot assembly.
The completed multi-view sketch of the mecanum wheel.