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/5YPKRMVTBCZWDOW3SXIPWOF3NQCVCO5H/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "1430733596.225211204293728138.JavaMail.root@pd02.embarq.synacor.com",
    "message_id_hash": "5YPKRMVTBCZWDOW3SXIPWOF3NQCVCO5H",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/5YPKRMVTBCZWDOW3SXIPWOF3NQCVCO5H/",
    "sender": {
        "address": "n8mh (a) embarqmail.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Mark L. Hammond",
    "subject": "[amsat-bb] Re: Configuring LUSAT-19 like AO-16???",
    "date": "2008-02-29T14:02:08Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "\n\nHello John, \n\nThanks for your query about LO-19. \n\nThanks to the good efferts of our AMSAT Operations VP, Drew KO4MA and his establishment of the right contacts, a few weeks ago I spent some time corresponding with the LUSAT/LO-19 team.   They are a great bunch of hams, and they are (rightfully so) very proud of their \"old\" bird.   \n\nWe came to the conclusion that the failure mode of LO-19 is quite different from that of AO-16, and that any change from its current state of CW telemetry would either be impossible, or sufficiently risky that it was best to \"leave well enough alone.\"  So, I think we can expect that LO-19 will continue to report CW telemetry for a long time.  It's a great bird and its 18 years of continous operations is an amazing feat. \n\nDrew KO4MA has been attempting contact with the WO-18 folks.   DO-17 isn't such a likely candidate for doing much of anything... \n\nOther thoughts...you can include IO-26 as being \"nearly the same\" as the original microsats, Oscars 16/17/18/19.   In fact, I have started some preliminary testing of IO-26.   The testing is especially slow, and it will take some time to sort out its current state (what works and what doesn't).  Once we know that, we can begin to consider what function(s) IO-26 might serve.  While we have no idea at the moment if it's feasible, in theory its hardware could permit being reconfigured like AO-16.  We just don't know what our options are for now. \n\nRest assured, we're working on it :) \n\n73, \n\nMark Hammond N8MH \n\n_______ \n\nDate: Thu, 28 Feb 2008 17:20:07 -0500 \nFrom: \"John Marranca, Jr\" < [email protected] > \nSubject: [amsat-bb]  Configuring LUSAT-19 like AO-16??? \nTo: [email protected] \nMessage-ID: \n< [email protected] > \nContent-Type: text/plain; charset=ISO-8859-1 \n\nGood Afternoon, Everyone. \n\nLast month, a question was posed about the possibility of reconfiguring \nLUSAT/Oscar 19 in the \"bent pipe\" style that AO-16 is currently in.  As I am \nwriting this, both AO-16 and LU-19 are overhead...and both have stellar \nsignals. \n\nIs there any news/update as to whether or not this can be accomplished?? \n\nUpon reading the Satellite Handbook, it appears as though 16, 17, 18, and 19 \nwere pretty much similar.  If I am wrong, then I will stand as corrected, \nbut if 16 could be converted in such a fashion, what prevents 19? \n\nWishing for Spring! \n\nJohn KB2HSH \n\n\n-- \nMark L. Hammond [N8MH] \n",
    "attachments": []
}