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/SC4E2JDWYA73GJU3JEOAVDNGOIMZPPCJ/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "SC4E2JDWYA73GJU3JEOAVDNGOIMZPPCJ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/NHX6X5EKQIQSZSS634TXEOLCBVH3Q3HB/?format=api",
    "sender": {
        "address": "bill (a) hsmicrowave.com",
        "mailman_id": "d7ecbf0c1df148f289f27dd7a8c37974",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/d7ecbf0c1df148f289f27dd7a8c37974/emails/?format=api"
    },
    "sender_name": "Bill Ress",
    "subject": "[eagle] Re: Eagle 10 MHz Clock",
    "date": "2007-04-11T16:45:58Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/2XBHQALU7PG3ZSKYXV4KFNCHLSAWS24I/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/FXVUYCDRZ4NODIH4SFOVW5FVH22M72XW/?format=api",
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/ATBE2P4MRJ273ULBHO7BPCXGLZ67CGAN/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Dick and Bdale,\n\nGood points about keeping the command receiver on 100% - no issue there. \nBut I think the matter is somewhat confused (at least for me) since I \nbelieve the command receiver that John has designed is also the \ndata/analog receiver. I don't recall that being the case is the past \nsatellites. If command and data function stay combined, then that's all \nthe more reason for considering John's suggestion for two U receivers.\n\nCorrect me if I'm wrong, but I also understand that there will also be a \nseparate L command receiver, but again not sure about that too.\n\nGosh - just think how handy a satellite top level block diagram might \nbe, even if its a work in progress. Or is there one and I haven't bumped \ninto it.\n\nRegards...Bill - N6GHz\n\nDick Jansson-rr wrote:\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>> Don't think power would be impacted since the spare unit would be in a\n>> power down mode.\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",
    "attachments": []
}