Design

The design process for this project was broken down into four different stages. First the customer requirements were attained through customer interviews, and these requirements were then translated into engineering requirements. A house of quality was used to ensure all the engineering requirements satisfied the customer requirements as well as any other requirements the team deemed necessary. This process is show in the Problem Definition. From there a functional decomposition was used to break down the project into its constituents. Benchmarking was performed to understand what current technologies were being used in similar applications. These technologies were combined in a morphological chart and then analyzed using a pugh chart to determine which combination of technologies would work best for our project. A feasibility analysis was performed to ensure all technologies would be applicable to our project. All of this is summarized in the System Design. From there, the project was broken down into three subsystems: Control, Navigation, and Force Actuation. Preliminary designs were worked up for each and a bill of materials was generated for the needed parts. This is shown in the Subsystem Design. The particulars of each subsystem were then designed and combined together to create out Detailed Design. This detailed design encompassed everything we planned on doing with this project. Although some modification were made as the project was built, the overall design remained fairly consistent.

Problem Definition & System Design

Team Vision for Problem Definition Phase

The project objectives were elaborated in detail to come up with a problem definition which satisfies all parties. Customer interviews were held, and engineering requirements were drafted. House of quality analysis was performed and use case scenarios were drafted.

Project Definition

An Inflatable Robotic Hand is a portable, mountable device that can inflate, manipulate an object, and deflate remotely. The system will be house in a container mounted on a RC car. This device will utilize some of the same principles, specifically the air muscles, used in previous RIT senior design projects P14253P09023P08023, and P08024. This project will add the ability of inflating out of a small container.

The goals of this project are to analyze previous air muscle designs, and other inflatable robot technologies, to identify an opportunity to combine these ideas into one product. The expected results is a functional prototype that can be applied to the task. The prototype must use air for generating actuation forces while resembling a hand with a minimum of three fingers.

1 Page Project Summary

Use Case

Use Case Scenario Flow Chart
Shows use case where user picks up a tennis ball

Project Goals & Key Deliverables

  • The arm, hand, and vehicle can be remotely controlled by user
  • Pick up a tennis ball
  • Mounted on an RC vehicle
  • Inflate out from a compartment
  • Actuation force is produced by air muscles

Customer Requirements (Needs)

Purpose

To decompose the Problem Statement into functions of elements needed to satisfy the customer.

Customer Requirements

Rqmt #ImportanceDescription
C0019Must use air for inflation and actuation forces
C0029Must be able to pick up a tennis ball up to 2 in off the ground
C0039Must resemble a hand or fingers
C0049Must inflate from a container housed on an RC vehicle
C0053Must deflate fully back into the container
C0069Must be remote controlled
C0079Material selection must withstand inflation/deflation cycles without popping or tearing
C0083Use a single controller to control both the robotic arm and the RC vehicle
C0093Prototype and final model must be built with a $750 budget
C0103Move object (tennis ball) from one location to another
C0111Mounted camera for targeting and navigation

Inputs

  1. PRP
  2. Problem Statement
  3. Customer Interviews
  4. Art North & Dr. Lamkin-Kennard.

Outputs

Customer Requirements

Engineering Requirements (Metrics & Specifications)

Purpose

Create a contract between the engineer and the customer where indisputable satisfaction of the engineering requirements equates to customer satisfaction

Engineering Requirements:

Rqmt #ImportanceEngineering RequirementUnitTarget ValueMarginal Value
0011Air compressor powerpsi> 120100
0029Air compressor flow ratescfm> 0.880.3
0039Inflation timesec< 25
0043Deflation timesec< 1015
0053Inflation arm reachin> 64
0061Object lift distancein> 64
0079Hand grip strengthpsi> 2015
0083Stored air volumeml> 1200200
0093Stored air pressurepsi< 10080
0109Number of fingers on robotic handunits= 33
0119Battery lifemin> 9030
0123Chassis load weight capacitylb< 40120
0139Chassis surface mount areain^2< 24x2430x30
0143Arm container cross-sectional areain^2< 6x68x8
0151Arm container heightin< 810

Inputs and Source

  1. PRP
  2. Dr. Lamkin-Kennard
  3. Art North

Outputs and Destination

  1. HoQ

Constraints

From Customer Requirements

  • Inflation mechanism must use air only
  • Robotic arm and hand must fit inside a small container

From Engineering Requirements

  • Weight of robotic arm, air compressor, tank, and control systems must not exceed chassis weight capacity
  • Must have large enough power source to supply power to the motors, compressors, and control systems

House of Quality

public/Problem Definition Documents/HoQ.PNG
public/Problem Definition Documents/HoQ_Legend.png

Inputs and Source

  1. PRP
  2. Customer Requirements
  3. Engineering Requirements
  4. Benchmarking Data

Outputs and Destination

Design phase

Team Vision for System-Level Design Phase

Our plan was to develop the functional decomposition of our system, come up with possible solutions, and out line the system architecture. We also planned on benchmarking the different components and analyzing the feasibility.

We were able to complete all of the tasks we set forth to do for this phase.

Functional Decomposition

alt text

Benchmarking

Benchmarking

Morphological Chart and Concept Development

Morphological Chart

Concept Selection

Concept Selection & Pugh Chart

Systems Architecture

alt Text

Feasibility: Prototyping, Analysis, Simulation

Feasibility

Risk Assessment

Updated Risk Assessment

Subsystem Design

Team Vision for Subsystem-Level Design Phase

Our primary objective in this phase was to prototype and analyze our 3 subsystems which were the Control, Navigation, and Force Actuation. For each subsystem, we came up with different proof-of-concepts for different designs, which we then benchmarked and chose the best design to move forward with.

Control: H-bridge, Motor drivers, Solenoid drivers,

Navigation: Motors, Chassis, Wheels, Gearbox, BOM

Force Actuation: Solenoid valves, Flow loop design, Arm designs, Hand, BOM

Sub-Subsystem Design & Engineering Requirements

border|Subsystem Archetecture

Feasibility: Prototyping, Analysis, Simulation

Control:

Micro-controller:

  • considered PWM requirements
  • MSP430

Peripherals:

  • Drivers
    • border|Circuit 1
    • solenoid drivers
    • motor drivers
    • compressor driver

Power Regulators:

Navigation:

Locomotion:

  • motors
    • CIM
    • Pololu 100:1 gear motor
  • wheels
    • Pololu wheels
  • gearbox

Structural: border|CAD

  • frame (2ft x 2ft)

Force Actuation:

Arm:

  • 2 arm designs considered
    • 4 Channel Arm (4ChA)
    • Slinky Arm (SA)
  • preliminary prototyping of 4 Channel Arm (4ChA)
    • mold being made
    • border|4 Channel Hand
    • material considerations: Smooth-On Ecoflex 0030, mold-star

Finger:

  • 1 finger design considered
    • PneuNets Bending Actuator (PNBA)
  • preliminary prototyping of PNBA has begun
    • prototype part made

Pressure Distribution:

  • Flow loop designed (schematic below)
  • Solenoid valves tested
    • border|solenoid valve border|solenoid manifoldborder|power supplyborder|solenoid valve 2
  • Pressure regulators tested
    • border|pressure regulator

Inputs and Source

  1. Engineering Requirements
  2. Concept Selection
  3. System Architecture

Outputs and Destination

  1. A list of Design Parameters, Quantified Targets, and acceptable tolerances
  2. Sensitivity analysis
  3. Concept Selection

Drawings, Schematics, Flow Charts, etc.

Air System Schematic

  • A, B, C, D, E - one-way solenoid valves
  • F - two-way solenoid valve

public/Photo Gallery/Air_System_Schematic.PNG

Valve Positioning:

  • 1 (power on - valve closed)
  • 0 (power off - valve open)
 Valves
TaskABCDEF
Tank Fill000100
Arm Inflation010010
Finger Inflation011000
Finger Deflation101101
Arm Deflation100111
Pressure Release000100

Bill of Materials (BOM)

Navigation:

QTYDescriptionSupplierCost ($)
-----------------Structural----------------------------------
630” Aluminum C-ChannelAndymark$18/ea
8C-Base Aluminum CornerAndymark$4/ea
42¼” - 20 Hex Head BoltsN/A$14
-----------------Locomotion----------------------------------
22.5” CIM MotorAndymark$28/ea
2Toughbox 14.88:1 Gear BoxAndymark$75/ea
44” Rubber Treaded WheelAndymark$4/ea
2½” x 4” Free AxleN/AN/A
2Direct Drive CollarN/AN/A
23’ Drive ChainN/AN/A
2Sprockets for Chain DriveN/AN/A

Air System:

QTYDescriptionSupplierCost per Part($)Link
1CompressorAndyMark69.00Link
1Check ValveMcMaster17.03Link
2Air TankAndyMark16.00Link
81-Way Solenoid ValveRIT0N/A
12-way Soleniod ValveRIT0N/A
17Soleniod Valve ConnectorRIT0N/A
2Pressure RegulatorRIT0N/A
22-Outlet ManifoldMcMaster22.94Link
61/4" NPT Compression FittingMcMaster1.35Link
41/8" NPT Compression FittingMcMaster1.30Link
25 ft.1/4" OD Polyethylene TubingMcMaster0.10 per footLink
25 ft.1/8" OD Polyethylene TubingMcMaster0.05 per footLink

Risk Assessment

Updated Risk Assessment

Detailed Design

Team Vision for Detailed Design Phase

Our primary objectives for this phase were to:

  • Update test plans
    • Control: motor and solenoid drivers, power supplies, controller mapping, transmission range
    • Navigation: motor/robot movement speed, battery life, frame weight and size
    • Force Actuation: mock flow loop, arm and finger
  • Acquire remaining parts necessary for test plans
  • Update schematics and flow charts for each subsystem
  • Come up with team and individual plans for MSD II
  • Prepare for the gate review

Detailed Design Phase To-Do List

Prototyping, Engineering Analysis, Simulation

The following subsystems will be prototyped:

Control System

Solenoid Drivers

Force Actuation System

Arm
Fingers
Mock Flow Loop

Drawings, Schematics, Flow Charts, Simulations

Control System

Motor Driver:
Motor Driver
Motor Driver Documentation

Power Supply:
5V Power Supply
5V Power Supply Documentation
24V Power Supply
24V Power Supply Documentation

Solenoid Driver:
Solenoid Driver

Drive System
Drive Controls Schematic
Priming of Air Flow System
Air Prime Controls Schematic
Arm and Finger System
Air Prime Controls Schematic
Controls Preliminary Code: Xbox controller Arduino code
Controls Risk Management: Bad User Input

Navigation System

Feasibility: Torque Analysis
Full Model Assembly:
Entire Mechanical System
Base Model Assembly:
Base Model
Upper Model Assembly:
Upper Assembly Model

Force Actuation System

Feasibility: Air System
Detailed Flow Loop:
Detailed Flow Loop Schematic
Mock Flow Loop:
border|Mock Flow Loop Schematic

Bill of Material (BOM)

We consolidated the BOM of each subsystem into one: Total BOM

Test Plans

Control System

Solenoid Driver Test

Control Test Plan

Navigation System

Motor Speed Test

Frame Test

Battery Life Test

Force Actuation System

Mock Flow Loop

Arm and Fingers Test

Design and Flowcharts

Updated System Architecture

3 Subsystems:

  • Control System
  • Navigation System
  • Force Actuation System

border|Updated System Architecture

Risk Assessment

Updated Risk Assessment