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

2.  Acquire development methods of a CubeSat project Introduction 2 Eye-Sat, student pilot project for a performant nanosatellite  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

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

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

5. 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 ! 5 Global Image of galaxy in visible domain and proximity infrared Technological Demonstration

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

7. Eye-Sat internal view

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

9. 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 9

10. 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. 10

11. EyeSat MO Service Operations 11 Area IdentifierService IdentifierArea Number Service Number Area Version eyesatstartracker11291 Interaction PatternOperation Identifier Operation Number Support in Replay Capability Set SENDping1No 1 SENDreset2No PUBLISH/SUBSCRIBEmonitorstr3No

12. EyeSat MO Service TM Data 12 NameStandardSTRDataFrame ExtendsMAL::Composite Short Form Part1 FieldTypeNullableComment frameheaderMAL::UOctetYesFrame Header deviceidMAL::UOctetYes ST-200 device Id (origin of data) expMAL::UShortYesExposure time in ms q1MAL::FloatYesQuaternion 1 q2MAL::FloatYesQuaternion 2 q3MAL::FloatYesQuaternion 3 q4MAL::FloatYesQuaternion 4

13. EyeSat MO Service TC Data 13 Operation Identifierreset Interaction PatternSEND Pattern SequenceMessageBody Type INSENDStrResetArgument NameStrResetArgument ExtendsMAL::Composite Short Form Part1 FieldTypeNullableComment resetChoiceStrResetEnumerationNoAlternative possible resets NameStrResetEnumeration Short Form Part3 Enumeration ValueNumerical ValueComment MCU1Resets board controler ARM2Resets the ST CPU POWER3Perfoms a power cycle

14. EyeSat MO Service Event Data 14 Area IdentifierService Identifier Area Number Service Number Area Version eyesatmanagemode11351 Interaction PatternOperation Identifier Operation Number Support in Replay Capability Set SENDacq2trans1No 1 SENDtrans2standby2No SENDsurvival2trans3No Event Name Object Number Object Body Type Related points to Source points to TransitionMode1TransitionModeReportNot usedThe origin of the transition event (TC or onboard check)

15. Any Questions ? 15