Show an email

GET /hyperkitty/api/list/[email protected]/email/PKPTX2KXBXRMKFLXGWSXUV35Q733LLET/
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/PKPTX2KXBXRMKFLXGWSXUV35Q733LLET/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "PKPTX2KXBXRMKFLXGWSXUV35Q733LLET",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/PKPTX2KXBXRMKFLXGWSXUV35Q733LLET/",
    "sender": {
        "address": "kd6pag (a) amsat.org",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "John Mock KD6PAG",
    "subject": "[amsat-bb] Re: PIC rotator control",
    "date": "2009-10-16T03:47:28Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "> I am re-visting a rotator controller.\n>\n> I am curious, should I push the processing of the \"compare and make a decision\" \n> onto the PIC, or pull that function back into the PC ?\n> \n> PC is LINUX \n>\n> I/O is serial \n\nI built a homebrew rotator controller, inspired by WB4APR 'Radio Shack' rotor\ncontroller.  But given that both convention serial and parallel ports are no\nlonger available on most laptops, and alot less common elsewhere, i decided to\nuse a USB PIC.  Initially, that was a EPROM-based PIC16C475 but later migrated \nto the flash-programmable PIC18F2550.  It also includes a serial port, so that\na laptop could talk to a TTL-level serial port radio.  \n\nMy intent was to put the pointing smarts into the PIC, but i never got that\nfar.  Currently, it reads the rotor position inside the PIC, but moving the\nrotor in software (for both LINUX and Windows). That much works, but i bogged\non the PIC side trying to adapt Microchip's composite USB driver code to work\nproperly with multiple devices.  There were reliability issues, whose details\ni have forgotten, that put the whole project, which included a distributable\nversion, onto the back burner.\n\nI'm sorry i can't be more helpful than that.  Eventually, i'll get back to\nthis project, and amateur satellites in general.\n\n\t\t\t  -- KD6PAG  (Networking Old-Timer, Satellite QRPer)\n",
    "attachments": []
}