P20151: Satellite Localization

Planning & Execution

Table of Contents

1 Intellectual Property Considerations
2 Team Setup
3 Team Values and Norms
- 3.1 Purpose
- 3.2 Rubric
4 Project Plans & Schedules
- 4.1 Purpose
5 Risk Assessment
6 Other Team Resources
7 Meeting Minutes, Notes, & Actions
8 Peer Reviews
9 Communication
10 Project Reviews

Intellectual Property Considerations

Our team is committed to sharing what we accomplish for use by others. There are no intentions of enabling a future commercial use for this project. Our team and stakeholders agree that this project is for the entire RIT community to benefit from in whatever way we deem best at the end of the project. We will be pursuing an Attribution-Noncommerical-ShareAlike 4.0 International Creative Commons license.

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

https://creativecommons.org/licenses/by-nc-sa/4.0/

Team Setup

Team Roles

Project Manager - Leads the team. Oversees project plan, deliverables, and communications. Makes sure EDGE pages are updated.
Lead Engineer - Makes sure all systems interface properly.
Communicator - Handles most emails outside the MSD team.
Scheduling - Helps write the project plan. Keeps track of MSD deliverables.
Editor - Reviews EDGE pages and is the point of contact for EDGE help.
Purchasing - Oversees funds acquisition and BOM. Purchases required items.
Facilitator - Ensures all members are engaged and not dominating during team meetings.

Relevant Fields

Astrodynamics - Orbit Determination and uncertainty analysis.
RF & TDOA - Antenna theory/modeling and math for Time Difference of Arrival.
Systems Modeling - Orbit models, higher level system function, physical models in CAD.
Test - software tests, hardware tests, verification and validation.
Fabrication - Creation of needed hardware and wiring.
Data Collection and Processing - Processing signal and sensor data. Transporting the data.
UI - User interface and software architecture.

Skillsets

Anthony: Proficient programmer for modeling/simulation in Java and Matlab. Strong background in dynamics, orbital mechanics, and numerical Analysis. Some work in localization. Self-starter and good organizer.

Luca: Proficient with CAD software such as PTC Creo. Experience with programming in Arduino and Java. Intermediate background with orbital mechanics. Have created a project similar to this in the past that can be used to influence future decision making.

Zach: Proficient in PTC Creo and OnShape, Strong background in Linear Algebra and Differential Equations, Experience with physical assembly, and strong verbal and presentation skills

Andrew: Proficient problem solver using computer applications including Matlab, VBA, Java, C, Assembly and HDLs. Experience using engineering software including AutoCad, ANSYS HFSS, GENESYS, Sonnet, Altera and TI CCS (for MSP430). Developing a strong background in RF engineering.

Matthew: Proficient with LabVIEW for data acquisition and Matlab for modeling/data processing. Familiarity with ANSYS Workbench for structural, modal, and harmonic response analysis. Proficient with Solidworks/SolidEdge for 3D modeling. Developing system modeling and vibration analysis techniques.

Connor: Proficient in electrical hardware such a op-amps, various signal filters and transistors. Ample experience in circuit wiring and physical assembly including soldering. Familiar with manufacturing and custom parts with large amount of machine shop experience.

Zoe: Skilled in C, C++, and Assembly. Experienced in programming numerical approximations in C (should be useful for orbital determination). Created a GUI’s in C# and Qt/Qwt. Familiar with Matlab. Comfortable with UDP and TCP protocols.

Failure Modes

These potential gaps in these skills may slow team progress.

Inadequate experience with Orbit Determination algorithms.
Inadequate experience with Time Difference of Arrival algorithms.
Limited experience with fabrication.
Limited experience with getting sponsors.
Limited experience setting up the environment for a microcontoller.

Team Setup. All members contribute to the listed items, but the associated role is in charge of it.

Team Values and Norms

Purpose

The LASSO team is committed to fostering a healthy team dynamic. In order to establish this environment and provide a reference point, values, norms, an escalation process, and a feedback system were defined.

Rubric

The team's values include communication, reliability, thoroughness, professional courtesy, accurateness, and commitment.

Values and Expectations

To measure how well the values were upheld, a rubric will serve as a guideline to evaluate each team member using a Peer Evaluation Form. The rubric can be found in the Values and Norms page.

If an issue with a team member arises, it will be addressed using the following escalation process.

Escalation Process

Project Plans & Schedules

Purpose

Ensure timely delivery of all required work products, identify prerequisite tasks with owners, ensure special resource needs are met.

Project Plan Part 1

Project Plan Part 2

Live Project Plan

Risk Assessment

Risk Management Part 1

Risk Management Part 2

Link to Risk Assessment Working Document (Excel Sheet)

Our three highest risks are the error of TDoA, interfering signals at the 437 MHz range, and the budget. The uncertainty in our TDoA calculations needs to be estimated as soon as possible, because this uncertainty will affect the accuracy of the orbit determination. If the TDoA uncertainty is too high, then the OD accuracy may fall out of our engineering requirements. In the next phase, we will have to figure out the uncertainties of TDoA and OD because it will decide the required distances between ground station and SDR sampling resolution required.

Next, we need to make a proof of concept antenna at 437 MHz to see if we can actually receive a satellite signal with an omnidirectional antenna. It is possible that other signals could drown out satellite signals and make them unrecognizable.

Lastly, our budget will affect the quality the SDRs and other related equipment that we can buy. This will affect how accurate of an OD calculation we can get. Our most common risks are technical and resource related. Although technical risks have a low likelihood the severity of the risk is very high. The most concerning resource related risks are in reference to our current budget, this will require thorough planning to avoid unnecessary spending.

Other Team Resources

Planned Meeting Space: We will meet in the MSD Design Center and the Alumni Conference Room on the 2nd floor of Gleason Hall.

Build & Test Space: We will use Bench #10 in the EE Senior Design Lab. As the project progresses, we may need rooftop access to different buildings on campus.

Program Repository: We will use GitHub for version control.

Required Training: We will need lab/studio safety training to use the EE Senior Design Lab. If we use the ME Machine Shop, we will need general shop safety training.

Meeting Minutes, Notes, & Actions

First Customer Interview Notes

Meeting Summaries

Peer Reviews

MSD1

Peer Review for Phase I: Problem Definition

Zach Grguras's Peer Evaluation

Peer Review for Phase II: System Level Design

Zach Grguras's Peer Evaluation

Peer Review for Phase III: Preliminary Detailed Design

Zach Grguras's Peer Evaluation

Peer Review for Phase IV: Detailed Design

Zach Grguras's Peer Evaluation

MSD2

Peer Review for Phase 0: Critical Design Update

Zach Grguras's Peer Evaluation

Peer Review for Phase I: Build & Test Prep

Zach Grguras's Peer Evaluation

Communication

Customer point of contact is Russell Jost
- Preferred method of contact is in person meetings and emails
- Meetings will take place weekly, with email exchanges occuring whenever necessary
- Customer is available during MSD time blocks
Zachary Grguras is in charge of all customer communication
- It is expected that all team members be CC'ed on all customer correspondance.
- Pre-read documentation shall be hand delivered to the customer no later than the afternoon before the review
It is expected that all in-team communication should be adressed in a timely manner
- Preferred method of communication between team is GroupMe
- It is expected that the guide will be included in communication with the customer