P18222: RIT Baja Two-Node DAQ
/public/

Problem Definition

Table of Contents

Team Vision for Problem Definition Phase

The goal for this phase was to gather information about the scope of the project, what the customer required, and what needed to be delivered at the end of the project.

What was accomplished this phase was customer interviews were done to draft problem definition, use scenarios, determine who the stakeholders are, and the customer and engineering requirements. Preliminary schedule and benchmarking were created during Phase I and will be updated per Phase II.

Project Summary

The RIT SAE Baja Team acquires multiple forms of data on their vehicle during a race. A few key systems that are monitored are the vehicle's frame, driveline, and suspension subsystems. Our project would streamline this acquisition of the race data into a multi-sensor node acquisition system. One node would acquire frame and suspension strain gauge data, one would acquire driveline temperature data, and another would capture hall effect data for engine RPM and wheel speed. The nodes would communicate with one another (via CAN) to collect data from the vehicle subsystems. The strain sensor node would collect strain points along the frame and suspension components to calculate frame stress. The temperature node would acquire temperature of driveline components including the clutch cover and belt. The Hall Effect sensor node would collect two RPMs to calculate clutch ratios. Expandability will be built into this system so that more sensors and nodes can be added to the DAQ unit for future race data collection.

Customer Interviews

Interviewee Date Notes
Nathan Mckerley 8/30/2017 Notes

Stakeholders

  1. Project Manager
  2. Data Acquisition Lead
  3. Drive Line Lead
  4. Suspension Lead
RIT Baja Team

RIT Baja Team

Use Cases

Scenario 1: Car rolls over in a race and damages suspension, data is analyzed after the race, suspension team determines if a redesign is necessary, project manager reviews re-design if re-design is proposed, redesign occurs.

Scenario 2: Car does not place high in the endurance race, race data is analyzed, driveline team determines if re-tuning or a redesign is necessary, project manager reviews re-design if re-design is proposed, re-tuning/redesign occurs if recommended and reviewed.

Scenario 3: Car gets first place in the endurance race, race data is analyzed, driveline team and suspension team determines design performed as desired, data is presented at the next design competition.

Workflow Map

Workflow Map

Project Goals and Key Deliverables

A working prototype that can acquire data from hall effect sensors, thermocouples and strain gauges as well as an external software program to be used for converting raw sensor data to data with proper units.

Customer Requirements (Needs)

Customer Requirements

Customer Requirements

The live Customer Requirements document can be found here.

Engineering Requirements (Metrics & Specifications)

Engineering Requirements

Engineering Requirements

The live Engineering Requirements document can be found here.

Constraints

Design Review Materials

The Problem Definition Review Presentation from 9/18/2017 can be found here.

House of Quality

House of Quality

House of Quality

The live House of Quality document can be found here.

Plans for next phase

Phase 2 Schedule

Phase 2 Schedule

The live schedule can be found here.

Individual Plans

Member Plan
Odysseus Adamides Phase 2
Amanda Vallat Phase 2
Ross Erwin Phase 2
Joseph Green Phase 2

Home | Planning & Execution | Imagine RIT

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

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