Show an email

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

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/EHZLFDAV2GVW65HYQLNTYKB6TX7FQHJI/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "CAJUhCTME7AfR0aYfcvpMCRfYGo_0q88RX+RfQjUpdVeH2H_B9Q@mail.gmail.com",
    "message_id_hash": "EHZLFDAV2GVW65HYQLNTYKB6TX7FQHJI",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/EHZLFDAV2GVW65HYQLNTYKB6TX7FQHJI/",
    "sender": {
        "address": "normanlizeth (a) gmail.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Lizeth Norman",
    "subject": "[amsat-bb] marks from space",
    "date": "2014-08-22T10:08:41Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi all!\nLatest craze is trying to decode 1200 baud ax.25 packets from\nsatellites. Satellite telemetry is not a busy terrestrial packet\nfrequency. As the number of chances that a ground station get at\nreceiving are limited and the environment different in the extreme,\nI'd like to get some input on how recover more data.\n\nWill concentrate on using a Fun Cube dongle pro + as the receiver.\n\nHave never had much success. Received a few frames from the ISS with a\nByonics Tiny Tracker 4. Last time I chased beepsats was a year and a\nhalf ago. Blew up the rotator control box it spun around so much.\nSince then, it's been one failure or another. Nothing has torched\nitself in a week or so. It's time to be daring.\n\nFound a (software modem) program called \"Dire wolf\" amongst others. It\ndoes a good job on the local APRS/packet traffic. I will try my TT4\nagain at some point. Did ask a similar question on that mailing list.\nAlso asked about the 9k6 TT4 rx feature. Was told that it was a\nsoftware switch, nothing more needed to be done. Enabling it should\nallow the tnc to decode the data. Since it won't encode that rate,\nsetting one up with a pc in another part of the house and using remote\ndesktop to monitor/control it and test isn't an option.\n\nDoing some reading about software decoders gives me the impression\nthat if the center of the passband is off 100 Hz or more, the\nalgorithm that decides what is a \"mark\" and what is a \"space\" fails.\nHow does a hardware modem compare? Are they different?\n\nObviously, ensuring the receiver is calibrated and centered on the\ncorrect frequency with the correct mode/ IF filter is one factor.\nAnother is transmitter LO temperature drift. Doppler correction is a\nfactor. Amplitude of the audio input is a variable.\n\nThere is a copy of virtual audio cable on my pc. It is possible to\nroute the signal from the receiver to an audio spectrum analyzer as\nwell as the software modem. Would this be any help troubleshooting?\n\nNorm n3ykf\n",
    "attachments": []
}