Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/KNPWDF7BMQB5FRLMFLO3Y5HFFROQRQC3/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "001c01c8f6d4$09fec3d0$0501010a@Cresswell2",
    "message_id_hash": "KNPWDF7BMQB5FRLMFLO3Y5HFFROQRQC3",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/KNPWDF7BMQB5FRLMFLO3Y5HFFROQRQC3/",
    "sender": {
        "address": "alancresswell (a) xtra.co.nz",
        "mailman_id": "0292a8a18be44d6a9fd4a622af40d892",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/0292a8a18be44d6a9fd4a622af40d892/emails/"
    },
    "sender_name": "Alan Cresswell",
    "subject": "[amsat-bb] Re: [Fwd: DO-64]",
    "date": "2008-08-05T08:19:52Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Wouter\n\nBear in mind that this happened about a minute or two before LOS and took me\nby surprise so these are not scientific observations.\nI was monitoring the beacon both by ear and with a visual display on\nspectran.  When the CW started the normal display gave way to the CW signal\nonly and it appeared to be on the centre frequency of the DSB beacon signal.\nI assumed at first that this was simply a new mode for the beacon.  There\nwere a few CW characters and then the beacon resumed.  The same thing\nhappened about 15 seconds later and then a couple of times more before LOS.\nI then realised that this is the exact pattern of RS-30, 5 or six CW\ncharacters at 15 second intervals.  When I brought RS-30 up on my display I\ndiscovered that RS-30 and Delfi have orbits that converge from opposite\ndirections once on each orbit and this convergence just happened to occur\nover ZL on that pass.  My next chance to have another look at this is the\n2246 UT pass on 6 August but I would think this can be checked before that\non rev 1484 over Europe at about 0930 UT on the 6th August.\n\nAlan\nZL2BX\n\n-----Original Message-----\nFrom: Wouter Jan Ubbels [mailto:[email protected]] \nSent: Tuesday, 5 August 2008 07:08\nTo: Alan Cresswell\nCc: [email protected]; Delfi-C3 Mission Control\nSubject: Re: [Fwd: DO-64]\n\nHi Alan,\n\nthat is very strange. 435.315 is not a command frequency and is far\naway enough of the transponder uplink and the actual command\nfrequencies so should not cause any trouble...\nHow did you find out that the CW on 145.870 came from RS-30?\nWould be interested in your further observations!\n\nthanks a lot and 73!\n\nWouter PE4WJ\n\n\nOn Tue, Aug 5, 2008 at 3:47 AM, Delfi-C3 Mission Control\n<[email protected]> wrote:\n> fyi\n>\n> Hi Delfi team,\n>\n> With no one other than myself to talk to on a 2226 UT DO-64 pass this\n> morning I decided to monitor the beacon towards the end of the pass.\n> Shortly before LOS the beacon stopped and sent CW for a second or two and\n> then the beacon restarted.  A few seconds later the same thing happened.\nI\n> eventually realized that the CW was the RS-30 downlink signal at\n435.315MHz.\n> The two spacecraft were on opposite tracks and approaching each other at\n> this time.  Why the 435.315MHz signal should stop the beacon and appear on\n> the 145.870MHz beacon frequency is a mystery to me.\n> I was about to post this on the amsat bulletin board when it occurred to\nme\n> that there could be a slight possibility that the effect on the beacon\ncould\n> be because the RS-30 signal hit a command and control frequency at\n> 435.320MHz so thought I would send it to you direct just in case.\n> In the absence of any comment I will post the info on the Amsat bb for\n> general interest.\n> With the current orbits of Delfi and RS-30 they are in this relationship\non\n> a regular basis so I will see what happens next time to the linear\ndownlink\n> frequency.\n>\n> Alan\n> ZL2BX\n>\n>\n\n\n",
    "attachments": []
}