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/TROJ5DOMI54K5VWXMABYBPF66V63DLZN/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "TROJ5DOMI54K5VWXMABYBPF66V63DLZN",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/TROJ5DOMI54K5VWXMABYBPF66V63DLZN/",
    "sender": {
        "address": "gerhardstein (a) montana.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Larry Gerhardstein",
    "subject": "[amsat-bb]  thanks",
    "date": "2010-05-08T04:49:09Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Greetings,\n\nI want to thank all of the good folks who helped me get my satellite \nstation on the air.  This has been a process since about last fall.  We \nwere gone during the winter and restarted the project when I returned \nhome.  I'd like to recognize W4AS, K7WIN, PE0SAT, KB7ADL, K0VTY, N6NKF, \nScott Hagerman (non ham), AA5PK, K6LCS, G8IFF, certainly others ... and \nmost of all Erich DK1TB, author of SatPC32, who spent much time \nresearching drivers, answering questions, and attempting to duplicate \nproblems I have been having.\n\nA few lessons learned... from all this.\n\n1) Don't jump to conclusions.  My rotor control spent about 3 months at \nYaesu service only to learn nothing wrong with it.  The technician at \nYaesu never suggested the trouble could be fixed by optical isolation of \nthe RS232 line going to the rotor control box.\n\n2) Do not assume the nature of a RS232 cable.  Use an ohm meter and \ndetermine if it is good or bad, straight through or cross-over or \nnull-modem.  If I had started out using the ohm meter on my cables, that \nwould have saved me much time and frustration.  Both GS-232 and CI-17 \ncall for straight through serial cables.  I made the mistake of using \ntwo null modem cables; unfortunately I did not know they were not \nstraight through until later when I thought to use an ohm meter.\n\n3) Don't assume you can construct a straight through RS232 cable by \nconnecting two null modem cables in series.  This may work, and it may not.\n\n4) Before installing optical isolators in the RS232 lines, make certain \nthe devices are compliant with the isolators.  I tried optical isolation \nin both the rotor control and the rig control lines.  An isolation \ndevice between computer and GS232 rotor interface was needed.  However, \nthe CI-17 does not like them.\n\n5) The optical isolators from CF that I used seem to have polarity.  \nMake certain the female end of the isolator is against the computer's \nmale connector.  Do not turn the isolator around and use sex-changers \nbetween computer and isolator.  This was just a random thing I tried.... \nit did not work.\n\n6) When running into difficulty as I did, document everything.  I kept \nrepeating the same trials over and over, wasting time, and about driving \nmyself to madness.\n\n7) In my opinion when using Windows 7 of Vista 64-bit, only install \ndrivers designed for those systems.  Drivers for 32-bit are not reliable \nin 64-bit applications and may cause the computer to crash to blue screen.\n\n8) Before ordering USB to serial conversion devices make certain the \ndrivers that come with those gadgets are compatible with the computer \noperating system you plan to use.  Many days after I received my KeySpan \ndevice, I called Tripp Lite.  The sales person there told me they do not \npresently have a 64-bit driver for the USA49WG.  Wish I had known that.\n\n9) Make sure the baud rate in the transceiver matches the baud rate \nbeing set up in the CAT setup menu.  If you can affort it, get a RS232 \nserial data analyzer.  I downloaded the free version of 232Analyzer.  \nFull version is about $140.  232Analyzer helped a lot and allowed me to \nsee both data transmitted and received.  This led me to the mismatched \nbaud rates in the ICOM and SatPC32.\n\nThese are the issued I stumbled on.  Different computer hardware, \ndifferent ham gear, different operating systems may produce different \nresults.  Beware of Murphy.\n\n73, Larry W7IN\n\n",
    "attachments": []
}