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/QRUBNUORHMEKP5N37ZRSWWIRVNC72OHR/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "QRUBNUORHMEKP5N37ZRSWWIRVNC72OHR",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/GFYLWBOILCXNNUPQIU3BB375KOVWVLYD/?format=api",
    "sender": {
        "address": "kq6ea (a) verizon.net",
        "mailman_id": "d2ef86d749ee450c8ad9ffc9f2e15cad",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/d2ef86d749ee450c8ad9ffc9f2e15cad/emails/?format=api"
    },
    "sender_name": "Jim Jerzycke",
    "subject": "[amsat-bb] Prolific Chipset Driver Issues",
    "date": "2014-01-19T17:43:41Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/GFYLWBOILCXNNUPQIU3BB375KOVWVLYD/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/YGYIAHISMQLZXGI6RLVLV5LFOLKI6273/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "The problem with using a cable with a \"Prolific\" chipset, is that many \nof these cables have counterfeit chips in them. What happens is you get \nthem set up with the included drivers, the cable and program work \nproperly, and then Windows Update replaces the driver with a newer \nversion, and the cable stops working.\n\nProlific has changed their drivers to include some checking steps, and \nif the driver software detects a non-genuine \"Prolific\" chipset, it \nwon't load, causing the cable to not work.\n\nAFAIK, FTDI chipsets have  not been counterfeited, and will continue to \nwork after Windows Update makes changes in your system.\n\n73, Jim  KQ6EA\n\nOn 01/18/2014 08:56 PM, K4FEG wrote:\n> Scott,\n> Frank, K4FEG here, I do not know if this would applicable to your \n> situation, but while I was having control issues with my Icom Ic-910H \n> and SatPC32, I reached out to Erich (writer of SatPC32) about the \n> issues and he told me that some of the cables and other interface \n> modules (USB/Serial adapters) need to have the /*FTDI chip set*/ in \n> them, /*I had to search for a specific type of USB/Serial adapter that \n> had the FTDI chip set in it.*/\n>\n> Once I got this adapter, and plugged it in on my Windows 8 and 7 PC's, \n> both operating systems instantly recognized the device and loaded the \n> proper driver to make the adapter work. /*Erich explained that the \n> PROLIFIC chip set, which is common in North America seems to have an \n> issue with his program.*/\n>\n> Another note is that there may be a firmware update for you Kenwood. I \n> have had others tell me that their TS-2000 would not properly control \n> with SatPC and when they got the various firmware updates for their \n> specific model radio, it helped to resolve their control issues.\n>\n> I do not know if this information is of help or not  but I thought \n> that it might, you may post your question on my BB, Star-COM.net, if \n> you like. My bb tries to cater more to real life situations and \n> operations on the satellites and working with operators and rovers to \n> facilitate working new grids on the \"birds\" you are most welcome to \n> come visit there if you wish.\n> 73 & best regards,\n> Frank\n> K4FEG\n> _______________________________________________\n> Sent via [email protected]. Opinions expressed are those of the author.\n> Not an AMSAT-NA member? Join now to support the amateur satellite \n> program!\n> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb\n>\n\n",
    "attachments": []
}