Show an email

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

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/F24EC6ORFKCPZ5AH3CTWPRPIZBVT2SJW/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "CAMkCmDqs2q0RHzuaRdJEZbPtjeAM7=mSd0HBnKWh20mFKt=NdQ@mail.gmail.com",
    "message_id_hash": "F24EC6ORFKCPZ5AH3CTWPRPIZBVT2SJW",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/F24EC6ORFKCPZ5AH3CTWPRPIZBVT2SJW/",
    "sender": {
        "address": "charlieray (a) gmail.com",
        "mailman_id": "827214bf3d8d45f8b41335a087b8b8e7",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/827214bf3d8d45f8b41335a087b8b8e7/emails/"
    },
    "sender_name": "Charles Reiche",
    "subject": "[AMSAT-BB] Fwd: Re: PSAT2 VHF Awakes",
    "date": "2021-04-30T03:27:55Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Thanks Bob,\n\nWas able to get through but unable to reply to the other station I heard. I\nthink my reply was formatted incorrectly using the \"B\" special QSL reply\nformat or my timing was off.\n\nI heard KE4AZZ make QSO #16 and saw the APRS confirmation.  My reply\naccording to this page http://aprs.org/QIKcom/Q2-DTMF-messages.txt  should\nbe:\nC40166327802277#   Message number (40= 40 Q S L, your number _, my number\nis %.) then modifier (qso #16) and then my callsign and key code, this is\nusing the radiogram format.\n\nEither way, on my Icom 9700 I have to edit the DTMF memory before sending\nthe reply, so the B or the C message format doesnt matter much differently\nfor me.\nI tried doing the Direct Input of B16 then switching quickly to a DTMF\nmemory to send  406327802277#  but couldn't get a reply out of the\nsatellite.  Only an 8 degree pass here in the NJ wet rained on trees.\n\nI recorded a video and uploaded it to Youtube for this last pass.\nhttps://youtu.be/aVr3wN7WI0s\n\nSomething fun and different! Hope to try again tomorrow.\n\n73\nN3CRT\nCharles Reiche\n\n\nOn Thu, Apr 29, 2021 at 7:33 PM Robert Bruninga <[email protected]> wrote:\n\n> yes, be quick. You might have 3 seconds for the manual entry,\n> bob\n>\n> On Thu, Apr 29, 2021 at 5:51 PM Charles Reiche <[email protected]>\n> wrote:\n> >\n> > My B(2...  was my attempt to reference the 2 digit QSO number of the\n> other station.\n> > So my QSO QSL reply to another stations QSO number 13 would look like\n> this:\n> >\n> > B13406327802277#\n> >\n> > Is there a problem with timing or timeout of the satellite receiving the\n> string of DTMF if I were to try to hand enter the B13 and send, then kick\n> over to my DTMF memory to send the stored QSL reply for the rest of the\n> string 406327802277# ?\n> >\n> >\n> > 73\n> > N3CRT\n> > Charles Reiche\n> >\n> >\n> > On Thu, Apr 29, 2021 at 5:26 PM Robert Bruninga <[email protected]>\n> wrote:\n> >>\n> >> yes,\n> >> * No spaces in the DTMF string.\n> >> And yes, your keycode is required.\n> >> Im not sure what the \"B(2\" typo is in your email?\n> >>\n> >> Bob\n> >> On Thu, Apr 29, 2021 at 3:20 PM Charles Reiche <[email protected]>\n> wrote:\n> >>\n> >> > So using the DTMF callsign encoder  I send\n> >> > *1320 632780 2277 #\n> >> >  *(Grid FN20)  (Call N3CRT) (decimal key code)#\n> >> >\n> >> > I get a QSO number via the digitalker reply.\n> >> > I hear someone else get a digitalker reply QSO number and I want to\n> QSL to that station.\n> >> > So I send B(2 digit QSO number of the other station) then 40 (QSL)\n> 632780 (my call) 1320 (my grid)  or are the last 4 supposed to be my\n> decimal key code?  2277?\n> >> > I'm only hung up on this last part before giving it a go.  \"Then the\n> remaining CCCCCCxxxx finish off the transmission with the full encoded\n> callsign as in the grid format..\"\n> >> >\n> >> > is the xxxx my decimal key code, or my grid?  I am guessing that the\n> CCCCCC call sign wont make sense to the decoder without the decimal key\n> code.\n> >> >\n> >> > 73\n> >> > N3CRT\n> >> > Charles Reiche\n> >> >\n> >> >\n> >> > On Thu, Apr 29, 2021 at 12:21 PM Robert Bruninga <[email protected]>\n> wrote:\n> >> >>\n> >> >> PSAT2 VHF awoke from an 8 Mo slumber on 26 Apr 2021.  We have no\n> idea why.  Its telemetry looks fine.  Volts between 6.2 and 7.0 volts (5\n> NiCds).  Exterior temps between -18 and +22 C.\n> >> >> See http://aprs.org/psat2.html\n> >> >>\n> >> >> PSAT2 will NOT be in APRS mode but a brand new experimental mode for\n> >> >> DTMF uplink and VOICE downlink.  So you preload your grid and\n> callsign\n> >> >> into a 16 digit DTMF memory in your radio and when the satellite\n> hears\n> >> >> this it will assign a QSO number and QSL the grid by voice and then\n> also generate an APRS packet for collection by APRS operators.  There is\n> even a way to send back a DTMF QSL so you can make it a 2-way DTMF. contact.\n> >> >>\n> >> >> Successful DTMF grids and messages will appear on a special URL on\n> the PSAT2 page (above).  To QSL, you key in that stations 2 digit QSL\n> number and then dump your pre-loaded QSL DTMF message..\n> >> >>\n> >> >> Since this is the first time this transponder is on the air and\n> because a DTMF uplink takes maybe 4 seconds, we dont want the uplink\n> >> >> saturated by a bunch of newbeees initially until we see if it\n> actually\n> >> >> works.  So read the docs and be sure you know what you are doing.\n> >> >>\n> >> >> There is a user operating manual available on the PSAT2 web page:\n> >> >> http://aprs.org/psat2.html\n> >> >>\n> >> >> Bob, WB4APR\n> >> >>\n> >> >> On Wed, Apr 28, 2021 at 3:20 AM Clary, James T (Jim) via AMSAT-BB\n> >> >> <[email protected]> wrote:\n> >> >> >\n> >> >> > A busy work day on board gave me the chance to put only one grid\n> (CK27) on the air today, but one grid is better than none. Another time\n> change occurs for us tonight; we'll be at GMT-9 for a couple days, and that\n> gets in the way of making the AO-91 pass at 28/1952Z. In the very off\n> chance that I can make that one, we should be in CK08 at the time. Later\n> on, I'll try to make passes on CAS-4A/B, AO-7/CW, XW-2F, and RS-44/CW in\n> the 29/0130-0333Z time frame; we should be in BK98 then. A little later,\n> we'll cross into BK88 hopefully in time for the 29/0506Z pass. 73/Jim, ND9M\n> >> >> >\n> >> >> >\n> >> >> > -----------------------------------------------------------\n> >> >> >\n> >> >> > Sent via AMSAT-BB(a)amsat.org. AMSAT-NA makes this open forum\n> available\n> >> >> > to all interested persons worldwide without requiring membership.\n> Opinions expressed\n> >> >> > are solely those of the author, and do not reflect the official\n> views of AMSAT-NA.\n> >> >> > Acceptable Use and Privacy Policies available at\n> https://www.amsat.org/about-amsat/\n> >> >> >\n> >> >> > View archives of this mailing list at\n> >> >> > https://mailman.amsat.org/hyperkitty/list/[email protected]\n> >> >> > To unsubscribe send an email to amsat-bb-leave(a)amsat.org\n> >> >> > Manage all of your AMSAT-NA mailing list preferences at\n> https://mailman.amsat.org\n> >> >>\n> >> >> -----------------------------------------------------------\n> >> >>\n> >> >> Sent via AMSAT-BB(a)amsat.org. AMSAT-NA makes this open forum\n> available\n> >> >> to all interested persons worldwide without requiring membership.\n> Opinions expressed\n> >> >> are solely those of the author, and do not reflect the official\n> views of AMSAT-NA.\n> >> >> Acceptable Use and Privacy Policies available at\n> https://www.amsat.org/about-amsat/\n> >> >>\n> >> >> View archives of this mailing list at\n> >> >> https://mailman.amsat.org/hyperkitty/list/[email protected]\n> >> >> To unsubscribe send an email to amsat-bb-leave(a)amsat.org\n> >> >> Manage all of your AMSAT-NA mailing list preferences at\n> https://mailman.amsat.org\n> >>\n> >> -----------------------------------------------------------\n> >>\n> >> Sent via AMSAT-BB(a)amsat.org. AMSAT-NA makes this open forum available\n> >> to all interested persons worldwide without requiring membership.\n> Opinions expressed\n> >> are solely those of the author, and do not reflect the official views\n> of AMSAT-NA.\n> >> Acceptable Use and Privacy Policies available at\n> https://www.amsat.org/about-amsat/\n> >>\n> >> View archives of this mailing list at\n> >> https://mailman.amsat.org/hyperkitty/list/[email protected]\n> >> To unsubscribe send an email to amsat-bb-leave(a)amsat.org\n> >> Manage all of your AMSAT-NA mailing list preferences at\n> https://mailman.amsat.org\n>\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/F24EC6ORFKCPZ5AH3CTWPRPIZBVT2SJW/",
            "counter": 2,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "utf-8",
            "size": 10998,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/F24EC6ORFKCPZ5AH3CTWPRPIZBVT2SJW/attachment/2/attachment.html"
        }
    ]
}