Week 5 - Sites at Lafayette
Contents
1. LCD and computers John Bloore John Bloore Computer controllable throttle input to motor controller John Gehrig John Gehrig Embedded Linux Installation VAB 820 https app asana com 0 search 27543017738645 2754301 7738645 due Feb 27 due Feb 28 due Feb 28 due Feb 28 due Feb 28 due Feb 28 due Feb 28 due Feb 28 due Feb 28 due Feb 28 due Feb 28 due Mar 1 due Mar 1 due Mar 1 due Mar 1 due Feb 28 due Feb 27 1 5 2 22 2015 Search Asana John Gehrig Place the purchase for embedded system John Gehrig Place the order for dashboard and microcontrollers Jordan Blake Jordan Blake Hardware interface control specification Jordan Blake Correct AMS layout errata Jordan Blake Completed pack wiring diagram Jordan Blake AIR failure sensor for main fuse Jordan Frank Jordan Frank Connector Inventory JF Jordan Frank Connector BOM JF Jordan Frank Connector Order JF Kai Ottaway Kai Ottaway Rearrange top of box Katie Nellis Katie Nellis Detailed specifications for each subsystem type Katie Nellis Updated system design Katie Nellis Correct BoB board errata Nate Hand Nate Hand Program the motor controller using the Curtis software Nate Hand Motor Controller Cooling system built Nick DiNino Nick DiNino GLV Battery Circuit Sketches ND Significant redesign of the circuit used as a power monitor has pushed back sketching of the circuit Nick DiNino GLV Power Internal Lay2. include a compliance matrix making it obvious that all requirements have been addressed by the plan Numerical specifications shall be considered passed if the measured value is demonstrated by empirical statistical trials to meet the specification at a 90 confidence interval https app asana com 0 search 27543017738645 2754301 7738645 5 5
3. of the circuit used as a power monitor has pushed back sketching of the circuit Nick DiNino GEV Battery Panet Sketches ND Rameel Sethi Y Rameel Sethi Simpte startus seftware cn Virtualbex Sam V Sam Seftwaretevet GAh eutine anctibrary desigt Stephen Mazich Y Stephen Mazich UserManuat https app asana com 0 search 27543017738627 27282623335957 due Feb 22 due Feb 21 due Feb 23 due Feb 22 due Feb 22 due Feb 21 due Feb 19 due Feb 22 due Feb 21 due Feb 21 due Feb 21 due Feb 20 due Feb 20 due Feb 19 2 3 2 22 2015 Search Completed pack wiring diagram Asana William Stathis William Stathis Sehemateimptementation for GA bus due Feb 22 Yiming Chen V Yiming Chen GempleteUserManuat due Feb 20 Zach Helwig V Zach Helwig YGtPanetSketehes ZH due Feb 21 V Zach Helwig GLY Hub Panet Sketehes ZH due Feb 21 Zach Helwig Side PanetParetSketehes ZH due Feb 21 Unassigned User Manual Update due Feb 21 ATP submission 2 due Feb 21 D011 Calibration and Accuracy due Feb 23 Any data acquisition system design or test plan must be accompanied by a Calibration and Error Analysis document that estimates the uncertainties associated with all system measurands This document must include both analytical estimates of measurement uncertainty as well as a justified design of acceptance tests to determine the uncertainty achieved in practice The testing design from this document shall be incorpor
4. pin adapter Motor controller TSV Advanced Circuits PCD AMS and BOB boards parts from Mouser parts from digikey 32 14 52 150 16 68 55 44 6 150 40 79 37 55 15 19 15 15 150 total 75 00 50 00 1 00 20 total 16 459 141 7 29 04 150 16 68 220 44 6 150 40 79 37 55 24 30 38 15 15 150 1397 9 75 00 50 00 3 00 20 00 148 00 512 00 459 00 141 70 Microcontroller Micro SD card 4GB Class 10 industrial Fuse 200A Class T A3A 300Vac 160VDC Fuse Holder 200A AC 300V a Pole molder Fans 119x25 24DC 100CFM 5W 2900RPM 43 dbA AIR 350A contractor 50A miniTactor Panel Drain Line 3 Grey Panel Source Neutral Blue LCD Character Display Module STN Y G Galvanically Isolated Ethernet Other Parts Total Money 5000 Total Requested 8310 43 Remaining Money 3310 43 A A WwW OQ A A A HRN N A A 308 924 00 10 54 31 62 28 34 113 36 71 81 287 24 40 95 163 80 94 35 660 45 40 280 00 51 26 205 04 54 33 217 32 11 5 46 00 102 408 00 1600 1 600 00 0 00 0 00 total 6 049 53 2 22 2015 Search Completed pack wiring diagram Asana Tasks due within the last 7 days Adam Cornwell Adam Cornwell Finatize system states and define inputs outputs Alex Hytha V Alex Hytha Femp Senser cheser and ordered V Alex Hytha S Safety Plan TSV safety plan must be written R ine AMIS PCP R ine B Reset AMS PGBs Reset Pacman A
5. Status Letter Week 5 2 22 15 LFEV Team Milestones VSCADA Last week System block diagrams and the GUI designs are drawn and included in the user manual Able to run python code automatically after the system startup This week We are going to deliver the user manual We will set up the logging daemon on the virtualbox Install Linux on the embedded system once it arrives Place the order for dashboard and microcontrollers DYNO Last Week User manual completed and submitted to the website Temperature sensor for motor selected and ready to order Dyno software loaded onto computer Dyno software works with Dyno sensors This Week Computer controllable throttle input to motor controller for safe and accurate out of room testing Motor controller programmed using the Curtis software TSV Last week we completed the schematic for implementing CAN on the BoB We also completed schematics for a full system reset and the 24V pack indicator though due to technical difficulties they are not all integrated into the same DxDesigner file Additionally we produced a pack wiring diagram for the TSV packs which was conspicuously missing from last year For next week we plan to begin working on the CDR write the maintainability plan and fix the AMS board schematics Also we will put out orders for the AMS boards the new LCD displays and the computers we will be using GLV Last week we sketched out all panel interfaces excep
6. ated into the system ATP D004 Acceptance Test Plan due Feb 23 The Acceptance Test Plan ATP is a document that describes how the system as a whole will be tested and demonstrated so as to prove compliance with all requirements and specifications The ATP should include forms that can be filled out by testers during execution These filled out forms will be used to create the ATR Compliance must be conclusively proved in any of the following three ways e Analysis detailed logical analysis can demonstrate compliance by reasoning from known facts a priori or empirically similar to the form of a mathematical proof Analysis can be used cited research results in conjunction with the documented results of subsystem QA testing along with generally accepted technical principles to prove system level requirements are met Analysis memos and relevant data are attached to the ATR e Test an explicit test experiment or demonstration can be used to prove compliance with a certain requirement by acquiring new empirical facts and combining these with analysis as described above The comprehensive results of any measurements conducted as part of an ATP testis included in the ATR along with date and time of the test the pass fail criteria uncertainty statistical confidence pass fail result witness name and witness signature e Inspection compliance is made evident by directly examining the system Photographs with detailed annotations or ot
7. dynamometer motor and controller to the design and the re engineering of the TSV system it is anticipated that the safety plans from previous years will need revision An updated system design comprising the final detailed and complete hierarchical due Mar 2 subsystem breakdown This breakdown shall be reflected in all other documentation consistently BOMs test plans ICDs schedules etc shall all use the same breakdown Detailed specifications for each subsystem type including interface definition block due Mar 2 diagram state diagram functional requirements and QA test plan An enhanced requirements analysis showing that the detailed design and testing meets all due Mar 2 requirements and constraints Operation of critical circuits or systems shall be simulated and proven against test benches using SPICE Modelsim Simulink or other simulators Simulation results shall be presented at CDR A system state demonstration that includes a detailed software simulation of overall system due Mar 2 states and state transitions User interface demonstrations with live computer interactivity that implements as much as due Mar 2 possible the final look feel and functionality of every user interface It is desirable that the state demonstration be integrated with the Ul demonstration https app asana com 0 search 27543017738645 2754301 7738645 3 5 2 22 2015 Search Asana Communication link demonstration that proves operation of an
8. given in GPROO7 Any team that creates or substantially improves software for the project shall deliver a software specific maintainability plan Others must use the software written for this project over the 5 year life of the system This deliverable documents how software maintainability will be achieved The software maintainability plan must be delivered in written form and accompanied by an oral presentation The plan should answer the following questions What is the design of the system API and how will this design support ongoing reliable operation maintenance and expansion How is system configuration maintained Will the system auto detect hardware configuration changes or will configuration maintenance be required If the latter what is the consequence of misconfiguration What tool chain will be used Is the tool suite up to date and actively supported Is the tool suite mature enough to have stable functionality Evidence must beprovided to support assertions What third party software will be incorporated into the system How will this be maintained upgraded or patched during the life of the system How are requirements in GPROO7 met D004 Acceptance Test Plan due Feb 23 The Acceptance Test Plan ATP is a document that describes how the system as a whole will be tested and demonstrated so as to prove compliance with all requirements and specifications The ATP should include forms that can be filled out by testers duri
9. her evidence gathered in an inspection is included in the ATR The ATP should be arranged to minimize the work involved in testing If possible multiple requirements should be demonstrated by each test The ATP should include a compliance matrix making it obvious that all requirements have been addressed by the plan Numerical specifications shall be considered passed if the measured value is demonstrated by empirical statistical trials to meet the specification at a 90 confidence interval https app asana com 0 search 27543017738627 27282623335957 3 3 2 22 2015 Search Asana Incomplete Tasks due within the next 7 days Adam Cornwell Adam Cornwell PACMAN Communication Library Alex Hytha Alex Hytha Complete and submit ATP Final draft Aloysius Posillico Aloysius Posillico TSAL Circuit Schematic AP Aloysius Posillico TSAL Approval and Submission AP Aloysius Posillico TSAL Component Purchase AP Brendan Malone Brendan Malone Model the motor in software Daniel Zakzewski Daniel Zakzewski Cockpit Panel BOM DZ Daniel Zakzewski Cockpit Panel Panel Sketches DZ Daniel Zakzewski Cockpit Panel Internal Layout sketch DZ Daniel Zakzewski VCI Internal Layout Sketch DZ Daniel Zakzewski VCI Purchase of Components DZ Hansen Liang Hansen Liang User Interface Demonstrations Hansen Liang Maintainability plan Jaejoon Yang Jaejoon Yang Communicate new TSV plan with MechEs Jaejoon Yang Put in order for AMS
10. ng execution These filled out forms will be used to create the ATR Compliance must be conclusively proved in any of the following three ways e Analysis detailed logical analysis can demonstrate compliance by reasoning from known facts a priori or empirically similar to the form of a mathematical proof Analysis can be used cited research results in conjunction with the documented results of subsystem QA testing along with generally accepted technical principles to prove system level requirements are met Analysis memos and relevant data are attached to the ATR e Test an explicit test experiment or demonstration can be used to prove compliance with a certain requirement by acquiring new empirical facts and combining these with analysis as described above The comprehensive results of any measurements conducted as part of an ATP testis included in the ATR along with date and time of the test the pass fail criteria uncertainty statistical confidence pass fail result witness name and witness signature e Inspection compliance is made evident by directly examining the system Photographs with detailed annotations or https app asana com 0 search 2754301 7738645 2754301 7738645 4 5 2 22 2015 Search Asana other evidence gathered in an inspection is included in the ATR The ATP should be arranged to minimize the work involved in testing If possible multiple requirements should be demonstrated by each test The ATP should
11. out Sketch ND Nick DiNino GLV Power Purchase of Components ND Rameel Sethi Rameel Sethi System Logging Daemon Yiming Chen System logging Daemon Sam https app asana com 0 search 27543017738645 2754301 7738645 due Feb 23 due Feb 26 due Mar 1 due Mar 1 due Feb 22 due Mar 1 due Feb 28 due Feb 28 due Feb 28 due Feb 19 due Mar 1 due Mar 1 due Mar 1 due Feb 28 due Feb 21 due Feb 21 due Feb 28 due Feb 28 due Feb 27 due Feb 27 2 5 2 22 2015 Search Asana Sam CAN Communication Library Draft due Feb 27 Stephen Mazich Stephen Mazich Complete and submit Calibration and Error Analysis document due Feb 28 William Stathis William Stathis Enhanced requirements analysis due Mar 1 William Stathis Revised WBS due Mar 1 Yiming Chen Yiming Chen System logging Daemon due Feb 27 Zach Helwig Zach Helwig Side Panel Design Approval and Submission ZH due Feb 28 Zach Helwig GLV Hub BOM ZH due Feb 28 Zach Helwig GLV Hub Internal Layout Sketch ZH due Feb 28 Zach Helwig Side Panel Panel Drawing ZH due Feb 28 Unassigned User Manual Update and Submission 2 due Feb 28 User Manual Update due Feb 21 ATP submission 2 due Feb 21 A summary of the approved system level Acceptance Test Plan due Mar 2 A safety plan per GPRO05 if required for the team s subsystem The plan must be approved due Mar 2 by faculty and read and agreed to by all students in all teams Given the significant addition of a
12. t the Cockpit Panel We also sketched out the internal layout circuit diagram sketch of the VCI TSI and Side Panel These sketches were added to our working User Manual In the upcoming week the GLV team plans on purchasing components for the GLV Power and VCI subsystems as well as the connectors for system integration A new user manual will be submitted Outstanding Action items Website Ken has started the process for getting us hosted long term Steve Morton Papers Budget Item Group SCADA Embedden Computer System Dashboard LCD display and controller Wireless Radio GPS radio DC DC converter Safety Loop Solid State Relay Slave Sensor Micro Controller Hardware GLV 24V battery Smart Charger overvoltage protector LTC4365 PolySwitch LVRO55 Container Board Red LED McMaster Carr 2779K7 Quantity Price 400 100 50 50 35 10 15 total 185 25 150 40 9 62 Total 400 100 50 50 35 20 60 715 185 25 150 40 19 24 Green LED McMaster Carr 2779K2 Wiring and fuses Acrylic Frame Veam Powerlocks Tractive System Active Light Lamp Physical Container Circuit Board Speaker BUZZ PIEZO CIRC 42 85MM PANEL Audio Amplifier Temperature Sensor Current Sensor Voltage Sensor Rate of Discharge Sesnor Rate of Charge Sensor State of Charge Sensor VCI Container DYNO 0 AWG gage wire 50ft Wire connector package Temp sensor LM20CIM7 NOPBCT ND 4 to 8
13. tR bypass vetage eurrentprebing High pewerpligs Aloysius Posillico Aloysius Posillico FS PanetSketehes AR Aloysius Posillico FS Gireuit Sketehes APR Bikram Shrestha Y Bikram Shrestha Design GUHer3 medes Brendan Malone Y Brendan Malone Usermarntat Daniel Zakzewski Y Daniel Zakzewski Side Pane BOM BZ Y Daniel Zakzewski VG Gireuit Sketehes DBZ V Daniel Zakzewski Side PaneHnternat Layout Sketeh BZ Daniel Zakzewski Side Panet Gireuit Sketehes DZ Hansen Liang V Hansen Liang Gheese new LGD display interface https app asana com 0 search 27543017738627 27282623335957 due Feb 18 due Feb 21 due Feb 19 due Feb 21 due Feb 21 due Feb 20 due Feb 19 due Feb 21 due Feb 21 due Feb 21 due Feb 21 due Feb 22 1 3 2 22 2015 Search Completed pack wiring diagram Asana Jaejoon Yang V Jaejoon Yang Prepesatfer20Vindieater design John Bloore V John Bloore Dyne e computeriniegration with sensors John Gehrig John Gehrig Place the purchase for embedded system Y John Gehrig Finatize sehedute with facutties Jordan Blake Jordan Blake Completed pack wiring diagram Jordan Frank Jordan Frank S Safetteep cirerit sketeR JF Kai Ottaway Kai Ottaway Rearrange top of box Katie Nellis V Katie Nellis Prepesatterfuttsystem reset designs Nate Hand Nate Hand Motor Controller Cooling system built Nick DiNino Nick DiNino GLV Battery Circuit Sketches ND Significant redesign
14. y wireless or wired due Mar 2 communication links Hardware interface control specifications captured in an interface control document and due Mar 2 System Drawing that documents the exact way subsystem types are instantiated and interconnected both internally and project wide Pinouts of all connectors conductor assignments in cabling shall be documented in the ICD Detailed software API specifications due Mar 2 A revised cost analysis and detailed program budget that documents costs to date and due Mar 2 demonstrates compliance with financial constraints A revised program schedule that documents progress to date and identifies the tasks due Mar 2 needed to complete the project The schedule should identify system and software critical path drivers to complete the project on time Report due a week before due Mar 2 D011 Calibration and Accuracy due Feb 23 Any data acquisition system design or test plan must be accompanied by a Calibration and Error Analysis document that estimates the uncertainties associated with all system measurands This document must include both analytical estimates of measurement uncertainty as well as a justified design of acceptance tests to determine the uncertainty achieved in practice The testing design from this document shall be incorporated into the system ATP D012 Maintainability Plan due Mar 2 The Maintainability Plan documents how the team plans to address the general maintainability requirements
Download Pdf Manuals
Related Search