1 / 21

Instrument Control Unit

ICU TEAM R. Cosentino, E. Pace, M. Focardi, S. Pezzuto, M. Pancrazzi, A. M. Di Giorgio. Instrument Control Unit. Plato Kickoff meeting - Paris, 8 November 2010. Overview. MEUs (4 N-DPU). F-DPUs. MEU-PSU. F-AEU. AEUs. Routing Unit.

zed
Download Presentation

Instrument Control Unit

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICU TEAM R. Cosentino, E. Pace, M. Focardi, S. Pezzuto, M. Pancrazzi, A. M. Di Giorgio Instrument Control Unit

  2. Plato Kickoff meeting - Paris, 8 November 2010

  3. Overview MEUs (4 N-DPU) F-DPUs MEU-PSU F-AEU AEUs Routing Unit • 4 MEU (the 16 normal DPU are gathered in 4 group of 4 DPUs) • 2 Fast DPU • 4 Ancillary Electronic Unit • 1 Fast Ancillary Electronic Unit • 1 MEU-PSU • Each unit include 2 router (main and redundant) Processor Unit ICU Power Supply Unit Memory Unit SpW interface to SVM S/C SVM Plato Kickoff meeting - Paris, 8 November 2010

  4. ICU common requirements MEUs (4 N-DPU) F-DPUs • Handle the communications with service module (SVM) • Receive and process telecommands for the ICU: the received commands shall be validated prior to their execution • Format and transmit cyclic and sporadic HK telemetry (HKTM) • Format and trasmit the scientific payload telemetry packets (PLTM) • Manage the SpaceWire network • Receive the onboard time (Central Time Reference) from the S/C, handle the time stamping of the data transmitted in HKTM and forward the CTR to the DPUs. • Produce state and diagnosis information (cyclic status, progress event). • Schedule the DPU tasks (by the way of commands sent to the DPUs) • Manage the data flow • Manage the mode transitions • Manage the Software parameters • Manage the maintenance of the ICU software • Support the maintenance of the DPU software • Compress the data using a lossless compression algorithm. A compression factor of at least 2:0 is required. MEU-PSU F-AEU AEUs Routing Unit Processor Unit ICU Power Supply Unit Memory Unit SpW interface to SVM S/C SVM Plato Kickoff meeting - Paris, 8 November 2010

  5. Topics • Functional characteristics in observation mode • Functional characteristics in configuration mode • SpaceWire network management • SpaceWire network architecture • Data volume and TM budget • Power processing estimation • In-flight SW maintenance • Analog housekeeping acquisition and monitoring • Switch on/off capabilities and power sequences • Hardware architecture • Budgets • ICU Activities plan Plato Kickoff meeting - Paris, 8 November 2010

  6. Functional characteristics (observation mode) • receive the flux, the centroids and the imagettes (F-DPU: every 2.5 s ; N-DPU: every 25 s); • compress the imagettes: a compression factor between 2 and 3 is guaranteed; • detect outliers (flux and centroid) by comparing the data corresponding to the same star and coming from N-groups telescopes (N=8 or N=16 or N=32); • stack the valid flux and centroids; • compute the mean and the std dev of the stacked measurements at a cadence depending of the sample category (50 sec. or 600 sec): F-DPU: K ≤ 20; N-DPU: K ≤ 2 (50 s) or K ≤ 24 (600 s); • bufferize and compress photometric and centroid data: a factor of ~ 2 is guaranteed; • format and transmit to the SVM the scientific packets (PLTM). Plato Kickoff meeting - Paris, 8 November 2010

  7. Functional characteristics (configuration mode) • Send the configuration parameters to DPU (eg. stars catalogue) • Cross check between data from telescopes of the same LoS (verify the consistency of the list and positions of all the stars). • Schedule the DPU tasks • Compress full-frames images from DPUs • Packetization and trasmission of DPUs ancillary data to SVM • ‘Far field’ full images • Parameters for background estimation (eg window position) • Parameters for candidate and reference stars • List and position of reference stars • Distortion matrix • Selected parameters of all the targets (position, mask, …) • No storage of data (only temporary buffering) • periodically or loss of the Los Plato Kickoff meeting - Paris, 8 November 2010

  8. SpW network management • The active ICU is responsible for managing the SpaceWire network: ICU is a remote network manager. • The active ICU configures the routers (routing table, link speed, etc.): the logical addressing will be used (no path addressing). • The active ICU manages (configures / monitors/ controls) its own routers and the MEU routers. Plato Kickoff meeting - Paris, 8 November 2010

  9. MEU2 AEU2 FDPU1 FDPU2 FAEU MEU3 AEU3 MEU4 AEU4 MEU1 AEU1 MEU2 AEU2 FDPU1 FDPU2 FAEU MEU3 AEU3 MEU4 AEU4 MEU1 AEU1 Router-M1 Router-M2 Router-R1 Router-R2 Router-M3 Router-R3 Memory Unit Processor Unit ICU-PSU Processor Unit Memory Unit ICU-M ICU-R SpW network architecture MEU-PSU MEU-PSU • 12 SpW (4 MEU + 2 FDPU + 4 AEU + 1 FAEU +1 MEU-PSU) • 1 SpW link to access ICU internal Memory Unit • 1 SpW link to connect the processor unit in the main ICU • 1 SpW link to connect the processor unit in the redundant ICU • 1 SpW link to connect together the main Spw network to the redundant SpW network • 1 SpW link to connect each ICU Processor unit to the ICU-PSU • 2 independent SpW interface (main and redundant) connect each ICU Processor Unit to the S/C S/C (R1) S/C (M1) S/C (M2) S/C (R2)

  10. Data volume and TM budget • 32 normal telescopes + 2 fast telescope • 4 detectors each telescope (4510X4510 CCDs) • Data volume = 212 Gb/day (imagettes, photometric data, centroid data, raw images) • Presently the TM rate is 109 Gb/day • ICU shall compress data by a factor 2 at least ICU shall manage an input data-rate from N-DPU and F-DPU of about 12 Mbps and an output data-rate to the SVM of about 1.5 Mbps. These data rates can be easily managed by the standard SpW link, running up to 100 Mbps. Plato Kickoff meeting - Paris, 8 November 2010

  11. Power processing estimation • Cold redundancy (nominal ICU on, redundant unit off) • Few prototype algorithms written in C and run on a LEON3 emulating board at 40Mhz • CPU workload estimates at 75 and 100MHz assuming linearity • Extended-Rice lossless compression algorithm; QuickSelect method for median • Sigma clipping for outliers detection For processors operating at 100 MHz the occupation rate is ~ 49%

  12. In-flight SW maintenance As baseline ICU shall be in charge of the in-flight maintenance of the DPU application software (scientific SW) and its own SW (TBD). The DPU and ICU application software shall be reconfigurable during the flight, with the following possibilities: • It shall be possible to apply patches to the software (partial SW modification); • It shall be possible to upload a new version of the application software, entirely replacing the previous installed version. • Several versions of the application software could be stored on board The DPU application software shall be stored in EEPROM (Electrically-erasable programmable read-only memory). Two approaches can be followed: ICU shall store in a dedicated EEPROM the DPU application SW and shall transmit it to the DPUs during the boot or each DPU shall have its own EEPROM on board, to store the application SW

  13. Analog housekeeping acquisition and monitoring • ICU (ICU-PSU) is responsible for acquiring its own voltage and current consumption and it shall also collect and transmit the HK data from the other subsystems. • The ICU is responsible for collecting the voltage and current consumption of each N-DPU board and of the router units. These data shall be collected through the SpW network. • The ICU is responsible for collecting the voltage and current consumption of the Fast DPU, the 4 AEU and the single F-AEU. These data shall be collected through the SpW network. • The ICU is responsible for collecting the CCD and camera analog HK (temperatures and voltages) coming from the FEE. These analog HK shall be collected through the N-DPU SpW network.

  14. Switch on/off capabilities and power sequences The primary voltage switch on/off commands of the MEU-PSU, F-DPUs, and ICUs are controlled by the S/C (one dedicated switch line per box). The on/off switching operations of the ICU Processor Unit are directly commanded by the SVM S/Cthanks to a discrete command sent to the ICU-PSU (By default, only the ICU-M is switched on) The on/off switching operations of the ICU-M Memory Unit and ICU-M Router Unit are commandedby the ICU-M Processor Unit thanks to a SpaceWire command sent to the ICU-PSU. The ICU-R Memory Unit and the ICU-R Router Unit can be switched on/off by the active ICU

  15. Switch on/off capabilities and power sequences Through the SpW network, the ICU shall control: - The N-DPU boards and MEU routers switch on/off commands, performed by the MEU-PSU • The switch on/off commands of the N-FEE/F-FEE, performed by the N-AEU/F-AEU • The switch on/off of the ICU Memory Unit and of the ICU Router Unit • The F-DPU boards switch on/off commands

  16. Hardware architecture Constraint: • Storing large amount of data (to achieve a compression factor of 2) • Handle a large number of SpW links Proposed Hardware characteristics: • a routing unit for an efficient management of the SpW network and a wide internetworking capabilities, implementing two or three routers • a processor unit (i.e. a motherboard with power processing capabilities) • a memory unit for data storage and buffering with one or more SpW links to manage and configure them • a power supply unit with redundancy (TBC).

  17. Hardware architecture • Processor unit: • The LEON2 AT697F fulfils the computation power requirements • A customized module including a HW-implemented Rice compressor • Basic SW features providing bootstrap capability • Low level SW drivers • On board memory management • Application SW loading capability • Extended memory board: 48 (-> 64) Gb/ICU SDRAM/DDRRAM • UFM (Ultra Fast Memory) memory module by EADS Astrium or the DHSA data store system from Thales Alenia Space. • Memories shall be configured, read and written by means of the standard RMAP (Remote Memory Access Protocol) SpW compliant protocol. • Power Supply Unit: • based on DC/DC converters with current limiting protections. • The HK collection function is also hosted in this board (TBC) as for MEU’s power supply sub-unit. • Router Unit: 2 (or 3) SpW Router AT7910 (8 x SpW + 2 // ports)

  18. Budgets Power budget: The ICU (Main + Redundant) overall power budget including memory units and 20% contingency is 40 W maximum. Data Compression budget: The data compression ratio has been measured using a customized version of the Rice lossless compression algorithm. The compression ratio is ~1.9-2.0 for the light curves, ~3.0 for the centroid curves and ~2.5 for the imagettes. These compression ratios are compatible with the TM budget requirements. Mass budget: The ICU (Main + Redundant) overall mass budget including memory units and 20% contingency shall be about 7.8 Kg Dimension budget: The ICU (Main + Redundant) overall dimension budget shall be 220 X 250 X 240 mm3

  19. Maturity of technologies • µprocessor ref: LEON2-FT AT697E - 100MHz Space Rad-Hard IC from ATMEL (TBC), as baseline. • Heritages: High Flight heritage - Launchers - telecomm. & scientic satellites • Europe: SMART-1 lunar mission, Alcatel Spacebus satellite platforms, Galileo... • USA: Deep Impact, Mars Reconnaissance Orbiter... • SpW router components ref: the SpW Router board is based on the board developed for the Bepi Colombo Space Mission from THALES ALENIA SPACE, as baseline. The board shall be capable of routing all the data flows coming from the Normal and Fast DPUs and formatted according to the Packet Utilization Standards. Heritages: Bepi Colombo Space Mission. • Memory ref: DSHA Solid State Mass Memory Unit – SD SDRAM from THALES ALENIA SPACE (TBC), as baseline. Heritages from datasheet : Radarsat-2, Pamela, Cosmo (9 units in flight, 2 on launch pad) Prisma, BepiColombo, Sentinel-1 (6 units under MAIT). • Programmable Logics devices ref: ACTEL RTAX2000 FPGA (or equivalent) rad-hard device (Total Ionizing Dose capabilities up to 300 krad) for control and communication processes, as baseline. Heritages: COSMO-SkyMed, Mars Phoenix and many other missions. • Power Supply electronics ref: the ICU Power Supply and Voltage Regulators will be based on the long experience that THALES ALENIA SPACE has in the manufacturing of DC/DC converters and Power Supplies for satellites. Heritages: many Space Mission and satellites with TAS contributions. • All the other electronics minor-components of the ICU are available in a space or military qualification level with heritages from a large number of space missions. Concerning the technology aspects, we have for the ICU:ICU TRL ≥ 8

  20. ICU Activities plan • ICU development plan • By March 2011 • Breadboard of Critical Points • Foreseen as a critical point • For feasibility / performance verification • By March 2011 • ICU design documents • Detailed architecture of the ICU • Draft by January/February 2011 • Complete release by April 2011 • Delivery of Breadboard (BB) • Purpose: validation of the detailed design • November 2011

More Related