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/OAQLYIHN2PSFMG25SM3REYGQREUICIZM/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "OAQLYIHN2PSFMG25SM3REYGQREUICIZM",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/KYUJL6FKEKU5QTYMRUINEFYDZYGVR2AZ/?format=api",
    "sender": {
        "address": "patrickdk (a) patrickdk.com",
        "mailman_id": "109126d06ee94bdda4a537b0d4836088",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/109126d06ee94bdda4a537b0d4836088/emails/?format=api"
    },
    "sender_name": "Patrick Domack",
    "subject": "[amsat-bb] Re: GO32 APRS ?",
    "date": "2008-09-18T13:36:26Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/KYUJL6FKEKU5QTYMRUINEFYDZYGVR2AZ/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/GB2AHP7NAWAGWN3XYESDYGR2WEYTQVAX/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "What I use is, 145.85 for the uplink (only use 145.93 with mice)\n\nu aprs via 4xtech\nhbaud 9600 (I guess your 8600 was a typo)\n\nThen you should just be able to send anything like normal\nI do alot of messages like:\n\n:CQ       :Hello on go32\n\nI'm using my d700 in packet mode with aprs software\n\nAlso, can you hear go-32 at all? it transmits about every other second  \nwith it's bbs stuff, so it should be a constant stream of stuff even  \nif no one is transmitting to it. Pretty much like the ao-51 downlink  \non 9600baud.\n\nQuoting \"Henk, PA3GUO\" <[email protected]>:\n\n> Grrrr\n>\n> I seem to fail to understand the APRS mode of GO32:\n>\n> Kenwood TS2000X\n> HamRadioDeluxe for auto doppler correction\n>\n> External TNC (PK96)\n> hbaud 8600\n> u aprs via 4xtech\n>\n> uplink 145.850\n> in CONV mode: \":AP hello\"\n> ... some days ago this worked twice, then nothing got digipeated\n>\n> uplink 145.930\n> in CONV mode: \":2 hello\"\n> ... never any success\n>\n> Then: I see JA stations getting stuff like this over it:\n> JA0CAW]APRS,4XTECH*,qAS,JH4BTI::JA5BLZ :GE ur599 TNXp\n> whereas I would have expected somethin like \"AP JA5BLZ ....\"\n> (AP in front)\n>\n> This is the only source of documentation I have:\n> http://web.usna.navy.mil/~bruninga/GO32-ops.html\n>\n> Which states:\n>\n> 145.85 MHz All APRS messaging (or fixed station non-Mic-E   \n> positions). . Only TOCALLs that begin with \"APxxxx\".\n> 145.93 MHz All APRS Mic-E positions and status(D7, D700 and D710s   \n> with comment set to \"Committed, Special or PRIORITY\"...\n> The reason for these uplink distinctions is due to GO-32 hardware   \n> that will only digipeat a packet on 145.85 that has\n> a TOCALL beginning with \"A\". (All APRS fixed station packets and all  \n>  APRS messages including D7 and D700's) . The\n> 145.93 channel will only accept packets that begin with a digit   \n> between 1,2,3,4,5,6,7. . But fortunately the D7 and\n> D700's do this naturally as long as the position comment is set to   \n> \"committed, SPecial or PRIORITY\"...\n>\n> Q1: do the TOCALLs need APxxx or Axxx on 850 ? (in CONV mode type :APxxx ?)\n> Q2: should here \":2xxx\" work ?\n>\n> Thanks !\n> Henk, PA3GUO\n>\n> .... so lost :-)\n>\n>\n>\n>\n>\n>\n>\n>\n>\n>\n>\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 program!\n> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb\n>\n\n\n\n\n",
    "attachments": []
}