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/K2H3YFZZOIDAWCGXGJ6Z3VRXT732OVJI/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "01cf01d06c81$e34c8c10$a9e5a430$@net",
    "message_id_hash": "K2H3YFZZOIDAWCGXGJ6Z3VRXT732OVJI",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/TBHQJZOUCFVGVIU47HQERTKDZVAJN4L6/?format=api",
    "sender": {
        "address": "kb2m (a) arrl.net",
        "mailman_id": "a9e21a68ea694587a3f7c02f0f3d12dd",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/a9e21a68ea694587a3f7c02f0f3d12dd/emails/?format=api"
    },
    "sender_name": "[email protected]",
    "subject": "Re: [amsat-bb] LVBTracker issue and minor SatPC32 glitch",
    "date": "2015-04-01T13:43:50Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/QQJ4ISF33ZO3P4QVNWBTUWZVN6RJY2UJ/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": " Kevin,\nThe 9100 always uses the same comports, the LVB also the same. After I get\nthe memory error the calibration is then off in the LVB, at least 10\ndegrees, usually more. I can, to save the pass look out the window at the\nantenna and come up with approximate az el offsets to get me through the\npass. I can live with this issue of turning on the LVB first, I just thought\nit should be fixable.\n The SatPC32 issue I brought up is also a minor inconvenience. But, I use my\n9100 with DXLab and SatPC32. With DX lab all I have to do is de-select the\n9100 while I'm using it with SatPC32. When I want to use the 9100 for PSK31\nor other data modes It's a simple 9100 2 menu change, and selecting the 9100\nin DXLab commander. I work the data modes, and when done I simply deselect.\nI then have to bring up SatPC32 as it would lose the 9100 in the process. It\nwould be great if SatPC32 acted as nicely as DXLab commander :D \n I hope I made this clear, but I'm in the middle of moving to Florida in 2\ndays and don't have time to elaborate any more. In a few months I plan on\ngetting on the birds from down there also, maintaining two sat stations one\nhere and one in Florida. So I wanted to try and resolve some of these nits.\nI already have a second LVB that I built from a kit that I will be using\ndown there when I get setup, along with a TS-2000.I need to yet buy the\nrotor, pre amps, and antennas. I'm thinking the new M2 LEO set will get\nunder the zoning boards radar nicely.\n\n73 Jeff kb2m\n  \n   \n\n\n-----Original Message-----\nFrom: AMSAT-BB [mailto:[email protected]] On Behalf Of Kevin\nSchuchmann\nSent: Tuesday, March 31, 2015 22:04 PM\nTo: [email protected]\nSubject: Re: [amsat-bb] LVBTracker issue and minor SatPC32 glitch\n\nJeff,\n   I have the same setup without the issues except that satpc32 needs to be\nstarted last which makes sense because otherwise it will complain about com\nports not there.\n\n   I'm wondering if you have ever watched the com ports carefully, windows\nloves to move things around so when you turn on the 9100 first is it\ngrabbing the usual lvb port? so the lvb gets what was the 9100 port? so\ninstead of a simple w035 090 command the lvb is seeing\n\\$FEFE7CE01A05005603FD\\$FEFE7CE01C0001FD\\w10  or some other string of\n9100 setup/frequency command from satpc32 and all that crud blows it's mind\nrequiring you to reset the LVB?\n\n   Just a thought...\n\n73 Kevin WA6FWF\n\n\nOn 3/31/2015 2:57 PM, [email protected] wrote:\n> Does anyone have this issue,\n>\n> I have to turn my sat system on in a certain sequence.\n>\n>   \n>\n> 1.       Turn on the LVBTracker.\n>\n> 2.       Turn on the 9100.\n>\n> 3.       Start SatPC32.\n>\n>   \n>\n> Today I had a visitor in my shack who turned the Yaesu 5500 on first \n> causing the LVB issue, so don't just say 'don't do that' J.\n>\n>   \n>\n> If I turn on the 9100 before the LVBTracker I get a memory error on \n> the LVBTracker and have to do a re-calibrate, a real pain if you're \n> trying to work a bird that's already up. If I run SatPC32 before I \n> turn on the radio I get a SatPC32 error that could be a little easier \n> to resolve then it is. I would like to see a de-select, select \n> sequence of the cat control to acquire the radio instead of a SatPC32 \n> reboot, sometimes with a task manager assist in Win7 to halt the rotor\n>\n>   serverSDX. I have no idea what would cause the LVB to behave in this \n> manner. Anyone have the LVB issue? Any solutions?\n>\n>   \n>\n> 73 Jeff kb2m\n>\n\n",
    "attachments": []
}