MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric...

11
-1- MMO: Payload AIV MMO-SWG #3 [March 2006] C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbite AIV (Assembly, Integration, Verifi cation) for BepiColombo MMO Payoads Y. Kasaba, T. Takashima, H. Hayakawa (JAXA/BepiColombo Project Office)

Transcript of MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric...

Page 1: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-1-

MMO: Payload AIVMMO-SWG #3 [March 2006]

C. Noshi/RASC, Kyoto Univ.

MMO

Mercury Magnetospheric Orbiter

AIV (Assembly, Integration, Verification)for BepiColombo MMO Payoads

Y. Kasaba, T. Takashima, H. Hayakawa(JAXA/BepiColombo Project Office)

Page 2: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-2-

MMO: Payload AIVMMO-SWG #3 [March 2006]

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013

Implementation phase [old Ph-B/C/D]

Payload Selection

Definition phase[old Ph-A/B]

Launch2013.8B

PM (Ph.B) ESA JAXA both

ESA JAXA both

Technical study

Pre-PM1

MMO&MCS STM test

JAXA(ISAS)

ESA

(Calendar year)

PDR 2007.12E

Integrated Test & AIV

FM(Ph.C/D)

Pre-PM2

PRR2005.3B

PRR=Preliminary requirements Rev.PDR=Preliminary Definition Rev. CDR=Critical Design Rev. QR=Qualification Rev.

MMO-FM at ESTEC

(by ESA plan)

MMO-STM at ESTEC

(by ESA plan)

ITT

MMO-STM2009.5M

MMO-EM2010.6B

MMO-FM2011.9B

CDR2009.6E

MIC/EIC2010.3B-6B

Sub-Env test2010.7B-9E

QR 2011.8E

AIV2010.11B-2011.7E

2008.8E

2008.7M-2009.5E@JAXA/ESTEC

STMtest

ComponentDummy

Mercury orbit2019.8 ~ 2years

Now!!

RFP

AO

Overall Schedule (Mar 2006)

Is it OK? Install of STM 2008.8E Install of FM 2010.3B Env. Test 2010.7B-9E

“EM” & “Sub-system level reviews” can benegotiable each by each.

Is it OK? Install of STM 2008.8E Install of FM 2010.3B Env. Test 2010.7B-9E

“EM” & “Sub-system level reviews” can benegotiable each by each.

Page 3: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-3-

MMO: Payload AIVMMO-SWG #3 [March 2006] STM Schedule (Mar 2006)

Calender year1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Design and I/F Definition - -

MMO-PRR (2005 1-3B)BBM Manufacturing & Test - -

MMO-I-PDR (2007 9E) 9E

MMO-PDR (2007 11-12E) 12E

MDP: STM development & test ? ?

MPPE/MAST/WPT: STMmanufacturing & test

- - 4B 8E

MMO: STM IT/test @ ISAS 7M

MMO: STM IT/test @ ESTEC 5E

MCS: STM IT/test @ ESTEC 6B

MMO-I-CDR (2009 5-6E) 2E

MMO-CDR (2009 5-6E) 6E

reviewMMO: MIC/EIC (2010 3B-6B) 3B 6B

MCS: EM IT/test @ ESTEC 6B

MIC/EIC result review?Instrument Env Test (2010 7B-9E) 7B 9E

MMO-I-QR (2011 10B) 10B

MMO: AIV (2010 11B-2011 7E) 11B 7E

MMO-QR (2011 7-8E) 8E

2010 (H22) 2011 (H23)2006 (H18) 2007 (H19) 2008 (H20) 2009 (H21)

<Mile Stone> Payload STM: submission to System 2008 8EMPPE, MSASI (Hood only?), WPT-S, MEFISTO-S, MAST

Payload STM test should be done by 2008 Aug.

MMO-STM test in ISAS will be end in 2009 May.

Page 4: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-4-

MMO: Payload AIVMMO-SWG #3 [March 2006] EM Schedule (Mar 2006)

Calender year1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Design and I/F Definition - -

MMO-PRR (2005 1-3B)BBM Manufacturing & Test - -

MMO-I-PDR (2007 9E) 9E

MMO-PDR (2007 11-12E) 12E

Each: EM Manufacturing / Test(outside of MDP)

- 1B 8E

Each: EM Manufacturing / Test(inside of MDP)

10B 3E - -

MDP: EM IT/test 5B 9E -

MMO Payload: EM IT/test 10B-

12E

-

MMO-I-CDR (2009 5-6E) 2E

MMO-CDR (2009 5-6E) 6E

reviewMMO: MIC/EIC (2010 3B-6B) 3B 6B

MCS: EM IT/test @ ESTEC 6B

MIC/EIC result review?Instrument Env Test (2010 7B-9E)

7B 9E

MMO-I-QR (2011 10B) 10B

MMO: AIV (2010 11B-2011 7E) 11B 7E

MMO-QR (2011 7-8E) 8E

2010 (H22) 2011 (H23)2006 (H18) 2007 (H19) 2008 (H20) 2009 (H21)

<Mile Stone> Payload EM integration test schedule is TBD

PWI: from 2007 Oct. ??MGF: from 2008 Feb. ??Others: from 2008 May ??

Page 5: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-5-

MMO: Payload AIVMMO-SWG #3 [March 2006] Software Schedule (Mar 2006)

Calender year1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Design and I/F Definition - -

MMO-PRR (2005 1-3B)BBM Manufacturing & Test - -

MMO-I-PDR (2007 9E) 9E

MMO-PDR (2007 11-12E) 12E

MDP: CPU design 2B-3E

- -

MDP: Software design / Loadestimation

4B 3E

MDP: DPU test board 4B 9E

MDP: MDP Emulator H/Wdevelopment (& plimitive sensoremulator)

4B 9E

Each: Sensor Emulator develop 10B-

11EMDP: OS development 10B

-11E

MDP: Middleware development 4B 6E

MDP: Application Software test 4B 9E - -

MDP: Software IT test 10B-

12E

-

MMO-I-CDR (2009 5-6E) 2E

MMO-CDR (2009 5-6E) 6E

MMO-I-QR (2011 10B) 10B

MMO: AIV (2010 11B-2011 7E) 11B 7E

MMO-QR (2011 7-8E) 8E

2010 (H22) 2011 (H23)2006 (H18) 2007 (H19) 2008 (H20) 2009 (H21)

<Mile Stone> Software development does not have major milestones.Parts related to EM test will be synchronized to the System.

Page 6: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-6-

MMO: Payload AIVMMO-SWG #3 [March 2006] FM Schedule (Mar 2006)

Calender year1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Payload A/O (2004 4-11)

Design and I/F Definition - -

MMO-PRR (2005 1-3B)BBM Manufacturing & Test - -

MMO-I-PDR (2007 9E) 9E

MMO-PDR (2007 11-12E) 12E

MMO-I-CDR (2009 5-6E) 2E

MMO-CDR (2009 5-6E) 6E

Each: FM Manufacturing / Test(outside of MDP)

- - - - 4B 12E

Each: FM Manufacturing / Test(inside of MDP)

- - - - 4B 9E

MDP: IT/test @ MHI or ISAS 10B-

12EMMO Payload: FM IT/test @ISAS

1M-2M

reviewMMO: MIC/EIC (2010 3B-6B) 3B 6B

MCS: EM IT/test @ ESTEC 6B

MIC/EIC result review?Instrument Env Test (2010 7B-9E)

7B 9E

MMO-I-QR (2011 10B) 10B

MMO: AIV (2010 11B-2011 7E) 11B 7E

MMO-QR (2011 7-8E) 8E

2006 (H18) 2007 (H19) 2008 (H20) 2009 (H21) 2010 (H22) 2011 (H23)

<Mile Stone> Payload FM: submission to System 2010 MarchPayload FM: Environment test 2010 7B-9E

There might be no chance to remove payloads at ESTEC.

Page 7: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-7-

MMO: Payload AIVMMO-SWG #3 [March 2006]

5Days/ 1Week week1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 3W1

PSU,IPD,DPU installation Function Test

EWO,WPT- Pre, SC- Pre installation Function Test

MEFISTO- E, MEFISTO- Pre, AM2P installationSORBET installation Function Test

MGF- I (MGF- O) installation (?) Function Test

Reserved: Repair of each component

Function Test after repairs

MDP- 1,MDP- 2 Set upMDP- 1 Function TestMDP- 2 Function Test

* 4 hours each: for the change of configuration

EM Schedule for MDP (Mar 2006)

Integration test plan for MDP-2 (& MDP-1) with PWI & MGF

Details will be discussed in PWI local meeting in Kanazawa in this week.

~Plan: 13 weeks ~(FM: less)

MDP/Instrument tests by“Emulators with SpW” ?

MDP/Instrument tests by“Emulators with SpW” ?

Page 8: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-8-

MMO: Payload AIVMMO-SWG #3 [March 2006] Action Items in 2006FY

• Definition of the Schedule, Test location, and Responsibility/Members

• Definition of the procurement items from each teamto each team

• Definition of the test items in Component-level test in MDP-level test

in System-level test

• Definition of the Test environment in Component-level testin MDP-level testin System-level test

It will be defined as “MMO Payload Test Plan” (Draft version is in I-IRD etc.)

by JAXA/BepiColombo Project Office.

Please discuss in each team, and clarify your Action Items & Request to System / Other teams in CDD and/or Progress report.

Page 9: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-9-

MMO: Payload AIVMMO-SWG #3 [March 2006]

Sensor SpaceCube etc.

Signal Generator

Spacewire

PC

Ether etc.

GPIB etc.

EM/FM: Test Configuration Concept

System level test @ ISAS (/ ESTEC / Launch site)

Sensor MDP / MDP emulator

Signal Generator

Spacewire

PC

Ether etc.

GPIB etc.

MDP level test @ ISAS / MHI etc.

SpaceCube etc.

Spacewire

Sensor MDP > DMC

Signal Generator

Spacewire

PC

Ether etc.

GPIB etc.

TM/TCGround System

IEEE1553B?

(TLM only!)

Board/unit level test @ each institution

Page 10: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-10-

MMO: Payload AIVMMO-SWG #3 [March 2006]

SpaceCube: present status• SpaceWire Analyzer on SpaceCube

– Under development, Finished until October (distribution or purchase : after Oct. with soft)

– Analyzer will be distributed by MMO-project with SpaceCube

• GSE– Using SpaceCube with SpaceWire Analyzer– Middle ware (User I/F) will be define next year

SpaceWire Analyzer on SpaceCube

PC

RMAP packet content

001101110111

TLM COM Sensor with SpW I/F

SpW

RS232

RMAP HOST RMAP Target

Page 11: MMO: Payload AIV MMO-SWG #3 [March 2006] -1- C. Noshi/RASC, Kyoto Univ. MMO Mercury Magnetospheric Orbiter AIV (Assembly, Integration, Verification) for.

-11-

MMO: Payload AIVMMO-SWG #3 [March 2006]

Space-Cube (TBC) for GSE

• Mini-PC            with VGA, USB, Ether, CF-I/F

• SpW port  :  3 ports• OS  :  T-kernel (TRON)• Language  :  C (C++ ?)• Development  :  Cross-Compiler on Linux• SpW I/F  :  special API for SpW I/F prepared• SpW user program  :  Sample program that is to r

ead and wite SpW packet attached. If necessary, user can develop programs using APIs for SpW.