Transcript File

CWNC FRC Sessions
Team 5740
10/26/2016
Contact:
David Pacella
[email protected]
D.Pacella
Page 1
Agenda
• Engineering Team Formation and Roles
 Mechanical
 Systems
 Electrical
• Next Meeting
 Logistics
 Marketing
 Documentation
 Communication
• Events
 Pittsburgh and Cleveland
• Misc
 Andy Mark
D.Pacella
Page 2
Team Formation
• Leadership Team
 Matt Esser (Systems Engineering)
 Jake Ball (Software Engineering)
 Colton Eisenreich (Electrical Engineering)
 Zak Diethorn (Mechanical Engineering)
• Team Captain
 Let’s pick a captain!
• Treasurer
 ???
• Team Communications
• Media, Marketing and Events Coordinator
 Danielle Millich + ???
• Student Coordinator
• FIRST Coordinator
• Subteam Coordinator
 This is renamed “Systems Engineer”
D.Pacella
Page 3
Roles: Systems Engineer
• Systems Engineer
 Responsible for making sure the overall design meets the system
requirements.
 What are requirements?
 What are specifications?
• Simply: requirements are what your program should do
• Specifications: how you plan to do it including the finished
good’s “data sheet”
• Requirements represent the application from the perspective
of the user (aka customer) as a whole
• Specification represents the application from the perspective
of the technical team.
• Specifications and requirements roughly communicate the
same information, but to two completely different audiences
D.Pacella
Page 4
Roles: “Sys E”
• Systems Engineer
 Responsible for making sure the overall design meets the system
requirements.
 Responsible for ensuring the size, weight, power, safety and other
critical design features meet the requirements.
 Mechanical: ensuring that the volume space claim of our solution is
within the rules
 Electrical: ensuring that the electronics function safely (fuses, etc)
 Software: coordinating the understanding of the interplay between
software and electrical.
 Overall, ensuring that the mechanical, electrical, software, quality
teams are working to a common design solution
D.Pacella
Page 5
Roles: “Mech E”
• Mechanical Engineering Team
 Responsible for making sure the mechanical engineering achieves the
necessary form, fit, and function to meet the overall system level
requirements
 Will work with a CAD package (Solidworks or Inventor)
 Will work the “Pencil CAD” early and often!
– Sketch, erase, sketch, erase, etc
 Will be responsible for generating usable output files (DXF’s) that can
be used
 Will ensure the design analysis sufficient to meet all the use cases
D.Pacella
Page 6
Roles: “Spark E”
• Electrical Engineering Team
 Responsible for making sure the electrical engineering achieves the
necessary form, fit, and function to meet the overall system level
requirements
 Will work with a CAD package (Altium)
 Will work with a simulation application (LT Spice)
 Will work the “Pencil and Paper” early and often!
– Fresh paper and sharp pencils are often the birth of many a good circuit
topology
 Will ensure the design analysis sufficient to meet all the use cases and
that all electronics are thoroughly tested
 Responsible for designing the functional tests
D.Pacella
Page 7
Roles: “Soft E”
• Software Engineering Team
 Responsible for making sure the software engineering achieves the
necessary functionality to meet the overall system level requirements
 Will work with a software design package (LabView)
 Will work with secondary hardware and development environments,
such as Arduino or Raspberry Pi to develop extensions to the base
RoboRIO (OPTIONAL)
 Will work the “Psuedo Code” early and often!
– You must develop the logical flow of the program from a high level before you
begin coding. The pseudo code is your translator of system requirements to
design, which yields the SPEC.
 Will ensure the software verification and testing sufficient to meet all
the use cases
– Must think about how you can try to BREAK things, and design in limits and
features to safely handle out of bounds conditions
D.Pacella
Page 8
Engineering Training
Mechanical Engineering
Tools
D.Pacella
Page 9
Engineering Training
D.Pacella
Page 10
Engineering Training
D.Pacella
Page 11
Mechanical Engineering Tools
• Solid Works
 Here are steps for downloading our full suite of SOLIDWORKS
software. This software is for the team’s personal computers and not
for school computers.
1. SOLIDWORKS Download :
http://www.solidworks.com/sw/education/SDL_form.html
2. SEK-ID = XSEK12
3. Choose 2016-2017 version
4. CAD/Electrical serial number : 9020005940533938CVWHHPG4
5. Composer serial number
: 9020005240846036PDMWZMD7
6. Here are the number of activations on each serial number:
20
7. If you do not activate the license, you will only receive a 30-day
license. Please give this serial number out to team members
only. This serial number will expire July 31, 2018.
8. If for any reason you have a problem with the software installation,
please send an email with screen shots of the error
to [email protected].
D.Pacella
Page 12
Mechanical Engineering Tools
• Solid Works, continued
1. To learn more about SolidWorks Electrical, go here:
http://www.solidworks.com/sw/products/electrical-design/solidworkselectrical-professional.htm
2. To learn more about SolidWorks Composer, go here:
http://www.solidworks.com/sw/products/technicalcommunication/solidworks-composer.htm
3. Additional Helpful Tutorials: www.solidworks.com/EDU_Robots
D.Pacella
Page 13
Engineering Training
Electrical Engineering
Tools
D.Pacella
Page 14
Training
• Electrical
 Schematic Capture: We will be using Altium
 Schematics can be generated for wiring diagrams
 Schematics can be generated to eventually design custom PCB’s
 There are TONs of YouTube videos on Altium walkthroughs
• Simulation
 Linear Technology’s famous LTSpice
 This is a powerful, FREE electronic simulation tool to model and
understand circuits.
 Simple: resistor and capacitor timing circuits
 Complex: DC-DC converters, audio amplifiers, transistors, op-amps
 Other FREE simulators: Texas Instruments “TINA”
D.Pacella
Page 15
Electrical Engineering Tools
• Altium License Information
• License: SN-07784668
• Activation Code: NXJ7-9VRG
• Customer Number: 1576357
• License: Altium Designer
• Type: Standalone
• Usage: Student
• User Count: 1
• Account: FRC2016 - #5740
• Contact: David Pacella
• Start Date: 9/30/2016
• End Date: 9/30/2017
D.Pacella
Page 16
Electrical Engineering Tools
D.Pacella
Page 17
Engineering Resources Summary
• Mechanical
 CAD Modelling Tools
– Solidworks: We qualify for 20 seats of Solidworks
– Auto Desk Inventor
• Electrical
 Altium will be used for schematic capture, wiring diagrams, and PCB
layout
 LTSpice will be used for circuit simulation
• Software
 Lab View
 Computer with LabView: connect to last years controller for continued
development and practice with PID control using last years motors and
encoders
• Assembly
 Practice crimping with wires, various screw terminals, and crimp tools
 Tools and assembly area: clear labeling and reduced clutter
D.Pacella
Page 18
Events
FRC Events
D.Pacella
Page 19
Regional Event
 Pittsburgh Regional
– Week 3
– Wednesday, March 15, 2017 - 12:00am to Sunday, March 19, 2017 - 11:59pm
 Cincinnati Regional
D.Pacella
Page 20
Misc
Miscellaneous
D.Pacella
Page 21
Tools and Such
• Andy Mark
 Purchased a bunch of things on sale
D.Pacella
Page 22