P16261: EV Team 3-Phase AC Motor Controller A
/public/

Systems Design

Table of Contents

Team Vision for System-Level Design Phase

Summary:

Functional Decomposition

Purpose

Our Functional Decomposition diagram shows the breakdown of function that the motor controller should perform. The driving question for the entire diagram from the top down is "how?", where the answer to that comes from the box(es) below. Conversely when read from the bottom up the question of "why?" is answered from the box above. Many of the boxes come from the engineering requirements.
Functional Decomp

Functional Decomp

Benchmarking

Purpose

Avoid redundant work by identifying already available solutions and concept options. Furthermore, to determine what the market has to offer versus what we currently have.
Benchmarking of Different MCUs

Benchmarking of Different MCUs

Concept Development

Purpose

Generate new concept options or combinations that can potentially exceed the benchmark concepts. Furthermore, the concepts can be subjectively worse than the current configuration, but improved in cost, or some other aspect. In general we aimed to improve upon the build of the default controller (what is currently mounted).

Concept Generation

Various Ideas for Concepts

Various Ideas for Concepts

Initial Concepts 1, 2 , 3

Concepts 1,2, and 3

Concepts 1,2, and 3

Morphological Chart

Purpose

The purpose of the morphological chart is to use the functional decomposition chart to develop different ideas and concepts of what *could* make up our final design. What flows together, what doesn't, just get the creative thoughts flowing. The ideas presented should fit the customer and engineering requirements but does so by using a variety of components.

Morphological Chart

Morphological Chart Options

Morphological Chart Options

Concept Selection

Selection Criteria

Selection Criteria for the Concepts

Selection Criteria for the Concepts

Agreed Upon Concept

Our Chosen Concept

Our Chosen Concept

Pugh Chart

The Pugh Chart Puts It All Together

The Pugh Chart Puts It All Together

Systems Architecture

Mapping of the Engineering Requirements

Mapping of the Engineering Requirements

Feasibility Questions

Why use FOC, Anyway?

Why use FOC, Anyway?

How can we best Monitor Velocity?

How can we best Monitor Velocity?

How can we best Monitor Throttle Position?

How can we best Monitor Throttle Position?

Risk Assessment

Updated Risk Management Table

Updated Risk Management Table

Design Review Materials

Customer Requirements

CAN BUS Via EVT

Delfino versus Piccolo Overview

Slow speed/no speed FOC

Plans for next phase

By next review we hope to be building the supporting circuit and programming the MCU so that we can begin doing simple simulations and mock ups. By doing this we allow ourselves ample time to make adjustments (Fail soft and quickly!)

Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Subsystem Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Integrated System Build & Test with Customer Demo | Customer Handoff & Final Project Documentation