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/SZ3LPMOP4OH47BA5DIDZXFYY6V7JQBKB/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "SZ3LPMOP4OH47BA5DIDZXFYY6V7JQBKB",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/E2X2WVZG65EQOOH4KYFUVIJLWBL7WICD/?format=api",
    "sender": {
        "address": "ai6do (a) yahoo.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Ryan Noguchi",
    "subject": "Re: [amsat-bb] APRS Satellite PATHs",
    "date": "2019-07-10T18:37:10Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/KTVWZJ6DB4JV2NDGR2A4FJBFJS6GUDOB/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/D4G4T4N76ZAXEN5NDQCOZWKHABGB34AQ/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": " Yes, that's correct. FalconSat-3 doesn't digipeat using the generic ARISS or APRSAT paths.  \n\nAgreed, it's a pain to have to keep changing PATH, baud rate, and data band between FalconSat-3 and the other packet satellites. At least there are only two configurations to have to toggle between. Once you've done it a couple dozen times, it becomes second nature. \n\nYes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode, but the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode and enable (crude) Doppler correction. I haven't used them yet so don't know if 5 kHz steps will cut it.  \n\n73, Ryan AI6DO\n\n    On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse via AMSAT-BB <[email protected]> wrote:  \n \n Regardless of the other operational requirements of FalconSAT-3, you are saying FalconSAT-3 will not digipeat using the generic paths. That means the text in the links provided is incorrect. Or is there some other qualifier I have missed?\n\nPSAT2 is also a different beast apparently. The text in the link imply APRS uplinks are narrowband. From the PSAT2 link:\n\nUplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31\nUser Station Software Configuration: \nFirst bullet - Radios must be in Narrowband and track to 1 KHz Doppler on the uplink.\n\nThe reason for asking is to be able to make as few changes to an HT (D72) as possible. And the main use is to achieve a digipeat. When a satellite is the only APRS network available it could be a useful way to get information out.\n\nBest regards,\nFred N7FMH\n\n\n-----Original Message-----\nFrom: AMSAT-BB [mailto:[email protected]] On Behalf Of Ryan Noguchi via AMSAT-BB\nSent: Wednesday, July 10, 2019 12:11 PM\nTo: [email protected]\nSubject: Re: [amsat-bb] APRS Satellite PATHs\n\n FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband at different frequencies than the 1200 bps packet satellites. If you want to be digipeated by FalconSat-3, you need to use the PFS3-1 PATH. \n\n73, Ryan AI6DO\n\n  \n",
    "attachments": []
}