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/MLIOPXFLN2QSHFGP7PMVKJSJYDA7OWGG/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "CAHxrdOS3w3tP-ry-a==7nYZE1_a0N3s9PhiF=e2Mwbpk-FjyTg@mail.gmail.com",
    "message_id_hash": "MLIOPXFLN2QSHFGP7PMVKJSJYDA7OWGG",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/MLIOPXFLN2QSHFGP7PMVKJSJYDA7OWGG/",
    "sender": {
        "address": "robert.ehresman (a) gmail.com",
        "mailman_id": "a60c893db7cb4ddaaf9e522aacf338bd",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/a60c893db7cb4ddaaf9e522aacf338bd/emails/"
    },
    "sender_name": "Robert Ehresman",
    "subject": "Re: [amsat-bb] :  DSLWP: First Amateur Radio Transmissions from",
    "date": "2018-06-07T13:12:37Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Bob:\n\nThanks very much for the detailed reply! I'm sure I'm not the only\nappreciative reader either.\n\nSo from your description it sounds like a station with approximately 1/4\nthe antenna elements typically considered necessary for closing an EME echo\npath on CW might be the lower margin of success. I have had 22 elements in\nthe air on 70cm before but not now unfortunately, and not on an \"EL\" rotor\nbefore. I have some work to do.\n\nI'm not familiar with the Airspy's dynamic range off hand, but the RTLSDR's\nis not great. Seems like SDRs with a few more sampling bits would provide a\nleg up like the Lime.\n\nAnyway, it certainly helps to know where to start. Thanks again!\n\n73;\nBob KV4PC\n\nOn Wed, Jun 6, 2018, 11:36 PM N6RFM1 gmail <[email protected]> wrote:\n\n> Hi Bob,\n>\n>\n>\n> As you have read in earlier posts, several of us (and the list grows\n> slowly I think) have been able to both receive and decode signals.  My\n> understanding is that early in the launch PY2SDR, CD3NDC, PY4ZBZ, K4KDR and\n> myself received signals.  By some quirk of fate, I was able to report the\n> first properly decoded packet back to the team’s server.\n>\n>\n>\n> The setup here – 11 elements on 70cm (custom “Alaskan Arrows” with solid\n> elements), SSB E. SP-7000 on UHF preamp, 28 meters of ½ inch hardline,\n> bias-T,\n>\n> Airspy rtl-sdr dongle.  Not a superstation by any stretch.\n>\n>\n>\n> At this point the DSLWP-B is in a lunar orbit.  While DSLWP-A has been\n> reported on S-band, we don’t know its status or location.\n>\n>\n>\n> See http://destevez.net/2018/06/dslwp-bs-journey-to-the-moon-part-iii/\n> for much more detail.  This blog reflects a tremendous effort by many\n> experts including EA4GPZ, BG2BHC and Scott Tilley, among others.  (Early\n> this year Scott discovered that the “long dead” IMAGE satellite was in fact\n> alive.)\n>\n>\n>\n> The DSLWP team has now conducted several tests after the lunar injection.\n> Cees Bassa and Jan PA3FXB have had some amazing results with the Dwingeloo\n> radio telescope in the Netherlands, during a lunar test window a few days\n> ago.  Alas, we can only dream of such an antenna, and place to put it!\n>\n>\n>\n> Perhaps more relevant to your question - a very big round of applause for\n> Piotr SP5ULN who was successful with a decode from the lunar orbit.\n> Piotyr’s setup is a Cushcraft 719B 19 el Yagi, SSB Electronics LNA\n> (SP-7000), 30m of RF-10 coax, bias tee and simple RTL-SDR.  So, we remain\n> hopeful… Others may have also been successful, but the DSLWP telemetry\n> server seems to be down and I can’t tell if there were any other recent\n> contributors.  Perhaps Wei BG2BHC will give us another update and we can\n> find out what the setup was.\n>\n>\n>\n> BTW, there is another test and hopefully some of the friends in Japan will\n> be successful too.\n>\n>\n>\n> One more point, as far as I am aware only GMSK has been transmitted.  But,\n> there is also a JT4G transmitter on –B.  Hopefully, JT4G will be easier to\n> receive.  I for one hope that will be the case.\n>\n>\n>\n> 73,\n>\n>\n>\n> Bob\n>\n> N6RFM\n>\n>\n>\n",
    "attachments": []
}