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/NH3KOVJB2RGTXFEEST4CGVONJUS63CZ5/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "NH3KOVJB2RGTXFEEST4CGVONJUS63CZ5",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/NH3KOVJB2RGTXFEEST4CGVONJUS63CZ5/",
    "sender": {
        "address": "k9qho6762 (a) sbcglobal.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "WILLIAMS MICHAEL",
    "subject": "[amsat-bb] Re: LVB Tracker Problem",
    "date": "2010-10-12T21:12:55Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Bob,\n \nI built the LVB tracker up from one of Howard's early bare boards.\n \nI had these problems interfacing to an old Wilson 550 rotor. I added relay circuits inside the old rotor box. The relay coils had supression diodes. The relays were switching 120 VAC which I think was the root cause. I started this project with the LVB tracker's power supplied from the rotor. I eventually gave the LVB tracker its own supply. Then I added supression circuirtry inside the LVB Tracker cabinet. I finally solved the problem and ran for years until the rotor just gave out mechanically. \n \nThe spikes would stop the tracker in a pass when there was relay activity. Sometimes I could just power down/up and  the LVB tracker everything would be OK. Sometimes reload SATPC32, and occassionally it would corrupt the calibration constants so I had to reload. One thing is certain, the LVB Tracker is a tough one.\n \nWhen the rotor gave out, I purchased a 5500. No problems using the 5500.\n \nFood for thought, and I don't want to send you down the wrong path.\n \nListen to Howard.\n \nGood luck with your problem.\n \nMike\nK9QHO\n\n\n\n\n",
    "attachments": []
}