1 / 14

IES Operations

IES Operations. P. Mokashi IES Team Meeting, SwRI 29 May 2013. Uplink development during cruise. Uplink development for comet phase. Science & Operations Planning. Science Ground Segment System. Two main subsystems Observation Management Subsystem (OBM)

brandi
Download Presentation

IES Operations

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. IES Operations P. Mokashi IES Team Meeting, SwRI 29 May 2013

  2. Uplink development during cruise

  3. Uplink development for comet phase

  4. Science & Operations Planning

  5. Science Ground Segment System • Two main subsystems • Observation Management Subsystem (OBM) • Used to define instrument campaigns, observations and their associated planning, trajectory, attitude and resource characteristics and constraints • Science Planning and Scheduling Subsystem (SPS) • Automated scheduling and timeline generation based on definitions, constraints and priorities using JPL’s ASPEN system • Includes spacecraft dynamics and geometry models • Will generate activity timeline and instrument commanding

  6. SGS System • Features • Includes monitoring campaign capability • No ability to manually schedule observations • The only way to get them scheduled and at desired times is by changing the criteria (duration, frequency, geometric or other model based constraints, pointing) • Includes ride-along campaigns (or eventually will) • Status • Concept has undergone several changes • Very ambitious system and schedule • Present status of some components is uncertain

  7. Basic IES Operation • Would like to be on all the time (monitoring) in normal mode with some other RPC sensors • Burst mode • Would like periodic burst mode operations. All operating RPC sensors would like burst mode at the same time • Additional burst mode operations determined by trajectory and models, like boundary crossings • Data has to be collapsed significantly as bandwidth allocation for IES is very low, even in burst mode • Select the ranges and combine counts in adjacent energy/azimiuth/elevation bins

  8. Tables • IES Operation is driven by mode tables • Each table defines • Normal or burst mode • Cycle length (128s, 256s, 512s, 1024s) • Selection of energies for data return • Collapse (sum) of counts in adjacent • Energies • Elevations • Azimuths • 13 tables can be stored on board • Trade time resolution vs energy resolution vs angular resolution

  9. Macros • Internal sequences – programmable series of commands separated by delta times • Can call itself (loop) so a regular continuous sequence can be setup (example – cycle between 5 hours of normal mode and 1 hour burst mode OR cycle between high energy and angular resolution tables) • 8 macros stored on board of which 4 are available for customization • 1 being used for gain test

  10. Gain Tests • Gain Tests will be performed periodically to determine the nominal MCP operating voltages • How frequently? • Last gain test configuration: • ~17 min at each 2525V, 2550V, 2575V, 2600V and back to nominal voltage of 2500

  11. Post Hibernation Commissioning • March 31 & Apr 1, 2013 • Distance from earth 4.2 to 4.3 AU • OWLT: ~35 min • 18 hours total with Sun in FOV for most of the time • Science data expected near real time (with light time delay)

  12. Commissioning Plan

  13. Commissioning Plan

More Related