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/EXQVTK7TYGHLQBUJXYPGHYG4LKSZKQNI/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "EXQVTK7TYGHLQBUJXYPGHYG4LKSZKQNI",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/EXQVTK7TYGHLQBUJXYPGHYG4LKSZKQNI/",
    "sender": {
        "address": "k6vug (a) sbcglobal.net",
        "mailman_id": "37fd9aee884c4835a5c51104b6295d3a",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/37fd9aee884c4835a5c51104b6295d3a/emails/"
    },
    "sender_name": "[email protected]",
    "subject": "Re: [amsat-bb] Trying to understand downlink corrections",
    "date": "2018-07-10T21:36:29Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": " A big thank you for all the replies !  \n \nW3AB/GEO, \nJust to clarify, SatPC32 has the latest TLEs and does all the work during the pass. However, at AOS I have to apply a small correction to the downlink frequency (via SatPC32's feature) in order to zero beat the CW beacon. After that, it tracks nicely throughout the pass. So my question was (a) why do I need the correction and (b) why is the correction different for different satellites. \n \nJay, \nThanks, I did calibrate it as much as SDRsharp would allow and it seems to be dead-on for ground VHF transmissions.  Assuming it was still off by a little, I thought it would be off by the same amount for all satellites. \n \nAlan, \nThanks for the detailed explanation, the temperature based drift was my first guess due to the size limitations. I had not thought of the component degradation and esp., seasonal changes and the PC clock.   \n \nPedro, \nThanks for the TLE updating tip.  I guess TLEs change to keep up with orbit drift, etc. right?  \n \nAgain, thanks everyone, this is fascinating and it looks like there is no way to \"Set-it-and-Forget-it\"...  \nSo, for now, I'm making a list of downlink corrections for the satellites that I'm playing with and that have a CW beacon.  \nSome day, if I get my hands on some SDR code I may look into adding auto-zero-beat like FLDIGI or DM780 or CWGET. \n \n \nBest 73s, \nUmesh \nk6vug \n \n\n\n\n    On Tuesday, July 10, 2018, 12:59:21 PM PDT, W3AB/GEO <[email protected]> wrote:  \n \n Umesh,\n\nAre you asking about doppler corrections that must be made during the operation or a fixed frequency before you start?\n\n___\nSent from my two way wrist watch\n73 de W3AB/GEOOn Jul 10, 2018, at 12:43, Jay Cox via AMSAT-BB <[email protected]> wrote:\nDon't forget your SDR could be off by a few parts per million in frequency if you haven't calibrated it to a known frequency source.  At 435 MHz, being off by 3 parts per million would translate to a 3*435 =1305 Hz or 1.305 KHz offset from the actual intended frequency of reception.\nJay F. CoxKG5BZW\n\"Knowledge can only exist if doubt is possible.\"  -- stolen from an amazon.com review of \"On Certainty:\" by by Ludwig Wittgenstein. \n\n    On Tuesday, July 10, 2018, 1:43:09 PM CDT, Alan <[email protected]> wrote:  \n \n Umesh,\n\nThere are two primary satellite issues.  First, the published frequencies\nare usually nominal values obtained during ground checkout. Over time due to\nnormal component aging, radiation, loss of voltage regulation, etc they can\ndrift.  \n\nThe second is the temperature effect you mentioned.  You will find that the\nbeacon and transponder calibration will change slightly with the spacecraft\ntemperature as it goes through periods of eclipse and full illumination.\nThere is also a slight seasonal shift which you can see.  This is most\nprominent in CubeSats which have very little thermal inertia.  Also, the are\ntradeoffs to be made in terms of power consumption, radiation resistance,\nand performance.  AO-7 also drifts due to the lack of a battery to stabilize\nthe voltage.  \n\nAnother issue is your station computer clock.  They can drift rather badly,\nand the operating system may not do a very good job of syncing them with a\nreliable time standard.  There are some free programs which do an excellent\njob available.\n\n73,\n\nAlan\nWA4SCA\n\n\n\n\n<-----Original Message-----\n<From: AMSAT-BB [mailto:[email protected]] On Behalf Of\n<[email protected]\n<Sent: Tuesday, July 10, 2018 12:28 PM\n<To: AMSAT BB <[email protected]>\n<Subject: [amsat-bb] Trying to understand downlink corrections\n<\n<Greetings,\n<I have been using a SDR dongle to receive the downlinks of SSB satellites.\nThe\n<combination of SatPC32's Downlink Correction feature and the SDR's visual\n<display helps to zero beat the CW beacon exceptionally well.  The Lat/Lon\nis\n<good to 6 decimals.  However, I find that the downlink correction needed\nis\n<quite different for different satellites. Could it be due to rounding off\nerrors or\n<due to temperature variations at the satellite itself ?   Maybe this has\nbeen\n<explained earlier, but I wonder why ?\n<\n<Obviously, the more I learn, shows how less I know...  Thanks for any\npointers\n<!\n<\n<73!\n<Umesh\n<k6vug\n<\n<Sent via [email protected]. AMSAT-NA makes this open forum available\nto all interested persons worldwide without requiring membership. Opinions expressed\nare solely those of the author, and do not reflect the official views of AMSAT-NA.\nNot an AMSAT-NA member? Join now to support the amateur satellite program!\nSubscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb\n\n  \n",
    "attachments": []
}