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/Q6DWXIFSY6Y6XAUGGFWITLNEUTFZTYGM/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "7969338DDAAD47D38FB564051BAE2EA9@CSI9020",
    "message_id_hash": "Q6DWXIFSY6Y6XAUGGFWITLNEUTFZTYGM",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/ZX5ZMRRV43D2Z5ULCERUSUM53LCOAJ3D/?format=api",
    "sender": {
        "address": "scott23192 (a) gmail.com",
        "mailman_id": "120e10e05ba14969a11da0a96d21e355",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/120e10e05ba14969a11da0a96d21e355/emails/?format=api"
    },
    "sender_name": "Scott",
    "subject": "Re: [amsat-bb] WISP on 64-bits WIndows",
    "date": "2017-10-20T16:44:13Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/VH3GRMUBBY7Q7H3MO4TQHZRC3AQDSHMH/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Thank you so much for chasing this down!\n\nLast night was my first attempt to use WiSP with a transmit-enabled radio \nsetup and I also got the \"NO -5\" errors.  But not fully understanding WiSP, \nI did not know what that might be about.\n\nI have un-checked the \"NVT Enabled\" option and will look forward to trying \nagain on the next pass!\n\n-Scott,  K4KDR\n\n\n==================================================\n\n-----Original Message----- \nFrom: Edson W. R. Pereira\nSent: Friday, October 20, 2017 12:36 PM\nTo: [email protected]\nSubject: Re: [amsat-bb] WISP on 64-bits WIndows\n\nThank you to everyone that has contacted me privately.\n\nLast night I installed Windows 7 32-bits and WISP on a virtual machine and\nto my surprise, the problem I have been having persisted. After a lot of\nhair pulling (not much left anyway) and investigation, I found that the\nculprit was neither Windows nor WISP. It was the serial to TCP bridge HW\nVSP software. If the NVT option of HW VSP is enabled, it inserts some\ncontrol data in the data stream when it finds some pattern on the input\ndata stream. In the case of a dir fill, it was introducing three 0xFF bytes\nright in middle of the KISS frame. This was being sent over AX.25 to\nFalconsat-3 and was the cause of the \"NO -5\" error.\n\nI've tested requesting a dir fill during the last pass here and Falconsat-3\nreplied with a nice \"OK PY2SDR\"! Now let's grab some headers and try to\nupload a small file.\n\n73, Edson PY2SDR\n\n\n\nOn Thu, Oct 19, 2017 at 4:26 PM, Edson W. R. Pereira <[email protected]>\nwrote:\n\n>\n> Has anyone successfully requested directory fill from Falconsat-3 using\n> Windows 64-bits? It seems that WISP sends a corrupt request to the\n> satellite on Windows 64-bits. I have tried running WISP on two different\n> machines. Both with Windows 64-bits -- one running Windows 7 64-bits and\n> the other running  Windows 10 64-bits. On both, every time MSPE requests a\n> directory fill, I get a \"NO -5 PY2SDR\" response from the satellite. Roland\n> PY4ZBZ tried on his 32-bits Windows 10 system and the satellite replies\n> with a OK.\n>\n> Comparing the directory fill request packet sent to the satellite by my\n> station and Roland's, it seems that, on my station, WISP is corrupting the\n> directory hole pair data and also introducing one more byte to the \n> request.\n>\n> This is PY4ZBZ (good) request:\n>\n> 10 F4 00 42 8F E5 59 FF FF FF 7F 0D 0A\n>\n> This is PY2SDR (bad) request:\n>\n> 10 F4 00 BF 12 E0 59 FF FF FF FF FF FF 7F\n>\n> 73, Edson PY2SDR\n>\n> \n\n",
    "attachments": []
}