CubeSat (ENG491CU1)Informational Meeting

Get Interdisciplinary Design Experience Working on One of the Worlds Smallest Satellites

Fall 2005

Presentation Overview

People Involved Introduction to CubeSats Introduction to ION

Semester Priorities and Teams Class Information Calendar Next Steps

People

Purvesh Thakker (ECE PhD Student)

Prof. Gary Swenson (ECE Remote Sensing)

Prof. Victoria Coverstone (AE Orbital Mechanics)

Prof. Matt Frank (ECE Software)

Systems TeamProgram Manager(s) (1-2 Graduate Student TAs)

Faculty Advisors (Remote Sensing, Orbital Mechanics, and Software)

Systems TeamProgram Manager(s) (1-2 Graduate Student TAs)

Faculty Advisors (Remote Sensing, Orbital Mechanics, and Software)

Electrical TeamElectrical Team

Software TeamSoftware Team

Attitude Determination and Control (ADCS)

Team

Attitude Determination and Control (ADCS)

Team

Ground Station TeamGround Station Team

Mechanical TeamMechanical Team

Corporate Partners, Electronic Services Shop, External Faculty Advisors, Machine Shop

Corporate Partners, Electronic Services Shop, External Faculty Advisors, Machine Shop

Cubesat Satellites

PPOD 3 CubeSats

Cubesat Satellites

Cubesat Project History.– Started as collaboration between California Polytechnic State

University (Cal Poly) and Stanford University.– Provides a standard for design of picosatellites.

Provides for common deployer. Allows for reduced cost and development time. Lets any individual or organization develop their own satellite.

Standard cubesat satellite is:– 10 cm cube with mass of 1kg.

Approximately 60 registered Cubesat Teams. Typically launches provided by Russian company.

– Multiple cubesat’s piggy-back along commercial launch.– 6 cubesats were launched Summer 2003.

University of Illinois CubeSat

Illinois Tiny Satellite Initiative started in ~August 2001

Various majors (AE, CE, EE, ME, TAM, CS, GE)

Typically 15 students involved

Over 100 students involved to date

Completed ION shown with DNEPR launch vehicle from Russia’s Kosmotras

University of Illinois Cubesat - ION

Costs– Parts/Labor: $30,000 USD.– Launch: $85,000 USD.

Delivered to Cal Poly: April 2005 Launch date: Tentatively November, 2005

– DNEPR launch provided by Kosmotras.– 14 cubesat satellites expected launched.

UIUC, Cornell, Norway, Cal Poly, South Korea, Taiwan, Arizona…

Launch Parameters– Low Earth Orbit at 650-700 km.– Orbit lifetime 14+ years.

ION Missions

Mission 1: ION’s photometer studies dynamic drivers of the upper mesosphere

Thunderstormconvection

Mountains

Waves of oxygen airglow perturbations carried by

wind (760nm)

ION

Misssion 2: ION tests VAT thrusters from Alameda

Mission 3: ION tests SID processor board from Tether Applications

Mission 4: ION tests B/W CMOS camera

Mission 5: ION demonstrates ground based attitude control on a CubeSat

Sensor telemetry

Actuator commands

ION Hardware

ION Photos

ION’s Earth ground track

Photometer with lens and filter housing

Thruster (above) and thruster firing (below)

Photograph from CMOS camera

Torque coil on a PC board

0 2 4 6 8 10 12-5

-4

-3

-2

-1

0

1

2

3

4

5Angular Body Rates

(

deg/

sec)

Time(hr)

roll

pitchyaw

-70

-65

-60

-55

-50

-45

-40

-180-170 -160

-150-140

-130

-120

-110

-100

-90

-80

-70

-60

-50

-40-30

-20-100

102030

40

50

60

70

80

90

100

110

120

130

140150

160 170

Antenna strength along outside of bagel-shaped pattern

ION Internal Wiring

More ION Photos

ION Software

Environmental Testing

ION vibration test in test PPOD

Thermal-vacuum chamber

U IU C C u b e S a t V ib ra tio n R e sp o n se Da ta

E T S 2 005 -2 7 , DNE P R H ig h L e v e l In p u t, L o n g A xis

0

0.01

0.1

1

10 100 1000 10000

F re q u e n c y, Hz

Satellite Response Control Response Required Grms

DNPER High level Vibration Test Response Data, Long Axis

Fall 2005 Priorities

ION 1– Prepare Ground Station– Practice, practice, practice communication– Battery charger– Launch and operations?– Publications, tutorials

ION 2– Prototype power, C&DH internal software– Order and test communication system– Design structure, attitude control system– Define payloads

Fall 2005 Teams

ION 1 Ground Team: Improve ground communications system, practice communication

ION 2 Power Team: Build prototype of design from Summer ION 2 Command & Data Handling Team: Develop prototype internal

communication software ION 2 Communications Team: Implement and test communications

hardware including ground station ION 2 Structures Team: Design the structure of the satellite ION 2 Attitude Control Team: Design hardware and software for

controlling satellite orientation

ION 2 Sensors Teams: Develop payloads to support various satellite missions

Teams – ION 1 Ground Team

Fix Antenna Practice communications with satellites Misc. ground station improvements Backup stationary antenna Operate satellite after launch

Develop remote ground stations Train ground operators

Teams – ION 2 Power

Solar Panel power point tracking Battery charger Satellite sleep mode System watchdog timer Voltage, current, and temperature sensors PIC Regulators Switches Latchup protection

Teams – ION 2 Cmd & Data Hnd.

Define internal satellite communication Prototype internal communication bus with PICs Document internal communication interface PIC Training documents

PICs Memory I2C communication Packet definition Memory management Error and flow control Prototype Main PC Board Satellite to ground communication software

Teams – ION 2 Communications

Design communication system Select flight and ground hardware Test and modify hardware as needed Design and develop antenna

Teams – ION 2 Structures

Satellite fabrication Fulfill all Cubesat physical spec requirements. Design frame, mounts, etc Switches, data port, separation springs Removable battery Epoxies Solar panel construction Deployable antenna?? Vibration Testing Thermal/Vacuum testing

Teams – ION 2 ACS

Handles all ACS hardware and software Performs attitude/orbit simulation and analysis

ACS sensors and actuators ACS processor Attitude control software Attitude determination software

Class Meetings

Weekly Systems Team Meeting– Poll each team– Discuss activities from previous week– Discuss plans for next week– Announcements, etc.– Occasional special presentations by advisors/faculty.

Lab Hours– No class “lab hours”– Each team establishes own weekly lab hours– Declare team lab hours team proposal– Log all hours with a brief description of what was done– Class requires ~50 lab hours per credit (per university

guidelines)

Resources

Course Web Site– http://cubesat.ece.uiuc.edu

Course Class Drive– V:\cubesat folder on Cubesat computers– See Training folder

Labs– 206H Talbot– 330E Everitt Lab

ECE/Talbot Machine Shops

Tentative Calendar

Thursday, Aug 25: Informational Meeting Monday, Aug 29: Meet with TA / Select Teams Tuesday, Aug 30: First Systems Meeting Tuesday, Sept 6: Team Proposals

Tuesday, October 18: Design Review

Thursday, Dec 8: Final Demo / Documentation Review

Team Proposals

Ten minute presentation for each team Each team member should discuss their focus

item

Team Members with major, year, credits/hours Team semester plans Focus items for each person Week by week planned schedule Team weekly lab hours

Handouts

Getting Started SSH into Class Drive Class Registration Form

Registering for CubeSat

Juniors/Seniors register for Interdisciplinary Senior Design for 1 to 3 credits– ENG491CU1 (Fall)– ENG491CU1 (Spring)– Need to have approval form signed to register

(available on Web Site)

Grad students register for Independent Study– Course number varies by department– Thesis/Master’s Project sometimes possible

Grading

Based on – Lab hours– Contributions to team– Participation in systems meetings– Participation in reviews– End of semester activity summary

Success in course depends on your individual initiative

Next Steps

Register for class Sign up for class email list Meet with TA to identify team Get access to labs, computer accounts, etc Become familiar with project

– Read ION paper– Read documentation for your team– Browse available team files on class drive

Establish regular team work sessions Team proposal due one week after teams established