Meeting Minutes: Team Operation Charge

4/7/2018 Page 1 of 2

I. Block Diagram a. Engine: i. Not enough torque to get turn-over. ii. Also need to make sure battery pack is charged (plan ahead). iii. Connect to starter instead of using alternator for starting (will need to weld a new bracket possibly). iv. Could study engine on its own without other parts factoring performance. v. Or we could pull out APU and do separate tests so APU could be more isolated and be less interfaced. b. Alternator Controller: (inverter controller) i. Enable line must be connected to positive. c. Batteries: i. New bow is in, but they are having trouble charging the batteries. ii. The other team wants to have it charged by tomorrow and possibly take it for a spin. iii. 360 pack should float not be grounded

II. Efficiency Diagrams- Some in documentation on CD. a. Could estimate efficiencies in gear reducer, differential, axles, wheels, etc. i. Most differentials: 10% loss ii. Portal Axles: 3-5% loss iii. Gear reducer: 3-5% loss b. The original documentation on the gear reducer is available.

III. From Shop Today: a. Possibly check once more with charged batteries to see if we can get it started. b. But we probably need to take the engine out, and work on it separately.

IV. To test the Alternator: a. Pull off with inverter and some wires, but try to keep everything close to generator if possible b. Possibly recreate setup for generator. c. Need a liaison to communicate with Unique Mobility for troubleshooting. (John) d. Could de-couple starting and charging feature if needed.

V. Cost analysis on another propulsion system (4WD) just in case.

VI. Questions: a. Contact Unique Mobility-John b. Can engine be started? Try de-coupled mode. 4/7/2018 Page 2 of 2

c. Does the alternator operate correctly as either a starter or inverter? d. Can we clarify the workings inside the ‘black boxes?’ e. Alternator-controlling load or throttle? Check Dave Riche’s paper on throttle control. f. What do we want the data acquisition system to collect data on to monitor performance? Check with Herb Hess to clarify. g. Who could get us up to speed with the state of the current DAS software? i. LabView – MEs have some experience. Edwin volunteered. ii. Tim and Jason could explain LabView changes from the summer.

VII. Tasks/Goals: a. Write up meeting notes to keep Herb in the loop. i. Identify strengths and weaknesses for improvement. b. Formulate questions for interview with Dean and Herb. c. Get in shop and work on alternator, identify problems. d. Contact Unique Mobility. e. Continue work on website. f. Continue reading documents and learning about HMVEE current state.

VIII. Strengths and Weaknesses: a. Strengths- i. Team is much more knowledgeable on state of HMVEE. ii. There was more productive discussion of problems and possible solutions. iii. More questions asked and answered. b. Areas for improvement- i. Meeting organization. ii. Documentation of deliverables and weekly goals. iii. Team member reports.