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/GA4OKCTCWKOCWRGNMHUCTNH5UDBI7U3B/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "CAN6TEUfWhJDHutUc9dyvNXPb_z51efvSHakYFKwSf5_n2uv79Q@mail.gmail.com",
    "message_id_hash": "GA4OKCTCWKOCWRGNMHUCTNH5UDBI7U3B",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/PBII43JOVNMJO4YLEMJKSRKIJDRUSJZS/?format=api",
    "sender": {
        "address": "amsat-bb (a) wd9ewk.net",
        "mailman_id": "21664df01bef4757931b7cdb42a9e768",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/21664df01bef4757931b7cdb42a9e768/emails/?format=api"
    },
    "sender_name": "Patrick STODDARD (WD9EWK/VA7EWK)",
    "subject": "Re: [amsat-bb] APRS Messaging QSOs",
    "date": "2020-08-26T20:05:22Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/PBII43JOVNMJO4YLEMJKSRKIJDRUSJZS/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Robert,\n\nThere are a few issues at play currently...\n\n1. Availability of orbiting digipeaters. The current ISS packet system\nappears to be hard of hearing. It can hear strong signals, and those\nwith lower-power stations - like the APRS-ready HTs - are only able to\nget through on the higher passes. If the new ISS radio and power supply\nare installed and set to operate an APRS digipeater, this issue with\nthe ISS digipeater may go away.\n\nBesides the ISS, NO-84's digipeater is rarely on. FalconSat-3 is\navailable, but that requires more sophisticated radio gear due to its\nuse of 9600bps packet and operating cross-band. FalconSat can be worked\nwith just a Kenwood TH-D72 or TM-D710G, as those radios support cross-\nband packet at 9600bps, and (try to) do that full-duplex.\n\n2. Unattended stations. This has been an issue for a long time on\n145.825 MHz. It is not legal for US stations to operate in the\n145.800-146.000 MHz and 435-438 MHz subbands unattended, yet it\nhappens. I referenced this in articles I wrote for the AMSAT Journal\nand QST in the past couple of years, and those are available from the\n\"Articles\" folder in my Dropbox space at http://dropbox.wd9ewk.net/\n\n3. Button-pushing. It can take many presses to generate a very short\nmessage using a DTMF keypad on APRS-ready radios. Some of the radios,\nthe Kenwood HTs and mobile radios in particular, provide a way to store\nprepared messages (they are called \"phrases\" in the Kenwood manuals)\nthat can be called up with fewer button presses. Others use programs\nlike UISS on a Windows system to handle APRS, including messaging.\nUISS can work with software like AGWPE or SoundModem, avoiding the need\nfor a TNC.\n\nThe APRS messaging protocol takes care of showing the sender and\nrecipient. This can leave the message text to convey information like a\ngrid locator(s) and state, or a \"TNX/73\" at the end of a QSO. The AMSAT\nJournal article I co-wrote about packet on the TH-D72 and TH-D74, which\nis available from:\n\nhttps://www.amsat.org/station-and-operating-hints/\n\ndescribed my message setup. I store 3 prepared messages in my radios,\nand normally use two of the 3 in making QSOs, following the process\noutlined in AMSAT Field Day rules for a complete QSO.\n\nA small computer could be useful here, allowing more radios to be used\nwith the orbiting packet digipeaters. A TNC probably isn't needed, if\nthe audio hardware on the computer is connected to the radio's speaker\nand mic jacks. If the small computer could compile a list of stations\nheard, and the user could select one of those stations for a message,\nthat could reduce the button pressing needed to send messages.\n\nHoping for the new ISS radio and power supply to be installed and\nactivated soon...\n\n\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\nTwitter: @WD9EWK or http://twitter.com/WD9EWK\n\n\n\n\n\n\nOn Wed, Aug 26, 2020 at 7:02 PM Robert Bankston via AMSAT-BB <\[email protected]> wrote:\n\n> It's a shame that their are not more APRS messaging satellite QSOs being\n> done via ARISS and other satellites.  Is this because...\n>   * Lack of equipment?  * Erratic operational schedules?  * Proliferation\n> of non-attended stations (beacons)?  * Too much button pushing?\n> Most ops you an HT and very few of those have APRS messaging capability.\n> Those HT's that do (including mobiles) are a bit clunky and require fast\n> thumbs to complete all of the necessary steps to complete a QSO.  Of course\n> the more you do it, the more second nature it becomes, but that circles\n> back to the erratic scheduling.\n> One solution could be to develop an app or software with prescribed\n> message formatting and QSO automation, similar to similar FT8.\n>   (click on target call in station list)  * [Target Call] [My Call] [My\n> Grid]  * [My Call] [Target Call] (Target Grid]  * R [Target Grid]  * RR [My\n> Grid]  (click on log QSO)\n> Single board computers could easily handle the task (even the Pi Zero),\n> for those worried about keeping their station small. Only thing left would\n> be a microarduino TNC or soundcard and a couple cables to the HT mic and\n> earphone jacks.\n> Just a thought.\n> 73, Robert KE4AL\n>\n>\n",
    "attachments": []
}