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/U4U5SGSKUGEB3U2QH4AN4D65NITLDQW4/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "024401cf8e97$80135430$8039fc90$@com",
    "message_id_hash": "U4U5SGSKUGEB3U2QH4AN4D65NITLDQW4",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/NZZA24CI3U3PZVQIFGL74HR3HXQQ4LQG/",
    "sender": {
        "address": "kk0sd (a) tnics.com",
        "mailman_id": "288310e151a34b40b123f21344c13c43",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/288310e151a34b40b123f21344c13c43/emails/"
    },
    "sender_name": "Gary Mayfield",
    "subject": "Re: [amsat-bb] Fodtrack Serial rotor controller on HamLib",
    "date": "2014-06-23T03:59:15Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/FK74MBAQO3KZ2AMAYDJ42FBG3U5FNPHM/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "FODTrack was/is a parallel port controller.\n\n73,\nJoe kks0d\n\n-----Original Message-----\nFrom: [email protected] [mailto:[email protected]] On\nBehalf Of Jim Jerzycke\nSent: Sunday, June 22, 2014 7:40 PM\nTo: [email protected]\nSubject: Re: [amsat-bb] Fodtrack Serial rotor controller on HamLib\n\nI would suspect it's using the Yaesu GS-232 protocol.\n\nJim  KQ6EA\n\n\nOn 06/22/2014 06:08 PM, Greg D wrote:\n> Hi folks,\n>\n> So all this talk about Gpredict got me to look at updating my own \n> setup, which pre-dated the modern Gpredict capabilites.  But being so \n> archaic, I need some help connecting the dots...\n>\n> I have Gpredict / Hamlib talking to my Yaesu FT-736R radio for Doppler \n> tracking just fine, but the rotor is a problem.  My controller is \n> home-brewed, and emulates the subset of the \"Yaesu serial protocol\" as \n> output from the original DOS version of FODTrack.  The syntax is the \n> letter \"W\" followed by the Azimuth, a space, the Elevation, and \n> terminated with a carriage return (hex 0d).  Both the Az and El are \n> whole decimal integers.  When I moved to Linux and Predict (the \n> ncurses version) in 2002, I modified the software to copy that same \n> syntax, and all was fine.\n>\n> Tab forward over a decade to my question:  What model \"Yaesu \n> controller\" was FODTrack thinking it was talking to?  I need to find \n> an equivalent model for Hamlib's rotctl daemon, and none of the \n> choices seem to match.  They all seem to want to talk to a single \n> rotor (Az or El, not both).  Is there an equivalent model, Yaesu or \n> otherwise, that accepts \"Waaa eee\\n\" for Az + El positioning?\n>\n> Thanks,\n>\n> Greg  KO6TH\n>\n> _______________________________________________\n> Sent via [email protected]. Opinions expressed are those of the author.\n> Not an AMSAT-NA member? Join now to support the amateur satellite \n> program!\n> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb\n>\n\n_______________________________________________\nSent via [email protected]. Opinions expressed are those of the author.\nNot an AMSAT-NA member? Join now to support the amateur satellite program!\nSubscription settings: http://amsat.org/mailman/listinfo/amsat-bb\n\n\n",
    "attachments": []
}