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/4GOUEGD3P4JADCP7N47Q2RZN4SYHBVWV/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "4GOUEGD3P4JADCP7N47Q2RZN4SYHBVWV",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/NHX6X5EKQIQSZSS634TXEOLCBVH3Q3HB/?format=api",
    "sender": {
        "address": "K3IO (a) verizon.net",
        "mailman_id": "79a9b3ddaa4b44baae47f92374974ac4",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/79a9b3ddaa4b44baae47f92374974ac4/emails/?format=api"
    },
    "sender_name": "Tom Clark, K3IO",
    "subject": "[eagle] Re: Eagle 10 MHz Clock",
    "date": "2007-04-11T03:40:30Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/BKSAJBFHITVQQSNQ52MLHHTVSP5YGOQR/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7B2BULZGYR77GPS7NVMPVP4DE5SVI4BM/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Bill Ress wrote:\n> (snip)\n>\n> If indeed the clock is used by all LO's it is important that the LO \n> designers know the reference's characteristics so that synthesis schemes \n> and loop bandwidths can be better defined.\n>   \nAssume that it is a low noise crystal. Signals will come from an N-port\ndriver that is a part of the USO. A good standard level will be 0 dBm\ninto 50 ohms (although it could be a tad higher -- like up to 1V RMS =\n+13 dBm if really needed).\n\nI would suggest that each user system could use the precision reference\nif it is available, but should switch over to an internal oscillator if \nthe precision source goes away. This is the way most counters, spectrum\nanalyzers, etc work and it permits a good, simple \"fail soft\" option.\n> With that in mind, can you Tom, 1) determine what the specs of the \n> $ystem USO might be (or point me to a place when I might deduce them), \n> and 2) what's a realistic time frame for deciding if that $ugar \n> daddy/mommy comes through with a commitment? We not only have to get a \n> handle on the 10 MHz oscillator but the RF distribution circuitry after it.\n>\n> In regards to the RF distribution circuitry, I count 8 users of the 10 \n> Mhz clock. Help me out here if I missed one....\n>\n> 1) V Transmitter\n> 2) U Receiver (maybe two?)\n> 3) L Receivers (two)\n> 4) S Transmitter\n> 5) S2 Receiver\n> 6) C Transmitter\n> 7) IHU\n> 8) Spare (for X or K beacon or a \"contributing\" customer)\n>   \nAs Lyle mentioned, all the DSP widgets need the reference signal also.\nFor precise ranging it is likely that some really tight special DSP code\nwill be loaded into the DSP engines for maximum accuracy. This will be\nto ensure the flattest possible phase response thru the system (the\ngroup delay tau is measured as d(phase)/d(freq) over the however wide\nthe passband can be).\n\nThinking of obtaining the best possible accuracy, we may want to do U/V\nand a microwave pair simultaneously to provide a calibration of the\nionosphere; the one-way group delay thru the ionosphere varies as 1/f²\nand has a magnitude ~2M at S-band.\n\n73, Tom\n\n\n",
    "attachments": []
}