Eye-Sat : an astronomy

student nanosatellite

CCSDS meeting, March 23, 2015

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

Eye-Sat Planning Phase 0/A

Phase B

Phase C

Phase D

Sept 2012

Sept 2013 March

2015

Feb 2016

Launch inApril 2016

RDP

Sept 2014

RCD

RQ RADec. 2015

3

piggy-back launch

Mission Centre

Control Centre

Ground Stations

ScientificMission

ScientificProducts

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 !

5

Global Image of galaxy in visible domain and proximity infrared

Technological Demonstration

Eye-Sat external view

Solar panel

X band antenna

S band antenna

Eye-Sat launching configuration

Solar protection

6

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

9

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

EyeSat MO Service Operations

11

Area Identifier Service Identifier Area NumberService Number

Area Version

eyesat startracker 1 129 1

Interaction Pattern Operation IdentifierOperation Number

Support in Replay

Capability Set

SEND ping 1 No

1SEND reset 2 No

PUBLISH/SUBSCRIBE monitorstr 3 No

EyeSat MO Service TM Data

12

Name StandardSTRDataFrame

Extends MAL::Composite

Short Form Part 1

Field Type Nullable Comment

frameheader MAL::UOctet Yes Frame Header

deviceid MAL::UOctet Yes ST-200 device Id (origin of data)

exp MAL::UShort Yes Exposure time in ms

q1 MAL::Float Yes Quaternion 1

q2 MAL::Float Yes Quaternion 2

q3 MAL::Float Yes Quaternion 3

q4 MAL::Float Yes Quaternion 4

EyeSat MO Service TC Data

13

Operation Identifier reset

Interaction Pattern SEND

Pattern Sequence Message Body Type

IN SEND StrResetArgument

Name StrResetArgumentExtends MAL::Composite

Short Form Part 1Field 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 3 Perfoms a power cycle

EyeSat MO Service Event Data

14

Area Identifier Service Identifier Area Number

Service Number

Area Version

eyesat managemode 1 135 1

Interaction Pattern Operation Identifier Operation Number

Support in Replay

Capability Set

SEND acq2trans 1 No1

SEND trans2standby 2 No

SEND survival2trans 3 No  

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 ?

15