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/GDWTTIYLFU2G5JHNARIODVCVYUAD5VAI/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "GDWTTIYLFU2G5JHNARIODVCVYUAD5VAI",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/SDEYB5HBQC3WH7WPYWDZ4YTWT63JIQJM/?format=api",
    "sender": {
        "address": "ve9qrp (a) gmail.com",
        "mailman_id": "4d6061838db34aba9a1c4722addebfaf",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/4d6061838db34aba9a1c4722addebfaf/emails/?format=api"
    },
    "sender_name": "Bruce Robertson",
    "subject": "[amsat-bb] Re: LVB tracker questions",
    "date": "2008-01-10T01:34:52Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/6EPHBRTV2RPEYGQ5IZUBBE5HVCWTB2OB/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "On Jan 9, 2008 6:45 PM, Howard Long <[email protected]> wrote:\n> Hi Kevin and Andrew\n>\n> >  1) the LVB does its calibration in software, no variable supplies.\n> >  2) it keeps accepting commands and acting on them.\n> >  3) on the right side is the desired location, left side is the actual\n> location.\n> >  4) I know it works with the GS-232a protocol   W135 035  W (az)  (el)\n> >   maybe someone else knows.\n> >  5) Howard has mentioned this before on the bb and I believe its in his\n> > write-up on the tracker that he does multiple samples and averages them\n> > to get a more stable reading.\n> >  6) I think the diodes you are referring to go to the plus voltage for\n> > the position pots and to ground, if those are the ones you are talking\n> > about then they are there to limit any spikes on the az or el position,\n> > any negative voltage gets shunted to ground, any positive voltage greater\n> > than the supply gets shunted there.\n>\n> That about sums it up!\n>\n> As well as the GS-232A protocol it also supports Easycomm I. It looks at the\n> command sentences and automatically knows from their structure what protocol\n> is in use. Smart eh? ;-)\n>\n> The GS-232A seemed to be the most widely supported protocol at the time, and\n> I've not had any complaints yet that it should support anything else.\n>\n> Note that there are some esoteric GS-232A scheduling commands that are not\n> supported. Also calibration is performed differently. The reason calibration\n> is done in software was so that I didn't need to have to keep adjusting the\n> G-5500 trimpots every time I changed the rotator controller interface.\n>\n> As Kevin has already alluded to, the movement of the rotor is monitored\n> simultaneously as commands are accepted. All commands are acted upon\n> immediately whether or not the rotor is already moving. So you can override\n> a previous command immediately simply by sending another. This is how a real\n> GS-232A works.\n>\n> Note that the LVB Tracker does not detect a stalled rotor by itself - this\n> is a job for your favourite tracking software.\n>\n> 73, Howard G6LVB\n>\n>\n\n\nThis is a wonderful addition to the stable of AMSAT-related project.\nAs I've been toying around with designing a track-box for Tony AA2TX's\niRotor interface, I've learned quite a bit by reading the articles in\nthe Journal relating to the LVB Tracker.\n\nYou mention GS-232A protocol and Easycomm I. I have my code parsing\nthe GS-232A, which is easier because the parsing can be done by\ncharacter position. But I was hoping to use serial-line rotor command\nprotocol that included the name of the satellite being tracked so that\nthat info could also be displayed. Does anyone know of such a beast,\nespecially if it is supported by SatPC32? I went through that\nprogram's manual but had no joy.\n\n73, Bruce\nVE9QRP\n",
    "attachments": []
}