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/WHEP3V2KREMZ2UK3JYAZORDGXB22BY5I/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "WHEP3V2KREMZ2UK3JYAZORDGXB22BY5I",
    "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-10T03:06:20Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/N2MTLNMXZ7CXS4BERHPB6RBNB63N4B4R/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/YHI726XKOOSDMZIPPF2MMNBXAWV2AR3L/?format=api",
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/AV4VB7PTRXWHLK7SJSN3KZEK4VJVLRQ7/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Bill et al:\nThe requirement for the 10MHz reference descends from the July 2004 \nmeeting in Orlando.  As far as I know, it was never thoroughly \njustified, it was stated and made sense at the time.  Still does, to me, \ntho I could be convinced on a case basis that we might not need it.\n\n73,\njim\[email protected]\n\n\nBill Ress wrote:\n\n>Some very good dialog has been taking place, lead by Juan Rivera as he \n>heads up the prototype U Receiver build and test project.\n>\n>Several very important questions have been raised but I'd like to \n>address just one with this post.\n>\n>I've volunteered to design and build the S2 Receiver and the C \n>Transmitter and support microwave component efforts on the phased array \n>for each. I am finishing efforts on a \"prototype\" single channel \n>(assuming there might be several) S2 downconverter.\n>\n>I fully recognize than \"many\" system design parameters have not yet been \n>defined but I'm trying to get that \"definition\" effort moving along.\n>\n>This is the first one I'd like to address.\n>\n>In the coarse of designing the LO for the \"prototype\" S2 downconverter I \n>have not been too concerned with use of the 10 MHz satellite clock. But \n>I think it's time for \"system\" project guidelines to be developed for \n>this issue since it can affect the design of all LO's. I have looked for \n>guidance on the subject in Eaglepedia and have come up short. Point me \n>in the right direction if it's there (and I just couldn't find it).\n>\n>I hope I'm not rehashing old discussions (I've only been on the team \n>since last October) but here are my questions:\n>\n>1) What is the reason for requiring all LO's to be locked to a 10 MHz \n>satellite system clock or are they?\n>\n>2) Have the performance specifications for the 10 MHz clock been \n>developed and what are they (in particular phase noise, frequency \n>stability, susceptibility to digital hash, and power level available to \n>each using subsystem - to name a few)?\n>\n>My apologies for sending to the entire Eagle list but I'm not sure who \n>has the responsibility for the clock.\n>\n>Probably more questions to follow!!!\n>\n>Regards...Bill - N6GHz\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",
    "attachments": []
}