[Smwg] ESA Review of PIF

Barkley, Erik J (3970) erik.j.barkley at jpl.nasa.gov
Thu May 4 00:42:05 UTC 2017


A quick comment re #5.  For NASA, what are called Mars "overflights" are determined by calculating the logical equivalent of a PIF from the point of view of the in-situ asset (ie Rover).   So this comes closest to equating the rover to an aperture.  The Rise and Set are then calculated from the various communications relay assets/spacecraft (e.g., MRO, MEX, etc).

Best regards,

From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Colin.Haddow at esa.int
Sent: Wednesday, May 03, 2017 3:06 AM
To: CCSDS Service Mgmt WG (smwg at mailman.ccsds.org) <smwg at mailman.ccsds.org>
Subject: [Smwg] ESA Review of PIF

Dear all,
                  we've just completed the ESA review of the current draft of Planning Information Formats events and have identified the following points and questions.

  1.  It would be useful to add the OWLT as an optional parameter to all events

  1.  It would be useful to add the elevation angle as a mandatory parameter to the FwdComsStartEvent, RetComsStartEvent ,FwdComsEndEvent and RetComsEndEvent events (JP would this cause any problems with respect to TDRS ?)

  1.  KeyholeEvent should be split into 2, KeyholeStart and KeyholeEnd

  1.  Question; should OWLT or RTLT be used ?

  1.  Question: How should comms events be handled for Rovers, e.g. define the relay spacecraft (or Rover) as an aperture or define specific events for Rover visibility or any other ideas ?

Anyway these can be used as input to the PIF discussion in San Antonio.

Cheers for now,


Dr. Colin R. Haddow,
HSO-GI, European Space Agency,
European Space Operations Centre,
Robert-Bosch-Str 5,
64293 Darmstadt,

Phone; +49 6151 90 2896
Fax;      +49 6151 90 3010
E-Mail;  colin.haddow at esa.int<mailto:colin.haddow at esa.int>

This message and any attachments are intended for the use of the addressee or addressees only.

The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its

content is not permitted.

If you received this message in error, please notify the sender and delete it from your system.

Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20170504/f4152cd7/attachment.html>

More information about the SMWG mailing list