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/5IWBFFKCHFBBAJWXPES7ZU6EMDAGW45N/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "5IWBFFKCHFBBAJWXPES7ZU6EMDAGW45N",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/6BGZWWT5GPVFUBF4S6OLNZMD2WPOVPMN/",
    "sender": {
        "address": "hans.bx2abt (a) msa.hinet.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Hans (BX2ABT)",
    "subject": "Re: [amsat-bb] Yubileiny RS-30 CW beacon",
    "date": "2018-06-01T14:39:00Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/5FM22X3UIXIOUAWQWNU2CKJB7CNQYKLM/",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/HEWVNR44IVYJTNJ5YZBL5VIMHZHMGNIP/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hello Hugh and Jean-Pierre,\n\nThanks for pointing out SatNOGS to me. I'm new to sats and didn't \nrealize that SatNOGS had this capability. I'll check it out.\n\nSo it seems RS-30 is dead. I checked the SatNOGS recordings, but I \ncouldn't detect any CW. A pity, 'cause back in 2009 it was one of the \nfirst sat signals I received on my HT with a simple antenna.\n\nI asked this question before on this list, but what other sats do have \nreliable and reasonably strong beacons (in morse code)? Any suggestions \nare welcome. Cheers.\n\nHans\n\nBX2ABT\n\n\n\nOn 06/01/2018 10:10 PM, Jean-Pierre Godet wrote:\n>   Hi, Hans,\n>\n>   The last record of Yubileiny-1 RS-30 CW telemetry I done was on \n> november 12th 2012. It died sometime in november 2012 and the CW \n> beacon was on 435.315 MHz and was pure CW A1. 435.215 MHz was used by \n> the digital telemetry downlink (with the russian Doka-B ground \n> stations). But anyway, I listen from time to time to the frequencies \n> of the missing birds, just in case... My russian favorite was \n> Mozhyets-4 RS-22.  :-) and my favorite chinese Xiwang-1 (Hope-1, \n> HO-68)my favorite, which is still possible to hear from time to time \n> when solar panels are under the sun (like AO-7).\n>\n>   Hans, there are a lot of others satellites sending CW telemetry on \n> 70 cm.\n>\n>\n>\n> On 01/06/2018 13:15, Hans (BX2ABT) wrote:\n>> Hello all,\n>>\n>> I'm trying out my 4 element 70cm LFA and (finally) received some \n>> decent signals from Athenoxat-1 (437.485 MHz). I had some good passes \n>> for Yubileiny RS-30 in the last couple of days, but I didn't observe \n>> anything. So, questions:\n>>\n>> 1) is RS-30 dead or still alive?\n>>\n>> 2) if alive, on which frequency is the morse code beacon active \n>> 435.215 or 435.315?\n>>\n>> 3) what mode should I use then: FMN or pure CW.\n>>\n>> I would like to know if anybody has observed RS-30 recently. On the \n>> web I can't find any recent observations. Thank you.\n>>\n>>\n>> Hans\n>>\n>> BX2ABT\n>>\n>> _______________________________________________\n>> Sent via [email protected]. AMSAT-NA makes this open forum available\n>> to all interested persons worldwide without requiring membership. \n>> Opinions expressed\n>> are solely those of the author, and do not reflect the official views \n>> of AMSAT-NA.\n>> Not an AMSAT-NA member? Join now to support the amateur satellite \n>> program!\n>> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb\n>>\n> _______________________________________________\n> Sent via [email protected]. AMSAT-NA makes this open forum available\n> to all interested persons worldwide without requiring membership. \n> Opinions expressed\n> are solely those of the author, and do not reflect the official views \n> of AMSAT-NA.\n> Not an AMSAT-NA member? Join now to support the amateur satellite \n> program!\n> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb\n>\n>\n>\n\n",
    "attachments": []
}