CNES eyesat and MO

Download Report

Transcript CNES eyesat and MO

Eye-Sat :
an astronomy student
nanosatellite
CCSDS meeting, March 23, 2015
Introduction
Eye-Sat, student pilot project for a performant nanosatellite
 Acquire development methods of a
CubeSat project
 Setting support for other CNES JANUS
nanosatellite projects (engineering,
management, documentation)
 Build
a
triple
CubeSat
performant as possible
as
 Develop necessary building blocks
 In orbit Demonstrator of new
technologies reusing CNES R&T
2
Eye-Sat Planning
Phase 0/A
Launch in
April 2016
Phase B
Sept 2012
Sept 2014
Phase C
Sept 2013
RDP
March 2015
Feb 2016
Phase D
RCD
RQ
Dec. 2015
3
RA
Scientific
Mission
piggy-back
launch
Ground
Stations
Control Centre
Operations
Mission
Centre
Scientific
Products
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
5
Eye-Sat external view
X band antenna
Eye-Sat launching configuration
Solar protection
S band antenna
Solar panel
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 Number
Service
Number
Area Version
eyesat
startracker
1
129
1
Interaction Pattern
Operation Identifier
Operation
Number
Support in
Replay
Capability Set
SEND
ping
1
No
SEND
reset
2
No
PUBLISH/SUBSCRIBE
monitorstr
3
No
1
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
exp
MAL::UShort
Yes
ST-200 device Id
(origin of data)
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
Operation Identifier
reset
Interaction Pattern
SEND
Pattern Sequence
Message
Body Type
IN
SEND
StrResetArgument
Name
Extends
Short Form Part
Field
resetChoice
Name
Short Form Part
Enumeration Value
MCU
ARM
POWER
13
Type
StrResetEnumeration
Numerical Value
1
2
3
StrResetArgument
MAL::Composite
1
Nullable
Comment
No
Alternative possible resets
StrResetEnumeration
3
Comment
Resets board controler
Resets the ST CPU
Perfoms a power cycle
EyeSat MO Service Event Data
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
No
SEND
trans2standby
2
No
SEND
survival2trans
3
No
Event Name
TransitionMode
14
Object
Number
1
Object Body Type
TransitionModeReport
Related
points to
Not used
1
Source points to
The origin of the
transition event
(TC or onboard check)
Any Questions ?
15