Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/IJEC6AHQFH53XYD4RTBQS33YUJ4EOEWR/?format=api
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/IJEC6AHQFH53XYD4RTBQS33YUJ4EOEWR/?format=api", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api", "message_id": "CAJCSnOZNPy5X4dNEZCE5QLCZ2giukG2vB_f3Ok2cZ3mzqRve_g@mail.gmail.com", "message_id_hash": "IJEC6AHQFH53XYD4RTBQS33YUJ4EOEWR", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/IJEC6AHQFH53XYD4RTBQS33YUJ4EOEWR/?format=api", "sender": { "address": "scott23192 (a) gmail.com", "mailman_id": "120e10e05ba14969a11da0a96d21e355", "emails": "https://mailman.amsat.org/hyperkitty/api/sender/120e10e05ba14969a11da0a96d21e355/emails/?format=api" }, "sender_name": "Scott", "subject": "[amsat-bb] LilacSat-2 Ground Interference Resolved (hopefully!)", "date": "2020-07-04T23:48:51Z", "parent": null, "children": [], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "Hello everyone.\n\nBy the quirk of the orbital pattern, for several months I've found myself\nat home -and- on the radio during some high, usually weekend evening passes\nof LilacSat-2 (CAS-3H). Seems like I often get a good pass around 6pm or\nso on the East Coast Fri/Sat/Sun.\n\nIt's bad enough that you never really know when LilacSat-2's FM transponder\nmight be active (144.350 up; 437.200 down; no tone), but it seemed like\nevery time I did catch it active there would be obvious ground stations\ngetting into the uplink. You could still make contacts, but it was tough\nsqueezing in between stations that had no idea they were being\nretransmitted across the entire country.\n\nI never could catch a call sign, but suspected they might be centrally\nlocated since the conversations often lasted from AOS to LOS.\n\nWell, last week I finally got a partial call sign. After searching on QRZ,\nI thought I might be on the right track & sent an email to Mark, AA0YY.\nRight there on his QRZ page was mention of an AllStar node set to 144.250!\nNot EXACTLY the uplink freq of LilacSat-2, but in the ballpark. AND, he's\nlocated in Missouri which is pretty close to the center of the continental\nU.S.\n\nMark was super helpful and copied his reply to Dan, KE0OZU, who\ncollaborates with him on their AllStar system. That nailed it. Dan\nreplied that while Mark's AllStar node was on 144.250, it was actually\nDan's own AllStar node that was set square on 144.350.\n\nI didn't mention anything to either of them about changing frequency...\ndidn't have to. Dan immediately replied that he would change his system's\nfrequency to avoid the conflict with LilacSat-2.\n\nI've only been around for a couple of passes since Dan made the change, but\nso far no more ground repeater conversations on the uplink. There's some\ngeneral static noise on LilacSat-2 when no one transmits, but otherwise the\nsignal can often be absolutely crystal clear.\n\nSo, only time will tell if that was the ONLY ground repeater getting into\nLilacSat-2's uplink, but hopefully it was an isolated case. The up/down\nstatus of the FM Transponder is still a hit or miss proposition, but since\nthe other FM sats are often crowded, folks might want to check to see if\nthis one is active when you have a high pass.\n\n-Scott, K4KDR\n", "attachments": [] }