Eye-Sat : an astronomy student nanosatellite CCSDS meeting, March 23, 2015

Eye-Sat, student pilot project for a performant nanosatellite Introduction Eye-Sat, student pilot project for a performant nanosatellite Acquire development methods of a CubeSat project Build a triple CubeSat as performant as possible Setting support for other CNES JANUS nanosatellite projects (engineering, management, documentation) Develop necessary building blocks In orbit Demonstrator of new technologies reusing CNES R&T

Eye-Sat Planning Phase 0/A Launch in April 2016 Phase B Phase C Sept 2012 Phase B Sept 2014 Sept 2013 Phase C March 2015 RDP Phase D Feb 2016 RCD RQ RA Dec. 2015

Scientific Mission piggy-back launch Mission Centre Control Centre Ground Stations Scientific Products Operations

Eye-Sat mission Cartography of zodiacal light (polarity, intensity) in visible and near-infrared domain Zodiacal light is a faint, roughly triangular, diffuse white glow seen in the night sky but difficult to see from the Earth Characterization of interplanetary dust Essential for weak sources observation (exoplanets, galaxies) First mission dedicated to zodiacal light ! Global Image of galaxy in visible domain and proximity infrared Technological Demonstration

Eye-Sat external view X band antenna Eye-Sat launching configuration Solar protection S band antenna Solar panel

Eye-Sat internal view

Eye-Sat ground to space interfaces and MO Software architecture principles Components reused

Software architecture principles Maximum reuse of components and COTS : Reuse of generic PUS M&C and scheduling components in C onboard Reuse of a generic M&C component called IMIS on ground Reuse of flight dynamics components for orbit determination and prediction Reuse of CNES MO Java framework, MO/SPP, and ESA open source graphical MO editor

Software architecture principles Use of MO for what ? To bridge the different components and make them interoperate To define onboard and on ground service interfaces Automatic generation of PUS interfaces, ground MO Java API’s and IMIS component interface PUS messages are fully “Moified”. Use of MO/SPP on ground to receive/read and write/send those messages What use of MO ? MO services are defined using only MAL concepts. COM is not used. Reuse of a generic M&C component called IMIS on ground. No use of M&C MO services. If there is no existing component for some specific missing service, MO framework may be used to develop it.

EyeSat MO Service Operations Area Identifier Service Identifier Area Number Service Number Area Version eyesat startracker 1 129 Interaction Pattern Operation Identifier Operation Number Support in Replay Capability Set SEND ping No reset 2 PUBLISH/SUBSCRIBE monitorstr 3

EyeSat MO Service TM Data Name StandardSTRDataFrame Extends MAL::Composite Short Form Part 1 Field Type Nullable Comment frameheader MAL::UOctet Yes Frame Header deviceid ST-200 device Id (origin of data) exp MAL::UShort Exposure time in ms q1 MAL::Float Quaternion 1 q2 Quaternion 2 q3 Quaternion 3 q4 Quaternion 4

EyeSat MO Service TC Data Operation Identifier reset Interaction Pattern SEND Pattern Sequence Message Body Type IN StrResetArgument Name StrResetArgument Extends MAL::Composite Short Form Part 1 Field Type Nullable Comment resetChoice StrResetEnumeration No Alternative possible resets Name StrResetEnumeration Short Form Part 3 Enumeration Value Numerical Value Comment MCU 1 Resets board controler ARM 2 Resets the ST CPU POWER Perfoms a power cycle

EyeSat MO Service Event Data Area Identifier Service Identifier Area Number Service Number Area Version eyesat managemode 1 135 Interaction Pattern Operation Identifier Operation Number Support in Replay Capability Set SEND acq2trans No trans2standby 2 survival2trans 3   Event Name Object Number Object Body Type Related points to Source points to TransitionMode 1 TransitionModeReport Not used The origin of the transition event (TC or onboard check)

Any Questions ?