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/B003MQ29B2/ref=sr_1_5?crid=11YRNPWDVWGCU&keywords=usb+cable+with+choke&qid=1658187349&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-toroid-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 mailto:mcway...@comcast.net > 408-234-8023 > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net mailto: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
