-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathDeMi.tex
2078 lines (1609 loc) · 163 KB
/
DeMi.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
\documentclass[12pt]{article}
\pdfpagewidth 8.5in
\pdfpageheight 11.0in
\usepackage{fullpage}
\usepackage{url}
\usepackage{graphicx}
\usepackage{subfigure}
\usepackage{booktabs}
\usepackage{multirow}
\usepackage{rotating}
\usepackage{float}
\usepackage{acronym}
\usepackage{setspace}
\usepackage{amsmath}
\usepackage[hypcap]{caption}
%\onehalfspacing
\usepackage{pdfpages}
\usepackage{tabularx}
\usepackage{bigstrut}
\usepackage{epstopdf}
\usepackage{hyperref}
\usepackage{caption}
%\usepackage{subcaption} is incompatible with subfigure
\usepackage{lscape}
\usepackage{longtable}
\usepackage[section]{placeins}
\title{CubeSat Deformable Mirror Demonstration\\Preliminary Design Review\\}
\author{Kristin L. Berry (KB)\\
Ashley K. Carlton (AC)\\
Zachary J. Casas (ZC)\\
James R. Clark (JC)\\
Vladimir V. Eremin (VE)\\
Zaira G. Garate (ZG)\\
Julian Lemus (JL)\\
Immanuel David Madukauwa-David (IM)\\
Tam Nguyen T. Nguyen (TN)\\
Alexandra E. Wassenberg (AW)\\\\\\\\\\
Department of Aeronautics and Astronautics\\
Massachusetts Institute of Technology\\
}
\date{\today}
\begin{document}
\maketitle
\newpage
\renewcommand{\abstractname}{Executive Summary - ZG, AW}
\begin{abstract}
%\section*{Payload}
The search for signs of life on Earth-like exoplanets requires imaging technology that can produce high contrast and dynamic range images. Current high-performance space telescopes struggle to correct for aberrations in the light wavefront, causing the achievable contrast of images to be reduced. However, adaptable wavefront control imaging technology, specifically deformable mirrors, provide a viable solution to this problem. In the deformable mirror system, a wavefront sensor measures aberrations in an approaching wavefront, and an adaptive optics computer calculates the errors in the wavefront. Electrostatic actuators then deform the surface to correct the wavefront.
Utilizing deformable mirrors in conjunction with coronographs onboard space telescopes could produce images with higher achievable contrast in the direct imaging of exoplanets.
A proposed CubeSat Deformable Mirror demonstration (DeMi) will begin the process of testing the stability, calibration, and predictability of more complex, higher actuator count deformable mirror systems in space which could later be used in high performance space telescope missions.
While in these future applications the deformable mirror system will be used to aid in observing stars or other objects, the mission goal of DeMi is to provide a low-cost, quick access platform on which to demonstrate MEMS wavefront control deformable mirror imaging technology in space and to accomplish this with commercial off the shelf components whenever possible.
The Payload for DeMi is an optical system that allows for the testing and technology demonstration of a deformable mirror system. To keep the design of the Payload simple as possible, a laser will be used as an internal light source for the technology demonstration. Additionally, an external source option has been included to satisfy the ultimate goal of using this technology on a larger space telescope for imaging of bright stars. Due to the added complexity required of the ADCS system on a CubeSat platform, the external source imaging will not require a precise star acquisition and navigation system.
This document presents a detailed overview of the role and design of the Payload for the DeMi mission, as well as the preliminary designs of the various satellite subsystems.
%\section*{Design}
A 3-unit CubeSat platform was selected to carry out this scientific mission due to its low manufacturing and launch costs. This architecture allows the use of commercially available components to streamline the design process and reduce costs. The satellite will be placed on a 500 km Low Earth Orbit at a 40-degree inclination to facilitate communications with the NASA Wallops ground station. This arrangement provides about 45 minutes of ground access time per day. Uplink and downlink connections will be made through a UHF deployable monopole antenna mounted on the spacecraft's chassis. To acquire electrical power, the spacecraft will be equipped with four body-mounted side solar panels. A 10-watt-hour secondary (rechargeable) battery supplies the satellite with energy during eclipse. This configuration minimizes the total surface area and disturbance torques acting on the spacecraft.
%\section*{Risks}
At this stage in the design process, there are some important risks to consider. One of these risks is the very tight margin between the average power needed to operate under certain conditions and the power supplied by the solar panels and battery. Another uncertainty is the ability of the Avionics subsystem to process all Payload and the ADCS data. Finally, while all subsystems have preliminary design and component choices, these still have the potential to undergo changes that could cause conflicts with the current system architecture.
%\section*{Future Work}
Of course, the design must undergo more iteration before it is implemented. Future work includes detailed finite element structural to would ensure that the satellite and all its components will survive launch environment in their current configuration. Additionally, a steady-state thermal analysis must be completed in order to characterize the temperature dependence of the battery and solar panel performance and the temperature gradient across the satellite. This would improve the current power supplied calculations and determine whether the proposed heating design will be effective. The current ADCS design could be refined with more accurate models of external disturbances and an attitude control loop. Also, further work is required to optimize the payload component configuration using optical modeling software.
\end{abstract}
\newpage
\tableofcontents
\listoffigures
\listoftables
\section*{List of Acronyms}
\begin{acronym}
\acro{COTS}{Commercial Off The Shelf}
\acro{CG}{Center of Gravity}
\acro{DeMi}{Deformable Mirror Demonstration}
\acro{DM}{Deformable Mirror}
\acro{DOD}{Depth of Discharge}
\acro{EPS}{Electrical Power System}
\acro{FOV}{Field of View}
\acro{LEO}{Low-Earth Orbit}
\acro{MEMS}{Microelectromechanical Systems}
\acro{P-POD}{Poly-Picosatellite Orbital Deployer}
\acro{PDM}{Power Distribution Module}
\acro{PSF}{Point Spread Function}
\acro{ADCS}{Attitude Determination and Control System}
\acro{IMU}{Inertial Measurement Unit}
\acro{STK}{Satellite Tool Kit}
\end{acronym}
\newpage
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Introduction - AW}
Deformable mirror wavefront control systems correct for aberrations in the wavefront to produce high contrast images. This technology has been employed in ground telescope observation to counter wavefront distortions induced by Earth's atmosphere. However, deformable mirrors have yet to be utilized on a space platform. Such an implementation could remove aberrations in the wavefront due to speckles from diffraction, noise, phase errors, and thermal drift. A proposed CubeSat Deformable Mirror demonstration (DeMi) will begin the process of testing adaptive optics technology in the space environment for future implementation on space telescopes and potentially with free-space laser communication. The use of deformable mirrors in conjunction with coronographs on-board space telescopes will be able to produce images with higher achievable contrast in the direct imaging of exoplanets. This document presents a detailed overview of the role and design of the payload for the DeMi mission, a high actuator count MEMS deformable mirror yet to be tested in space, as well as the preliminary designs of the various satellite subsystems which support the flight of the payload in low Earth orbit.
\subsection{Mission Statement}
The mission of the Deformable Mirror Demonstration is to provide a low-cost, quick-access platform on which to demonstrate microelectromechanical (MEMS) wavefront control deformable mirror imaging technology on-orbit.
\subsection{Motivation}
The driving force behind the DeMi mission is the desire to directly image Earth-like exoplanets in the search for signs of life, requiring imaging technology that can produce high contrast and dynamic range images. However, current high-performance space telescope technology suffers from wavefront aberrations, such as speckles, which can result from diffraction, noise, phase errors, and thermal drift and reduce the achievable image contrast \cite{cahoy-unpublished}.
A solution to this problem is to implement adaptable wavefront control imaging technology in the form of a deformable mirror system. Specifically, a Boston Micromechanics
Mini MEMS Deformable Mirror \cite{bos-micro-demi}, shown in Figure~\ref{fig:Intro_demi} will be used. In the deformable mirror system, a wavefront sensor measures aberrations in an approaching wavefront. An adaptive optics computer then calculates the errors in the wavefront reflecting off of the deformable mirror surface by subtracting the wavefront from a reference wavefront \cite{adaptive-optics-overview}. Finally, electrostatic actuators in an array beneath the membrane surface of the mirror individually deform the surface to correct the wavefront. A comparison of the effects of a flat and deformable mirror on an aberrated wavefront is demonstrated in Figure~\ref{fig:Intro_wavefront}.
\begin{figure}[!ht]
\centering
\includegraphics[width=2in]{images/introduction_1.png}
\caption{Boston Micromechanics MEMS Deformable Mirror \cite{bos-micro-demi}}
\label{fig:Intro_demi}
\end{figure}
\begin{figure}[!ht]
\centering
\includegraphics[width=4in]{images/introduction_2.png}
\caption{Comparison of the effects of a flat and deformable mirror on an aberrated wavefront}
\label{fig:Intro_wavefront}
\end{figure}
Adaptive optics technology is currently being used in conjunction with coronographs in ground telescopes to correct for distortions caused by Earth's atmosphere and to resolve light from nearby objects. An example is seen in Figure~\ref{fig:Intro_exo} of three exoplanets imaged using the Palomar Observatory's Hale Telescope with adaptive optics technology \cite{serabyn2010}.
\begin{figure}[!ht]
\centering
\includegraphics[width=3.75in]{images/introduction_3.PNG}
\caption{Three exoplanets directly imaged using a combination of adaptive optics and a coronagraph with the Palomar Observatory's Hale Telescope.}
\label{fig:Intro_exo}
\end{figure}
However, factors such as high speeds of atmospheric turbulence and limited numbers of photons from targeted exoplanets reduce the achievable image contrast. A solution to this issue is to incorporate deformable mirror wavefront control technology in high performance space telescope missions. The DeMi mission will take the initial step by testing the stability, calibration, and predictability of a more complex, higher actuator count deformable mirror system in space.
A space telescope utilizing a high performance coronograph and deformable mirror wavefront control system to directly image Earth-like exoplanets could potentially cost over a billion dollars. Therefore, a 3U CubeSat platform was selected to conduct the DeMi mission. The 3U CubeSat is a simple, standard platform, with low volume (10 cm $\times$ 10 cm $\times$ 30 cm) and mass (maximum 4 kg for a 3U CubeSat set by the CubeSat Design Specification document \cite{cubesat-specs}). CubeSats additionally have low manufacturing and launch costs and can provide relatively quick and easy access to space, as opportunities exist for them to fly as auxiliary payloads on rockets for other planned missions.
The technology that will be tested in the DeMi mission has a number of foreseeable future applications, including implementation on high performance space telescopes, such as for direct imaging of Earth-like exoplanets, or for use with free-space laser communication in order to correct for aberrations in the atmosphere \cite{cahoy-unpublished}.
\newpage
\section{Mission Overview - ZG}
\subsection{Requirements}
\paragraph{Mission Level Requirements}
\begin{itemize}
\item \textbf{MLR-1} The system design shall follow a 3-unit CubeSat platform.\\
Parent Requirement: MS-1
\item \textbf{MLR-2} The system shall primarily use commercial off the shelf (COTS) and CubeSat parts and components.\\
Parent Requirement: MS-1
\item \textbf{MLR-3} The system shall accommodate and operate a MEMS deformable mirror demonstration experimental payload.\\
Parent Requirement: MS-1
\item \textbf{MLR-4} The system shall operate and produce operational and experimental data for a period of $<$3 months$>$ [goal of 12 months].\\
Parent Requirement: MS-1
\end{itemize}
\paragraph{Systems Requirements}
\begin{itemize}
\item \textbf{SYS-1} The system shall survive launch conditions.\\
Parent Requirement: MLR-4
\item \textbf{SYS-2} The system shall include electrical, mechanical, and software interfaces to the payload\\
Parent Requirement: MLR-3
\item \textbf{SYS-3} The system shall comply with the requirements and constraints listed in the most current CubeSat Design Specification (CDS) document \cite{mission_cubesat}. \\
Parent Requirement: MLR-1
\item \textbf{SYS-4} The system shall be capable of sending and receiving data and instructions to and from the ground.\\
Parent Requirements: MLR-3, MLR-4
\item \textbf{SYS-5} The system shall have a deorbit time of 25 years or less \cite{mission_deorbit}.\\
Parent Requirement: MLR-4
\end{itemize}
\subsection{Design Overview}
The DeMi mission will consist of one small satellite following the 3-unit CubeSat Design Specifications established by the California Polytechnic State University. The satellite will be the size of three stacked 10 cm cubes (called ``units''), measuring a total of 10 cm $\times$ 10 cm $\times$ 30 cm. In accordance to CubeSat specifications, the satellite's mass will not exceed 4 kilograms. In general, CubeSats are launched as secondary hosted payloads inside a standard Poly-PicoSatellite Orbital Deployer (P-POD) \cite{cubesat-specs}.
The CubeSat platform was selected because it offers a low-cost quick access option. Multiple vendors already sell many off-the-shelf CubeSat components with flight heritage for most standard satellite subsystems. Over the past several years, many university projects have been designed and flown on CubeSats.
\subsection{Concept of Operations}\label{sec:systems_conops}
DeMi will be a 3-unit CubeSat on a Low-Earth Orbit (LEO) with an altitude of 500 km at an inclination of 40$^\circ$. This orbit inclination was selected in order to reach the NASA Wallops ground station located in the state of Virginia. The altitude of 500 km positions the satellite well within Low-Earth Orbit exposing the Payload to the space environment while still allowing 6 to 7 ground access opportunities per day for communications with the ground station.
Figure~\ref{fig:Mission_ConOps} shows a timeline of the DeMi concept of operations and mission milestones. Immediately following separation from a standard P-POD, the satellite will begin to charge its primary batteries through solar panels covering the long faces of the structure. During this first stage, the satellite's antenna will be deployed and will emit intermittent beacon signals in order to be located by the ground station. The ADCS (Attitude Determination and Control System) torque coils will detumble the satellite and align it in a nadir-pointing position. The detumble stage will last approximately 2 weeks assuming a tip off rate of 10$^\circ$/sec. A detailed detumbling analysis can be found in Section~\ref{adcs_analysis}. The mission schedule allows up to one month for detumbling, yet any short delays during this stage would not be detrimental to the mission overall.
\begin{figure}[!ht]
\centering
\includegraphics[width=5in]{images/MissionOverview_1.png}
\caption{Timeline of the concept of operations for the DeMi Mission}
\label{fig:Mission_ConOps}
\end{figure}
Once the satellite is in fully operational status, the Payload will begin to conduct scientific experiments and collect data. Two different data capture modes will be performed during the mission: internal source experiments will be done during the first 3 months of operations, while external source experiments will occur during the remainder of the mission. The satellite will attempt to downlink the collected data whenever it passes over the NASA Wallops ground station and is given instructions to begin downlink.
The majority of the time, the satellite will be in stand-by mode; in other words, it will not be capturing or downlinking data. In case of a subsystem malfunction, the satellite will go into safe mode to diagnose the source of the problem.
Given the satellite's altitude, inclination, and surface area, analyses performed using STK predict that the satellite will deorbit within 7.8 years. This timeline agrees with the current 25-year deorbit requirement outlined by NASA standards \cite{nasa-deorbit}.
\subsection{$N^2$ Diagram}
The N$^2$ diagram was an essential tool in the early stages of the design process. It allowed the design team to determine the levels of interaction between different subsystems and exchange input and output variables and values.
\begin{figure}[!ht]
\centering
\includegraphics[width=5in]{images/MissionOverview_2.png}
\caption{High-Level $N^2$ diagram showing input/output relationships between subsystems}
\label{fig:Mission_N2}
\end{figure}
As highlighted Figure~\ref{fig:Mission_N2}, the Payload requirements drive the design of all the other subsystems. While the Payload does not receive design inputs from other subsystems, its design outputs cascade down effectively driving the design of the rest of the satellite. A more detailed view of the DeMi N$^2$ diagram can be found in Appendix 1.
\subsection{System Level Budgets}
\subsubsection{Mass}
In agreement with CubeSat standards, the total mass of the satellite must not exceed 4 kg. Figure~\ref{fig:Mission_mass2} shows the total mass of the satellite broken down by subsystem. As of PDR, the design is projected to weight 3.26 kg and 3.90 kg with added margin. Following industry standards, the subsystem margin percentages used in this analysis correspond to the Mass Growth Allowance values for Preliminary Design published by the American Institute of Aeronautics and Astronautics \cite{mission_aiaa}. Figure~\ref{fig:Mission_mass2} illustrates that the mass of the satellite is driven primarily by the Payload, which takes up approximately one third of the total. The Power and ADCS subsystems closely follow with 26\% and 22\% respectively.
\begin{figure}[!ht]
\centering
\includegraphics[width=5in]{images/MissionOverview_3.png}
\includegraphics[width=5in]{images/MissionOverview_5.png}
\caption{System Mass Budget}
\label{fig:Mission_mass2}
\end{figure}
\subsubsection{Power}
This section presents the power used by the spacecraft during each of its modes of operation as well as the power supplied by the solar panels and battery.
The power used by the satellite during each mode is outlined in Figure~\ref{fig:Mission_power2}. The first two items, ``Safe/Uplink'' and ``Detumbling'', do not occur on a regular daily basis during the operational lifetime of the satellite, which is why their duration is not expressed in minutes per day and their values are not included in the average power calculation.
During its operational period, the satellite will cycle between the data capture, downlink, and stand by modes. As shown in Figure~\ref{fig:Mission_power2}, the most power is drawn by the antenna in the Communications subsystem during downlink.
The satellite is expected to require an average of 3.54 Watts with up to 4.18 Watts with an 18\% margin applied. This allowance percentage of 18\% was derived from input from course faculty and the fact that most components will be commercial off the shelf (COTS) with flight heritage.
Curerntly, the Power system design carries a tight margin. The solar panels and battery are projected to supply up to 3.84 Watts; however, this would not satisfy the average power with margin needed at this stage in the design process. The power supplied is only 8.5\% higher than the expected power needed without margin. This issue is discussed in detail in Section~\ref{sec:power}.
\begin{figure}[!ht]
\centering
\includegraphics[width=5in]{images/MissionOverview_4.png}
\includegraphics[width=5in]{images/MissionOverview_6.png}
\caption{System Power Budget}
\label{fig:Mission_power2}
\end{figure}
\newpage
\section{Subsystems}
\FloatBarrier
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% PAYLOAD
\subsection{Payload}
The Payload for DeMi is an optical system that allows for the testing
and technology demonstration of a deformable mirror system. It must include the following elements: the deformable mirrors the
mission aims to test, a light source to create a wavefront, and a detector to measure the wavefront. These components are attached
to an optical breadboard and are in an enclosure to block out external
light. The challenge in this project is to create an optical system capable of testing the accuracy and reliability of current deformable mirror technology and evaluate its future applications while meeting the mass, volume, and other constraints imposed by the 3U CubeSat platform.
\subsubsection{Requirements - AC}\label{sec:payload_requirements}
\begin{itemize}
\item \textbf{PLD-1} The Payload shall command a MEMS deformable mirror to run a pre-defined test sequence for at least 5 minutes each orbit. \\
Parent Requirements: MLR-3, MLR-4
\item \textbf{PLD-1.1} The Payload shall have the ability to control any combination of actuators within 0.001 s of each other, at a minimum rate of 100 Hz, with a minimum stroke of 1.5 $\mu$m, and with a precision of at least 1 nm.\\
Parent Requirement: PLD-1
\item \textbf{PLD-2} The Payload shall have the ability to measure and reconstruct the optical wavefront at one wavelength for the duration of a 5 minute test sequence each orbit at a frequency of at least 10 Hz.\\
Parent Requirements: MLR-3, MLR-4
\item \textbf{PLD-2.1} The Payload shall have the ability to measure the optical wavefront at a minimum rate of 10 Hz for at least one minute each orbit.\\
Parent Requirement: PLD-2
\item \textbf{PLD-2.2} The Payload shall have the ability to measure the optical wavefront at a minimum rate of 100 Hz for at least 30 seconds each orbit.\\
Parent Requirement: PLD-2
\item \textbf{PLD-2.3} The Payload shall have the ability to reconstruct the optical wavefront with a minimum accuracy of 100 nm rms.\\
Parent Requirement: PLD-2
\end{itemize}
There are two types of requirements on the Payload. The first set (PLD-1) applies to the features of the deformable mirror system. The second set (PLD-2) pertains to the measurement and reconstruction of the wavefront. The complete requirements document can be found in Appendix~\ref{app:requirements}.
The requirements on measuring and reconstructing the wavefront (PLD-2) apply to the detector. Nominally, the detector must operate (capture images) for at least 5 minutes per orbit, and be able to function at a minimum of 10 Hz (PLD-2). The requirement is further separated into a ``Diagnostic Mode'' used for calibration and full frame images, and a ``Burst Mode'', used for data capture. In ``Diagnostic Mode'', the Payload is required to take images for at least a minute per orbit at 10 Hz (PLD-2.1). In ``Burst Mode'', the Payload is required to take images for at least 30 seconds per orbit at a minimum of 100 Hz (PLD-2.2). For both modes, the reconstruction accuracy must be a maximum of 100 nm rms (PLD-2.3).
\subsubsection{Decisions Made and Trade Studies - AC, KB}
\paragraph{Payload Architecture - AC}
While in future applications the deformable mirror system will be used to aid
in observing stars or other objects, the mission goal of DeMi is to characterize the deformable
mirror system, and to accomplish this with commercial off the shelf (COTS) components
whenever possible, providing a quick and simple platform for space (MLR-3, MLR-4).
As mentioned previously, there are a few key components that are integral to the design: the
deformable mirror system to test, a light source to create a wavefront, and a detector to measure the wavefront.
To keep the design as simple as possible, the use of an internal light source, such as a laser, is desirable for the technology demonstration.
Many techniques exist for measuring and reconstructing a wavefront \cite{FGadaptiveoptics}. These can be divided into sensored and sensorless approaches.
Sensorless approaches, such as the Gerchberg-Saxton-Based Estimation Scheme \cite{gerchberg}, are likely to be used for a direct imaging application of a large space telescope mission for their ability to eliminate non-common path optical errors. However, sensorless approaches require additional computational resources, time, and occasionally additional detectors or detector translation \cite{cahoy2013}.
Therefore, only sensored
approaches are considered for this platform due to the compact form
factor, the desire to use simple COTS components, and processing capabilities. There are numerous wavefront
sensing approaches that could be implemented, as well as
modified versions of those presented here, but the two designs discussed are chosen for their ability to be simply implemented in a compact platform.
While other designs (see Section~\ref{sec:payload_interferometer}) may be able to achieve higher precision, the Shack-Hartmann wavefront sensing system fits in the allotted volume with minor modifications to components, and allows for sufficient mirror characterization, meeting our mission goal and requirements (Section~\ref{sec:payload_requirements}). Therefore, the Shack-Hartmann wavefront sensing design in Figure~\ref{fig:SHWFS} has been chosen to image the wavefront.
\subparagraph{Design Decision: Shack-Hartmann Wavefront Sensor - AC}
For the wavefront sensing design in Figure~\ref{fig:SHWFS}, a Shack-Hartmann lenslet array is used, allowing for accurate wavefront measurement and reconstruction sensitivity. The design has an internal source (laser diode), whose path is denoted by a dotted red line, and an aperture for imaging an external source, whose path is denoted by a dotted green line.
\begin{figure}[ht]
\centering
\includegraphics[width=5in]{images/payload_SHWFS.jpg}
\caption{Design decision: Wavefront Sensing design with a Shack-Hartmann lenslet array}
\label{fig:SHWFS}
\end{figure}
For the internal source, the laser diode module emits a collimated elliptical beam. This beam enters a linear polarizer (where its intensity is halved). The beam then encounters a flat mirror at 45 degrees, reflecting the beam 90 degrees, and proceeds to a primary beam splitter. Here, the beam is reflected 90 degrees to a secondary polarizing beamsplitter, and reflected another 90 degrees. The beam then goes through a quarter waveplate (where the beam is now elliptically polarized) before striking the deformable mirrors. The deformable mirrors reflect the beam back through the quarter waveplate, rendering the beam now linearly polarized with an orientation that allows it to pass through the secondary beam splitter. The beam then proceeds through the lenslet array, creating a spot diagram on the detector corresponding to shape of the wavefront (see Section~\ref{sec:payload_sh}).
For the external source, the wavefront beam enters a plano-convex lens and passes through a collimating lens. The beam then enters a linear polarizer (where the intensity is halved). The beam passes through the primary beam splitter, and then to the secondary polarizing beamsplitter, which reflects the beam 90 degrees towards the quarter waveplate and the deformable mirrors, as mentioned previously, and follows an identical path as the internal light source to the detector.
The chosen design allows the detector to image both an internal and external source. While the mission goal can be accomplished with just an internal source, the ultimate goal of using this technology on a larger space telescope for imaging of bright stars motivates the use of an external source. Therefore, the option for an external source is included in the design.
Due to the added complexity required of the ADCS system on a CubeSat platform, the external source imaging will not require a precise star acquisition and navigation system. In contrast, with pointing knowledge from ADCS, the shutter on the aperture will be commanded open when a bright star is in the field of view (FOV). Based on preliminary models looking at five bright stars (Alpha Centauri, Arcturis, Canopus, Sirius, and Vega), the satellite would expect to see the same bright star every orbit for an average of three to five minutes\footnote{Based on an STK simulation performed by Annie Marinan.}. The pointing requirement on the maximum ADCS slew rate to keep the star on the same pixel on the detector is discussed in the Paragraph Pointing Requirement.
It is necessary that the aperture for imaging an external source be small, given the volume constraints of the CubeSat platform after accommodating all of the key elements of the system (deformable mirror, mirror driver electronics, detector, and necessary imaging optics). Due to the physical size of these key elements, it is not practical to design the external source imaging as a typical reflecting telescope. While it may be possible to accommodate an aperture lens with relatively large diameter ($>60$ mm), the corresponding longer focal length would not fit in the volume, and the space for folding (and resizing) the beam is limited. While the smaller aperture will limit the angular resolution and sensitivity and increase the size of the point spread function (PSF), tight angular resolution is not a requirement for this technology demonstration. Therefore, this design has an aperture lens with diameter 12.7 mm, with a minimum focal length on the order of its diameter. Using the Rayleigh criterion, the angular resolution at 500 nm is 9.907".
The current design allows for open and closed loop control. Images and centroid solutions can be sent to the ground, allowing for evaluation of the mirror performance over time. In addition, closed loop control (active correction of the wavefront on orbit) can also be implemented on-board using the centroids and calculated slopes to command the mirrors. Calculating mirror response from slopes requires little additional processing \cite{centroids}.
All optical elements of the system are preliminarily chosen.
(See Appendix~\ref{app:payload_components} for the full list of
elements with part numbers and mass totals.) Glass elements are
chosen to be UV fused silica over other types of glass whenever possible for
their better performance in space \cite{radiation_optics} due to a
high coefficient of thermal expansion and better UV transmission. All
elements also have anti-reflective coatings that are efficient in the
visible spectrum (400 - 700 nm). All components in Figure~\ref{fig:SHWFS} are shown with their mounts. However, the mass and volume of the mounts are only estimates of the custom mounts that will be built for all optics. Custom mounts will be built to adapt the optics for space applications. All elements must be mounted in stress-free mounts (e.g., no glass touching metal) and mounted to an optical breadboard with multi-footed lens tubes that are made of aluminum, or of a metal that has a similar coefficient of thermal expansion as the lens it holds. Future modeling and optimization of the optical design will yield more exact component choices.
\subparagraph{Other Designs Considered: Michelson Interferometer with Nanopositioner - AC}\label{sec:payload_interferometer}
The interferometer design shown in Figure~\ref{fig:interferometer} is slightly modified from a typical interferometer due to volume constraints on the Payload and the requirement for high contrast imaging. It has an internal source (laser diode), whose path is denoted by a dotted red line.
The laser beam is first resized, passes through a neutral density filter, then is reflected 90 degrees by a
flat mirror. The light is then divided by a beam splitter oriented 45
degrees to the beam. The transmitted beam travels to the deformable
mirror where it is reflected back towards the beam splitter. Half of
the beam is deflected by 90 degrees at the beam splitter and strikes
the detector. The reflected beam travels to the flat mirror on the
nanopositioner where it is reflected and half of it then is transmitted
through the beam splitter and reaches the detector. The two beams that
reach the detector interfere to produce fringes \cite{traeger} that are analytically well understood as a function of beam coherence/divergence and mirror tip/tilt \cite{demtroeder} and that can be simulated for a variety of different deformable mirror shapes.
\begin{figure}[ht]
\centering
\includegraphics[width=5in]{images/payload_interferometer.jpg}
\caption{Other considered design: Michelson Interferometer with the flat mirror on a nanopositioner.}
\label{fig:interferometer}
\end{figure}
For this particular design, as mentioned previously, a flat mirror is on a nanopositioner, or a piezo linear stage, which moves in increments of fractions of the incoming wavelength. This allows for higher precision fringe patterns, allowing for better mirror characterization.
What is not shown in Figure~\ref{fig:interferometer} is the controller for the nanopositioner \cite{newport_nanopositioner}. It does not currently fit within the constraints of the satellite in terms of mass, volume, and power needs, and would require significant modifications, if it were to be implemented. Also, the additional moving part (nanopositioner) increases the risk and complexity of the mission, making the Shack-Hartmann wavefront sensor the design choice.
\subparagraph{Payload Operations - AC}
For the initial demonstration and on-orbit testing, an internal light
source will be used. This eliminates any Payload specific requirements
on the satellite's attitude and inclination. For the latter half of
the mission, an external light source will be used, in order to attempt to image the optical wavefront from a star. All downlinked files will be timestamped.
\begin{enumerate}
\item{\textbf{Status Checks}}
After detumbling, and two weeks of commissioning, as described in
Section~\ref{sec:systems_conops}, the Payload will perform a status check of all instruments. This includes the deformable mirror system, the detector, and the laser. Each element will be turned on and checked for error or status codes. Any available status information directly from the deformable mirrors, detector, and laser will be sent to the ground.
\item{\textbf{Calibration}}
The next phase is to calibrate the system using the ``Diagnostic Mode" requirements outlined in Section~\ref{sec:payload_requirements}. This involves turning on the laser and recording several images in this configuration with the detector, without deforming the mirrors (acts as a flat mirror). From these images, on-board processing algorithms can find the centroids \cite{centroids} and average them to obtain new `standard centroids', which will be used for wavefront comparison calculations throughout the remainder of the mission. These images, averages, and new centroid solutions will be stored on-board and sent to the ground.
\item{\textbf{Data Capture: Internal Source}}
The next, and most important, stage is data capture using the internal source. The laser is turned on, then the mirror is deformed by a predetermined test sequence of commands, and the wavefront is imaged on the detector. The test sequence will include `poking' one actuator at a time, and `poking' combinations of actuators in commonly known shapes, such as Zernike polynomials and Fourier modes. Then, the images will be read from the detector, centroids will be found, and one full image and the collection of centroid solutions will be stored on-board and sent down to the ground. Local wavefront slopes will be found from the centroid solutions using simple on-board algorithms, and the mirrors will be commanded for active wavefront correction on-board.
\item{\textbf{Data Capture: External Source}}
The second part of data capture will be with an external source. This external source will be a bright star, such as Vega or Sirius, as mentioned previously. With
knowledge from ADCS, the shutter will be commanded open, and the laser
will be commanded off, allowing an external source to be imaged. The
images will be read from the detector, the centroids will be found, and one
full frame image along with the collection of centroid solutions will be stored on-board
sent to the ground. Identical to data capture with an internal source, local wavefront slopes will be found from the centroid solutions using simple on-board algorithms, and the mirrors will be commanded for active wavefront correction on-board.
\end{enumerate}
\paragraph{Deformable Mirror System - KB} \label{par:payload_dms}
Deformable mirrors (DMs) are mirrors whose surfaces can be dynamically deformed. This deformation is often achieved by actuators placed beneath the mirror's surface which can be commanded to push or pull the surface they are attached to inward or outward. The maximum amount an actuator can push the mirror's surface inward or outward is called the \emph{stroke} of the mirror. The maximum local variation in the slope of the wavefront which can be reconstructed is limited by the maximum stroke of the DM, so DMs with larger strokes allow for the reconstruction of wavefronts with larger amplitude variations. While many DMs are very large, this study uses MEMS DMs controlled by electrostatic actuators a few $\mu m$ long which can be individually controlled by applying voltages to the correct actuator electrodes.
There are few vendors which sell MEMS deformable mirrors which can be realistically be modified to fit inside a CubeSat. Two companies' products are considered here: Boston Micromachines and Iris Adaptive Optics. The Boston Micromachines (BMC) Mini DM comes in three different sizes of stroke and aperture. Since there is little room for resizing optics in the system, the aperture of the DM limits the beam size which will travel through the Shack Hartmann lenslet array. For a sufficiently large Shack Hartmann lenslet array, a larger beam size will allow the wavefront to be sampled by more lenslets, resulting in a better resolution for wavefront reconstruction. As such, larger apertures are preferable. As shown in Table~\ref{table:payload_dms}, each option meets or exceeds Payload's requirements. While the Iris AO PT111 does have a larger aperture \emph{and} a larger stroke, its driver board is larger and much more difficult to modify than the BMC Mini's. As such, the largest BMC mini DM, with a 2.25 mm aperture and a stroke of 5.5 $\mu \text{m}$, is selected.
\begin{table}[!ht]
\caption{Deformable Mirrors Considered for Payload Design}
\begin{tabular}{|l||l|llll|}
\hline
&\textbf{Requirement}&\textbf{Mini 1.5 $\mu$m}& \textbf{Mini 3.5 $\mu$m} & \textbf{Mini 5.5 $\mu$m} &\textbf{Iris AO PT111} \\ \hline
Stroke& Min 1.5 $\mu$m & 1.5 $\mu$m & 3.5 $\mu$m & 5.5 $\mu$m & 5 or 8 $\mu$m \\ \hline
Rate& Min 100 Hz& 8 kHz & 8 kHz & 8 kHz & $>$ 6.5 kHz\\ \hline
Control Precision& 1 nm & 0.09 nm& 0.2 nm & 0.3 nm & 0.3 or 0.5 nm \\ \hline
Response Time& 0.001 sec & 20 $\mu$s & 100 $\mu$s & 500 $\mu$s& $< 200 \mu$s \\ \hline
Aperture& - & 1.5 mm & 2.0 mm &2.25 mm&3.5 mm\\
\hline
\end{tabular}\label{table:payload_dms}
\end{table}
\paragraph{Detector - KB} \label{par:payload_detector}
There are two kinds of detectors normally used to detect and record incoming light in telescope systems: (charge coupled device) CCD detectors and (complementary metal oxide semiconductor) CMOS detectors. While until recently CCD detectors have been largely preferred for their high efficiency and better noise performance, CMOS production technology has improved and is now competitive in noise performance. Whereas CCD detectors read out pixels one-by-one in series, CMOS detectors can read out individual pixels in parallel. This makes it possible to take images much more quickly with CMOS detectors than with similar CCD detectors. Additionally, CMOS detectors are more resistant to radiation damage, making them particularly well suited to a space environment.
We considered several options for detectors, manufactured by Thorlabs, e2v, and Imaging Development Systems (IDS,) which are summarized in Table~\ref{table:payload_detectors}. (For more information on how the data rate shown in this table was calculated, please see Section~\ref{sec:data_rate}.) The e2v frame-transfer CCD easily meets Payload's requirements, but at the cost of a detector area twice the size of any of the CMOS detectors and a corresponding increase in mass. (Frame transfer CCDs are able to achieve fast readout speeds by having half the detector dedicated to actively imaging and the other half of the detector dedicated to slowly reading out the data.) Since the requirements could be met with a smaller, lighter, and cheaper CMOS detector, the frame transfer CCD was not selected.
The UI52-41LE-M CMOS detector from IDS was selected from the CMOS detectors considered for its small 5.2 $\mu \text{m}$ pixel size, and its ability to meet the ``Diagnostic Mode'' frame rate requirement of 10 fps in fullframe mode and the ``Burst Mode'' frame rate requirement of 100 fps in a 640 x 480 subframe mode. While not included in the rough error model used to calculate the accuracy shown in Table~\ref{table:payload_detectors}, a smaller pixel size should allow for a more precise centroid calculation, which will result in a more precise measurement of the local slope of the wavefront. This detector comes with a pre-mounted lens tube which the Shack Hartmann lenslet array will be placed in.
\begin{table}[!ht]
\caption{Detectors Considered for Payload Design}
\begin{tabular}{|l||l|llll|}
\hline
Detector & Req. PLD-2
&47-20&DCC1545M&UI1221LE-M&UI5241LE-M\\ \hline \hline
Manufacturer&-&e2v&Thorlabs&IDS&IDS\\ \hline
Type&-&Frame transfer CCD&CMOS&CMOS&CMOS\\ \hline
Fullframe rate& 10 Hz & 5 MHz & 25 fps & 87.2 fps & 50 fps \\ \hline
Subframe rate& 100 Hz & - & 79 fps & 100 fps & 102 fps \\ \hline
Accuracy & 100 nm rms & 11.2 nm rms & 45 nm rms & 45 nm rms & 45 nm rms \\ \hline
Data Rate& - & 52.4 Tbit/s & 259 Mbit/s & 207 Mbit/s & 310 Mbit/s \\\hline
\end{tabular}\label{table:payload_detectors}
\end{table}
\paragraph{Shack-Hartmann Lenslet Array - AC} \label{sec:payload_sh}
A Shack-Hartmann lenslet array consists of a matrix of small lenses (called lenslets) of the same focal length, where the array is focused on the detector. Each lenslet forms a ``spot'', creating a spot diagram on the detector. Figure~\ref{fig:lenslet_array} demonstrates incoming light through a lenslet array. The local tilt of the wavefront across each lenslet can then be calculated from the position of the focal spot on the sensor; the displacement, $\Delta x$, equals the local slope of the wavefront. Any phase aberration can be approximated to a set of discrete tilts. By sampling an array of lenslets, all of these tilts can be measured and the whole wavefront approximated. Only tilts are measured, so the lenslet array cannot detect discontinuous steps in the wavefront.
\begin{figure}[ht]
\centering
\includegraphics[width=5in]{images/payload_SH.png}
\caption{The result of two wavefronts, plane (top)
and abberated (bottom), entering a Shack-Hartmann lenslet array, and their
resulting spot diagrams on the detector \cite{ctio_AO}.}
\label{fig:lenslet_array}
\end{figure}
To get the best measurement of the wavefront, the maximum number of spots, and therefore lenslets, is desired. As a result, for a constant beam size, a lenslet array should be chosen with the lowest pitch (distance from the center of each lens) in order to get the maximum number of spots for the beam.
Therefore, the microlens array MLA150 was chosen from ThorLabs \cite{MLA150} (see Figure~\ref{fig:MLA150}), with a pitch of 150 $\mu$m.
The lenslet is 10 mm square, so it contains about 66 by 66 lenslets. It is mounted in the lens tube on the detector. For an approximate beam size of 2.25 mm (see Paragraph ``Deformable Mirrors'' above), approximately 15 by 15 lenslets will be used of the lenslet array. See Paragraph ``Pixels per Lenslet Spot'' below for a discussion of the pixels used on the detector per lenslet.
\begin{figure}[ht]
\centering
\includegraphics[width=4in]{images/payload_MLA.jpg}
\caption{The MLA150 lenslet array from ThorLabs \cite{MLA150} chosen for the Shack-Hartmann Wavefront Sensing design consists of many microlenses, aligned closely together.}
\label{fig:MLA150}
\end{figure}
\subsubsection{Analysis - AC, KB}
\paragraph{Pointing Requirement - KB}\label{sec:pointing_requirement}
During external data acquisition, it is desirable to have the image of the star be on the same pixels of the detector for the duration of the exposure time, so that the image of the star is not spread across many pixels on the detector.
To determine the pointing requirement which achieves this, it is necessary to calculate the plate scale of the detector.
%and the amount of time needed to get a reasonable SNR for a star of a reasonable magnitude.
The plate scale of the detector is the relationship between angular distance on the sky and pixel size on the detector, and is typically measured in arcseconds per pixel. The plate scale used to calculate the pointing requirement was estimated to be 28 arcseconds/pixel by Eduardo Bendek\footnote{[email protected]} at NASA AMES.
%%% insert calculations to get to this point.
The pointing requirement for ADCS during external source imaging can then be determined by using Equation~\ref{pointing}.\\
\begin{equation}\label{pointing}
\text{maximum slew rate} = \frac{\text{plate scale}}{\text{maximum exposure time}}
\end{equation}
%is there a better way to do simple formulas that don't really need to be in equation form?
The longest amount of time spent continuously collecting incoming light is the maximum exposure time. The maximum exposure is 0.1 seconds and occurs during ``Diagnostic Mode'' if the incoming light is collected continuously between reading out images. Plugging everything into Equation~\eqref{pointing}, the maximum slew rate requirement during external source data acquisition is $\frac{22 \text{ arcseconds/pixel}}{0.1 \text{ s}} \approx 4.7$ arcminutes/s.
\paragraph{Data Rates to Avionics - KB}\label{sec:data_rate}
The rate at which Payload will output image data from the detector to Avionics is a function of the number of pixels of the image selected for output (either the full frame or a subframe), the number of bits per pixel, and the rate at which images are taken in frames per second (fps). The simple formula for this is shown in Equation~\eqref{data}. \begin{equation}\label{data} r_{out} = \text{pixels} \times \frac{\text{bits}}{\text{pixel}} \times \text{fps}
\end{equation}
%is there a better way to do simple formulas that don't really need to be in equation form?
These values and the calculated data output rate for the selected detector, the IDS UI52-41LE-M CMOS, are shown in Table~\ref{table:payload-data-rates}. The data output rate for more of the detectors considered for this design are shown in Table~\ref{table:payload_detectors}. Note that the $640 \times 480$ subframe will be used for ``Burst Mode,'' and the $1280 \times 1024$ full-frame will be used for ``Diagnostic Mode.''
\begin{table}
\begin{center}
\caption{Data output rates by detector and subframe mode}
\begin{tabular}{|c||c|c|}
\hline
& Fullframe & Subframe \\
\hline
IDS CMOS UI5241LE-M & & \\
\hline
Bits Per Pixel & 10 & 10\\
Pixel Resolution & 1280 x 1024 & 640 x 480 \\
Image rate & 50 fps & 102 fps\\
Data Rate & 655.4 Mbit/sec & 310 Mbit/sec \\
\hline
\end{tabular}\label{table:payload-data-rates}
\end{center}
\end{table}
\paragraph{Pixels per Lenslet Spot - AC}\label{sec:payload_pixels}
In order to image the spots created by the Shack-Hartmann microlenslet array, spots must fall on their own unique pixels. At least four pixels are required per lenslet spot (a two by two square of pixels) to account for the event in which a spot lands between two pixels, or at the center of four pixels.
The incoming beam is 2.25 mm (see Paragraph ``Deformable Mirrors'' above). This corresponds to about 15 by 15 spots. The detector has a pixel size of 5.2 $\mu$m, so a 2.25 mm beam corresponds to about 425 px square. Therefore, over twenty pixels are available for each lenslet spot, so there is no concern for multiple spots falling on the same pixel.
\paragraph{Actuators per Lens - AC}
The chosen BMC deformable mirrors have a total of 32 actuators (a 6 by 6 array, with no corners) with an actuator pitch of 450 $\mu$m \cite{BMC}. The Shack-Hartmann lenslets have a pitch of 150 $\mu$m, so there will be a minimum of four spots devoted to each actuator. Therefore, there is no concern for individual actuators to be untested or characterized improperly.
\subsubsection{Summary of Outputs - AC}
The Payload's operational requirements are major drivers for the design of the rest of the satellite. A summary of mass totals, power needs, and thermal requirements of all major Payload components can be found in Table~\ref{fig:payload_summary_table}.
During data capture mode, the Payload must be kept within $0^\circ$C to $50^\circ$C, will draw a maximum power of 4.5 W, will output a maximum data rate of 550 Mbit/s, and, during external data acquisition only, has a maximum slew rate of 4.7'/s.
With all components, the Payload is 1.00 g, and 1.25 kg with a 25\% margin.
\begin{table}
\caption{Summary of the mass totals, power needs, and thermal needs of the major Payload components.}
\begin{tabular}{|c||c|c|c|c|} \hline
\textbf{Component} & \textbf{Mass (g)} & \textbf{Power (W)} & \textbf{$T_{operating}$ ($^\circ$C)} & \textbf{$T_{storage}$ ($^\circ$C)} \\ \hline \hline
Laser diode & 24.45 & 0.0045 & -10 to 50 & unknown \\
Detector & 46.64 & $<$ 2 W & 0 to 50 & -20 to 80 \\
DMs + Driver & 189.9 & $<$ 2.5 W & -10 to 50 & unknown \\
Optical Breadboard & $\sim$250 & -- & -- & -- \\
Optical Enclosure & $\sim$300 & -- & -- & -- \\ \hline \hline
Totals & 996.9 & 4.5 max & 0 to 50 & -20 to 80 \\ \hline
\end{tabular}\label{fig:payload_summary_table}
\end{table}
\subsubsection{Risks - KB}
Payload has two major risks that may present a problem moving forward with the design. Several of the smaller components needed to assemble the optical system (mounts, o-rings, spacers) are not available commercially in sizes small enough to fit within the CubeSat. As such, these components will need to be custom machined. (Their masses and volumes were estimated by scaling down similar COTS components for the purposes of mass budgeting.) It is possible that these estimates will prove to be incorrect, or that it will prove difficult to machine these components at the small sizes necessary. This presents a low probability, but high impact risk, as we are already close to exceeding our mass budget.
The other major risk that Payload faces is that it will produce data too quickly for Avionics to consume it, or that it will require too much processing power for Avionics to make space for incoming data quickly enough by processing the incoming images and outputting much smaller files with wavefront solutions. This risk has largely been obviated by Avionics's move to a FPGA architecture, but since the performance of the wavefront reconstruction algorithm on the FPGA has not yet been tested, there is still some chance that this will prove to be problematic. This risk is low probability and low impact, as nearly the same amount of useful data can be extracted about the DM's performance by outputting simple centroid solutions for the images, rather than a full wavefront reconstruction.
\subsubsection{Future Work - AC}
Future work includes optical modeling of the system using the software ZEMAX \cite{zemax}. Modeling the system with ZEMAX will determine the
final beam profile on the detector. This will allow for more precise calculations of data rates, for example. Optimization of the space will
be determined to find the best choice of optical components. Thermal
effects on the beam and optical components will be also analyzed, along with the effects of slight misalignments (i.e. with lenslet array).
Also, to determine the feasibility of the interferometer with the nanopositioner design, discussions with various nanopositioner manufacturers are needed to resolve if the nanopositioner elements can be appropriately modified for a CubeSat platform. Preliminarily, a nanopositioner would require additional power and processing. Further effects on other subsystems needs to be determined.
Furthermore, while the design allows for imaging of an external source, when and how to image an external
source still needs to be determined. Specific bright stars need to be chosen, and their revisit times calculated more precisely based on the orbital parameters unique to DeMi.
Lastly, specific properties of the deformable mirror system need to be explored. For example, a stroke analysis needs to be performed. Also, research needs to be done to try to predict the deformable mirror system's performance in a space environment, and how this might be quantified and corrected.
\newpage
\FloatBarrier
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% POWER
\subsection{Power - JC} \label{sec:power}
\subsubsection{Requirements}
\begin{itemize}
\item \textbf{POW-1} Power subsystem shall supply 3.54 watts to power bus on average over each orbit.
\\
Parent Requirement: MLR-3
\item \textbf{POW-1.1} Power subsystem shall have solar panels to supply power to other systems while satellite is in sunlight and recharge batteries for eclipse.
\\
Parent Requirement: POW-1
\item \textbf{POW-1.1.1} Solar panels shall supply 3.54 watts after 12 months of operation.
\\
Parent Requirement: POW-1.1
\item \textbf{POW-1.2} Power subsystem shall have rechargeable (secondary) batteries to supply power during eclipse.
\\
Parent Requirement: POW-1
\item \textbf{POW-1.2.1} Secondary batteries shall have 6.5 watt-hours of capacity after 12 months / 6,000 cycles.
\\
Parent Requirement: POW-1.2
\item \textbf{POW-2} Power subsystem shall supply 13.84 watts of power for peak operations
\\
Parent Requirement: MLR-3
\end{itemize}
The required power is calculated in Equation~\ref{eq:power-required}. The number of cycles is calculated in Equation~\ref{eq:power-num-cycles}. The required battery capacity is calculated in Equation~\ref{eq:power-batt-size}.
\subsubsection{Decisions Made}
The chosen solar panel configuration is four body-mounted side panels. Body-mounted panels are chosen over deployable panels because they minimize the surface area of the satellite, and are symmetrical. Minimizing surface area minimizes the disturbance torques, which reduces the power needs of the ADCS, and being symmetrical eliminates a pointing constraint. The zenith and nadir faces are left bare so that they can be coated with a paint that improves the thermal characteristics of the satellite. The zenith face is also left bare to accommodate an aperture that allows the Payload to image external light sources; the limitations imposed by the placement of the aperture and the required shape of a top-mounted solar panel limit the available area for solar panels, making it impractical to panel.
The remainder of the Power subsystem is composed of a stack of modules to manage power distribution throughout the satellite. An EPS (Electrical Power System) takes power from the solar panels and manages the current and voltage levels to ensure that the panels deliver power at maximum efficiency. A secondary (rechargeable) battery supplies the satellite with energy during eclipse; the 10-watt-hour model was chosen, as this satisfies the required capacity and depth-of-discharge (see Equation \ref{eq:power-batt-size}). A PDM (Power Distribution Module) supplies power to systems which are not part of the main system stack, such as the torque coils.
The satellite's Power subsystem does not include a primary battery. A primary battery is not included in the design because the satellite is covered on most sides by solar panels and is power-positive in detumbling mode, so it will charge as soon as it exits the P-POD. The only reference to a CubeSat containing a primary battery was a description of a CubeSat that lacked solar panels entirely.\cite{libertad-1}
\subsubsection{Trade Studies}
STK was used to compare the average power obtained by the solar panels under several circumstances. The two variables were the inclusion or omission of a solar panel on the top face of the satellite, in addition to the four side-mounted panels, and the orientation of the satellite in its orbit. The three orientations considered were ``face-first'', ``corner-first'', and spinning about its long axis. The face-first and corner-first attitudes are illustrated in Figure \ref{fig:power-orientations}.
\begin{figure}[ht]%
\centering
\includegraphics{images/power-face-first.png}%
\hspace{0.5in}
\includegraphics{images/power-corner-first.png}
\caption{The ``face-first'' and ``corner-first'' attitudes. Images generated from STK.}%
\label{fig:power-orientations}%
\end{figure}
\begin{table}[ht]
\caption{Power values for various panel configurations and satellite attitudes.}
\label{tab:power-trade-study}
\begin{center}
\begin{tabular}{|c|c|c|c|} \hline
& \textbf{Face-first} & \textbf{Spinning} & \textbf{Corner-first} \\ \hline
\textbf{Side panels} & 3.77 W & 4.16 W & \textbf{4.52 W} \\\hline
\textbf{Side and top panels} & 4.45 W & 4.84 W & 5.19 W \\\hline
\end{tabular}
\end{center}
\end{table}
After confirming with ADCS that the satellite could orbit in the corner-first attitude without difficulty, the corner-first attitude is chosen because it maximized available power.
These power values are averaged over the entire orbit, that is, taking the incoming power to be zero during local night and including that in the average. This is done because the satellite is active during the entire orbit, and its average power needs are calculated over the entire orbit. To ensure that comparisons between power required and power received are valid, the same is done for the power generated.
\subsubsection{Analysis}\label{sec:power-analysis}
The average power required by the satellite subsystems is the time-weighted average of the power required during the various modes of the satellite:
\begin{equation}
P_{req,avg} = \frac{1}{T_{total}}\sum_{modes}{ \sum_{systems}{T_{mode} \: P_{sys,mode}} } = 3.54 \ \text{W}
\label{eq:power-required}
\end{equation}
To meet those needs, the solar panels are required to gather more power, to account for the inefficiency of the EPS ($\eta = 0.85$ in the worst case\cite[p.~9]{EPS-manual}). This required orbital-averaged power is compared to the results from the STK simulation in Table \ref{tab:power-trade-study}. This requirement can then be scaled by a factor of $\frac{T_d + T_e}{T_d}$ to compute the power required from the solar panels while in sunlight.
\begin{align}
P_{req,panels} = \frac{T_d + T_e}{T_d}\frac{P_{req,avg}}{\eta} &= 6.61 \ \text{W (dark)}\nonumber\\
&= 5.21 \ \text{W (bright)}\nonumber\\
&= 4.16 \ \text{W (orbit avg)}
\label{eq:power-required-panels}
\end{align}
``Bright'' and ``dark'' here refer to the two orbital cases which have the most and least solar exposure for the satellite. Because the orbit is fixed in inertial space, it appears to rotate with respect to the Earth-Sun vector over the course of a year. Every six months, the satellite transitions from a ``dark'' orbit, which is in the sunlight 63\% of the time, to a ``bright'' orbit, which is 80\% sunlit, and back again. The two orbits are illustrated in Figures \ref{fig:power-bright-orbit} and \ref{fig:power-dark-orbit}, respectively. The incoming power values, described in the Trade Studies section and tabulated in Table \ref{tab:power-trade-study}, were computed in a ``dark'' orbit.
\begin{figure}[ht]%
\centering
\includegraphics{images/power-bright-orbit}%
\caption{A ``bright'' orbit, where the satellite is exposed to the sun 80\% of the time. Image generated from STK.}%
\label{fig:power-bright-orbit}%
\end{figure}
\begin{figure}[ht]%
\centering
\includegraphics{images/power-dark-orbit}%
\caption{A ``dark'' orbit, where the satellite is exposed to the sun 63\% of the time. Image generated from STK.}%
\label{fig:power-dark-orbit}%
\end{figure}
The satellite drains the most energy from the battery if it performs a ground station pass (maximum duration: 9.77 minutes) and scientific operation (maximum duration: 5 minutes) during local night:
\begin{equation}
E_{req,batt} = T_{sci} P_{sci} + T_{comm} P_{comm} + (T_e - T_{sci} - T_{comm}) P_{standby} = 3.9 \ \text{Wh}
\label{eq:power-batt-req}
\end{equation}
The excess power is the power generated by the panels that does not go into powering the satellite or charging the battery -- in other words, the difference between the power required power and the power generated:
\begin{align}
P_{excess} = P_{panels} - P_{req,panels} &= 0.63 \ \text{W (dark)}\\ \nonumber
&= 2.57 \ \text{W (bright)}
\label{eq:power-excess}
\end{align}
It can be useful to model the excess power as an average over the entire orbit, rather than just during local day (for first-order approximations of the equilibrium satellite temperature):
\begin{align}
P_{excess,avg} = P_{excess} \: \frac{T_d}{T_d + T_e} &= 0.40 \ \text{W (dark)}\\\nonumber
& = 2.06 \ \text{W (bright)}
\label{eq:power-excess-avg}
\end{align}
The number of charge-discharge cycles of the battery is approximately equal to the number of orbits that the satellite will have to sustain:
\begin{equation}
N_{cycles} = \frac{T_{year}}{T_{orbit}} = 5500 \approx 6000 \ \text{(with 10\% margin)}
\label{eq:power-num-cycles}
\end{equation}
According to SMAD, the depth of discharge of a lithium-ion battery expected to survive approximately 10,000 cycles should be limited to 60\% \cite[p.~651,~Fig.~21-16]{SMAD}. This means that the minimum battery size is:
\begin{equation}
E_{batt} \geq \frac{E_{batt,req}}{DOD} = \frac{3.9 \ \text{Wh}}{0.60} = 6.5 \ \text{Wh}
\label{eq:power-batt-size}
\end{equation}
\subsubsection{Summary of Outputs}
\begin{table}[ht]
\caption{Outputs to other systems (mass, volume, power consumed, and survival and operating temperatures).\cite[p.~9]{EPS-manual}\cite[p.~11,~21]{PDM-manual}\cite[p.~9]{Battery-manual}\cite[p.~2]{Solar-panel-datasheet}}
\label{tab:power-outputs}
\begin{center}
\begin{tabular}{|l|p{0.55in}|p{0.65in}|p{0.9in}|p{1.1in}|p{1.3in}|} \hline
\textbf{Component} & \textbf{Mass} (kg) & \textbf{Volume} (U) & \textbf{Power consumed} (W) & \textbf{Survival temperature} ($^\circ$C) & \textbf{Operating temperature} ($^\circ$C) \\ \hline \hline
Solar panels & 0.540 & 0 & 0 & -40 to 80 & -40 to 80 \\\hline
EPS & 0.083 & 0.15 & 0.1 & -50 to 100 & -40 to 85 \\\hline
Battery & 0.256 & 0.2 & 0.1 & -10 to 50 & 0 to 50 \\\hline
PDM & 0.060 & 0.25 & 0.16 & -50 to 100 & -40 to 85 \\\hline \hline
\textbf{Total} & \textbf{0.939} & \textbf{0.6} & \textbf{0.36} & \textbf{-40 to 80} & \textbf{-40 to 80} \\\hline
\end{tabular}
\end{center}
\end{table}
The power subsystem's outputs were the mass and volume of its components, the power consumed, and the survival and operating temperatures. The mass and volume were supplied to the Structures subsystem, to ensure that the components would meet the mass and volume constraints of a 3U CubeSat. The power consumed was taken into consideration in the power budget. The survival and operating temperatures were used by the Thermal subsystem, to establish the required temperatures in each operating mode. The values are summarized in Table \ref{tab:power-outputs}.
Some of the components did not contribute to the outputs to other subsystems. The solar panels are fixed to the sides of the Cubesat, so they do not occupy any of the three units of internal volume, indicated by assigning them a volume of zero. The battery's low-temperature constraint was not taken into account for the total survival and operating temperature ranges, because the battery has a built-in heater that keeps it above zero degrees Celsius.\cite[p.~12]{Battery-manual}
\subsubsection{Risks}
The solar panels will supply 4.52 watts on average over an orbit, which is a 28\% margin over the power needs. However, the EPS is not perfectly efficient. The connection to the solar panels is the least efficient, with a minimum efficiency of 85\%\cite[p.~9]{EPS-manual}. When this is taken into account, as few as 3.84 watts may actually be supplied to the battery power bus. This has a margin of 8.5\% over the satellite's average power needs (which might then be further eroded by inefficiencies in the power lines), which is less than the 18\% margin goal set by Systems, and substantially less than the 30\% margin recommended by JPL.
This system risk is mitigated by the 32\% margin of available power over the standby power need of 2.92 watts. This provides assurance that the satellite will be power-positive during its standby mode. Should the satellite find itself unable to meet its power needs with the nominal five minutes of data capture every orbit, it can be commanded to spend more time in standby and downlink modes to restore balance to the power budget.
This strategy brings with it a mission risk: that if the 8.5\% margin is not enough, and the satellite is forced to spend more time in standby mode, it will not spend enough time on data capture and downlink modes to complete its science objectives.
However, as mentioned in Analysis (Section \ref{sec:power-analysis}), the available power from the solar panels was calculated for the darkest orbit that the satellite will experience. For the brightest orbit, the average power generated by the solar panels over the entire orbit increases to 7.42 watts, which, taking the worst-case EPS efficiency into account, results in 6.31 watts reaching the power line. This has a 78\% margin over the average power required. In fact, the duration of data capture mode could be increased nearly six-fold to 29 minutes per orbit while maintaining a 30\% margin at 60\% depth of discharge. This possibility mitigates the mission risk: if the satellite is forced to reduce the duration of data capture and downlink modes during darker orbits to conserve power, it can make up for any shortfalls of captured data during brighter orbits.
\subsubsection{Future Work}
The performance of the solar panels and batteries is temperature-dependent. In particular, the battery becomes more effective as its temperature increases, while the solar panels become less efficient. Going forward, it would be useful to perform a more detailed simulation of the satellite that incorporates a thermal model, to more accurately measure the effect of satellite temperature and dissipated excess energy.
\newpage
\FloatBarrier
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% COMM
\subsection{Communication - ZC}
\subsubsection{Requirements}
\begin{itemize}
\item \textbf{COMM-3.1} The subsystem shall transmit at 19.2 kb/s for uplink and 1.5 Mb/s for downlink. \\
Parent Requirement: COMM-3
\item \textbf{COMM-3.2} The subsystem shall have a bandwidth of 445-455 MHz for uplink and 460-470 MHz for downlink. \\
Parent Requirement: COMM-3
\end{itemize}
The driving requirements for the Communications subsystem are that it should transmit at the data rates and frequencies (Comm-3.2) that are necessary to transmit all data to the ground station. The required frequencies are 445-455 MHz for uplink and 460-470 MHz for downlink. The required data rates are 19.2 kb/s for uplink and 1.5 Mb/s for downlink.
\subsubsection{Decisions Made}\label{sec:comm_decisions}
The L-3 Cadet Nanosat UHF Radio was chosen for use on DeMi. It transmits at the frequencies and data rates outlined in the requirements. The transceiver has an extra 4 GB of storage that avionics uses in addition to any of its storage.
Because the transceiver is transmitting and receiving at UHF frequencies, a very common antenna choice is to use a measuring tape antenna that is tuned to the frequency that is desired. Because the antenna works like a quarter-wave monopole, the desired length of the antenna is calculated by dividing the wavelength of the signal by 4. Because the transmitting and receiving frequencies are different, the average of these frequencies is used to compute the wavelength. With a frequency of 465 MHz, the wavelength equals .645 meters. Then, the length of the antenna can be determined using Equation~\ref{eq:comm-antenna-length}.
\begin{equation}\label{eq:comm-antenna-length}
\lambda = c/f
\end{equation}
In Equation~\ref{eq:comm-antenna-length}, $l$ is the length of the antenna, and $\lambda$ is the wavelength.
Using a wavelength of .645 meters, the desired length of the antenna is about .164 meters. The
gain of this antenna will be approximately 3 dB and the beam width approximately $65^\circ$. DeMi is
using two of these antennas so that communication can occur even if it is rotated 180 degrees
from where it is supposed to be.
The ground station that DeMi communicates with will be the NASA Wallops UHF Ground Station. This ground station is being used because the transceiver chosen for DeMi was also used in the Dynamic Ionosphere CubeSat Experiment, and the ground station that was used in that mission was the NASA Wallops UHF Ground Station. The diameter of the dish is 18.29 meters, the gain is 35 dB and the beam with is $2.9^\circ$.
\subsubsection{Trade Studies} \label{sec:communications-trade-studies}
The main factor in choosing the transceiver on DeMi is the maximum data downlink rate. Because Payload is generating so much data, the Communications system needs to have a high downlink rate to ensure that all of that data can be sent to the ground. Several options were investigated, and the transceiver with the highest data rate is being used. The transceivers that were considered and their maximum data rates are shown in Table~\ref{table:comm_transceivers}.
\begin{table}[ht]
\caption{Communications Trade Study for Maximum Downlink Data Rate}
\begin{center}
\begin{tabular}{| c | c |} \hline
\textbf{Tranceiver} & \textbf{Maximum Downlink Rate} \\ \hline \hline
Espace Payload Telemetry System & 1 Mb/s \\
AstroDev Li-1 UHF Transceiver & 38.4 kb/s \\
ISIS TXS Small Satellite S-Band Transmitter & 100 kb/s \\
Tyvak UHF Transceiver & 200 kb/s \\
L-3 Cadet Nanosat UHF Radio & 1.5 Mb/s \\
Microhard MHX2420 Modem & 230.4 kb/s \\ \hline
\end{tabular}\label{table:comm_transceivers}
\end{center}
\end{table}
\subsubsection{Analysis}
The maximum amount of data downlink per pass-by can be calculated by multiplying the downlink data rate and the access duration per pass-by. Given the downlink data rate of 1.5 Mb/s, and the access duration of $586$ seconds per pass-by, the maximum amount of data that can be downlinked in one pass-by is 109.9 MB. Because the satellite is not always directly above the ground station, the satellite is not always downlinking at the maximum data rate. To account for this, and for space for telemetry data and error correcting code, a margin of a factor of 2 is added, so the maximum amount of data from payload that can be downlinked per pass-by is about 54.95 MB. Although this is not as much data as payload is creating, on-board processing is used so that the amount of data that needs to be downlinked is below the maximum amount that is allotted for payload.
A link budget was created in order to determine the link margin for a worst case and a best case for uplink and downlink. The uplink budget and the downlink budget are detailed in Appendix~\ref{app:link_budgets}.
The first calculation for the link budget is to determine the worst case propagation path length. The best case length is 500 km because that is the altitude at which the satellite is orbiting. Figure~\ref{fig:comm_propagation_path} shows how a wave propagates through that atmosphere.
\begin{figure}[ht]
\centering
\includegraphics[width=5.5in]{images/comm-angles.png}
\caption{Diagram of propagation path of a signal from a satellite \cite[p.~12]{ITU-R}.}
\label{fig:comm_propagation_path}
\end{figure}
In order to determine the propagation path length, $r$, the path length of the first layer and the second layer must be determined and added together. The equation for calculating the path length of a layer is as follows in Equation~\ref{eq:comm_path_length} \cite[p.~9]{ITU-R}.
\begin{equation}\label{eq:comm_path_length}
a_n = -r_n\cos(\beta_n) + \frac{1}{2}\sqrt{4r_n^2\cos^2(\beta_n)+8r_n\delta_n+4\delta_n^2}
\end{equation}
In this equation, $a_n$ is the path length through layer $n$, $r_n$ is the radius from the center of the Earth to the beginning of layer $n$, $\beta_n$ is the exiting incidence angle, and $\delta_n$ is the thickness of layer $n$.
The angle $\beta_n$ can be calculated using Equation~\ref{eq:comm-exit-angle} \cite[p.~10]{ITU-R}.
\begin{equation}\label{eq:comm-exit-angle}
\beta_{n+1} = \arcsin\biggl(\frac{n_n}{n_{n+1}}\sin(\alpha_n)\biggr)
\end{equation}
In this equation, $n_n$ is the refractive index of layer $n$, and $\alpha_n$ is the entry incidence angle. Angle $\alpha_n$ can be calculated with the last equation needed in order to calculate the propagation length, Equation~\ref{eq:comm-entry-angle} \cite[p.~9]{ITU-R}.
\begin{equation}\label{eq:comm-entry-angle}
\alpha_n = \pi - \arccos \biggl(\frac{-a_n^2 - 2r_n\delta_n - \delta_n^2}{2a_n r_n + 2a_n \delta_n}\biggr)
\end{equation}
Values that still need to be defined are $\beta_1$ (because it cannot be calculated using the Equation~\ref{eq:comm-entry-angle}), $\delta_1$, $\delta_2$, $n_1$, and $n_2$. $\beta_1$ is just equal to the complimentary angle to the minimum angle at which the Wallops Ground Station can track, which is $5^\circ$. $\delta_1$ will be equal to the altitude at which the atmosphere ends which one can say is about 100 km. $\delta_2$ is just the orbiting altitude minus $\delta_1$. $n_1$, which is simple the refractive index of air, is 1.000293. The last remaining value to be defined is $n_2$, which is the refractive index of a vacuum, which is just 1. Using these equations, one can find that $a_1$ equals 707 km, and $a_2$ equals 1375 km. This means that the worst case propagation path length is equal to 2082 km. The refraction of the wave in air did not change the path length by very much. Without accounting for the refraction, the path length can be calculated using the equation for $a_n$. In this calculation, $r_n$ equals $r_1$, $\beta_n$ equals $\beta_1$, and $\delta_n$ equals 500 km which is the altitude at which DeMi orbits. These values give a path length equal to 2077 km, which is only 5 km shorter than the path length when taking refraction into consideration.
The next value calculated in the link budgets is the Equivalent, Isotropic Radiated Power (EIRP). In order to calculate the EIRP, Equation~\ref{eq:comm-eirp} should be used \cite[p.~476]{SMAD}.
\begin{equation}\label{eq:comm-eirp}
EIRP = P_{tx} + G_{tx} - L_{output}
\end{equation}
In Equation~\ref{eq:comm-eirp}, $P_{tx}$ is the transmitter power, $G_{tx}$ is the transmit antenna gain, and $L_{output}$ is the output loss which is equal to all losses associated with the transmitter. All of these values can be found in the two link budgets in Appendix~\ref{app:link_budgets}.
Another calculated value in the link budget is the space loss. This is the loss of the signal as it is transmitted through space. It can be calculated using Equation~\ref{eq:comm-space-loss} \cite[p.~476]{SMAD}.
\begin{equation}\label{eq:comm-space-loss}
L_s = 92.45 + 20\log_{10}(r) + 20\log_{10}(f)
\end{equation}
In Equation~\ref{eq:comm-space-loss}, $L_s$ is space loss, $r$ is the propagation path length, and $f$ is the frequency of the transmitted signal. All of these values can also be found in the two link budget tables in Appendix~\ref{app:link_budgets}.
Equation~\ref{eq:comm-antenna-temp} can be used to calculate the transmitting antenna temperature \cite{pozar}.
\begin{equation}\label{eq:comm-antenna-temp}
T_{antenna} = \eta T_{sky} + (1 + \eta) \frac{T_{sky} + T_{ground}}{2}
\end{equation}
In Equation~\ref{eq:comm-antenna-temp}, $\eta$ is the antenna efficiency, $T_{sky}$ is the temperature of the space behind the receiving antenna. The temperatures used for uplink are determined by using the background temperature of space. For downlink, the temperature of the Earth is used. $T_{ground}$ is the temperature of the ground around the antenna. For uplink, this is the temperature of the Earth, and for Downlink, it is the background temperature of space.
The system noise temperature, $T_{sys}$, is calculated by adding the transmitting antenna temperature and the receiver temperature \cite{pozar}. The receiver temperature for both cases is unique to the receiver and can be determined by the manufacturer.
The next calculated value is the Receiver Gain to Noise Temperature. This is computed using Eqn.~\ref{eq:comm-gain-to-noise} \cite[p.~477]{SMAD}.
\begin{equation}\label{eq:comm-gain-to-noise}
\frac{G}{T} = G_{rx} - T_{sys}
\end{equation}
In Equation~\ref{eq:comm-gain-to-noise}, $G/T$ is the receiver gain to noise temperature, $G_{rx}$ is the receiving antenna gain, and $T_{sys}$ is the system noise temperature. Using $G/T$, the total losses in the system, and EIRP one can determine the receiver carrier to noise ratio \cite[p.~477]{SMAD}.
\begin{equation}\label{eq:comm-carrier-to-noise}
\frac{C}{N_0} = EIRP + \frac{G}{T} - L_{total} + 228.6
\end{equation}
Using the value from Equation~\ref{eq:comm-carrier-to-noise} and the data rate in decibels, one can calculate the energy per bit to noise ratio \cite[p.~478]{SMAD}.
\begin{equation}\label{eq:comm-energy-to-noise}
\frac{E_b}{N_0} = \frac{C}{N_0} - R_b
\end{equation}
Finally, the link margin can be determined by subtracting the required energy per bit to noise ratio from the predicted one \cite[p.~478]{SMAD}. The best and worst case link margins for uplink and downlink are shown in Figure~\ref{fig:comm_cases}.
\begin{figure}
\hfill
\subfigure[Best Case Communication]{\includegraphics[width=3in]{images/communications-best-case.PNG}}
\hfill
\subfigure[Worst Case Communication]{\includegraphics[width=3in]{images/communications-worst-case.PNG}}
\hfill
\caption{Representation of Satellite and Ground Station during a.) Best Case Communication and b.) Worst Case Communication}
\label{fig:comm_cases}
\end{figure}
\subsubsection{Summary of Outputs}
There were several outputs during the design process from the Communications subsystem. These outputs include the ground station to the orbits subsystem, which is NASA Wallops UHF Ground Station, the beam width of Wallops UHF Ground Station and DeMi to ADCS, which are $2.9^\circ$ and $65^\circ$ respectively. The operational and survival temperatures of the transceiver to the Thermal subsystem, the power for each mode to the Power subsystem, and the mass and volume to the Structures subsystem are detailed in Table~\ref{table:comm_summary_outputs}.
\begin{table}[ht]
\caption{Communications Budgets}
\begin{center}
\begin{tabular}{|c||c|} \hline
\textbf{Output} & \textbf{Value} \\ \hline \hline
Power (Standby) & 0.51 W \\
Power (Data Capture) & 0.51 W \\
Power (Downlink) & 11.44 W \\
Power (Uplink) & 0.51 W \\
Power (Safe Mode) & 0.51 W \\
Mass & $\sim$ 0.235 kg \\
Volume & 0.069 U \\
Operating Temperature Range & $-20^\circ$ to $70^\circ$ \\
Survival Temperature Range & $-40^\circ$ to $80^\circ$ \\ \hline
\end{tabular}\label{table:comm_summary_outputs}
\end{center}
\end{table}
\subsubsection{Risks}
Initially, there were concerns that Communications may not be able to downlink enough of the
data from the Payload; however, Avionics has decided that because of this risk, DeMi will be
doing on-board processing so that less data is required to be downlinked. There is the risk
that there may be a lot of interference at the frequencies that DeMi uses. In order to determine
this, there would have to be a ground station site survey and if there were a problem with
interference, specialized receiver software would have to be developed to mitigate the issue.
\subsubsection{Future Work}
The main issue to be addressed is testing of measuring tape antennas. There is currently not very much information out there that is available to DeMi concerning them, so research to determine the exact gain, beam width and radiation patterns should be conducted.
\newpage
\FloatBarrier
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% AVIONICS
\subsection{Avionics}
\subsubsection{Requirements - VE}
\begin{itemize}
\item \textbf{AVI-1} Avionics shall provide the necessary interfaces to support all subsystems.\\
Parent Requirements: MLR-3, SYS-2
\item \textbf{AVI-3} Avionics shall write and store data to a mass storage device onboard the satellite.\\
Parent Requirements: MLR-4, SYS-2
\end{itemize}
The main Avionics subsystem requirements are to provide the necessary interfaces, calculations and data storing capability to support functioning of all other subsystems during the mission operation. In addition, Avionics shall be able to recover from potential single event effects and permit software updates and reprogramming in orbit.
However, the most important requirements to consider are the memory and processor capabilities because they are the most difficult to satisfy with the current level of technology.
One of the sub-requirements of the mass storage device is to be determined (TBD). Because the data processing algorithms that the Avionics will perform are not yet fully determined, the memory read and write speed required to support the data processing is also unknown. However, memory speed is an essential parameter that has to be considered when there is a good enough estimation of data after image processing, so the requirement has been written as a placeholder until the algorithms have been determined more thoroughly.
\subsubsection{Trade Studies - VE}
There are two main Avionics configurations considered that are both able to satisfy subsystem’s requirements. They are presented in Table~\ref{table:avionics_hardware_options}. The major difference between configurations is the capability of the first system to do real time image processing, which results in higher complexity and power consumption of that system (see The Steepest Ascent Mission Interface Computer in Table~\ref{table:avionics_hardware_options}). The second configuration only allows downloading raw images to the ground stations without processing them.
\begin{table}[ht]
\caption{Hardware Options}
\label{table:avionics_hardware_options}
\begin{center}
\begin{tabular}{| c || p{6cm} | p{6cm} |} \hline
& \textbf{Processing on-board} & \textbf{Raw images to the ground} \\ \hline \hline
Component name & The Steepest Ascent Mission Interface Computer CS-MIC-G-EM & Single Board Computer Motherboard + Pluggable Processor Module with Texas Instruments MSP430F2618 \\ \hline
Power consumption & 0.5 - 1.25 W & 10 mW \\ \hline
Capabilities & Telemetry/Telecommand + Real time image processing on FPGA & Telemetry/Telecommand\\ \hline
Storage Capacity & Up to 16 GB & Up to 2 GB \\ \hline
Processors & TI MSP430 + Xilinx FPGA (model can be selected) & TI MSP430F2618 \\ \hline
Interfaces & I2C, SPI, UART & I2C, SPI, UART \\ \hline
Mass & 62 g & 88 - 114 g \\ \hline
\end{tabular}
\end{center}
\end{table}
To select the appropriate hardware, Payload requirements should be considered first, since they introduce the most limitations to the processor and memory capabilities.
\begin{table}[ht]
\caption{Camera imaging modes}
\label{table:avionics_modes}
\begin{center}
\begin{tabular}{| c || p{3cm} | p{3cm} | p{3cm} |} \hline
\textbf{Mode} & \textbf{640x480 px ``subframe''} & \textbf{640x480 px ``subframe''} & \textbf{1280x1024 px ``full frame''} \\ \hline \hline
Frame Rate & 100 fps & 10 fps & 10 fps \\ \hline
Data Rate & 310 Mbit/s & 31 Mbit/s & 131 Mbit/s \\ \hline
Duration & 30 s & 300 s & 60 s \\ \hline
Memory Required & 1.14 GB & 1.14 GB & 0.96 GB \\ \hline
\end{tabular}
\end{center}
\end{table}
If the approach where all the data generated by Payload is sent to ground station without processing it, the Payload will be generating around 1 GB of data every time (Table~\ref{table:avionics_modes}). For a given downlink speed of 1.5 Mbit/sec, 600 s is required to downlink all the captured data, or 10 ground accesses. Since there is only one ground access every three orbits, in general, this particular approach is considered to be ineffective in terms of Payload’s active time.
That is why the second approach is considered. It assumes all necessary calculations to be done on-board and only results are sent to the ground. It dramatically reduces the amount of transferred data to around 10-100 KB instead of gigabytes and enables to implement a closed loop deformable mirror control system.
The next decision for the Avionics subsystem is the processor. Now, there are higher but still reasonable requirements for processing power according to the computation tasks that it will be solving:
1) centroid, delta x and delta y computations, 2) slope reconstruction, and 3) linear algebra for mirror controller.
The Steepest Ascent Mission Interface Computer CS-MIC-G-EM is a good fit for such tasks because it has a Field-programmable gate array (FPGA) to be configured for image processing and a microcontroller for general tasks such as telemetry and ADCS computations (see Section~\ref{adcs_analysis}).
\subsubsection{Decisions Made - VE}
The CS-MIC-G-EM meets the requirements of supporting telemetry and telecommand operations. In addition, it provides a platform to perform advanced on-board pre-processing of data, allowing for more sophisticated analysis to be performed and more efficient use of available downlink bandwidths.
Other key features of the CS-MIC-G-EM include its storage capability, allowing data from multiple Payload units to be stored centrally. It also includes the ability to reprogram the on-board processing units, allowing in-flight updates of algorithms to be performed as well as novel concepts to be supported.
\begin{figure}[ht]
\centering
\includegraphics[width=5in]{images/Avionics_fig1.png}
\caption{Structure diagram of Mission Interface Computer CS-MIC-G-EM \cite{avionics_clyde_space}}
\label{fig:avionics_MIC}
\end{figure}
CS-MIC-G-EM provides a number of options that allow different system architectures to be accommodated. The FPGA Fabric (see Figure~\ref{fig:avionics_MIC}) can be used to implement data processing algorithms, allowing data to be pre-processed before being transmitted to the ground. The attached ROM, RAM and Mass Storage can be used to accommodate more complex algorithms that require buffering of data as well as filter weights/ lookup table values to be stored.
The decision to use CS-MIC-G-EM (see Figure~\ref{fig:avionics_MIC}) is made mainly because it enables the fastest possible onboard image processing \cite{avionics_FPGA}, which reduces the amount of data which is sent to the ground and provides with a capability to build a closed loop deformable mirror control system.
The general system architecture is shown in Figure~\ref{fig:avionics_architecture}. The selected Mission Interface Computer also allows for separation of telemetry from image processing data. The first is processed on CPU (TI MSP430 microcontroller), which runs an operating system and performs general control tasks, while the latter is done on FPGA (see Table~\ref{table:avionics_hardware_options}) and written into Mass Storage device (see Figure~\ref{fig:avionics_MIC}).
\begin{figure}[ht]
\centering
\includegraphics[width=7in]{images/Avionics_fig2.PNG}
\caption{System's structure diagram}
\label{fig:avionics_architecture}
\end{figure}
Another important component is the operating system that is required to control the satellite. Since low power microcontrollers (MSP430) are used, FreeRTOS from Real Time Engineers Ltd. \cite{avionics_RTOS} or Salvo from Pumpkin, Inc. \cite{avionics_pumpkin} real-time operating systems are the best options. Image processing software is embedded into the FPGA as synthesized hardware architecture which can be done from MATLAB code using HDL Coder.
The Avionics subsystem provides the following interfaces with other subsystems (see Table~\ref{table:avionics_interfaces}). It is important to mention that all analog interfaces are implemented in a Power Distribution Module (PDM). It allows collecting all the data from analog sensors and sending over a single I2C interface to the Avionics board. The PDM implements torque coil drivers as well.
\begin{table}[ht]
\caption{Avionics hardware interfaces with other subsystems}
\label{table:avionics_interfaces}
\begin{center}
\begin{tabular}{| p{2cm} | l | c | c |} \hline
\textbf{Subsytem} & \textbf{Component} & \textbf{Interface} & \textbf{Data rate} \\ \hline \hline
\textbf{Payload} & Detector (IDS UI-5241LE-M) & GbE & 550 Mbit/s max \\
& Mirror driver (BMC Mini-Driver) & USB 2.0 & 480 Mbit/s max \\
& Laser (ThorLabs CPS 186) & GPIO & -- \\ \hline
\textbf{Power} & EPS, PDM & 12C & 400 Kbit/s max \\ \hline
\textbf{ADCS} & 5 sun sensors & Analog (via PDM) & 100 bit/s$^1$ \\