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/YIJBGUOVWA7X7VOZ6E4VOG2ACLBTGZAM/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "CABaTVVbPxVSz6TPT4Y=vKQ-gOH+9rWsq5zmheFUrQpbjy1=EJQ@mail.gmail.com",
    "message_id_hash": "YIJBGUOVWA7X7VOZ6E4VOG2ACLBTGZAM",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/YIJBGUOVWA7X7VOZ6E4VOG2ACLBTGZAM/",
    "sender": {
        "address": "ke6blr.robert (a) gmail.com",
        "mailman_id": "5735282710844f98ae684420fabf77f2",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/5735282710844f98ae684420fabf77f2/emails/"
    },
    "sender_name": "KE6BLR Robert",
    "subject": "[amsat-bb] AISAT Downlink Issues -- Defined",
    "date": "2019-04-21T17:45:34Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hello Satellite APRS Operators,\n\nI am new to this SIG. And, this is my first post. So, I hope it arrives as\nintended.\n\nAs you know, AISAT became available recently for Satellite APRS. One of the\nnice things about having an APRS Digipeater mounted to the Stage 4 Rocket\nplatform is this equipment inherits solar panels, batteries, and antennas.\n\nUnfortunately, the design team was given only 6 days to build and deliver\nthe satellite. Apparently, end to end testing of the Digipeater was not\npossible. So, I believe they deserve a lot of slack.\n\nNow, there are many (4ish) quirks in the downlink.\n\nNOTE: the AISAT uplink appears nominal.\n\nTo explain the downlink issue we need to examine a sample packet. For this\nwe can thank K4KDR for transmitting the packet and KG4PID for receiving the\npacket. If I remember this correctly, KG4PID is running PI-TNC and APRX\nwhile K4KDR is running Direwolf and UISS. The main thing to note here is\nthat displaying packets may require more flexible software.\n\nSample packet from the APRX error log via KG4PID:\n\n2019-04-11 02:06:38.961 ax25_to_tnc2(KG4PID-14,len=112) rejected the\nmessage: 00 86 a2 40 40 40 40 60|96 68 96 88 a4 40 6c 82|92 a6 82 a8 54 60\n40 40|40 40 40 40 61 03 f0 3a|43 51 2d 30 20 20 20 20|20 3a 3d 33 37 34 37\n2e|36 36 4e 2f 30 37 37 33|36 2e 36 37 57 60 64 65|20 4b 34 4b 44 52 20\n73|63 6f 74 74 32 33 31 39|32 40 67 6d 61 69 6c 2e|63 6f 6d 20 56 69 72\n67|69 6e 69 61 20 20 46 4d|31 37 65 73 7b 31 39 35| = .CQ    0|K4KDR\n6A|ISAT*0  |    a..:|CQ-0    | :=3747.|66N/0773|6.67W`de| K4KDR\ns|cott2319|2@gmail.|com Virg|inia  FM|17es{195|\n\nThis same packet after byte by byte parsing with a simple Python script on\nmy Mac laptop:\n\n@@@\n\nrobertmachale@ucrwpa-2-1-10-25-34-138 ~/Documents/SCC/AISAT-EXPLAIN $\npython explainAisat.py\n\nSpace Communcator Club\nLas Flores, California 92688\nhttp://www.spaceCommunicator.club/igates/\n\n\n1: byteAsHex: 00, byteAsText: 0, byteAsAScii: 0, byteAsChar: ,\nendOfDigipath: 0\n1: SSID: 0, Digipeated: 0\n2: byteAsHex: 86, byteAsText: 134, byteAsAScii: 67, byteAsChar: C,\nendOfDigipath: 0\n3: byteAsHex: a2, byteAsText: 162, byteAsAScii: 81, byteAsChar: Q,\nendOfDigipath: 0\n4: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n5: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n6: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n7: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n8: byteAsHex: 60, byteAsText: 96, byteAsAScii: 48, byteAsChar: 0,\nendOfDigipath: 0\n8: SSID: 0, Digipeated: 0\n9: byteAsHex: 96, byteAsText: 150, byteAsAScii: 75, byteAsChar: K,\nendOfDigipath: 0\n10: byteAsHex: 68, byteAsText: 104, byteAsAScii: 52, byteAsChar: 4,\nendOfDigipath: 0\n11: byteAsHex: 96, byteAsText: 150, byteAsAScii: 75, byteAsChar: K,\nendOfDigipath: 0\n12: byteAsHex: 88, byteAsText: 136, byteAsAScii: 68, byteAsChar: D,\nendOfDigipath: 0\n13: byteAsHex: a4, byteAsText: 164, byteAsAScii: 82, byteAsChar: R,\nendOfDigipath: 0\n14: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n15: byteAsHex: 6c, byteAsText: 108, byteAsAScii: 54, byteAsChar: 6,\nendOfDigipath: 0\n15: SSID: 12, Digipeated: 0\n16: byteAsHex: 82, byteAsText: 130, byteAsAScii: 65, byteAsChar: A,\nendOfDigipath: 0\n17: byteAsHex: 92, byteAsText: 146, byteAsAScii: 73, byteAsChar: I,\nendOfDigipath: 0\n18: byteAsHex: a6, byteAsText: 166, byteAsAScii: 83, byteAsChar: S,\nendOfDigipath: 0\n19: byteAsHex: 82, byteAsText: 130, byteAsAScii: 65, byteAsChar: A,\nendOfDigipath: 0\n20: byteAsHex: a8, byteAsText: 168, byteAsAScii: 84, byteAsChar: T,\nendOfDigipath: 0\n21: byteAsHex: 54, byteAsText: 84, byteAsAScii: 42, byteAsChar: *,\nendOfDigipath: 0\n22: byteAsHex: 60, byteAsText: 96, byteAsAScii: 48, byteAsChar: 0,\nendOfDigipath: 0\n22: SSID: 0, Digipeated: 0\n23: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n24: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n25: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n26: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n27: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n28: byteAsHex: 40, byteAsText: 64, byteAsAScii: 32, byteAsChar:  ,\nendOfDigipath: 0\n29: byteAsHex: 61, byteAsText: 97, byteAsAScii: 48, byteAsChar: 0,\nendOfDigipath: 1\n29: SSID: 0, Digipeated: 0\nrobertmachale@ucrwpa-2-1-10-25-34-138 ~/Documents/SCC/AISAT-EXPLAIN $\n\n@@@\n\nNotice 3 issues with the Digipath:\n\n1) SSIDs arrive as ASCII rather than 4 bits in the AX.25 subfield\n2) The Digipeated flag arrives as * rather than 1 bit in the AX.25 subfield\n3) One extra (blank) callsign field exists at the end of the Digipath\n\nAlthough the Kenwood will pickup the packet we may need to tap into the TNC\nraw output to decipher the packet manually. I can only imagine the Kenwood\ndisplay will reject the packets as malformed. So, this leaves us with\nAPRSDroid, UISS, and custom APRS software for displaying packets received.\n\nFeel free to follow APRS packets from AISAT on our iGate report:\nhttp://www.spaceCommunicator.club/igates/\n\nAlso, you will find a note on this AISAT issue including helpful screen\nshots here: http://www.spaceCommunicator.club\n\nLet me know your feedback and how I can help.\n\nHappy Easter + Passover + Holiday!\n\n73s\n\nRobert MacHale\nKE6BLR\n(949) 371-6319\[email protected]\n",
    "attachments": []
}