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/VXNGGEVVCTNLGQDF66ZYXI2MLM6GEUSS/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "VXNGGEVVCTNLGQDF66ZYXI2MLM6GEUSS",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/ROPG7NNM3XOFIAJZ64DP6N27Z63KJEF5/?format=api",
    "sender": {
        "address": "w5pfg (a) amsat.org",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Clayton W5PFG",
    "subject": "Re: [amsat-bb] CAS-2T & HO68 Beacon Report",
    "date": "2016-11-25T19:20:51Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/ROPG7NNM3XOFIAJZ64DP6N27Z63KJEF5/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "My assumption is that people listening for the CAS-2T beacon have not \nbeen patient the last few days. It is not continuously transmitting as \nit was after launch. There is a very long pause between transmissions \n(several minutes.) I copied the same series of letters as K8YSE/7 yesterday.\n\nThere might be some confusion on reporting satellite operational status \non the AMSAT OSCAR Status Page (http://www.amsat.org/status.)\n\n\"Not Heard\" can be subjective. Either the transponder was not heard or \nthe beacon was not heard. My opinion is to only use \"Not Heard\" when you \nhave tried the transponder and telemetry/beacon frequencies. Only if you \ndo not hear either one should you report \"Not Heard.\"\n\n73\nClayton\nW5PFG\n\nOn 11/25/2016 12:26, John Papay wrote:\n> Some are reporting hearing the beacon of\n> CAS-2T, however, I had not been hearing it\n> for the past few days.  Yesterday I set it on\n> the Beacon Frequency and waited without tuning\n> around.  Sure enough it was eventually heard,\n> but not in a continuous stream. It would send\n> \"CE\" and then go silent for a while.  Then it\n> would send \"CASS\" and go silent, maybe for a minute\n> or two before sending \"CE\" again.  No response on\n> the voice repeater frequency.  In the past it had\n> stuttered when activated.\n>\n> The HO-68 beacon was heard on frequency sending the\n> data but often times it would stop sending in the middle\n> of the data group.  It would go off for some time and then\n> come back sending a few characters before going off again.\n> The beacon frequency has been absolutely stable\n> for years.  Frequency settings have not been changed here\n> for years and it is always right there every time.\n>\n> 73,\n> John K8YSE/7\n\n",
    "attachments": []
}