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/ATBE2P4MRJ273ULBHO7BPCXGLZ67CGAN/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "ATBE2P4MRJ273ULBHO7BPCXGLZ67CGAN",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/NHX6X5EKQIQSZSS634TXEOLCBVH3Q3HB/?format=api",
    "sender": {
        "address": "wb4gcs (a) amsat.org",
        "mailman_id": "87014499e012476c8198fad186f7f963",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/87014499e012476c8198fad186f7f963/emails/?format=api"
    },
    "sender_name": "Jim Sanford",
    "subject": "[eagle] Re: Eagle 10 MHz Clock",
    "date": "2007-04-12T00:59:54Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/SC4E2JDWYA73GJU3JEOAVDNGOIMZPPCJ/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "All:\nU and L receivers will always be on, is my understanding of \nrequirements.  I've seen nothing to change that.  The subject of 1 or 2 \nreceivers at U and/or L is fuzzy, and a topic I wish to bring to closure \nover the next month or so.\n\nThere is a top-level block diagram, possibly in need of slight revision, \non EaglePedia, in the report of the \"Black Forest\" meeting in Oct/Nov of \n2005.\n\nTom:  Pls forward to Bill.\n\nThanks & 73,\nJim\[email protected]\n\n\nBill Ress wrote:\n\n>Hi Dick and Bdale,\n>\n>Good points about keeping the command receiver on 100% - no issue there. \n>But I think the matter is somewhat confused (at least for me) since I \n>believe the command receiver that John has designed is also the \n>data/analog receiver. I don't recall that being the case is the past \n>satellites. If command and data function stay combined, then that's all \n>the more reason for considering John's suggestion for two U receivers.\n>\n>Correct me if I'm wrong, but I also understand that there will also be a \n>separate L command receiver, but again not sure about that too.\n>\n>Gosh - just think how handy a satellite top level block diagram might \n>be, even if its a work in progress. Or is there one and I haven't bumped \n>into it.\n>\n>Regards...Bill - N6GHz\n>\n>Dick Jansson-rr wrote:\n>  \n>\n>>In my recollection there has been no option to anything with a command\n>>receiver at all in past satellites. This receiver was ON to be able to do\n>>its function regardless of other 'activities' on the satellite. In other\n>>words, it could not be messed with for any reason. Such a capability is\n>>absolutely essential for the health (and recovery) of the satellite and its\n>>mission.\n>>\n>>Dick Jansson, KD1K\n>>[email protected] \n>>[email protected] \n>>---------------------------\n>>\n>>\n>>-----Original Message-----\n>>From: [email protected] [mailto:[email protected]] On Behalf Of\n>>Bdale Garbee\n>>Sent: Wednesday, 11 April, 2007 1439\n>>To: Bill Ress\n>>Cc: [email protected]; EAGLE\n>>Subject: [eagle] Re: Eagle 10 MHz Clock\n>>\n>>\n>>On Tue, 2007-04-10 at 14:12 -0700, Bill Ress wrote:\n>>\n>>  \n>>    \n>>\n>>>Don't think power would be impacted since the spare unit would be in a\n>>>power down mode.\n>>>    \n>>>      \n>>>\n>>Please don't assume that it's ok to have the power to a command receiver\n>>switchable without substantial discussion and review.  All prior AMSAT\n>>projects that I'm aware of have had command receivers always on, even if\n>>they weren't always in use.  I'm pretty confident that includes both of a\n>>redundant pair.  Happy to be corrected by others with better knowledge of\n>>history if I'm mis-remembering some relevant case.\n>>\n>>Bdale\n>>\n>>_______________________________________________\n>>Via the Eagle mailing list courtesy of AMSAT-NA\n>>[email protected]\n>>http://amsat.org/mailman/listinfo/eagle\n>>\n>>\n>>\n>>  \n>>    \n>>\n>\n>_______________________________________________\n>Via the Eagle mailing list courtesy of AMSAT-NA\n>[email protected]\n>http://amsat.org/mailman/listinfo/eagle\n>\n>  \n>\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/ATBE2P4MRJ273ULBHO7BPCXGLZ67CGAN/?format=api",
            "counter": 2,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "us-ascii",
            "size": 4194,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/ATBE2P4MRJ273ULBHO7BPCXGLZ67CGAN/attachment/2/attachment.html"
        }
    ]
}