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/JI7YEMTR572SCYEWFPQZGWV426HQDCSV/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "JI7YEMTR572SCYEWFPQZGWV426HQDCSV",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/SBOZCWPFKZP35I6YLEHSVFBVG56G46UK/?format=api",
    "sender": {
        "address": "faunt (a) panix.com",
        "mailman_id": "fea5a111bdd14188b4f0e2ebfecfadc9",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/fea5a111bdd14188b4f0e2ebfecfadc9/emails/?format=api"
    },
    "sender_name": "Doug Faunt N6TQS +1-510-655-8604",
    "subject": "[amsat-bb] Re: LCU-3 and ICOM 471 or 271",
    "date": "2009-01-21T22:36:24Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/CRXHTK6NET4AZKFUSSOKEBE5KLNBEL72/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/BNPZ2DSTY7446SBWXIZ52X2MD3T2EEPS/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "That's the way it was set up.  But main window persists in\ntransmitting out of the second digital window.\n\nI just have assigned the main RX audio channel to that second\ninstantiation of MMTTY, and it operates as it should.  It's just wierd\nthat the main logging window persists in actuating the second digital\nwindow.\n\n73, doug\n\n   Date: Wed, 21 Jan 2009 21:26:52 -0000\n   From: \"Richard Ferch\" <[email protected]>\n\n   Doug,\n\n   Are the two copies of MMTTY run from two different folders? This is \n   required in order that each copy can have its own mmtty.ini file. You \n   can set up the MMTTY copy used from DI1 to receive from the left \n   channel (main RX) and transmit using FSK, and set up the copy used from \n   DI2 for AFSK, receiving from the right channel (the 2nd RX). \n   Alternatively, you could set the second copy up for FSK, but that would \n   require a separate serial port for each copy of MMTTY - typically you \n   would do this for SO2R (FSK from both radios).\n\n   I have used such a setup, configured for FSK in DI1 and AFSK in DI2, in \n   SO1V with the two VFOs linked. If you program a couple of function keys \n   with {CAT1ASC} macros to switch the radio between FSK D and AFSK A you \n   can even transmit in FSK from DI1 or AFSK from DI2 as you choose (both \n   copies transmit from VFO A). Using the same configuration in SO2V with \n   the 2nd RX unlinked, the DI2 copy becomes a read-only decoder for the \n   2nd RX and the radio transmits only from DI1 in FSK.\n\n   73,\n   Rich VE3KI\n\n\n\n   --- In [email protected], Doug Faunt N6TQS +1-510-655-\n   8604 <faunt@...> wrote:\n   >\n   > I've got a dual-RX K3, and have N1MM runnig with two copies of MMTTY.\n   > But in trying to get thing figured out, I find I'm transmitting from\n   > the wrong window.  I have to be \"in the seocnd window\" to TX FSK.\n   > But the first window is the main RX and since I;m not in split, that's\n   > my TX VFO.\n   > \n   > What have I got confused?\n   > \n   > 73, doug\n   >\n\n\n\n",
    "attachments": []
}