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/R4WNCDOQRIWV4K4EI44GKDIFQCHVMLRL/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "R4WNCDOQRIWV4K4EI44GKDIFQCHVMLRL",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/R4WNCDOQRIWV4K4EI44GKDIFQCHVMLRL/",
    "sender": {
        "address": "rob (a) itr-datanet.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Rob Hardenberg PE1ITR",
    "subject": "[amsat-bb]  Solution to cubesat tracking",
    "date": "2007-04-20T21:36:33Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "To all Cubesat designers on the bb,\n\nI find it very hard and difficult to track and find the cubesat beacons. The reason is they are\ntransmitting short packets once every 2 or 5 minutes.\nI was thinking on a simple solution to this problem. Why not running the beacons with continues\nwave on very low power? Say 2 ~ 4 milliwatt or so.\nOn a packet burst the beacon can switch on high power, but in between its switching back to low\npower cw. This way its not doing to much on the cubesats power budget and it would easy to track.\n\nThis idea is already been tested succesfull. The last few months we are doing tests with the 4\nmilliwatt 216.980MHz beacon on RAFT. Signals received on a 10 el yagi are very good. I could track\nthe raft milliwatt beacon back to 3 degrees above the horizon with realtime dsp. On my webpage are\nthe results of these experiments: http://www.pe1itr.com/satellite/raft.htm\n\nMaybe this idea could be used in de next cubesat launch?\n\n\n73 Rob PE1ITR\nhttp://www.pe1itr.com\n\n",
    "attachments": []
}