Hi Marty, Lets start from beginning. How is your CAT communication signaling built in your system? Do you have a USB to RS-232 converted cable or direct RS-232 to RS-232 cable between PC and your FT-1000MP? To me it seems a simple loss of that connection for some reason. Even just the bit rate setting could be changed or COM port number.
73, Reino OH3mA -----Original Message----- From: Marty Wayne via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: 23. heinäkuutata 2022 4:29 To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Marty Wayne <mcway...@comcast.net> Subject: Re: [wsjt-devel] Hamlib Error I can’t even get the radio and wsjt-x to communicate. I misspoke when I said that the Hamlib error happened while using FT8. Actually, I had taken a short break. I believe I shut down wsjt-x and restarted when I returned. That is when aI started getting the Hamlib error. I hadn’t changed the power as there was no communication. In checking the sound preferences, CODEC does not show up to select. Does that mean anything? Marty Wayne mcway...@comcast.net 408-234-8023 > On Jul 22, 2022, at 5:56 AM, robert evans LAST_NAME via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > As a diagnostic.. > > While sending CQ for example.. > > Reduce the transmit power, > by both audio and transmitter settings and see if the phenomenon goes > away at lower powers. > > If with the output minimized the phenomenon persists then it is > probably not RFI related. > > If you find a reduced output power that does not exhibit the > phenomenon, then it is probably RFI related. And, you have a clue as > how much shielding and isolation you might need. > > Operating at the reduced power while introducing changes gives you > method of testing improvements. > > BCNU DE N2LO~> > >> On 07/22/2022 12:07 AM Black Michael via wsjt-devel >> <wsjt-devel@lists.sourceforge.net> wrote: >> >> >> If it runs at startup but fails during/after transmit than it is probably >> RFI. >> >> Here are some potential solutions -- ordered by cost. >> >> #1 Free - Move USB cables to another port -- some ports are more susceptible >> than others. >> #2 Free -- Check your grounding system. rod-outside-the-shack is a common >> problem when it's not bonded to the main house ground. >> http://www.k9yc.com/GroundingAndAudio.pdf >> #3 Add some USB shield isolators (see my QRZ page). >> #4 Good USB cables like this >> https://www.amazon.ca/Tripp-U023-006-Device-Ferrite-Chokes/dp/B003MQ2 >> 9B2/ref=sr_1_5?crid=11YRNPWDVWGCU&keywords=usb+cable+with+choke&qid=1 >> 658187349&sprefix=usb+cable+with+choke%2Caps%2C139&sr=8-5 >> #5 Maybe free (if you have chokes...otherwise can get a bit costly) -- add >> chokes to USB cables first, then all other cables including power, ethernet, >> and control cables. >> Fair-Rite torroids are good quality -- do NOT buy cheap Chinese ones -- >> https://www.fair-rite.com/product/toroids-5943003801/ You can use clip-ons >> but torroids allow multiple wraps and give better results. >> https://www.fair-rite.com/product/round-cable-snap-its-431176451/ >> I couldn't find type 31 torroids at Fair-Rite as of 20220721 but >> Palomar has some >> palomar-engineers.com/ferrite-products/ferrite-cores/ferrite-ring-tor >> oid-combo-pack/ >> >> >> Mike W9MDB >> >> >> >> >> On Thursday, July 21, 2022 at 12:29:33 PM CDT, Marty Wayne via wsjt-devel >> <wsjt-devel@lists.sourceforge.net> wrote: >> >> >> I was working 20 Meter FT-4 and at one point I got a Hamlib error, >> communication timed out. See report below. Im not computer savvy. What >> might be the issue? >> >> Rig-FT-1000MP >> iOS 12.5 >> SignaLink USB interface >> WSJTx 2.5.2 >> WSJTx 2.5.4 >> >> Hamlib error: Communication timed out >> rig_get_vfo: returning -5(Communication timed out >> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication >> timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo >> return(-5) Communication timed out >> ft1000mp_get_update_data: Timeout >> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication >> timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: >> Timeoutft1000mp.c(1675):ft1000mp_get_update_data return(-5) >> Communication timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo >> return(-5) Communication timed out >> ft1000mp_get_update_data: Timeout >> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication >> timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: >> Timeoutft1000mp.c(1675):ft1000mp_get_update_data return(-5) >> Communication timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: Timeout)rig_get_vfo: elapsed=439ms >> rig.c(2587):rig_get_vfo return(-5) Communication timed out >> rig_get_vfo: returning -5(Communication timed out >> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication >> timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo >> return(-5) Communication timed out >> ft1000mp_get_update_data: Timeout >> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication >> timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: >> Timeoutft1000mp.c(1675):ft1000mp_get_update_data return(-5) >> Communication timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo >> return(-5) Communication timed out >> ft1000mp_get_update_data: Timeout >> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication >> timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: >> Timeoutft1000mp.c(1675):ft1000mp_get_update_data return(-5) >> Communication timed out >> read_block_generic(): Timed out 0.402040 seconds after 0 chars >> ft1000mp_get_update_data: Timeout >> ft1000mp_get_update_data: Timeout)rig_get_vfo: elapsed=439ms >> rig_get_vfo: elapsed=439ms while testing getting current VFO >> >> Timestamp: 2022-07-21T17:16:46.329Z >> >> >> >> 73, >> >> Marty, W6NEV >> _ . . . . _ _ _ . . . . _ . . . . . _ mcway...@comcast.net >> 408-234-8023 >> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
