Past Semester's Competition Posters

Monday, August 29, 2022 11:25 AM

92

UTD-CSECE-Raytheon-UAS-Showcase-Poster-June-2022

Research Documents Page 1

Research Documents Page 2
Spring 23
Monday, January 23, 2023 9:40 AM

Communicating with Raspberry Pi via MAVLink¶

https://ardupilot.org/dev/docs/raspberry-pi-via-mavlink.html

Making a MAVLink WiFi bridge using the Raspberry Pi¶

https://ardupilot.org/dev/docs/making-a-mavlink-wifi-bridge-using-the-raspberry-pi.html

Github link to mavlink setup with Ardupilot

https://github.com/ArduPilot/ardupilot_wiki_copy/blob/master/dev/source/docs/raspberry-pi-via-
mavlink.rst

Setting up Wi-fi for Raspberry Pi

https://www.seeedstudio.com/blog/2021/01/25/three-methods-to-configure-raspberry-pi-wifi/#:
~:text=Using%20the%20arrow%20keys%20on,Network%20Options”%20and%20press%20Enter.
&text=Select%20Wi-fi%2C%20then%20follow,menu%20to%20close%20Raspi-Config.

Research Documents Page 3

UTD Student Blog Detailing Experience in Project
Monday, August 29, 2022 11:43 AM

Link: https://alex.doud.io/raytheon-drone-project-sem-1/

Raytheon Autonomous Drone Project Semester 1

Research Documents Page 4

Research Documents Page 5
Research Documents Page 6
Research Documents Page 7
Research Documents Page 8
Research Documents Page 9
Research Documents Page 10
Research Documents Page 11
Research Documents Page 12
Research Documents Page 13
Research Documents Page 14
Research Documents Page 15
Research Documents Page 16
Research Documents Page 17
Statement of Work (Official Rules)
Friday, September 9, 2022 9:24 AM

RIS_UAS_SOW_2022-2023_v1 (002)

Research Documents Page 18

Research Documents Page 19
Research Documents Page 20
Research Documents Page 21
Research Documents Page 22
Research Documents Page 23
Research Documents Page 24
Research Documents Page 25
Research Documents Page 26
Research Documents Page 27
Research Documents Page 28
Research Documents Page 29
Research Documents Page 30
Research Documents Page 31
Research Documents Page 32
Research Documents Page 33
Research Documents Page 34
Research Documents Page 35
Research Documents Page 36
Fall 21 - Spring 22 Final Report
Monday, September 19, 2022 9:38 AM

drone_58549_20191558_Drone_SP22_4349_Final_Report

Research Documents Page 37

Research Documents Page 38
Research Documents Page 39
Research Documents Page 40
Research Documents Page 41
Research Documents Page 42
Research Documents Page 43
Research Documents Page 44
Research Documents Page 45
Research Documents Page 46
Research Documents Page 47
Research Documents Page 48
Research Documents Page 49
Research Documents Page 50
Research Documents Page 51
Research Documents Page 52
Research Documents Page 53
Research Documents Page 54
Research Documents Page 55
Research Documents Page 56
Research Documents Page 57
Research Documents Page 58
Research Documents Page 59
Research Documents Page 60
Research Documents Page 61
Research Documents Page 62
Research Documents Page 63
Research Documents Page 64
Research Documents Page 65
Research Documents Page 66
Research Documents Page 67
Research Documents Page 68
Research Documents Page 69
Research Documents Page 70
Research Documents Page 71
Research Documents Page 72
Fall 20 - Spring 21 Final Report
Monday, September 19, 2022 9:41 AM

pacehoneycutt_67995_13594999_Spring_EE4349_2021_...

Research Documents Page 73

Research Documents Page 74
Research Documents Page 75
Research Documents Page 76
Research Documents Page 77
Research Documents Page 78
Research Documents Page 79
Research Documents Page 80
Research Documents Page 81
Research Documents Page 82
Research Documents Page 83
Research Documents Page 84
Research Documents Page 85
Research Documents Page 86
Research Documents Page 87
Research Documents Page 88
Research Documents Page 89
Research Documents Page 90
Research Documents Page 91
Research Documents Page 92
Questions
Monday, August 29, 2022 11:47 AM

1. Since we are identifying and tagging drones:

a. Will we have a standardized method for tagging? Ex. Infrared
b. Will the ground drones be identifiable w/ a logo? What will our drones seek for?
c. Is there a set path the ground drones will use? Or do they need to be fully autonomous with
obstacle avoidance?
d. Possibly using real time video processing to identify other UVSs?

2. Concrete Task List (Requirements) - what does it need to do?

1. Specifications:
a. Are their weight limits? We want to optimize weight anyway but it might be necessary.
b. Price Range? Might be answered in Talk with Raytheon.
c. Operational time: How long will the competition be?
d. Battery chemistry constraints? LiPo, NiMH, Alkaline, etc.
e. Temperature constraints for components?
f. Power consumption of specific components – FC, ESC...

2. Necessary Parts: Don't have specs yet so not sure what we can do here, but we can have a
possible model so we can have a price point to haggle with Raytheon.

a. For UAV & UGV they'll have mostly the same parts, but one will have props the other will
have wheels, etc.
i. Motors: x4 (maybe)
ii. ESC: x4 (maybe)
iii. IC - flight controller or custom IC?
1) If custom - power distribution circuit
iv. Computer - since it will be autonomous (1st place had companion computer)
v. Battery - specs depend.
vi. Camera
vii. GPS
viii. LIDAR - Obstacle Avoidance.
ix. 6 axis gyro
1) Alternatively gyroscope and accelerometer separately
x. Receiver/Transmitter - need manual override , Telemetry, interface with team
xi. Software, idk too much abt it yet.

Questions and Problems Page 93

Block Diagram
Wednesday, August 31, 2022 2:23 PM

UAV Parts Page 94

Radiolink TS100

Wednesday, September 7, 2022 2:59 PM

UAV Parts Page 95

UAV Parts Page 96
UAV Parts Page 97
UAV Parts Page 98
UAV Parts Page 99
UAV Parts Page 100
UAV Parts Page 101
FC
Wednesday, September 7, 2022 3:02 PM

UAV Parts Page 102

Raspberry Pi 4 vs Nvidia Jetson Nano
Friday, September 9, 2022 11:37 AM

Jetson Nano vs Raspberry Pi 4_ The Differences _ All3DP

UAV Parts Page 103

UAV Parts Page 104
UAV Parts Page 105
UAV Parts Page 106
UAV Parts Page 107
UAV Parts Page 108
UAV Parts Page 109
UAV Parts Page 110
UAV Parts Page 111
UAV Parts Page 112
UAV Parts Page 113
UAV Parts Page 114
UAV Parts Page 115
Monday, August 29, 2022 11:51 AM

UGV Parts Page 116

Motor Testing
Monday, October 17, 2022 1:40 PM

Parts Testing Page 117

Parts Testing Page 118
 Presentation Requirements
Monday, August 29, 2022 2:34 PM

I. Presentations have changed.

a. Used to be brief since we had reports. But now people prefer presentations. Rough Format for Slides
b. Now you gotta put all your important info there without going too far. 1: Title
i. Be concise but you need to put relevant info here. 2: Intro
II. Should follow same format as report. 3 (2-5 slides): Background
a. Format: What it is
i. ABSTRACT What the problem is
1) General summary: what, why, approach, intro to project. What is required specifications
2) Lay foundations, set up background of issue/concept your project focuses on. What are the constraints
ii. BACKGROUND 4: Block Diagram (2-5 slides)
1) What's been done before in concept? 5: Conclusion?
2) What is the general specs etc.?
3) Cite sources
4) Problems vs benefits of prior designs. WHAT NOT TO DO
5) What are we taking/rejecting from prior designs? 1. Show pics with little to no text.
iii. BLOCK DIAGRAM 2. Show too little information.
1) Requirements 3. Show too much information.
2) Constraints 4. Have only 1 draft of slides.
3) Benefits of previous designs 5. Have periods.
4) Make sure you have an optimal design 6. Capitalize wrong.
a) Nothing should be extraneous everything should be connected to the 7. Pick ugly colors. WHITE/Light colors are better.
constraints and requirements 8. Add animations.
5) After BD is made, break down each individual block, its own constraints and 9. Subjective constraints. BE specific w/ numbers with that your constraints are.
requirements. 10. Make stupid mistakes that are easy to clown you for.
6) Doesn’t have to be perfect 1st time around. Just a general understanding of 11. Can have a role slide.
what device will be.
a) Will be edited from class to class
7) Test each individual block individually BEFORE putting it together. WHAT TO DO
a) READ THE DATASHEETS 1. Show abstract/intro/background BEFORE describing the project.
i) May contain test circuits to test if it works. 2. Show block/circuit diagram
ii) Keep that data. Explain experiment to verify it will work for design. 3. TEXT on LEFT, IMAGES on RIGHT
iv. CONCLUSION 4. Use white space.
5. Justify text.
6. Go back and edit text multiple times.
7. Be consistent with format, grammar, and mechanics
8. Optimize spacing by playing with bullet point spacing, omitting definite/indefinite articles.
9. Caption images.
10. Cite Links to images as credit. Or have references slide.
DRAW.IO 11. Don’t use animations.
12. Use pictures often to keep audience engaged.
13. For components:
a. Use diagram instead of just a component's picture. Diagram will tell you more, but not
necessary either. Graphs will be more useful because it shows why the component is useful
if you have clearly defined constraints.
14. Homogenize format across all slides. Is more professional.
15. Can have Gantt Chart and budget, but people don't really care about them. Put it in extra material
section.
16. MAKE SURE BLOCK DIAGRAM HAS Voltages, Currents, Power etc. Pulse, type of signal (PWM,
PPM)

NOTES FROM DR WETZ LEC Page 119

More on Presentations
Wednesday, August 31, 2022 2:31 PM

If the sponsor doesn't talk back in time: REQUIREMENT - Lower Bound for specs DRONE PROJECT EXAMPLE - Raytheon Last Year
CONSTRAINT - Upper Bound for specs
Just do research on your own. I. Objective
a. State purpose and who your working with
II. INTRO to drones. Add more pictures. What does autonomous mean? Who uses them?
I. EXAMPLE FROM LOCKHEED EMPLOYEE Applications? Past? Future? Tagging?
a. MOTIVATION - problem III. Project Requirements
b. PREVIOUS WORK- what's been done before a. Make it as big as possible for max visibility
i. Sentences are longer in the slide, but what you will be saying will be IV. Constraints
different. a. DON’T MISSPELL STUFF
1) Since ppt gives a double function as a report, more robust V. Background
explanation is on slide while quick summary is what you say. Use a. What they did last year. Performance, components, speed.
pictures to help illustrate points. VI. Block Diagram
c. RESEARCH OVERVIEW a. Current Voltage Power Labelled. Signal, Power, Current, Voltage, PWM, PCM, etc.
i. What you will do for your project. VII. Flight controller choices.
ii. MAJOR FOCUS POINTS a. Re-establish requirements.
1) Enumerate requirements & constraints b. Denote how you are weighing your choices between each component.
iii. Can use arrows to point to specific things. Don't go overboard tho
d. Couple of slides showing setup. (YOUR BD can go there) DRONE PROJECT FINAL 1st Semester
e. BLOCK TESTING
i. Showing how each result will go. I. Block Diagram is a lot more robust and complex.
f. KNOW YOUR AUDIENCE - explain things that your audience should know that
are essential to presentation
g. CONCLUSION

NOTES FROM DR WETZ LEC Page 120

How to Manufacture Designs ?
Monday, September 19, 2022 2:36 PM

SAMPLE: PCB - Connectors are really important in design.

• Once you design a circuit - • Types of Connectors

○ Lay out the schematic in the program - EAGLE, BANTAM I think ○ DB Cable - multiple pins for a lot of data flow, but low current low
▪ Every component has a symbol and footprint. Footprint comes with through voltage.
holes, connections, etc. ○ Jumper Cables - good for dev kits with pinouts like MSP etc.
▪ Make sure they are CORRECT so that your component fits correctly. ▪ Not recommended to turn it in with that. You want connections
○ Eagle will help you visualize how it will be laid out and connected. to lock onto pins. Find locking connectors.
○ Disorganized wires may be bad. ○ JST connectors - low voltage low current - digital signals, not for
• Bad design: current or voltage carrying stuff.
○ For high continuous current - higher gage wire.
• Good design: ▪ You don't necessarily need higher gage for max current if it is
○ part fits snugly, no wasted space. just a temporary spike, as long as it can handle the heat.
• Don't have to use the Dev kit, can make your own circuit. Easier than it looks since pinouts are ○ Screw Terminals also exist. Not reliable/robust can get loose and
just made accessible on a dev board. short.
• Dev boards come with other buttons and a programmer as well. Not necessary once • You can buy premade cable assembly depending on your needs.
flashed. Can remove that as well. • Locking able connector arrays can be very useful in saving space.
• Cable sheathing can help with organization as well.
• JTAG can help you flash firmware onto a circuit.
Surface Mount Parts
• Case code - standard sizes for surface mount components. Software that can help with design:
• BGA package - Ball grid array. Each ball connector is a pinout. Really hard to • Solidworks - CAD Modeling
even use them. • Autodesk Eagle
• Before you even order a circuit, have design layed out so you know how to
connect to it.
• IC pinouts - 100x usually - they'll be microcontrollers and stuff.
• https://en.wikipedia.org/wiki/Surface-mount_technology Searching on Mouser.com
○ Good resource for surface mount tech • Don't bother using search function.
○ Use search menu on left under Products menu.
• EX: Say you want a resistor
○ Use parametric search
▪ Edit all filters at once.

NOTES FROM DR WETZ LEC Page 121

Sponsor Meeting 1
Wednesday, September 7, 2022 11:43 AM

1. Since we are identifying and tagging drones:

a. Will we have a standardized method for tagging? Ex. Infrared
b. Will the ground drones be identifiable w/ a logo? What will our 1. Dr. Wetz -
drones seek for? 2. Gretchen:
c. Is there a set path the ground drones will use? Or do they need to
be fully autonomous with obstacle avoidance? EVADERS - Will be following a set path - set on a specific place on a field static.
d. Possibly using real time video processing to identify other UVSs? 2 and 3 - Starting point. 50 yards Move 90 degrees twice in a certain amount of time.
Evaders need to switch lanes. Need to detect what lanes they are in, switch to a specific
2. Concrete Task List (Requirements) - what does it need to do? lane.

3. Specifications: THE UAV doesn't need to have a pattern. They can seek however they want.
a. Are their weight limits? We want to optimize weight anyway but it
might be necessary. IR laser to disable it. You'll have the component. You will find the evader with a QR code.
b. Price Range? Might be answered in Talk with Raytheon. Will need camera. - are we getting the technology?
c. Operational time: How long will competition be?
d. Battery chemistry constraints? LiPo, NiMH, Alkaline, etc. Operating Time - Can move as fast or slow as you want, but need to make time limit.
e. Temperature constraints for components? Necessary for battery.
f. Power consumption of specific components – FC, ESC...

4. Necessary Parts: Don't have specs yet so not sure what we can do here, Ground Drones- do they need obstacle avoidance? No obstacle avoidance for them
but we can have a possible model so we can have a price point to haggle needed. Still wanna be within bounds. So its still a good idea to use it.
with Raytheon.

a. For UAV & UGV they'll have mostly the same parts, but one will How will scoring be done? Not known yet.
have props the other will have wheels, etc.
i. Motors: x4 (maybe)
ii. ESC: x4 (maybe)
iii. IC - flight controller or custom IC?
1) If custom - power distribution circuit
iv. Computer - since it will be autonomous (1st place had
companion computer)
v. Battery - specs depend. It is on a field
vi. Camera
vii. GPS
viii. LIDAR - Obstacle Avoidance.
ix. 6 Axis Gyro
1) Alternatively gyroscope and accelerometer separately
x. Receiver/Transmitter - need manual override , Telemetry,
interface with team
xi. Software, idk too much abt it yet.

Dr. Wetz - Invited MAE and CSE Teams

Ethan Quarles -

Don't share with US citizens -

Statement of Work - Requirements for Project - Not comfortable sending it out until we're ready.

What this competition entails -

Competitively - UTD, SMU, UTA, UT Austin, A&M

April-May is competition date - at UTA.

You will need to develop an autonomous vehicle - Seeker and Evader

Meetings Page 122

SEEKER UAV - detect friend or foe USING IR - Technologies to choose from will be in SOW

This competition is fun but you will have engineering phases.

Requirements
Moving Fast
Have a demo by the end of September. Proposed solution
Prototype by the end of the summer.
Class requirements will be fit in.
Work has separate requirements. Really need to implement solutions EARLY. Implement and test EARLY.
Get ahead of issues early.

FOR Carlos - Blocked off times Fridays 12-1.

Logistics - Media Release Forms - List of People on Teams (ME EE CS) - Home Addresses

How planning will be done.

Gretchen -

Worked for Raytheon for 22 years

Defense Work - for DOD military
Directed energy
Sensors
Radars
Image sensors
Detection - for intelligence for DOD, intelligence

Started up in SW - worked up in infrastructure - was chief engineer for top pursuits

Systems engineer - Management now. Helps run business and develop people.
Loves working with Senior Project.

From Upstate NY, but lived in TX for as long as she worked at Raytheon.

Meetings Page 123

Sponsor Meeting 2
Friday, September 9, 2022 11:55 AM

Participants: EE Team, CSE Team, MAE Team, Dr. Wetz, Gretchen Mock

Still using zoom so time-limit might give us trouble again, but we can all just rejoin it seems like.

For next time - look at the plan in SOW, work with team, look at deadline dates. Look at plan for how we
will do for April Week 3

How are we storing and compiling code? Are we using github? Github will be a good idea. Can be used.

Meetings Page 124

Introductory Team Meeting
Sunday, September 11, 2022 10:37 AM

Meeting Details
▪ Date and Time: 9/11 at 12 pm
▪ Location: Teams
▪ Agenda:
• Introduction
▪ Talk to each other, introduce each other.
▪ Delineate roles within the team.
▪ Paperwork - Export Control, NDA, Media Release, IP agreement, Background
Check.
• Main Topic: Logistics and Planning
▪ Responsibilities to Instructors vs Responsibilities to Raytheon
□ Talk about what Dr. Wetz expects of EEs and what other professors
expect of CSEs and MEs.
 We need to select and analyze components for our
presentation.
◊ SBCs - Many different Choices - Would like CSE team's
input. I believe they can all run on linux builds provided by
the manufacturer (or can be flashed). Want to focus on
Max TOPS(tera-operations per second) vs wattage, current
draw, voltage operating point
 NVIDIA Jetson Family - Nano maybe? More than 1
type
 ROCKPi - seems to be an Rpi w/ dedicated ML and AI
 Beagleboard - Beaglebone AI
 Coral Dev Board
 RBP4 - cheapest most accessible but may or may not
be best TOPS/W ratio
◊ Everything else I believe will fall into place depending on
what type of SBC we get. That is going to be the most
important part
◊ Motors - what rating do we want.
 KV rating - ratio of unloaded rpm to peak voltage
 Type of motor depends on weight.
 Aiming for a 1.5-2 kg drone
 2:1 thrust to weight ratio
 Need formulas.
 Top Speed

□ Talk about how Gretchen has a timeline and deadlines for us to hit.
(Show SOW)
□ We need FAA Cert UAV Pilot
□ Obtain training for
 Project management
 Agile
 SRR SDR CDR TRR

Meetings Page 125

 □ Obtain training for
 Project management
 Agile
 SRR SDR CDR TRR
 Machine Learning
 Image Recognition
 FAA UAV PILOT CERT
 She made it clear she is not managing for us, she is just a
mentor. We have to handle all decisions ourselves. She is there
for advice
▪ Show DRAFT Timeline, Jira, Teams
□ Can everyone see SOW?
□ Have been trying my best to keep things organized, trying to give
backbone to the project - Teams, GroupMe, Jira
 Why Teams? Zoom?
 Why GroupMe?
 Why Jira?
 Any suggestions?
▪ Doodle Poll for Future Meetings
□ Only 10/16 filled it out, I need that filled out as soon as possible
because I need to speak to Gretchen about scheduling.
□ Individual discipline teams can meet on their own time/during class as
well.
□ May use the doodle poll for later.

Attendees
▪ Present
• Robert
• Javier
• Nick
• Jaelyn
• Andrew
• Stefan
• James
• Bhawika
• Pearl
• Jaedyn
• Vishnu
• Ethan
• Madelyn

▪ Not Present
•

Announcements


Status of Old Action Items

 (Paste the list of old action items from the last meeting here)

Meetings Page 126

  (Paste the list of old action items from the last meeting here)

Summary


Next Meeting
▪ Date and Time:
▪ Location:
▪ Agenda:
▪ Notes:

Meetings Page 127

Sponsor Meeting 3
Friday, September 16, 2022 11:15 AM

Meeting Details
▪ Date and Time: 9/16/2022 at 12:00 PM
▪ Location: Microsoft Teams
▪ Agenda:
• Intro/ How's everyone doing
• Confirm documents are all handed in
• Ensure documentation is being done
• Define Team Roles
• Parts selection WIP - Brainstorming
• FAA Certification

Attendees
EE TEAM
Carlos Mella-Rijo
Nicholas Partlow
Stefan Fahlsing
Andrew Riel
James Wallace
MAE TEAM
Madelynn Wimmer
Ethan Quarles
Jaelyn Ort
Vishnu Perincheery
Bhawika Kandel
Juan Buritica Yate
CSE TEAM
Robert Carr
Jaedyn Brown
Pearl Iyayi
Ja'lun Jerome Morris
Javier Lopez
ADMINISTRATORS
Dr. David Wetz
Director Gretchen Mock
Announcements
 1st EE presentation done - flawed but a good baseline of what we'll need to do
 Any presentations you all had to do?
 TENTATIVE DATE : April 13th - 15th

Status of Old Action Items

 n/a

Summary
 Paperwork
• Roster
• NDA
• IP Agreement
• That UTA one I forget the name of
• Media Release
• Background Check
 Documentation of Info
• How are we all keeping track of everything?
 Define Team Roles
 Perspective-

Meetings Page 128

  Perspective-
• Body Plan - Takes time, break it up into chunks
• Software - will take a long time - needs to get done ASAP
▪ System under test - Will need to be modded if physical is different
▪ Simulation software- don’t need a physical body.
▪ Debug tools are now available commercially to debug software.
□ Provides good insight into how that can work.
▪ Prototype by December
▪ FOR NEXT TIME - prototype proposal. What the prototype would look like
□ UAV
□ UGV
□ Demonstrate that they can move autonomously. At the very least they should be able to move.
▪ Leveraging what we already have to get parts selection quickly.
□ Programming ASAP
□ EE with MAE Team for ground drone. Figure out hardware and start programming. Obstacle avoidance, AI, GPS? How to keep it in
bounds.
□ Get Final report from last semester.
□ System requirements review - Understand the requirements
□ Preliminary design - trade studies, how you will build it, how it will meet requirements
□ Critical design review - detailed design - how it will all tied together
▪ Integration & Testing
□ SUPER IMPORTANT
 Integration - Making sure parts work together
◊ Incrementally testing. Add more and more things to it.
◊

OCTOBER Proposal and presentation

NOVEMBER Prototype

EE TEAM - Ground Drone and Air Drone Microcontroller, circuit design, circuit assembly.
Carlos Mella-Rijo - Lead, Project Manager, Microcontrollers
Nicholas Partlow
Stefan Fahlsing
Andrew Riel
James Wallace
MAE TEAM - Air and Ground Drone Body, Housing, etc.
Madelynn Wimmer
Ethan Quarles
Jaelyn Ort
Vishnu Perincheery
Bhawika Kandel
Juan Buritica Yate
CSE TEAM - Air Drone Ai, Image Processinf
Robert Carr
Jaedyn Brown
Pearl Iyayi
Ja'lun Jerome Morris
Javier Lopez
ADMINISTRATORS
Dr. David Wetz
Director Gretchen Mock
 Parts Selection
• Buying a dummy drone to test software
• Building out own drone.
• Computers
• Microcontrollers

 FAA Certification
 Questions/Comments?
 Planning phase should be done by the end of September - by next meeting I can order parts if we decide so that they can all get here by October so we
can begin testing.

Next Meeting
▪ Date and Time: 9/23/2022 12:00 PM
▪ Location: Microsoft Teams

Meetings Page 129

▪ Location: Microsoft Teams
▪ Agenda:
• Have a presentation for next week just where the process is.
• Long-term solution for each of your teams.
• Roles
• Parts selection
• IDENTIFY FAA CERT people

▪ Notes:

Meetings Page 130

Sponsor Meeting 4
Friday, September 23, 2022 11:15 AM

Meeting Details
▪ Date and Time: 9/23/2022 at 12:00 PM
▪ Location: Microsoft Teams
▪ Agenda:
Presentation of our overall plan and duties, etc.

Attendees
EE TEAM
Carlos Mella-Rijo
Nicholas Partlow
Stefan Fahlsing
Andrew Riel
James Wallace
MAE TEAM
Madelynn Wimmer
Ethan Quarles
Jaelyn Ort
Vishnu Perincheery
Bhawika Kandel
Juan Buritica Yate
CSE TEAM
Robert Carr
Jaedyn Brown
Pearl Iyayi
Ja'lun Jerome Morris
Javier Lopez
ADMINISTRATORS
Dr. David Wetz
Dr. Christopher McMurrough
Dr. Robert Woods
Gretchen Mock, Raytheon Sponsor
Jesse Lee, Raytheon Sponsor
Announcements
Status of Old Action Items
 n/a

Summary

Meetings Page 131

 

Next Meeting
▪ Date and Time: 9/23/2022 12:00 PM
▪ Location: Microsoft Teams
▪ Agenda:
• Have a presentation for next week just where the process is.
• Long-term solution for each of your teams.
• Roles
• Parts selection
• IDENTIFY FAA CERT people

▪ Notes:

Meetings Page 132

01 – Record Foe Hits
Wednesday, September 21, 2022 3:21 PM

ID: 1

Component: IR Receiver

Test: Record Foe Hits

Description:
For each foe configuration shoot 3 times from the IR gun at the UGV receiver from perpendicular
position at distance of 10ft. Validate the UGV screen increases hit count, lights and buzzer go off, log it,
and sends IRC message.

Points: 9

Verification:

Qual Test UGV Page 133

02– Record Friendly Hits
Wednesday, September 21, 2022 3:21 PM

ID: 1

Component: IR Receiver

Test: Record Foe Hits

Description:
For each foe configuration shoot 3 times from the IR gun at the UGV
receiver from perpendicular position at distance of 10ft. Validate the
UGV screen increases hit count, lights and buzzer go off, log it, and
sends IRC message.

Points: 3

Qual Test UGV Page 134

03 – ArUco Marker Dimensions
Saturday, March 18, 2023 2:54 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 135

04 – Aruco Marker Grid
Saturday, March 18, 2023 2:54 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 136

05 – Controlled 50 Yard Dash
Saturday, March 18, 2023 2:54 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 137

06 – 0.17 MPH Speed Control
Saturday, March 18, 2023 2:54 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 138

07 – 0.26 MPH Speed Control
Saturday, March 18, 2023 2:55 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 139

08 – 0.49 MPH Speed Control
Saturday, March 18, 2023 2:55 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 140

09 - Controlled 0.26 MPH Speed and Turn 30 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 141

10 - Controlled 0.26 MPH Speed and Turn 100 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 142

11 - Controlled 0.26 MPH Speed and Turn 170 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 143

12 - Controlled 0.26 MPH Speed and Turn 240 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 144

13 - Controlled 0.26 MPH Speed and Turn 310 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 145

14- Controlled 0.26 MPH Speed and Turn 380 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 146

15 - Controlled 0.49 MPH Speed and Turn 30 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 147

16 - Controlled 0.49 MPH Speed and Turn 60 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 148

17 - Controlled 0.49 MPH Speed and Turn 90 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 149

18 - Controlled 0.49 MPH Speed and Turn 120 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 150

19 - Controlled 0.49 MPH Speed and Turn 150 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 151

20 - Controlled 0.49 MPH Speed and Turn 180 Seconds Mark
Saturday, March 18, 2023 3:03 PM

ID:

Component:

Test:

Description:

Points:

Qual Test UGV Page 152