P07221: FSAE Vehicle Dynamics
/public/

Home

Table of Contents

Administrative Information

Project Name
FSAE Vehicle Dynamics Platform
Project Number
P07221
Project Family
P07220 FSAE Autosports - Family of Projects
Track
Vehicle Systems Technology
Start Term
2006-2
End Term
2006-3
Faculty Guide
Dr. Alan Nye (ME)
Faculty Consultant
Prof. George Slack (EE)
Primary Customer
FSAE Racing Team
Secondary Customers
FSAE Competition Rules

Project Overview

The Vehicle Dynamics System Senior Design Project was initiated because of a strong desire of the students to understand and learn more about the operation, tuning, and design of the RIT Formula race car. This vehicle is built from the tires up every year with all of the work being placed upon the students to design, build, test, and successfully compete with the car.

Along with being a student interest project, the Vehicle Dynamics System also provides a way for RIT to expand its Multidisciplinary Senior Design Class, making it very attractive to the school as well. Opportunities for challenging projects exist for students majoring in not only engineering, but also computer science, information technology, industrial design, mathematics, and even nutrition, biology and pre-med, which in the past have not been incorporated with the multi-disciplinary projects.

With this being said, this report will layout what the framework of the system is, the goals of the first senior design team, and a list of possible projects of the future so that the system can be more thoroughly understood.

Staffing Requirements

Faculty Staffing
Team Member Discipline Role / Skills email address
Alan Nye ME Faculty Guide, Will work closely with the team on an on-going basis to facilitate success. ahneme@rit.edu
George Slack EE Faculty Consultant, Will provide EE discipline technical support on an intermittant basis. gbseee@rit.edu
Student Staffing
Team Member Discipline Role / Skills email address
Laurie Underhill ME Project Manager- This student is responsible for guiding his or her team members to achieve the goals set forth in the mission statement above. The Project Manager will need to delegate work effectively, and will also have a key role in design approval by being able to evaluate the input from all of his or her teammates, and help the team make critical decisions. This position is responsible for managing finances, setting up meetings, and editing the final report presented at the end of each Senior Design section. lju4592@rit.edu
Sean Carmody ISE Process Control Coordinator- This student is responsible in aiding the Project Manager with the overall organization of the project throughout the course of Senior Design I and II. Since the project will come together during testing days that are scheduled for the spring quarter, this student will have the additional responsibility of creating a schedule of tests to be performed. These tests will serve to validate the vehicle dynamics model through correlation with DAQ data acquired during the testing. sjc8414@rit.edu
Anthony Capobianco ME Test Engineer- This student has the responsibility of seaming the gap between the previous Data Acquisition Senior Design Project and the Vehicle Dynamics Platform Project. The main objective of the Test Engineer is to update the current DAQ system on the F13 racecar so that accurate data can be collected during spring quarter testing. This data will be needed to validate the vehicle dynamics model created by the Analysis & Simulation Engineers, so the Test Engineer will work to eliminate as much error from data collection as possible. The position involves detailed analysis of currently functioning electrical systems on the Formula car, and possible repair and redesign of existing systems. The student should be majoring in Electrical Engineering or Mechanical Engineering, and should have experience with CDS TrackMaster Software and Command Link. awc1275@rit.edu
Nick Tryt ME Test & Analysis Engineer- This student is responsible for seaming the gap between the physical vehicle and the simulated model of the vehicle. This involves eliminating as much error from the DAQ system as possible, as well as refining the vehicle dynamics model controls. The Test & Analysis Engineer will work closely with the Test Engineer throughout Senior Design I and II. The Test & Analysis Engineer is also responsible for coming up with the requirements for a stand alone DAQ system. Ntryt@mail.rit.edu
Kyle Burmester & Laurie Underhill 2 ME Analysis & Simulation Engineers- These students are responsible for generating a vehicle dynamics model of the RIT FSAE F13 Racecar. Their objective is to correlate the model to test data collected over the summer. The model will be flexible enough so that it can be expanded to future RIT FSAE racecars, allowing the RIT FSAE team to be able to make design changes more confidently, as well as to predict how changes in tuning will affect the handling of the vehicle. The model will be verified through testing performed during Senior Design II. The Analysis & Simulation Engineers are also responsible for generating a vehicle dynamics database so that a record of design and tuning decisions, along with explanations of these choices can be referred to with ease. KJB8643@rit.edu
Franklin DiBartolomeo ME Design and Analysis Engineer- This student is responsible for assisting the design engineer in the creation of the test stand that will be used during spring quarter testing. This student may also be called on to help model specific subsystems of the vehicle. The test stand should promote ease and efficiency of testing. Dragcarz@hotmail.com
Todd Mangiagli ME Design Engineer- This student is responsible for the design and manufacture of the test stand that will be used during testing days in the spring quarter. The position should be filled by a student majoring in Mechanical Engineering, and who has a strong background using Pro-Engineer or another 3-D modeling program. Besides modeling the physical elements of the Vehicle Dynamics Platform, the Design Engineer must keep a log of all hand calculations and resources used during any design process that takes place. The person who fills this position is responsible for ordering any materials that are required by the project after approval by the team and Project Manager, setting up shop time for machining, and fabricating any structures that are required by the project. As such, the Design Engineer must be familiar with machining processes and practices. The student who takes on this role must be able to communicate technically with the Analysis Engineer. The student entering into this role must have a strong background in Materials Processing, Statics, Mechanics of Materials, and DME. tvm_8@hotmail.com

Continuation, Platform, or Building Block Project Information

The Vehicle Dynamics Platform Team has a strong desire to help keep RIT at the forefront of technology, specifically through the development of an analysis system for the Formula SAE Racing Team. This project will require the knowledge and skills of students from various academic backgrounds, predominantly in the field of engineering. The Vehicle Dynamics Platform Team will expand upon the Data Acquisition Senior Design Project that was completed in 2005, creating both a physical testing station, and a computer analysis system that takes the acquired vehicle dynamics data and translates it into useful tuning and design information. These outputs can then be used immediately to make any necessary alterations to the car so that it can achieve optimum performance and handling.

Principle Sponsor or Sponsoring Organization

This project is sponsored by the RIT FSAE Competition Team.

Detailed Project Description

Customer Needs

The Vehicle Dynamics System Senior Design Project was initiated because of a strong desire of the students to understand and learn more about the operation, tuning, and design of the RIT Formula race car. This vehicle is built from the tires up every year with all of the work being placed upon the students to design, build, test, and successfully compete with the car.

Along with being a student interest project, the Vehicle Dynamics System also provides a way for RIT to expand its Multidisciplinary Senior Design Class, making it very attractive to the school as well. Opportunities for challenging projects exist for students majoring in not only engineering, but also computer science, information technology, industrial design, mathematics, and even nutrition, biology and pre-med, which in the past have not been incorporated with the multi-disciplinary projects.

Learning Objectives for Student Members

One of the primary goals of this project is for each student member to acquire useful skills and experience in areas related to their intended career paths. Each student is expected to contribute to the workload to accomplish this project, and to interact with one another successfully. This project has been specifically tailored to utilize a variety of majors within the field of engineering and beyond this major so that the students learn how to communicate and interact with each other effectively. In addition to being multidisciplinary across the Kate Gleason College of Engineering, the Vehicle Dynamics Team hopes to attract students from other majors outside of the engineering fields. Students from Mechanical Engineering Technology, Industrial Design, Finance, and other departments will be consulted for guidance and assistance when necessary. By the end of Senior Design II, each student member should have applied the knowledge that they have been gathering over the course of their education at RIT.

Primary Customers

The Vehicle Dynamics System Design Team is sponsored directly by RIT and may receive additional funding from the RIT SAE Formula Team as well if the need is justified. As such, the design team will remain focused on achieving the goals laid out by these two groups, each customer having their needs defined below:

Kate Gleason College of Engineering

The college wishes to have a system that is complete two weeks before the end of the quarter to allow adequate time for testing and debugging. The system needs to be proven on the F13 race car, however, the main goal of this project is to create a system that is flexible enough to be utilized in future applications. The vehicle dynamics platform should foster a deeper understanding of the mechanics and dynamics of Formula SAE racecars, which will in turn help students to apply this knowledge to in their careers. The system must be user friendly and easy to learn.

RIT SAE Formula Race Team

The RIT Formula Team hopes that this project will create an even greater interest in learning about vehicle dynamics and mechanics within the team. Through a combination of hands on testing and vehicle dynamics simulation, the team will be able to understand the limits of their racecar, and will be able to tune the car to the best of their ability. Tuning the racecar is one of the most important aspects in racing and bringing down race times. By providing hard data immediately to the team members as the car is being driven, the team can more readily and quickly resolve problems with the handling, performance, or safety of the car. The team hopes to have a working system on the F13 racecar as a prototype of the design. In the years that follow F15, the team hopes to implement the system within future cars.

Background Information Provided by the Customer

In 2005, an RIT Senior Design Team implemented the first Data Acquisition System onto the F13 Formula SAE Race Car. The background of this project is summarized on the RIT EDGE website, however, a more detailed description can be found in the Final Design Report, which will be provided if you decide to be on this senior design team. Each student participating in the Vehicle Dynamics Platform Senior Design Project is required to read this report before the first meeting of Senior Design I in Winter 2007.

Look up project P05109 for information on the DAQ system on F13 under the Project Information Tab on the left side of the screen, in the 2005-2005 archives.

These are some websites that you might want to look at if you are interested in being on the team.

http://www.rit.edu/~formula/lobby/lobby.htm

http://www.carbibles.com/suspension_bible.html

http://www.competitiondata.com/commander/prod_main_commander.htm

Race Car Vehicle Dynamics by Milliken

Customer Concept

With this being said, this report will layout what the framework of the system is, the goals of the first senior design team, and a list of possible projects of the future so that the system can be more thoroughly understood.

Framework

The Vehicle Dynamics Senior Design Team is responsible for creating a system. As with all systems, there are several subsystems that makeup the overall structure. This section will layout the four main divisions of the Vehicle Dynamics System, along with preliminary goals that are associated with each.

public/FSAETestingSystem.jpg

public/FSAEAnalysisSystem.jpg

public/FSAESimulationSystem.jpg

public/FSAEDesignSystem.jpg

public/FSAEFramework.jpg

Customer Deliverables

This year, the team hopes to establish the Vehicle Dynamics System more than anything and get the wheels spinning on related project creation for future students. The team will focus on gaining and in-depth knowledge of the testing, analysis, and simulation programs available currently, and will work on creating their own simple model of the F13 race car that will be modified to work with the new F15 car that will be finished in 2007. The model will use simplified theory and will rely on much of the work done by Milliken and others as documented in Race Car Vehicle Dynamics. The team will also be responsible for providing guidance for future senior design teams who wish to model the subsystems of the car for a more detailed and realistic simulation of the car. The simplified model must be expandable and modular to facilitate this. If time permits, the F13 suspension system will be modeled as well, with the results of this simulation being compared against DAQ data and hand calculations. A report of possible areas where improvement can occur will also be included, paying special attention to tuning and design changes in the specific realm of the suspension system.

Probably the most difficult task of the team will be to make the system flexible and therefore able to work with any car the Formula Team can think up. This means for starters that newly designed system components, such as the analysis and simulation systems must be created with a lot of foresight and with a lot of input from experienced Formula Team members and drivers. In addition, and probably even more difficult will be making the current DAQ system a completely independent system that can be installed easily and reliably on any RIT Formula Car. This will involve a lot of analysis and design specifications, along with some possible DAQ simplification for future cars. The DAQ system is an amazing system to have, but unfortunately, it has some limitations in interchangeability and ease of use currently. The 2006-2007 Senior Design Team will have a lot on their hands as they address this issue.

The team will also complete all of the testing tasks mentioned above. Creating the test stand, test procedures, and just basic methodology will be the first steps in making the system functional and easy to learn and operate.

The final results will be extensive, and it is expected that each team member will gain a lot of valuable experience in a variety of fields and areas of interest pertaining to race care vehicle dynamics.

  1. All written documentation must be performed in an organized and uniform format. Any documents that are submitted as final must follow the format included in Appendix A of this document. An electronic version will be available to all team members upon project start up.
  2. All files must be saved on both CD and jump drive back ups for future project use and reference. As such, all files must be saved in a transferable format. A Master Drive will be purchased for the team on which all final files will be saved in case of emergencies. The Project Manager is responsible for the Master Drive.
  3. All calculations and design specifications must be performed and documented in U.S. Customary Units. Electrical components that are available only in metric call-outs are allowed, but must have all parameters converted into U.S. Customary Units within the context of the final report.
  1. Each team member will have a log book that will be used throughout the course of the Vehicle Dynamics Senior Design Project to record meeting information, research performed, and any other information that is relevant to the team and/or project.
  2. The Team will have two to three formal meeting times established each week. This time will be spent updating each member with the progress that has been made by each sub-section of the team. Minutes will be recorded by the Process Control Coordinator. 10 to 20 hours are expected per week from each member of the team depending on role. All positions mentioned above will more than likely require 20 hours a week to accomplish the goals of this project to the furthest degree possible.
  3. All purchases must be approved by the Project Manager and must be logged in the team budget file. The budget file will consist of both a hard copy and an electronic version that will be updated weekly. A backup budget file will be stored on the Master Drive.
  4. The team will have a completed project two weeks before the end of Senior Design II so that enough time is allowed for testing of the system, data collection, and any system debugging that needs to occur.

Project Budget and Special Procurement Processes

Intellectual Property Considerations

All work to be completed by students in this track is expected to be released to the public domain. Students, Faculty, Staff, and other participants in the project will be expected to release rights to their designs, documents, drawings, etc., to the public domain, so that others may freely build upon the results and findings without constraint.

Students, Faculty, and Staff associated with the project are encouraged to publish findings, data, and results openly.

Engineering Specifications

Detailed Course Deliverables

Senior Design I

Senior Design II

Grading and Assessment Scheme

Grading of students in this project will be fully consistent with grading policies established for the SD1 and SD2 courses. The following level describes an absolute level of expectation for the design itself, and for the hardware. However, the student team must also meet all requirements related to analysis, documentation, presentations, web sites, and posters, etc. that are implicit to all projects.

Level D:
The student team will
Level C:
The student team will deliver all elements of Level D PLUS:
Level B:
The student team will deliver all elements of Level D and C PLUS:
Level A:
The student team will deliver all elements of Level D, C, and B PLUS: The final presentation will include F13 being driven around an autocross course that has been analyzed by both the MatLab program written by the Analysis Engineers and the CARSim software that has been learned by the Simulation Analyst for the F13 car. The Vehicle Dynamics platform will collect the data as the car is driven around the track in real time, recording lap times and displaying a video of the car as it is being driven. The software package provided by the Computer Engineer and the Electrical Engineer will output the data into a useful interface, and directly compare it to the hand calculated data and the simulated data. Upon analyzing the data from all three references, the program will output a recommendation for tuning the car, whether it be changing the air to fuel ratio, interchanging springs with a different stiffness, or adjusting the damping of the vehicle. (The actual interface output of this will depend upon the experience and knowledge of the Computer and Electrical Engineers; simple graphs and charts may be output instead of an actual prompt or statement, so that the drivers and Formula Team members can easily analyze the data; ideally, the system will be smart enough to suggest what to tune -- this is a HUGE task, so the parameters we will analyze must be limited accordingly.) All of the parameters that can be changed will be determined by the design group during the first few weeks of Senior Design I. Upon further analysis, the students will learn how factors that cannot be changed as easily effect the performance of the vehicle, or possibly other parameters that can be changed may be stumbled upon. These parameters will be analyzed through hand calculations and CARSim, but will not be analyzed with the DAQ system. Instead, future Senior Design teams can write more code within the program if the design changes in a future car, or if another parameter becomes adjustable, such as driver seating position for example. The system will then have met its goal, and can offer useful information for the design engineers of the Formula Team in the future as they learn how each component and input to the car affects performance and handling. The project should also prove reliable correlation of DAQ data to CARSim data.

Three-Week SDI Schedule

Pre-Senior Design I tasks

The Vehicle Dynamics Analysis Project was initiated out of a strong desire for students to truly understand vehicle performance and handling to the best of their ability. Any person who agrees to participate on this team should be fully aware that it is a very large project with almost limitless options. As such, a general schedule has been laid out below with ideas that will help shape the direction of the project. Most of what is included here will remain solidly in tact, and must be completed to accomplish the goals presented in the mission statement of this project. This being said, however, there will be plenty of room for new ideas to be presented by all team members, and the direction the team decides to go in will be just that -- a team decision. If you are assigned a position on this team, you must be willing to learn and willing to listen, as well as willing to offer your own opinion. We are all relatively new at the design process, so these thoughts should always be at the front of your mind. A list of tasks is presented below. All team members are expected to have completed these before the first meeting of Senior Design I.

First Two Weeks

Week 1: Meeting #1
Team question and answer session concerning DAQ, previous senior design project, Formula SAE at RIT, machine shop rules and hours, introduction of each team member to the team this should include what your interests are in engineering or your respective field of study, your goals for the project, contact information, what your strengths are, and what you expect to bring to the team. This session will be approximately 2 hours long as we will be reviewing all of the tasks each team member was responsible prior to the start of Senior Design I. Come with your ideas and be ready to put your opinions out on the table. This is a pure brainstorming session with no feedback immediately. Each person will take their own notes, and will spend time on their own before the next meeting thinking about the ideas that were presented during this first meeting. In addition to this, each team member is responsible for talking to one member of the Formula team and finding out what they would like to know when they are driving and how a vehicle dynamics analysis system could help them. This will be very informal, just a way to introduce yourself to the team and get to know why we are working on this project in the first place.
Week 1: Meeting #2
During this session each member will bring their comments and concerns about the ideas brought forth in the first meeting. Team members will discuss the ideas they liked and disliked. From here, the team will start to layout the structure and form a timeline and schedule for the rest of the quarter as far as meeting times and deadlines go. Some deadlines have already been established and have been put in place to ensure the project is completed by the set date. The second session will involve an in depth needs assessment. Each member should be familiar with the DAQ system by this time, and should have a good idea of what the school and the RIT Formula Team wants out of this project through the brief discussions they had with the team members. A formal list of needs that will be referred to for the rest of the design process will be formulated at this time.
Week 1: Meeting #3
This meeting will begin the Voice of the Engineer part of the design process. The team will work together to sort through all of the ideas that were brought forth and debated in the first two sessions. A list of parameters that will be gathered, tests that will be performed, and methods of presenting the data will be created. A finalized schedule for the Winter Quarter will be completed at this time, and weekly meeting times will be established. Each sub-team will also set up times to meet besides the two to three formal meetings established each week.
Week 2: Meeting #4
During this meeting, the abstract goals that were decided upon during the third meeting will be brought to life through concept development. This will involve a drawing session that will last 2 hours where each person will draw what they envision the final design looking like. The first hour will be spent just drawing the physical system that the team will take down with them to the driving site, the DAQ system on the car, the way the software interface will look like, how the system can be made to be flexible and usable on future racecars, and pretty much any ideas that the team can think up. The second hour will involve rotation of drawings around the room so that each member can add comments or questions, or draw on your work themselves. At the end of the meeting, each person will present their original idea, and if another member made a comment or has a question, these issues will be addressed as well. This session will aid the design engineer when they begin drawing and creating the physical system in a 3-D modeling program, while allowing each team member to have input to the design process. The design engineers will be responsible for collecting all of the drawing information relevant to the physical model, and putting it into an organized format. They will then prepare a presentation that takes the ideas that they see best fit for the project, and come prepared to meeting #6 with their preliminary design ideas.
Week 2: Meeting #5
This meeting will be very brief, but is necessary for establishing the role of each team member. The parameters that were decided upon and refined during the first four meetings will be gathered by the Analysis Engineers, and will be sorted out and organized according to the means available for acquiring the data with the provided DAQ system. The Process Control Coordinator will meet with the Analysis Engineers between the 5th and 6th meeting to organize the parameters in such a way that they are gathered in the most efficient and easy to understand manner. This will involve becoming knowledgeable about how a competition is typically run, what drivers need as feedback to bring their times down, and what parameters influence suspension or engine tuning. The Electrical Systems Engineer will be responsible for mapping out the current wiring system on the car and coming up with ideas as to how to improve it, or simply assessing whether or not it is capable of operating the car and the DAQ system simultaneously. Any problem areas should be addressed and solutions proposed. The Simulation Analyst will be learning CARSim and TrackMaster inside out during this week of Senior Design. They will begin brainstorming ways to converge the data that can be gathered from static and dynamic analysis (hand calculations performed by the chassis/suspension engineer on the Formula Team), vehicle simulation, and actual test data gathered from the DAQ. The simulation system is more or less the link between the hand calculations and the physical data, so correlation of all three is a main priority of this project. The Computer System Engineer will be responsible for brainstorming methods of storing and outputting the data to an easy to understand user interface.
Week 2: Meeting #6
This meeting will be used to bring together all the work done by each sub-group. Brief progress reports will be presented by each group, and comments and discussion will follow. Objectives for the next week will be laid out, and assignments made to keep the project on track.

Deliverables

Roles and Responsibilities Matrix
Project Summary
Three Week Plan
Needs Assessment
Tentative Deliverables
QFD
Concept Development and Selection
Winter Schedule

Weekly Team Tasks

January 15th - January 19th

Sean

- Get formal confirmation of test sites and dates for spring quarter
- Start brainstorming session on testing
- Tire data analysis wrap up

Anthony

- Hand in final instructions on how to save data in Trackmaster
- Complete the rough draft of the DAQ manual
- 5 minute update for team on DAQ progress
- Get pricing for 4 sets of tires

Nick

- 20 minute presentation to team on how calibration works on DAQ with Command Link
- 5 to 10 concepts for test courses with brief description of each course purpose for testing
- Get pricing for a camera
- Complete the rough draft of the Trackmaster manual

Kyle

- Attend meeting Wednesday to review final CARSim model
- Come to Wednesday meeting with most up-to-date database for data entry (we will use the database each Friday from now on as a way to organize all of our work; entering test courses, CARSim model info, DAQ and Trackmaster manuals, all instructions, test sheets, calibration, and any other relevant documentation from each week)

Laurie

- Hold meeting on Wednesday to review final CARSim model to be reviewed by Anthonys contact at Magna Powertrain
- Update webpage with team deliverables for this week
- Meet with anybody who has figured out how to use Subversion correctly
- 10 minute presentation Friday on how to install/use Subversion
- Organize all deliverables completed and submit to Dr. Nye
- Type up brief overview of concept development/selection for other Vehicle Dynamics Track (ECU) Team and email to them
- Update tire report with Seans data and with Suspension design info from Vehicle Dynamics group

Franklin

- 10 minute presentation of Engine Dynomation for Honda 600CBR
- Talk to Anthony about ordering 4 sets of tires
- Meet up with Todd to generate Bill of Materials and Budget for the test stand, along with a series of selected design concept drawings (this needs to be done by the end of Friday); the final concept needs to be brought back to the customer for review

Todd

- Generate Bill of Materials and Budget for test stand, along with a series of selected design concept drawings (this needs to be done by the end of Friday); the final concept needs to be brought back to the customer for review
- Prepare informal meeting with as many Formula team members as possible to review the final concept; (feedback needs to be documented as part of our final project portfolio)

January 22nd - January 26th

Sean

- 9:00 am to 3:00 pm - Complete full matrix of all possible tests that can be performed on F13 - submit to Laurie for entry into the database by 3:00 pm
o Perform feasibility analysis on tests and come up with a rough draft of the final test plan over the course of the next week
- 11:00 am meeting with Nick to get Test Sheets Rough Draft completed
- 4:00 pm meeting to decide 3 summer runs to be used for correlating CARSim model (these runs will have to be repeated in the spring, but will provide a baseline for the model - this will be included as a separate day on Seans test plan schedule)
- Email/give hard copy of tire spring rate data to Laurie
- Gill Ong with Parking Services - meet with him and reserve lots possibly
- Still waiting to here back from Marketplace

Anthony

- 9:00 am to 3:00 pm - prepare for preliminary design review of upgraded DAQ
- PRELIMINARY DESIGN REVIEW of UPGRADED - 3:00 pm on Friday with team
o Final sensor list and what each is responsible for (why we need them)
o Validation of new sensors
o Budget
o Filtering techniques
o Sampling rate justification (be specific)
o Required test days/ tests to validate calibrations
o Three-axis accelerometer math channel to account for CG offset
- 1 page Instruction Sheet on how use DAQ Card/ DAQ/ Command Link/ TrackMaster
o This will be laminated and included on the cart for easy reference
o MAKE IT SIMPLE!!
- Rough Draft of DAQ manual submitted to Laurie for review over the weekend
- Tire pricing updates if any
- 4:00 pm meeting to decide 3 summer runs to be used for correlating CARSim model (these runs will have to be repeated in the spring, but will provide a baseline for the model)

Nick

- 9:00 am to 11:00 am - TrackMaster Manual - Rough draft submitted to Laurie for review over the weekend
- 11:00 am meeting with Sean to get Test Sheets Rough Draft completed
- 1:00 pm meeting with Laurie and Kyle to get F13 Car File updated for correct calibration
- Email/submit hard copy of test courses to Laurie
- Purchase camera - $310 (Talk to Laurie about this sometime Friday)
- Update team about CDS solution for screen errors that were being experienced last week
- 2:00 pm meeting with Laurie and Kyle to determine what plots should be use to show CARSim and TrackMaster correlation
- 4:00 pm meeting to decide 3 summer runs to be used for correlating CARSim model (these runs will have to be repeated in the spring, but will provide a baseline for the model)

Kyle

- 9:00 am to 12:00 pm - CARSim
- 1:00 pm meeting with Laurie and Nick to get F13 Car File updated for correct calibration
- Update Database
o Nicks test course layouts
o F13 CARSim model info screen
o DAQ and TrackMaster manuals will be available next week Friday

Laurie

- 9:00 am to 12:00 pm - CARSim
o Enter Seans tire data into CARSim
o Enter Hoosier 7 inch width tire data into CARSim
o Set up meeting date with Anthonys contact at Magna Powertrain
o Get new dongle for CARSim; install on new computer
- Meet with Dr. Nye at 10:00 am about budget and how to make purchases
- 1:00 pm meeting with Nick and Kyle to get F13 Car File updated for correct calibration
- 2:00 pm meeting with Nick and Kyle to determine what plots should be use to show CARSim and TrackMaster correlation
- 4:00 pm meeting to decide 3 summer runs to be used for correlating CARSim model (these runs will have to be repeated in the spring, but will provide a baseline for the model)
- Organize deliverables in binder for team to review Friday at 5:00 pm (have done before Friday)
- Begin creating extended projects summary report for submittal to Dr. Hensel at the end of the quarter

Franklin

- 9:00 am to 5:00 pm - Work with Todd to prepare for preliminary review of test stand next Friday

o Final Bill of Materials with prices typed up and submitted to Laurie by 5:00 pm for review over the weekend

- 5:00 pm submit Engine Dynomation throttle curve for Honda 600CBR to be put into CARSim model
- Tire pricing updates if any

Todd

- 9:00 am to 5:00 pm - Prepare for PRELIMINARY REVIEW OF TEST STAND next Friday at 3:00 pm
o Bill of Materials with pricing (work with Franklin)
o Hand sketches
o Pro-E models
o Weight and effort to push the cart up the hill analysis
o Have team try and push up another cart to see if they will actually do it
o Drawer organization and specific tools and equipment (exactly what should be on the cart, no more, no less)
o Ergonomic study: will the cart be user-friendly, easy to push/pull, and comfortable to work at
o Reevaluate the purpose of the cart and who will be working with it/at it to validate final design decision

January 29th - February 2nd

Sean

- Forward test sheet to Laurie for review at Formula meeting before Monday night, 1/29/07
- Submit complete full matrix of all possible tests that can be performed on F13 to Laurie via e-mail
o Submit feasibility analysis on tests and come up with a rough draft of the final test plan over the course of the next week

Anthony

- Work on filtering profile for each sensor - this should be documented and submitted to the senior design binder in 2 weeks
- Meet with Dr. Kempski in the next 2 weeks to discuss Butterworth filtering methods vs. other methods
- Call Stan and see if he can send us any testing sheets - if so, forward these to Nick and Sean
- Submit DAQ manual to Laurie for review this weekend
- Go through new sensor/parts list and see what we have at the shop already (organize sensor bin over the course of the next few weeks so that if we need spare sensors, parts, etc, we know where they are...the big gray bin in the CNC room)- submit final budget for sensors to Laurie two weeks from 1/26/07, and put purchase order in through Laurie
- Get official pricing for tires so we can put them into the budget and order them next Friday
- Proper DAQ calibration to be completed by the end of this quarter

Nick

- Meet with Laurie and Kyle Wednesday, 1/31/07 to come up with CARSim/TrackMaster plots that will be most useful by the team
- Come up with a list of possible plots of interest before Wednesday so the meeting can happen quickly
- Get gear data, geometry data, and tire rollout data for F13 Car File from Laurie
- Purchase camera - $310 (I will put the order in this Friday if the budget says we can get it; we'll have to talk to Dave about how to order this since it's through e-bay)
- Update team about CDS solution for screen errors that were being experienced last week
- Proper DAQ calibration to be completed by the end of this quarter

Kyle

- Meet up with Nick and Laurie Wednesday, 1/31/07 to go over plot selection (correlation between CARSim and TrackMaster) and to finish up the CARSim model
- Update Database
o Nicks test course layouts
o F13 CARSim model info screen
o DAQ and TrackMaster manuals will be available next week Friday
o Test Sheets

Laurie

- CARSim and plot meeting Wednesday
o Enter Seans tire data into CARSim
o Enter Hoosier 7 inch width tire data into CARSim
o Set up meeting date with Anthonys contact at Magna Powertrain
o Get new dongle for CARSim; install on new computer
- Decide 3 summer runs to be used for correlating CARSim model (these runs will have to be repeated in the spring, but will provide a baseline for the model)
- Organize deliverables in binder for team to review Friday at 5:00 pm
- Begin creating extended projects summary report for submittal to Dr. Hensel at the end of the quarter
- Work on Tire Data Tuning Report
- Work on system explanation for next year's Vehicle Dynamics Group Leader

Franklin

- Work with Todd on the test stand
- Find anything out at Sears? place orders next week

Todd

- Prepare for PRELIMINARY REVIEW OF TEST STAND next Friday at 3:00 pm
o Bill of Materials with pricing (work with Franklin)
o Hand sketches
o Pro-E models
o Weight and effort to push the cart up the hill analysis
o Have team try and push up another cart to see if they will actually do it
o Drawer organization and specific tools and equipment (exactly what should be on the cart, no more, no less)
o Ergonomic study: will the cart be user-friendly, easy to push/pull, and comfortable to work at
o Reevaluate the purpose of the cart and who will be working with it/at it to validate final design decision

Required Resources

Faculty
Item Source Description Available
Prof. Nye ME Faculty Guide Yes
Prof. Slack EE Technical Consultant Yes
Environment
Item Source Description Available
ME Shop ME 09-2360 Parts Fabrication Yes
Equipment
Item Source Description Available
F13 Race Car RIT FSAE Team Prior Year Competition Vehicle Yes
Desktop PC ME Dept Desktop Programming & DAQ Yes