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/SA3E4OU75KG4K3HDRHPBCS6RF23GWLMK/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "SA3E4OU75KG4K3HDRHPBCS6RF23GWLMK",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/FYVLHCM2XIYP7NME52FSAFNRDJYQC4ZI/?format=api",
    "sender": {
        "address": "rick (a) vk6xlr.net",
        "mailman_id": "de2295a1e6e34be9a968b05a57b7ad3a",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/de2295a1e6e34be9a968b05a57b7ad3a/emails/?format=api"
    },
    "sender_name": "Rick Kowalewski",
    "subject": "Re: [amsat-bb] Satpc32 and ICOM 9700",
    "date": "2020-05-11T08:11:34Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/437PTL7R76KZL7Q5SY6XZGI6KHHMF26H/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/LKKHBYZYLSKXWEEINAVUTNQIVX4S7CSJ/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Erich,\n\nBut on 2 different computers running Win7 or Win10?  Same problem on both?\nThe whole point of using USB, is it handles both comms and audio. CI-V \nis a step in the wrong direction and more cables to worry about.\n\n73,\nRick VK6RK\n\nOn 11/05/2020 15:42, Erich Eichmann via AMSAT-BB wrote:\n> Hi Mike,\n> your wrote:\n> \"The issue I have is that about once a week, the SATpc32 and the radio \n> fail to communicate. Then, I turn off the radio and shutdown SATpc32. \n> Irestart both and it is fine for another week or so.\n>\n> That has nothing to do with SatPC32 but is a problem of the USB port, \n> I think. I noticed the same sometimes. Here it helps to unplug the USB \n> cable from the PC and to plug it in again. With CAT control via the \n> CI-V connector of the IC-9700 you would not have the problem.\n>\n> 73s, Erich, DK1TB\n>\n>\n> 10.05.2020 um 06:03 schrieb Michael Walker via AMSAT-BB:\n>> Hi Rick\n>>\n>> I would have to say, my experience is not the same.  I use the VFO \n>> knob all\n>> the time, just like I was on 20M and I have never had an issue. I \n>> actually\n>> does work as it should and it continues to doppler tune just fine.\n>>\n>> Mine is on the USB port.  Maybe we should compare settings.  If I had \n>> the\n>> problem you are seeing, I would try reducing the baud radio (or even try\n>> increasing it).  I am at 19200, but I bet you could safely run at \n>> 9600 as\n>> the amount of data being moved is pretty trivial.  I am away from my\n>> computer, but I think my interval speed is set to 30.\n>>\n>> The issue I have is that about once a week, the SATpc32 and the radio \n>> fail\n>> to communicate.  Then, I turn off the radio and shutdown SATpc32.  I\n>> restart both and it is fine for another week or so.\n>>\n>> Mike va3mw\n>>\n>>\n>> On Sat, May 9, 2020 at 9:33 PM Rick Kowalewski via AMSAT-BB <\n>> [email protected]> wrote:\n>>\n>>> Would be nice if the USB settings \"worked as advertised\".\n>>>\n>>> If the VFO know is not moved, then yes, all is ok.  However, once you\n>>> start to tune around the bandpass, SatPC32 eventually 'loses' comms \n>>> with\n>>> the 9700 and will not doppler tune.\n>>> However, not all comms are lost.  If you select another line in CAT\n>>> Tuning, the radio now changes to that frequency.  You can even select\n>>> another satellite and frequency/mode changes.  BUT, radio no longer\n>>> follows doppler tuning and tuning the VFO does not update on SatPC32.\n>>> Go figure.\n>>>\n>>> Have tried both http://www.dk1tb.de/IC9700_settings.htm and\n>>>\n>>> https://www.amsat.org/wordpress/wp-content/uploads/2020/01/SatPC32-IC9700-Setup-1.pdf, \n>>>\n>>>\n>>> makes no difference.  Same under Win7 & Win10.\n>>>\n>>> Only cure is to restart Windows.\n>>>\n>>> 73,\n>>> Rick VK6RK\n\n",
    "attachments": []
}