PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM DATA_SET_ID = "MEX-M-MRS-1/2/3-EXT2-2335-V1.0" STANDARD_DATA_PRODUCT_ID = ENB PRODUCER_ID = "SUE" PRODUCT_ID = "M00SUE0L1A_ENB_100410448_00.TXT" PRODUCT_CREATION_TIME = 2012-10-05T13:55:16.000 INSTRUMENT_HOST_ID = "MEX" OBJECT = TEXT PUBLICATION_DATE = 2011-03-10 NOTE = "MEX SUE Experimenter Notes" END_OBJECT = TEXT END From rsimpson Thu Feb 4 14:44:50 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o14Mio717070; Thu, 4 Feb 2010 14:44:50 -0800 (PST) Date: Thu, 4 Feb 2010 14:44:50 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002042244.o14Mio717070@magellan.stanford.edu> To: gene.goltz@jpl.nasa.gov Subject: Re: MEX RS Supports, Week of 02/08/10 Through 02/14/10 Cc: rsimpson Content-Length: 254 Status: RO >Problem: S-band off at BOT + 40m!? Let's hope it's just a problem with the DKF. Can you add Stefan.Remus@sciops.esa.int to your distribution for these messages? He may be our best hope for MEX corrective action these days. Thanks, Dick From rsimpson Thu Feb 4 14:59:12 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o14MxCb17091; Thu, 4 Feb 2010 14:59:12 -0800 (PST) Date: Thu, 4 Feb 2010 14:59:12 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002042259.o14MxCb17091@magellan.stanford.edu> To: Stefan.Remus@sciops.esa.int, gene.goltz@jpl.nasa.gov, rsimpson Subject: MEX BSR 2010/041 at DSS 14 Content-Length: 452 Status: RO Stefan: The DSN information (DSN Keyword File) indicates that S-Band is off at 06:39:38, about 40 minutes after beginning of track and about 49 minutes before BSR surface observations begin. There is no information about S-Band from then until the end of the pass. Is it possible for you to confirm whether we have S-Band for this experiment? The preliminary activities are at the end of orbit 7829, th4e BSR itself is in orbit 7830. Thanks, Dick From Stefan.Remus@sciops.esa.int Fri Feb 5 01:56:38 2010 Return-Path: Received: from esa-sf1.esa.gmessaging.net (esa-sf2.esa.gmessaging.net [194.51.201.68]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o159ube20693 for ; Fri, 5 Feb 2010 01:56:38 -0800 (PST) Received: from esa-sf1.esa.gmessaging.net (localhost [127.0.0.1]) by localhost.esa.gmessaging.net (Postfix) with SMTP id DA902395FBB; Fri, 5 Feb 2010 10:56:32 +0100 (CET) Received: from sciops-mailgw.vilspa.esa.int (sciops-mailgw.vilspa.esa.int [193.147.152.105]) by esa-sf1.esa.gmessaging.net (Postfix) with ESMTP id BE213395FB7; Fri, 5 Feb 2010 10:56:32 +0100 (CET) Received: from sciops.esac.int (scimail.esac.esa.int [193.147.152.87]) by sciops-mailgw.vilspa.esa.int (Postfix) with ESMTP id DAD0311F8F0; Fri, 5 Feb 2010 10:56:37 +0100 (CET) Received: from [10.66.180.42] (ssow01.net3.lan [10.66.180.42]) (authenticated bits=0) by sciops.esac.int (8.13.1/8.13.1) with ESMTP id o159ubUu025345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Feb 2010 10:56:37 +0100 Message-ID: <3839_1265363792_4B6BEB50_3839_45355_1_4B6BEB55.8040503@sciops.esa.int> Date: Fri, 05 Feb 2010 10:56:37 +0100 From: Stefan Remus User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Dick Simpson 650-723-3525 Cc: gene.goltz@jpl.nasa.gov Subject: Re: MEX BSR 2010/041 at DSS 14 References: <201002042259.o14MxCb17091@magellan.stanford.edu> In-Reply-To: <201002042259.o14MxCb17091@magellan.stanford.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Length: 1447 Status: RO Dick, you are right, by mistake the S-band is switched off 2 minutes after switch on. This is related to a software bug. At the moment they are trying to get the S-band back into the schedule but I have still no confirmation that it is in place again. I let you know. Stefan From rsimpson Mon Feb 8 15:00:44 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o18N0im17337; Mon, 8 Feb 2010 15:00:44 -0800 (PST) Date: Mon, 8 Feb 2010 15:00:44 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002082300.o18N0im17337@magellan.stanford.edu> To: Stefan.Remus@sciops.esa.int Subject: Re: MEX BSR 2010/041 at DSS 14 Cc: rsimpson Content-Length: 473 Status: RO >you are right, by mistake the S-band is switched off 2 minutes after >switch on. This is related to a software bug. > >At the moment they are trying to get the S-band back into the schedule >but I have still no confirmation that it is in place again. Thanks, Stefan. I have not seen this bug before. It does not matter if the DSN Keyword File is not updated; if the spacecraft commands can be modified to keep the S-Band turned on, we will collect the data. From Stefan.Remus@sciops.esa.int Tue Feb 9 04:12:58 2010 Return-Path: Received: from esa-sf1.esa.gmessaging.net (esa-sf3.esa.gmessaging.net [194.51.201.69]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o19CCvV19550 for ; Tue, 9 Feb 2010 04:12:58 -0800 (PST) Received: from esa-sf1.esa.gmessaging.net (localhost [127.0.0.1]) by localhost.esa.gmessaging.net (Postfix) with SMTP id 7E68024A23A for ; Tue, 9 Feb 2010 13:12:51 +0100 (CET) Received: from sciops-mailgw.vilspa.esa.int (sciops-mailgw.vilspa.esa.int [193.147.152.105]) by esa-sf1.esa.gmessaging.net (Postfix) with ESMTP id 64D4624A1EE for ; Tue, 9 Feb 2010 13:12:51 +0100 (CET) Received: from sciops.esac.int (scimail.esac.esa.int [193.147.152.87]) by sciops-mailgw.vilspa.esa.int (Postfix) with ESMTP id 529CB11FAC4 for ; Tue, 9 Feb 2010 13:12:57 +0100 (CET) Received: from [10.66.180.42] (ssow01.net3.lan [10.66.180.42]) (authenticated bits=0) by sciops.esac.int (8.13.1/8.13.1) with ESMTP id o19CCuXU002278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 9 Feb 2010 13:12:57 +0100 Message-ID: <30005_1265717571_4B715143_30005_121160_1_4B71514A.9050101@sciops.esa.int> Date: Tue, 09 Feb 2010 13:12:58 +0100 From: Stefan Remus User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Dick Simpson 650-723-3525 Subject: Re: MEX BSR 2010/041 at DSS 14 References: <201002082300.o18N0im17337@magellan.stanford.edu> In-Reply-To: <201002082300.o18N0im17337@magellan.stanford.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Length: 1377 Status: RO Dick I got the confirmation. The S-Band is back in the commanding. Many thanks for your information pointing on this issue. Lets cross the fingers for a good observation and data. Stefan From rsimpson Tue Feb 9 09:23:55 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o19HNtB20167; Tue, 9 Feb 2010 09:23:55 -0800 (PST) Date: Tue, 9 Feb 2010 09:23:55 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002091723.o19HNtB20167@magellan.stanford.edu> To: Stefan.Remus@sciops.esa.int Subject: Re: MEX BSR 2010/041 at DSS 14 Cc: daniel.s.kahan@jpl.nasa.gov, gene.goltz@jpl.nasa.gov, rsimpson, sami.asmar@jpl.nasa.gov Content-Length: 585 >Dick I got the confirmation. The S-Band is back in the commanding. >Many thanks for your information pointing on this issue. Gene Goltz gets the credit for spotting the problem in the DSN Keyword File. >Lets cross the fingers for a good observation and data. Agreed. I am traveling to JPL to monitor this experiment. It should be fairly simple, but it has been a long time since the last MEX BSR and there have been some problems, especially at S-Band. It will be good to have a signal source on S-Band so that we can check performance. Thanks, Stefan. Dick From jesse.velasco@dsn.nasa.gov Mon Feb 8 15:46:26 2010 Return-Path: Received: from DSNOAM-MM.jpl.nasa.gov (dsnoam-mm.jpl.nasa.gov [128.149.207.83]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o18NkPV17630 for ; Mon, 8 Feb 2010 15:46:25 -0800 (PST) Received: from dsnoamex1.jpl.nasa.gov (Not Verified[128.149.207.88]) by DSNOAM-MM.jpl.nasa.gov with MailMarshal (v6,4,6,5922) id ; Mon, 08 Feb 2010 15:46:54 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAA918.FE65F3C5" Subject: MEX BI-STATIC DSS-14 DOY 041 S-BAND MASER RED Date: Mon, 8 Feb 2010 15:46:53 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MEX BI-STATIC DSS-14 DOY 041 S-BAND MASER RED Thread-Index: AcqpGP3Ipt+VgTukSnyCa8IlOPDMog== From: "Velasco, Jesse" To: "Dick Simpson 650-723-3525" , , "Goltz, Gene L (332K)" , "Asmar, Sami W (332K)" Cc: "!DL-DSN-MPSETD" , "Kurtik, Susan C (9200)" , "Medeiros, Tony M" , "Landon, Arthur J" , "Massey, Kim" , "Bracamonte, Larry H" Content-Length: 7164 Status: RO This is a multi-part message in MIME format. ------_=_NextPart_001_01CAA918.FE65F3C5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dick, The station declared the S-band TWM (Traveling Wave Maser) RED and will not be available for the Bi-Static support on DOY 041 over DSS-14. The station will only be able to provide X-band RCP/LCP and S-band LCP. The station can configure the S-band HEMT to receive S-band RCP. Please let us know if you would like the station to remain in the standard configuration, or change the S-band HEMT configuration over to RCP.=20 041 0400 0600 0920 1020 DSS-14 MEX T/P BISTATIC R/S 0041 N71M 1A1 =20 NMC,RRPA,RRPB,RSR=3D2,STWM,TLPA,TLPB,XHMT; Thanks Jesse Jesse Velasco NOPE MEX/SELE/VEX/ROSE/CLUS (626) 305-6315=20 THE TECHNICAL DATA IN THIS DOCUMENT (OR FILE) IS CONTROLLED UNDER THE U.S. EXPORT REGULATIONS, AND MAY NOT BE RELEASED TO FOREIGN PERSONS WITHOUT A LICENSE AUTHORITY.=20 This document has been reviewed for export control and it does NOT contain export-controlled technical data. From rsimpson Tue Feb 9 11:13:35 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o19JDZU21171; Tue, 9 Feb 2010 11:13:35 -0800 (PST) Date: Tue, 9 Feb 2010 11:13:35 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002091913.o19JDZU21171@magellan.stanford.edu> To: jesse.velasco@dsn.nasa.gov Subject: Re: MEX BI-STATIC DSS-14 DOY 041 S-BAND MASER RED Cc: DL-DSN-MPSETD@dsn.nasa.gov, KMassey@gdscc.nasa.gov, LBracamonte@gdscc.nasa.gov, arthur.landon@dsn.nasa.gov, daniel.s.kahan@jpl.nasa.gov, gene.l.goltz@jpl.nasa.gov, rsimpson, sami.w.asmar@jpl.nasa.gov, susan.c.kurtik@jpl.nasa.gov, tony.medeiros@dsn.nasa.gov Content-Length: 640 Status: R >The station declared the S-band TWM (Traveling Wave Maser) RED and will >not be available for the Bi-Static support on DOY 041 over DSS-14. The >station will only be able to provide X-band RCP/LCP and S-band LCP. The >station can configure the S-band HEMT to receive S-band RCP. Please let >us know if you would like the station to remain in the standard >configuration, or change the S-band HEMT configuration over to RCP. Jesse: For this experiment, the geometry strongly favors S-LCP echoes. So we should leave the normal configuration in place and let the HEMT receive S-LCP. Sorry for slow response. Regards, Dick From jesse.velasco@dsn.nasa.gov Tue Feb 9 11:38:30 2010 Return-Path: Received: from DSNOAM-MM.jpl.nasa.gov (dsnoam-mm.jpl.nasa.gov [128.149.207.83]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o19JcPV21269 for ; Tue, 9 Feb 2010 11:38:25 -0800 (PST) Received: from dsnoamex1.jpl.nasa.gov (Not Verified[128.149.207.88]) by DSNOAM-MM.jpl.nasa.gov with MailMarshal (v6,4,6,5922) id ; Tue, 09 Feb 2010 11:38:53 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: MEX BI-STATIC DSS-14 DOY 041 S-BAND MASER RED Date: Tue, 9 Feb 2010 11:38:31 -0800 Message-ID: In-Reply-To: <201002091913.o19JDZU21171@magellan.stanford.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MEX BI-STATIC DSS-14 DOY 041 S-BAND MASER RED Thread-Index: AcqpvBpEd32KMxb8QTSRyA6BPJKKHQAAn3Uw References: <201002091913.o19JDZU21171@magellan.stanford.edu> From: "Velasco, Jesse" To: "Dick Simpson 650-723-3525" Cc: "!DL-DSN-MPSETD" , "Massey, Kim" , "Bracamonte, Larry H" , "Landon, Arthur J" , , , , , "Medeiros, Tony M" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by magellan.stanford.edu id o19JcPV21269 Content-Length: 1250 Status: R Dick, I will advise the station to configure for the Bi-Static support following the standard Bi-Static procedure that is documented in the NOP. Jesse From rsimpson Tue Feb 9 13:06:24 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o19L6N721501; Tue, 9 Feb 2010 13:06:23 -0800 (PST) Date: Tue, 9 Feb 2010 13:06:23 -0800 (PST) From: Dick Simpson 650-723-3525 Message-ID: <21500.1265749584@magellan> Mime-Version: 1.0 To: gene.goltz@jpl.nasa.gov, daniel.s.kahan@jpl.nasa.gov, rsimpson Subject: MEX BSR Time Line Content-Type: multipart/mixed; boundary="-" Content-Length: 45009 Status: R This is a MIME encoded message. Decode it with "munpack" or any other MIME reading software. Mpack/munpack is available via anonymous FTP in ftp.andrew.cmu.edu:pub/mpack/ --- Gene and Danny: Here is the time line for the MEX BSR on day 041 (local time 08 February 20:00 to 09 February 02:20) at DSS 14. Word from Stefan Remus is that S-Band is back in the spacecraft sequence; but now we have the S-RCP maser 'red' at DSS 14. So we will collect S-LCP (and check that the recurring problems in late 2009 have been fixed), but the S-Band science will be limited without both polarizations. The surface observations start at (32S, 54W) and end at (42S, 65W); this is lightly cratered terrain northwest of the large basin Argyre. The spacecraft has just passed apoapsis, so everything happens slowly and signals are relatively weak; but we have just passed Mars opposition, so the small Earth-Mars distance makes the weak signals stronger. Incident angle on the surface varies from 45 to 56 degrees, meaning LCP should be stronger than RCP throughout but with RCP making gains toward the end. I should arrive in Burbank at 6:05 PM. I'll plan to grab some dinner en route to JPL and get to the main gate a little before 8 PM. Thanks, Dick 2010/041 (UTC) - - - - - - - 04:00 Begin Pre-cal at DSS 14 FGAIN = 60 dB (all channels, including X-RCP) FRO_X = 0; FRO_S = 0 (all SCHAN) Start 4-channel 25 kHz recordings after Step 4 Stop 25 kHz recording after Step 18 06:00 Begin track (X-Band may be ON; the DKF is not clear) 06:37 S-Band ON 06:50 Resume 25 kHz recording 07:00 Advise DSS 14 of switch to planetary coordinates at 07:10 07:05 Begin SLEW #1 07:10 DSS 14 switch to planetary coordinates 07:11 FRO_X = +29600 Hz (SCHAN 3) FRO_S = +5000 Hz (SCHAN 3) 07:12 Begin MINICAL #1 07:27 End of MINICAL #1 (end of step 5) 07:29 End SLEW #1 Begin 100 kHz recording (SCHAN 4) 08:25 Advise station of MINICAL #2 starting at 08:32 and Advise station of return to S/C pointing predictions at 08:47 08:31 End 100 kHz recording (SCHAN 4) Begin SLEW #2 08:32 Begin MINICAL #2 08:47 End MINICAL #2 (end of step 5) DSS 14 return to spacecraft pointing predicts 08:48 FRO_X = 0 Hz (SCHAN 3) FRO_S = 0 Hz (SCHAN 3) 08:50 End SLEW #2 09:06 X-Band telemetry ON 09:07 Early end of track (scheduled EOT 09:20) Go to zenith Begin post-cal when ready 10:20 End post-cal (or earlier, if post-cal complete) End 25 kHz recordings End of Activity --- Content-Type: application/octet-stream; name="TL_10041.doc" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="TL_10041.doc" Content-MD5: JYPaaBcD+Geip3mn39PxYQ== 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAOAAAAAAA AAAAEAAAOgAAAAEAAAD+////AAAAADcAAAD///////////////////////////////////// ... From daniel.s.kahan@jpl.nasa.gov Thu Feb 11 10:43:13 2010 Return-Path: Received: from mail.jpl.nasa.gov (mailhost.jpl.nasa.gov [128.149.139.105]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1BIhDj05835 for ; Thu, 11 Feb 2010 10:43:13 -0800 (PST) Received: from mail.jpl.nasa.gov (altvirehtstap01.jpl.nasa.gov [128.149.137.72]) by smtp.jpl.nasa.gov (Switch-3.4.2/Switch-3.4.1) with ESMTP id o1BIhB88006247 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified FAIL) for ; Thu, 11 Feb 2010 10:43:12 -0800 Received: from ALTPHYEMBEVSP30.RES.AD.JPL ([172.16.0.31]) by ALTVIREHTSTAP01.RES.AD.JPL ([128.149.137.72]) with mapi; Thu, 11 Feb 2010 10:43:11 -0800 Content-Type: multipart/mixed; boundary="_000_79D001DEDB0DEC47A247B110F3E86682072E61D13BALTPHYEMBEVSP_" From: "Kahan, Daniel S (332K)" To: "Simpson, Richard A (6520-Affiliate)" CC: "Martin.Paetzold@uni-koeln.de" , "Matthias.Hahn@uni-koeln.de" , "Silvia.Tellmann@uni-koeln.de" , "Thomas.Kuerten@uni-koeln.de" , "Asmar, Sami W (332K)" , "Goltz, Gene L (332K)" Date: Thu, 11 Feb 2010 10:43:10 -0800 Subject: MEX 2010-041 Bistatic Radar Data Thread-Topic: MEX 2010-041 Bistatic Radar Data Thread-Index: AcnBvc7pAV3j4C4FQRakmyn/J88GbQFv/gNwDF1L9rAAM8xNIAEn3t0gAAqqr7ACtgxCEAV/quiAAWBL5LAEIK+LAAAFPJnAAMOES+AHe4q6QBUycIVw Message-ID: <79D001DEDB0DEC47A247B110F3E86682072E61D13B@ALTPHYEMBEVSP30.RES.AD.JPL> References: <6.2.5.6.2.20090420054251.01e63e68@jpl.nasa.gov> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <79D001DEDB0DEC47A247B110F3E86682072E61D13B@ALTPHYEMBEVSP30.RES.AD.JPL> acceptlanguage: en-US MIME-Version: 1.0 X-Source-IP: altvirehtstap01.jpl.nasa.gov [128.149.137.72] X-Source-Sender: daniel.s.kahan@jpl.nasa.gov X-AUTH: Authorized Content-Length: 16851 Status: RO --_000_79D001DEDB0DEC47A247B110F3E86682072E61D13BALTPHYEMBEVSP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dick, A MEX Bistatic Radar Experiment on DOY 2010-041 was conducted at DSS-14. RSR open-loop data were recorded and played back to your MEX directory on r= sops2 as follows: - X-band RCP, 1-way - RSR2B3 - 25 kHz, 16 bits - 04:48:00 - 06:08:00 - 06:50:00 - 07:29:00 - 07:29:00 - 08:31:00 - 08:31:00 - 10:00:00 and: - S-band LCP, 1-way - RSR2A3 - 25 kHz, 16 bits - 04:48:00 - 06:08:00 - 06:50:00 - 07:29:00 - 07:29:00 - 08:31:00 - 08:31:00 - 10:00:00 and: - X-band LCP, 1-way - RSR3B3 - 25 kHz, 16 bits - 04:48:00 - 06:08:00 - 06:50:00 - 07:29:00 - 07:29:00 - 08:31:00 - 08:31:00 - 10:00:00 and: - S-band LCP, 1-way - RSR3A3 - 25 kHz, 16 bits - 04:48:00 - 06:08:00 - 06:50:00 - 07:29:00 - 07:29:00 - 08:31:00 - 08:31:00 - 10:00:00 plus: - X-band RCP, 1-way - RSR2B4 - 100 kHz, 16 bits - 07:29:00 - 08:31:00 and: - S-band LCP, 1-way - RSR2A4 - 100 kHz, 16 bits - 07:29:00 - 08:31:00 and: - X-band LCP, 1-way - RSR3B4 - 100 kHz, 16 bits - 07:29:00 - 08:31:00 and: - S-band LCP, 1-way - RSR3A4 - 100 kHz, 16 bits - 07:29:00 - 08:31:00 - Regards, Gene & Danny From gene.goltz@jpl.nasa.gov Wed Feb 10 02:21:03 2010 Return-Path: Received: from mail.jpl.nasa.gov (mailhost.jpl.nasa.gov [128.149.139.106]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1AAL2j01814 for ; Wed, 10 Feb 2010 02:21:02 -0800 (PST) Received: from ggoltz-xp.jpl.nasa.gov (ggoltz-2k.jpl.nasa.gov [137.78.78.47]) by smtp.jpl.nasa.gov (Switch-3.4.2/Switch-3.4.1) with ESMTP id o1AAL1lJ032706 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256 bits) verified NO); Wed, 10 Feb 2010 02:21:02 -0800 Message-Id: <6.2.5.6.2.20100210005241.02069478@jpl.nasa.gov> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Wed, 10 Feb 2010 02:10:17 -0800 To: Dick Simpson 650-723-3525 From: Gene Goltz Subject: MEX 2010-041 BSR Ops Log Cc: Sami Asmar , Daniel.S.Kahan@jpl.nasa.gov Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_1552685718==_" X-Source-IP: ggoltz-2k.jpl.nasa.gov [137.78.78.47] X-Source-Sender: gene.goltz@jpl.nasa.gov X-AUTH: Authorized Content-Length: 65846 Status: RO --=====================_1552685718==_ Content-Type: text/plain; charset="us-ascii"; format=flowed Dick, Attached please find the operations log for the MEX Bistatic Radar (BSR) experiment that was conducted at DSS-14, on 09 February (DOY 041). Very strong X-band (but weaker S-band) echoes were returned for this experiment. The S-band maser was declared "red" prior to the activity, so there was no S-band RCP data recorded; and S-band LCP ADC Amplitude continued to be irratic while the antenna was on point. - Gene & Danny --=====================_1552685718==_ Content-Type: application/octet-stream; name="MEX_BSR_20100210.xls"; x-mac-type="584C5334"; x-mac-creator="5843454C" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="MEX_BSR_20100210.xls" 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAAQAAAAAAAAAA EAAANQAAAAEAAAD+////AAAAAAAAAAD///////////////////////////////////////////// ... From wilson.chen@dsn.nasa.gov Wed Feb 10 08:03:16 2010 Return-Path: Received: from DSNOAM-MM.jpl.nasa.gov (dsnoam-mm.jpl.nasa.gov [128.149.207.83]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1AG3Fj02468 for ; Wed, 10 Feb 2010 08:03:15 -0800 (PST) Received: from dsnoamex1.jpl.nasa.gov (Not Verified[128.149.207.88]) by DSNOAM-MM.jpl.nasa.gov with MailMarshal (v6,4,6,5922) id ; Wed, 10 Feb 2010 08:03:41 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: 41 RMDC Radio Science Delivery Date: Wed, 10 Feb 2010 08:02:47 -0800 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 41 RMDC Radio Science Delivery Thread-Index: AcllM/P59jX5dCARTBGBh1JbY/bt8AABKBnQHmuFPCAy4ObskA== References: <200812231923.mBNJNVk10552@magellan.stanford.edu> From: "Chen, Wilson C" To: "Dick Simpson 650-723-3525" Cc: "!DL-DSN-RMDC" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by magellan.stanford.edu id o1AG3Fj02468 Content-Length: 284 Status: RO The listed files have been processed and delivered to: OSCARX://ftp/ras/sc41/odfs/10041O041_14X_1s.SC041 OSCARX://ftp/ras/sc41/odfs/10041O041_14S_1s.SC041 Regards, Wilson Chen RMDC Analyst Phone: 626-305-6269 Email: wcchen@jftl.jpl.nasa.gov wilson.chen@dsn.nasa.gov From rsimpson Thu Feb 11 12:49:20 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o1BKnKJ06913; Thu, 11 Feb 2010 12:49:20 -0800 (PST) Date: Thu, 11 Feb 2010 12:49:20 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002112049.o1BKnKJ06913@magellan.stanford.edu> To: daniel.s.kahan@jpl.nasa.gov Subject: RE: 2010/042 NMC Cc: rsimpson Content-Length: 1050 >Hope you got through the "morning" ok. The local park turns out to be sunrise-to-sunset. Angeles Crest was closed Big Tujunga Canyon was closed By the time I finished exploring, I was halfway to Bakersfile, it was 04:20 and time to head for the airport. Refueled the car, found someone to check it in, passed security, then waited at the gate while BUR and Southwest personnel activated the de-icing equipment. We were about 30 minutes late boarding and getting off the ground, but flying over the snow-covered green peaks of the coast range was sort of pleasant. There were a couple times when I nodded off, but I didn't really crash until 11 AM when I crawled into bed. Not much enthusiasm for going to Stanford later, so did a little work at home, cooked dinner, and went to bed early. Today seems almost normal except that I'm a little confused about which day this really is -- normal for all-nighter recovery. I'll probably get thrown off again by the Monday holiday. From rsimpson Thu Feb 11 13:32:54 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o1BLWsN07088; Thu, 11 Feb 2010 13:32:54 -0800 (PST) Date: Thu, 11 Feb 2010 13:32:54 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002112132.o1BLWsN07088@magellan.stanford.edu> To: Daniel.S.Kahan@jpl.nasa.gov, Stefan.Remus@sciops.esa.int, gene.goltz@jpl.nasa.gov, rsimpson Subject: MEX BSR with TLM Content-Length: 2153 Status: R Stefan: There frequently are periods of telemetry either before or after MEX bistatic radar experiments. The position of the DSN has been that BSR is complicated enough that no other activities should be scheduled during BSR passes. There have been instances recently when I told the Radio Science systems Group that they could allow the station to pick up the telemetry if it didn't impact the BSR -- especially if the telemetry came after the BSR. There has been at least one instance, however, where the station personnel changed the signal path in order to collect the telemetry, it was not changed back, and the BSR was affected. During the recent experiment on 2010/041, MEX MOC ordered DSS 14 to pick up telemetry just a few minutes before the BSR was to begin. I was at JPL and we objected; fortunately MEX MOC agreed shortly after and there were no telemetry problems. Gene Goltz notes that the new DSN keyword file for the week beginning 2010/046 shows a BSR on day 051 (05:05 - 12:10) with telemtry scheduled for 07:50:33 - 08:29:24 and 10:54:45 - 11:50:00. These are longer telemetry sessions and will probably be ignored by the DSN. In fact, the normal procedure has been to end the BSR track early and begin the ground post-cal after the HGA slew back to Earth and the post-experiment BCAL. So DSS 14 will probably not even be following the spacecraft during the second telemetry session. It might be wise to alert the people doing the MEX planning that these telemetry sessions will not usually be captured. If they want to use them for less important transmissions, there will be no harm. But they should not expect the data to be collected unless we can work out a new procedure with the DSN which protects the BSR configuration while the telemetry data are being collected. I think a new procedure is possible; but I don't know whether the DSN has personnel and time available to work out the changes. The BSR procedure has been embedded in the MEX Network Operations Plan, which makes changes more difficult but overall performance more uniform. Let me know if we should do anything on the DSN side. Thanks, Dick From Stefan.Remus@sciops.esa.int Fri Feb 12 01:13:54 2010 Return-Path: Received: from esa-sf1.esa.gmessaging.net (esa-sf3.esa.gmessaging.net [194.51.201.69]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1C9Drj21574 for ; Fri, 12 Feb 2010 01:13:54 -0800 (PST) Received: from esa-sf1.esa.gmessaging.net (localhost [127.0.0.1]) by localhost.esa.gmessaging.net (Postfix) with SMTP id 104A6300E3 for ; Fri, 12 Feb 2010 10:13:49 +0100 (CET) Received: from sciops-mailgw.vilspa.esa.int (sciops-mailgw.vilspa.esa.int [193.147.152.105]) by esa-sf1.esa.gmessaging.net (Postfix) with ESMTP id BE0AF300E1; Fri, 12 Feb 2010 10:13:48 +0100 (CET) Received: from sciops.esac.int (scimail.esac.esa.int [193.147.152.87]) by sciops-mailgw.vilspa.esa.int (Postfix) with ESMTP id 51DAE11FADA; Fri, 12 Feb 2010 10:13:53 +0100 (CET) Received: from [10.66.180.42] (ssow01.net3.lan [10.66.180.42]) (authenticated bits=0) by sciops.esac.int (8.13.1/8.13.1) with ESMTP id o1C9Dqtw022617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Feb 2010 10:13:52 +0100 Message-ID: <30005_1265966029_4B751BCC_30005_186566_1_4B751BD4.7020104@sciops.esa.int> Date: Fri, 12 Feb 2010 10:13:56 +0100 From: Stefan Remus User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Hannes.Griebel@esa.int, erhard.rabenau@esa.int Cc: MEXMPS , Dick Simpson Subject: Fwd: MEX BSR with TLM Content-Type: multipart/alternative; boundary="------------090503090101070008050405" Content-Length: 8388 Status: RO This is a multi-part message in MIME format. --------------090503090101070008050405 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello Hannes & Ruben, please look at the email Dick has sent explaining the normal configuration and the actual situation for BSR observations. The telemetry dump time scheduled around BSR observations has an impact on DSN side and a telemetry data loss is likely. In any case please let DSN know your further proceeding. Best regards, Stefan From Olivier.Reboud@esa.int Fri Feb 12 02:22:36 2010 Return-Path: Received: from esacom90-int.esrin.esa.int (esacom90-ext.esrin.esa.int [192.171.5.18]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1CAMZj21785 for ; Fri, 12 Feb 2010 02:22:35 -0800 (PST) Received: from esacom66.esrin.esa.int (192-171-5-30.esrin.esa.int [192.171.5.30]) by esacom90-int.esrin.esa.int (8.13.3/8.13.3/ESA-External-v4.0) with ESMTP id o1CAMZTl007579 for ; Fri, 12 Feb 2010 10:22:35 GMT Received: from esrinmta1.esrin.esa.int (esrinnotesadmin-a.esrin.esa.int [193.204.225.153]) by esacom66.esrin.esa.int (8.12.10/8.12.10/ESA-Internal-v3.2) with ESMTP id o1CAMYEg022553 for ; Fri, 12 Feb 2010 10:22:35 GMT In-Reply-To: To: Subject: Re: Fw: MEX BSR with TLM MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005 Message-ID: From: Olivier.Reboud@esa.int Date: Fri, 12 Feb 2010 11:22:32 +0100 X-MIMETrack: Serialize by Router on esrinmta1/esrin/ESA at 02/12/2010 11:22:34, Serialize complete at 02/12/2010 11:22:34 Content-Type: multipart/alternative; boundary="=_alternative 0038FE98C12576C8_=" Content-Length: 9459 Status: RO This is a multipart message in MIME format. --=_alternative 0038FE98C12576C8_= Content-Type: text/plain; charset="US-ASCII" Dear Dick, Thanks for your information, When there is this kind of important feed-back from your RS team, please put me, Michel.Denis@esa.int and James.Godfrey@esa.int in copy of your emails related to BSRs. (James Godfrey has replaced Peter Schmitz and is the MEX deputy SOM (S/C Ops manager), deputy of Michel Denis who remains the MEX SOM) Kind regards, Olivier, Mars-Express TT&C From Hannes.Griebel@esa.int Fri Feb 12 02:26:49 2010 Return-Path: Received: from esacom90-int.esrin.esa.int (esacom90-ext.esrin.esa.int [192.171.5.18]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1CAQnj21790 for ; Fri, 12 Feb 2010 02:26:49 -0800 (PST) Received: from esacom66.esrin.esa.int (192-171-5-30.esrin.esa.int [192.171.5.30]) by esacom90-int.esrin.esa.int (8.13.3/8.13.3/ESA-External-v4.0) with ESMTP id o1CAQnMC007903 for ; Fri, 12 Feb 2010 10:26:49 GMT Received: from esrinmta1.esrin.esa.int (esrinnotesadmin-a.esrin.esa.int [193.204.225.153]) by esacom66.esrin.esa.int (8.12.10/8.12.10/ESA-Internal-v3.2) with ESMTP id o1CAQnEg022830; Fri, 12 Feb 2010 10:26:49 GMT In-Reply-To: <4B751BD4.7020104@sciops.esa.int> To: Stefan Remus Cc: erhard.rabenau@esa.int, MEXMPS , Dick Simpson , Michel.Denis@esa.int Subject: Re: Fwd: MEX BSR with TLM MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005 Message-ID: From: Hannes.Griebel@esa.int Date: Fri, 12 Feb 2010 11:26:48 +0100 X-MIMETrack: Serialize by Router on esrinmta1/esrin/ESA at 02/12/2010 11:26:48, Serialize complete at 02/12/2010 11:26:48 Content-Type: multipart/alternative; boundary="=_alternative 003962A6C12576C8_=" Content-Length: 11450 Status: RO This is a multipart message in MIME format. --=_alternative 003962A6C12576C8_= Content-Type: text/plain; charset="US-ASCII" Dear Stefan and Dick, Whenever we switch on the TX, we automatically produce telemetry. This is the standard safe configuration. Only after that do we command the TX to switch to Radio Science mode with modulation OFF. The safe end state for the system is a configuration back to nominal modulation ON. There is virtually nothing I can do except for manually commanding shut down and start up with modulation OFF. I will manually make these settings for the TX OFF while in eclipse during Phobos fly by operations. That way we get a clean RS experiment without draining power during the eclipse. But it must be clear that this manual tampering with commanding and overriding safety settings comes with a lot of careful manual planning and modifications on my part and cross and triple checking by other team members to make sure we have a safe spacecraft at all times. While fine for the once in a lifetime Phobos visit, this procedure is impossible to implement on a routine basis. I would therefore suggest to set up the station for BSR and ignore the fact that the signal is modulated before and after the experiment. We are not dumping any data, so we won't loose anything. Let me know if this is acceptable for you. If you absolutely need an unmodulated signal, I suggest extending the BSR experiment time. Let's discuss this at the RS meeting here at ESOC on the 23rd. Best regards, Hannes. From rsimpson Fri Feb 12 11:31:51 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o1CJVpX22588; Fri, 12 Feb 2010 11:31:51 -0800 (PST) Date: Fri, 12 Feb 2010 11:31:51 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002121931.o1CJVpX22588@magellan.stanford.edu> To: Hannes.Griebel@esa.int Subject: Re: Fwd: MEX BSR with TLM Cc: Michel.Denis@esa.int, Stefan.Remus@sciops.esa.int, erhard.rabenau@esa.int, mexmps@esa.int, rsimpson Content-Length: 616 Status: RO >I would therefore suggest to set up the station for BSR and ignore the >fact that the signal is modulated before and after the experiment. We are >not dumping any data, so we won't loose anything. This is perfect. I have seen more telemetry sessions appearing in DSN Keyword Files and was worried that MEX was attempting to make use of the sometimes long waiting periods before and after BSR. If this is a normal configuration associated with safe mode recovery, don't even worry about manually suppressing telemetry. We can easily work around it (by ignoring the telemetry). Thanks, Dick From rsimpson Fri Feb 12 11:54:17 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o1CJsHc22655; Fri, 12 Feb 2010 11:54:17 -0800 (PST) Date: Fri, 12 Feb 2010 11:54:17 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002121954.o1CJsHc22655@magellan.stanford.edu> To: Olivier.Reboud@esa.int Subject: Re: Fw: MEX BSR with TLM Cc: James.Godfrey@esa.int, Michel.Denis@esa.int, rsimpson, stefan.remus@sciops.esa.int Content-Length: 1605 Status: R >When there is this kind of important feed-back from your RS team, please >put me, Michel.Denis@esa.int and James.Godfrey@esa.int in copy of your >emails related to BSRs. Olivier: I will plan to do that in the future. I have a report on strange carrier level modulations on the MEX X-Band signal during the 2010/041 bistatic radar experiment, which I will send later today. Do not be distracted by the section on DSN system temperatures, which is good news. The carrier modulation appears as 5 dB decreases in signal level every 85 seconds in X-RCP and as INCREASE in signal level in X-LCP. It is very hard for me to understand how this could happen. One possibility is that the HGA pointing is oscillating about the nominal boresight direction; but the oscillation would need to be almost +/- 1 degree to cause this much change in the X-Band signal levels. Unfortunately, we were not able to collect S-RCP to see whether comparable fluctuations (about 0.6 dB) were occurring there. And I don't see X-LCP increases when we started and ended the BSR slew -- although I think I have seen them during other BSR experiments. The good news is that the modulation should not affect the science. We derive the surface material properties from the ratio of X-RCP to X-LCP echo powers. Since both are modulated in the same way (by the S-RCP which illuminates the surface), the ratio calculations should not be affected, except for a slight increase in the noise of the measurements. Thank you for your continuing assistance, Dick From Stefan.Remus@sciops.esa.int Fri Feb 12 07:23:21 2010 Return-Path: Received: from esa-sf1.esa.gmessaging.net (esa-sf2.esa.gmessaging.net [194.51.201.68]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1CFNJj22156 for ; Fri, 12 Feb 2010 07:23:20 -0800 (PST) Received: from esa-sf1.esa.gmessaging.net (localhost [127.0.0.1]) by localhost.esa.gmessaging.net (Postfix) with SMTP id 3284240C029 for ; Fri, 12 Feb 2010 16:23:11 +0100 (CET) Received: from sciops-mailgw.vilspa.esa.int (sciops-mailgw.vilspa.esa.int [193.147.152.105]) by esa-sf1.esa.gmessaging.net (Postfix) with ESMTP id E32E540C022 for ; Fri, 12 Feb 2010 16:23:10 +0100 (CET) Received: from sciops.esac.int (scimail.esac.esa.int [193.147.152.87]) by sciops-mailgw.vilspa.esa.int (Postfix) with ESMTP id C1FD511FACB for ; Fri, 12 Feb 2010 16:23:18 +0100 (CET) Received: from [10.66.180.42] (ssow01.net3.lan [10.66.180.42]) (authenticated bits=0) by sciops.esac.int (8.13.1/8.13.1) with ESMTP id o1CFNIEl018328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 12 Feb 2010 16:23:18 +0100 Message-ID: <3839_1265988191_4B75725F_3839_188587_1_4B757269.1070808@sciops.esa.int> Date: Fri, 12 Feb 2010 16:23:21 +0100 From: Stefan Remus User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Dick Simpson Subject: Fwd: Re: Fwd: MEX BSR with TLM Content-Type: multipart/alternative; boundary="------------090200070807020907060607" Content-Length: 17368 Status: RO This is a multi-part message in MIME format. --------------090200070807020907060607 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello Dick, do you need additional information? Martin, Silvia and I will meet the MOC people at ESOC on the 23rd Feb. 2010. We are invited to give Science feedback and to discuss possible improvements in the planning. In case you have some information about your analysis or plannings we shall present please let Martin know. Anyhow it will be good to have something about BSRs in the presentation as well. Best regards, Stefan -------- Original Message -------- Subject: Re: Fwd: MEX BSR with TLM Date: Fri, 12 Feb 2010 11:26:48 +0100 From: Hannes.Griebel@esa.int To: Stefan Remus CC: erhard.rabenau@esa.int, MEXMPS , Dick Simpson , Michel.Denis@esa.int Dear Stefan and Dick, Whenever we switch on the TX, we automatically produce telemetry. This is the standard safe configuration. Only after that do we command the TX to switch to Radio Science mode with modulation OFF. The safe end state for the system is a configuration back to nominal modulation ON. There is virtually nothing I can do except for manually commanding shut down and start up with modulation OFF. I will manually make these settings for the TX OFF while in eclipse during Phobos fly by operations. That way we get a clean RS experiment without draining power during the eclipse. But it must be clear that this manual tampering with commanding and overriding safety settings comes with a lot of careful manual planning and modifications on my part and cross and triple checking by other team members to make sure we have a safe spacecraft at all times. While fine for the once in a lifetime Phobos visit, this procedure is impossible to implement on a routine basis. I would therefore suggest to set up the station for BSR and ignore the fact that the signal is modulated before and after the experiment. We are not dumping any data, so we won't loose anything. Let me know if this is acceptable for you. If you absolutely need an unmodulated signal, I suggest extending the BSR experiment time. Let's discuss this at the RS meeting here at ESOC on the 23rd. Best regards, Hannes. *Stefan Remus * 12/02/2010 10:13 To Hannes.Griebel@esa.int, erhard.rabenau@esa.int cc MEXMPS , Dick Simpson Subject Fwd: MEX BSR with TLM Hello Hannes & Ruben, please look at the email Dick has sent explaining the normal configuration and the actual situation for BSR observations. The telemetry dump time scheduled around BSR observations has an impact on DSN side and a telemetry data loss is likely. In any case please let DSN know your further proceeding. Best regards, Stefan -------- Original Message -------- *Subject: * MEX BSR with TLM *Date: * Thu, 11 Feb 2010 13:32:54 -0800 (PST) *From: * Dick Simpson 650-723-3525 __ *To: * _Daniel.S.Kahan@jpl.nasa.gov_ , _Stefan.Remus@sciops.esa.int_ , _gene.goltz@jpl.nasa.gov_ , _rsimpson@magellan.stanford.edu_ Stefan: There frequently are periods of telemetry either before or after MEX bistatic radar experiments. The position of the DSN has been that BSR is complicated enough that no other activities should be scheduled during BSR passes. There have been instances recently when I told the Radio Science systems Group that they could allow the station to pick up the telemetry if it didn't impact the BSR -- especially if the telemetry came after the BSR. There has been at least one instance, however, where the station personnel changed the signal path in order to collect the telemetry, it was not changed back, and the BSR was affected. During the recent experiment on 2010/041, MEX MOC ordered DSS 14 to pick up telemetry just a few minutes before the BSR was to begin. I was at JPL and we objected; fortunately MEX MOC agreed shortly after and there were no telemetry problems. Gene Goltz notes that the new DSN keyword file for the week beginning 2010/046 shows a BSR on day 051 (05:05 - 12:10) with telemtry scheduled for 07:50:33 - 08:29:24 and 10:54:45 - 11:50:00. These are longer telemetry sessions and will probably be ignored by the DSN. In fact, the normal procedure has been to end the BSR track early and begin the ground post-cal after the HGA slew back to Earth and the post-experiment BCAL. So DSS 14 will probably not even be following the spacecraft during the second telemetry session. It might be wise to alert the people doing the MEX planning that these telemetry sessions will not usually be captured. If they want to use them for less important transmissions, there will be no harm. But they should not expect the data to be collected unless we can work out a new procedure with the DSN which protects the BSR configuration while the telemetry data are being collected. I think a new procedure is possible; but I don't know whether the DSN has personnel and time available to work out the changes. The BSR procedure has been embedded in the MEX Network Operations Plan, which makes changes more difficult but overall performance more uniform. Let me know if we should do anything on the DSN side. Thanks, Dick From rsimpson Fri Feb 12 12:14:29 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o1CKETl22901; Fri, 12 Feb 2010 12:14:29 -0800 (PST) Date: Fri, 12 Feb 2010 12:14:29 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002122014.o1CKETl22901@magellan.stanford.edu> To: Stefan.Remus@sciops.esa.int Subject: Re: Fwd: Re: Fwd: MEX BSR with TLM Cc: rsimpson Content-Length: 1936 Status: R >do you need additional information? No, Hannes answered very completely. My only suggestion would be that we remind the operations people that telemetry is not collected during BSR at DSN stations. >Martin, Silvia and I will meet the MOC people at ESOC on the 23rd Feb. >2010. We are invited to give Science feedback and to discuss possible >improvements in the planning. In case you have some information about >your analysis or plannings we shall present please let Martin know. I will distribute a report later today based on quick-look analysis of the latest BSR data. There is a very strange modulation on the X-RCP carrier level. It causes a reduction of the carrier power by up to 5 dB every 85 seconds (the period is very consistent). The unusual aspect of the modulation is that the measured X-LCP power on the ground INCREASES by several dB at the same time as the X-RCP is decreasing. The best explanation I have today is that the HGA pointing is oscillating about the nominal boresight by almost +/- 1 degree. This seems large, but it might explain why the RCP goes down and the LCP goes up. Sometimes we see the LCP go up briefly when the HGA begins or ends its BSR slew; but we didn't see it on day 041. If we had been able to receive S-RCP, we should have seen a 0.6 dB oscillation in carrier power; but the S-RCP maser was down and the S-LCP measurements are not a good indicator of what might have been happening on S-RCP. I had not heard about the meeting on 23 February until I received the message from Hannes. I will send any other issues that I can think of; but support from MEX has been excellent, and I don't think of any others right now. Most of the problems I see are on the DSN end. I can also send some BSR results; but Martin should also have some recent figures which I sent him a few months ago for a SWT meeting. Thanks, Dick From Stefan.Remus@sciops.esa.int Mon Feb 15 02:40:09 2010 Return-Path: Received: from esa-sf1.esa.gmessaging.net (esa-sf3.esa.gmessaging.net [194.51.201.69]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1FAe9j02545 for ; Mon, 15 Feb 2010 02:40:09 -0800 (PST) Received: from esa-sf1.esa.gmessaging.net (localhost [127.0.0.1]) by localhost.esa.gmessaging.net (Postfix) with SMTP id 74061249B92 for ; Mon, 15 Feb 2010 11:40:03 +0100 (CET) Received: from sciops-mailgw.vilspa.esa.int (sciops-mailgw.vilspa.esa.int [193.147.152.105]) by esa-sf1.esa.gmessaging.net (Postfix) with ESMTP id 5AC58249B8E for ; Mon, 15 Feb 2010 11:40:03 +0100 (CET) Received: from sciops.esac.int (scimail.esac.esa.int [193.147.152.87]) by sciops-mailgw.vilspa.esa.int (Postfix) with ESMTP id 9A46811FAC4 for ; Mon, 15 Feb 2010 11:40:08 +0100 (CET) Received: from [10.66.180.42] (ssow01.net3.lan [10.66.180.42]) (authenticated bits=0) by sciops.esac.int (8.13.1/8.13.1) with ESMTP id o1FAe8g0012891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 15 Feb 2010 11:40:08 +0100 Message-ID: <30005_1266230403_4B792483_30005_224337_1_4B79248D.3080509@sciops.esa.int> Date: Mon, 15 Feb 2010 11:40:13 +0100 From: Stefan Remus User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Dick Simpson 650-723-3525 Subject: Re: Fwd: Re: Fwd: MEX BSR with TLM References: <201002122014.o1CKETl22901@magellan.stanford.edu> In-Reply-To: <201002122014.o1CKETl22901@magellan.stanford.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Length: 3060 Status: RO On 12.02.2010 21:14, Dick Simpson 650-723-3525 wrote: >> do you need additional information? >> > No, Hannes answered very completely. My only suggestion would > be that we remind the operations people that telemetry is not > collected during BSR at DSN stations. > > I will ask the MOC if the message is spread around accordingly. >> Martin, Silvia and I will meet the MOC people at ESOC on the 23rd Feb. >> 2010. We are invited to give Science feedback and to discuss possible >> improvements in the planning. In case you have some information about >> your analysis or plannings we shall present please let Martin know. >> > I will distribute a report later today based on quick-look analysis > of the latest BSR data. There is a very strange modulation on the > X-RCP carrier level. It causes a reduction of the carrier power by > up to 5 dB every 85 seconds (the period is very consistent). The > unusual aspect of the modulation is that the measured X-LCP power > on the ground INCREASES by several dB at the same time as the X-RCP > is decreasing. > > The best explanation I have today is that the HGA pointing is > oscillating about the nominal boresight by almost +/- 1 degree. > This seems large, but it might explain why the RCP goes down and > the LCP goes up. Sometimes we see the LCP go up briefly when the > HGA begins or ends its BSR slew; but we didn't see it on day 041. > If we had been able to receive S-RCP, we should have seen a 0.6 dB > oscillation in carrier power; but the S-RCP maser was down and the > S-LCP measurements are not a good indicator of what might have been > happening on S-RCP. > > Hopefully the telemetry data can explain more. In case I get news I let you know. > I had not heard about the meeting on 23 February until I received > the message from Hannes. I will send any other issues that I can > think of; but support from MEX has been excellent, and I don't > think of any others right now. Most of the problems I see are > on the DSN end. > > I can also send some BSR results; but Martin should also have > some recent figures which I sent him a few months ago for a > SWT meeting. > Ok, very good. I think so as well but it will help if he gets something he can take directly as long as it is not too much work on your side. > Thanks, > Dick > Thanks, Stefan From jesse.velasco@dsn.nasa.gov Tue Feb 16 17:48:42 2010 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: MEX BSR 2010/041 Report Date: Tue, 16 Feb 2010 17:47:04 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MEX BSR 2010/041 Report Thread-Index: AcqsP+19gl6HtQCJRPiMwuPSsCo4BwDMvEvw From: "Velasco, Jesse" To: "Dick Simpson 650-723-3525" Cc: "!DL-DSN-MPSETD" , , "Goltz, Gene L" , "Asmar, Sami W (332K)" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by magellan.stanford.edu id o1H1mfj15841 Dick, DR N105983 has been open to document the S-band MASER being red for support. Jesse From jesse.velasco@dsn.nasa.gov Wed Feb 17 07:38:04 2010 Return-Path: Received: from DSNOAM-MM.jpl.nasa.gov (dsnoam-mm.jpl.nasa.gov [128.149.207.83]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1HFc3j19498 for ; Wed, 17 Feb 2010 07:38:04 -0800 (PST) Received: from dsnoamex1.jpl.nasa.gov (Not Verified[128.149.207.88]) by DSNOAM-MM.jpl.nasa.gov with MailMarshal (v6,4,6,5922) id ; Wed, 17 Feb 2010 07:38:35 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: MEX BSR 2010/041 Report Date: Wed, 17 Feb 2010 07:38:20 -0800 Message-ID: In-Reply-To: <201002170200.o1H20In15893@magellan.stanford.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MEX BSR 2010/041 Report Thread-Index: AcqvdR9GsRxHPaXeTf2f88mURSg8mwAccaHw References: <201002170200.o1H20In15893@magellan.stanford.edu> From: "Velasco, Jesse" To: "Dick Simpson 650-723-3525" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by magellan.stanford.edu id o1HFc3j19498 Content-Length: 494 Status: RO Dick, The S-band MASER is still red the ETRO is DOY 049/2300 UTC. It was reported to me some parts had to be ordered that resulted in extending the ETRO. -----Original Message----- From: Dick Simpson 650-723-3525 [mailto:rsimpson@magellan.stanford.edu] Sent: Tuesday, February 16, 2010 6:00 PM To: Velasco, Jesse Subject: RE: MEX BSR 2010/041 Report >DR N105983 has been open to document the S-band MASER being red for >support. Is it still red? I thought it was due back about now. From rsimpson Wed Feb 17 09:09:47 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o1HH9kD19613; Wed, 17 Feb 2010 09:09:46 -0800 (PST) Date: Wed, 17 Feb 2010 09:09:46 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002171709.o1HH9kD19613@magellan.stanford.edu> To: jesse.velasco@dsn.nasa.gov Subject: RE: MEX BSR 2010/041 Report Cc: daniel.s.kahan@jpl.nasa.gov, gene.goltz@jpl.nasa.gov, rsimpson Content-Length: 542 >The S-band MASER is still red the ETRO is DOY 049/2300 UTC. It was >reported to me some parts had to be ordered that resulted in extending >the ETRO. Jesse: Just checking because we have another BSR on 2010/051. It would be nice to have both S-RCP and S-LCP to check some strange modulation on the carrier - which is better done with S-RCP. However, if the S-RCP maser is still down, we should do the same as on 2010/041. The stronger echoes will be on S-LCP so we should not change the configuration. Thanks, Dick From daniel.s.kahan@jpl.nasa.gov Thu Feb 18 10:55:07 2010 Return-Path: Received: from mail.jpl.nasa.gov (mailhost.jpl.nasa.gov [128.149.139.106]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1IIt7j22937 for ; Thu, 18 Feb 2010 10:55:07 -0800 (PST) Received: from mail.jpl.nasa.gov (altvirehtstap02.jpl.nasa.gov [128.149.137.73]) by smtp.jpl.nasa.gov (Switch-3.4.2/Switch-3.4.1) with ESMTP id o1IIt5gB032185 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified FAIL) for ; Thu, 18 Feb 2010 10:55:06 -0800 Received: from ALTPHYEMBEVSP30.RES.AD.JPL ([172.16.0.31]) by ALTVIREHTSTAP02.RES.AD.JPL ([128.149.137.73]) with mapi; Thu, 18 Feb 2010 10:55:06 -0800 From: "Kahan, Daniel S (332K)" To: "Simpson, Richard A (6520-Affiliate)" , "Goltz, Gene L (332K)" Date: Thu, 18 Feb 2010 10:55:05 -0800 Subject: RE: MEX BSR Time Line 2010/051 Thread-Topic: MEX BSR Time Line 2010/051 Thread-Index: AcqwCpdM3SlNiYyxTC+eAVyGosddPgAwMArg Message-ID: <79D001DEDB0DEC47A247B110F3E86682072E61D614@ALTPHYEMBEVSP30.RES.AD.JPL> References: <20739.1266436281@magellan> In-Reply-To: <20739.1266436281@magellan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Source-IP: altvirehtstap02.jpl.nasa.gov [128.149.137.73] X-Source-Sender: daniel.s.kahan@jpl.nasa.gov X-AUTH: Authorized Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by magellan.stanford.edu id o1IIt7j22937 Content-Length: 3405 Status: RO Dick, Just to verify, based on the SLCP results from the last experiment, are we okay this time with any RSR for SLCP, and with a nominal configuration (i.e., only 1 RSR channel each, no redundancy)? Danny -----Original Message----- From: Dick Simpson 650-723-3525 [mailto:rsimpson@magellan.stanford.edu] Sent: Wednesday, February 17, 2010 11:51 AM To: Goltz, Gene L (332K); Kahan, Daniel S (332K); Simpson, Richard A (6520-Affiliate) Subject: MEX BSR Time Line 2010/051 Gene and Danny: Here is the time line for the MEX BSR on day 051 (local time 19 February 21:05 to 20 February 04:00) at DSS 14. The surface observations start at (26S, 9E) and end at (39S, 5W); this is lightly cratered terrain northeast of the large basin Argyre. The spacecraft has just passed apoapsis, so everything happens slowly and signals are relatively weak; but we have just passed Mars opposition, so the small Earth- Mars distance makes the weak signals stronger. Incident angle on the surface varies from 39 to 51 degrees, meaning LCP should be stronger than RCP throughout but with RCP making gains toward the end. I'm not sure how it happened, but the surface observations last 73 minutes where the previous limit has been 65. So there's one X-Band FRO in the middle of the surface observations; otherwise, this should look a lot like the experiment we did on day 041 - hopefully with fewer glitches. For playback, I recommend the following for the 25 kHz data (no segment longer than 88 minutes): Pre-cal Track until start of 100 kHz data Surface observations until end of 100 kHz data Remaining track plus post-cal For 100 kHz playback three 18 minute segments and one 19 minute segment would be best; but I can carve these up at Stanford if you give me a 73 minute file from each RSR. Feel free to phone if there are problems; you should be able to reach me at 650-494-9272. Thanks, Dick 2010/051 (UTC) - - - - - - - 05:05 Begin Pre-cal at DSS 14 FGAIN = 60 dB (all channels, except X-RCP) FGAIN = 63 dB (X-RCP) FRO_X = 0; FRO_S = 0 (all SCHAN) Start 4-channel 25 kHz recordings after Step 5 (new NOP) Stop 25 kHz recording after Step 20 (new NOP) 07:05 Begin track (S- and X-Band should both be OFF) 07:50 X-Band ON, telemetry ON -- ignore it 08:14 S-Band ON 08:30 Resume 25 kHz recording Advise DSS 14 of switch to planetary coordinates at 08:45 08:42 Begin SLEW #1 08:45 DSS 14 switch to planetary coordinates 08:47 FRO_X = +25000 Hz (SCHAN 3) FRO_S = +5000 Hz (SCHAN 3) 08:48 Begin MINICAL #1 09:03 End of MINICAL #1 (end of step 5) 09:07 End SLEW #1 Begin 100 kHz recording (SCHAN 4) 09:40 FRO_X = +35000 Hz (SCHAN 3) 10:15 Advise station of MINICAL #2 starting at 10:21 and Advise station of return to S/C pointing predictions at 10:36 10:20 End 100 kHz recording (SCHAN 4) Begin SLEW #2 10:21 Begin MINICAL #2 10:36 End MINICAL #2 (end of step 5) DSS 14 return to spacecraft pointing predicts FRO_X = 0 Hz (SCHAN 3) FRO_S = 0 Hz (SCHAN 3) 10:39 End SLEW #2 10:55 X-Band telemetry ON S-Band LOS Early end of track (scheduled EOT 11:50) Go to zenith Begin post-cal when ready 12:50 End post-cal (or earlier, if post-cal complete) End 25 kHz recordings End of Activity From rsimpson Thu Feb 18 11:15:43 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o1IJFh622991; Thu, 18 Feb 2010 11:15:43 -0800 (PST) Date: Thu, 18 Feb 2010 11:15:43 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002181915.o1IJFh622991@magellan.stanford.edu> To: daniel.s.kahan@jpl.nasa.gov, gene.l.goltz@jpl.nasa.gov Subject: RE: MEX BSR Time Line 2010/051 Cc: rsimpson Content-Length: 1614 Status: R >Just to verify, based on the SLCP results from the last experiment, are we >okay this time with any RSR for SLCP, and with a nominal configuration (i.e., >only 1 RSR channel each, no redundancy)? Yes. Based on the 2010/041 experience, S-LCP is the least of our worries. Although it looked flakey in real time, the digital data looked very good. There were some problems with the ODs in getting the S-Band signal paths correct; but I think that had more to do with there being no S-RCP than anything else. The S-LCP pre-cal and post-cal have a couple artifacts, but it's easy to understand what was going on with the NMC log and the numbers look very good. I am still puzzled by the modulation you noticed on the X-RCP carrier; there has been nothing from ESA to explain this. It's not something we can fix in real time, but you might watch to see whether it appears again. I'm convinced it's happening on the spacecraft. Also puzzling is high system temperature on both X-Band channels. the stormy weather COULD explain it; but it rose while we were doing the S-Band pre-cal and stayed at a 2X level for the rest of the observations. Usually weather causes variable Tsys. Also, even though S-Band is not subject to the same weather variations, the S-LCP behavior actually seemed BETTER than it should have been and not variable at all. So 2010/041 was a little strange, and in more ways than I mentioned in my report. But S-LCP was the 'good' channel during that experiment; so I don't think we need to do anything special to build in S-Band redundancy. From daniel.s.kahan@jpl.nasa.gov Thu Feb 18 11:20:23 2010 Return-Path: Received: from mail.jpl.nasa.gov (mailhost.jpl.nasa.gov [128.149.139.106]) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) with ESMTP id o1IJKNj23032 for ; Thu, 18 Feb 2010 11:20:23 -0800 (PST) Received: from mail.jpl.nasa.gov (altvirehtstap01.jpl.nasa.gov [128.149.137.72]) by smtp.jpl.nasa.gov (Switch-3.4.2/Switch-3.4.1) with ESMTP id o1IJKM6F018605 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified FAIL) for ; Thu, 18 Feb 2010 11:20:22 -0800 Received: from ALTPHYEMBEVSP30.RES.AD.JPL ([172.16.0.31]) by ALTVIREHTSTAP01.RES.AD.JPL ([128.149.137.72]) with mapi; Thu, 18 Feb 2010 11:20:21 -0800 From: "Kahan, Daniel S (332K)" To: "Simpson, Richard A (6520-Affiliate)" , "Goltz, Gene L (332K)" Date: Thu, 18 Feb 2010 11:20:21 -0800 Subject: RE: MEX BSR Time Line 2010/051 Thread-Topic: MEX BSR Time Line 2010/051 Thread-Index: AcqwzsU4QAWCaUN/SAakP/xMurNkKQAAEw+A Message-ID: <79D001DEDB0DEC47A247B110F3E86682072E61D621@ALTPHYEMBEVSP30.RES.AD.JPL> References: <201002181915.o1IJFh622991@magellan.stanford.edu> In-Reply-To: <201002181915.o1IJFh622991@magellan.stanford.edu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-Source-IP: altvirehtstap01.jpl.nasa.gov [128.149.137.72] X-Source-Sender: daniel.s.kahan@jpl.nasa.gov X-AUTH: Authorized Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by magellan.stanford.edu id o1IJKNj23032 Content-Length: 386 Status: R > I am still puzzled by the modulation you noticed on the X-RCP carrier; > there has been nothing from ESA to explain this. It's not something we > can fix in real time, but you might watch to see whether it appears >again. I'm convinced it's happening on the spacecraft. This reminds of the frequency "jumps" that we analyzed last summer. Wonder if there could be a connection. From rsimpson Thu Feb 18 11:27:33 2010 Return-Path: Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.7p3+Sun/8.11.7) id o1IJRXE23051; Thu, 18 Feb 2010 11:27:33 -0800 (PST) Date: Thu, 18 Feb 2010 11:27:33 -0800 (PST) From: Dick Simpson 650-723-3525 Message-Id: <201002181927.o1IJRXE23051@magellan.stanford.edu> To: daniel.s.kahan@jpl.nasa.gov, gene.l.goltz@jpl.nasa.gov Subject: RE: MEX BSR Time Line 2010/051 Cc: rsimpson Content-Length: 408 >This reminds of the frequency "jumps" that we analyzed last summer. >Wonder if there could be a connection. I wouldn't rule it out. But one of the surprising things about the modulation was its regularity -- a dip every 85 seconds. The frequency jumps seemed more random -- except that they seemed to occur more often after mode changes. Even limit cycling is usually more random than 85 sec.