Version prior to v2.6 does not crash. RFI ? Is v2.6 more sensitive to RFI ?
toggle quoted messageShow quoted text
Regarding loosing the CAT connection, it happens during Rx when I turn the Rig VFO. This was not any issue until I installed v2.6. Just press "Retry" if WSJT-x lost the connection. It doesn't work any longer. Only reboot restores USB the connection.
I have plenty of Ferrites on all cables (mostly Fair-Rite of different kinds). I would say I spent >$1000 on ferrites to reduce RFI issues and also reduce noise from all the normal noise sources in a home. This includes some of my neighbors homes as well.
On 2022-09-22 05:11, Michael Black via groups.io wrote:
What you're describing sounds like RFI.
If problems are occurring only during transmit:
#1 Reduce power to zero and see if the problem stops -- if it does stop than it is definitely RFI. You will see certain higher power levels on certain bands that cause problems.
Then, if problems are occurring during non-transmit periods it indicates a system problem with USB devices so...
#1 Check USB Power Management option is turned off on all USB devices
Device Manager for Windows.
For Linux set autosuspend=-1 https://docs.kernel.org/driver-api/usb/power-management.html
#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.
Common grounding mistakes, sources, and solutoins:
A. Ground rod outside the shack that is not bonded to the main house ground.
B. Shack equipment bonded incorrectly (e.g. daisy chained instead of common ground point)
C. Desktop computer grounded to the house ground and not the shack ground. Run a separate RF ground from the computer chassis to your station RF ground.
For a laptop use the retaining screw of a DB9 or DB25 connector shell, if your device still has them.
D. Ethernet cables that bring RFI into the computer...which then ends up going to the rig too since the ethernet shield is tied to the case which is tied to USB shield which is tied to pin 4 on the USB cable (a very common problem on most all USB devices -- see my QRZ page).
Ethernet patch cables up through CAT6 are UTP, which stands for UNSHIELDED Twisted Pairs, four to be specific. There is NO separate shield conductor in the jacket, nor a metallic shield around the RJ45 connector itself.
Just use a ferrite toroid at each end.
E. Wall warts -- 24VAC supplies in sprinkler and alarm systems are notorious for picking up RFI into your electrical system.
24 VAC transformers can be RF-bypassed using .005 ufd caps from each output lead to safety ground. You can often use the cover plate mounting screw as your ground connection.
F. Speaker wires The same approach as E also works for external speaker audio leads.
G. Lamps (yes...lamps around the house have unshielded wires as do many other appliances).
H. Washer/Dryers are notorious for generating and picking up RFI. In general, newer high-efficiency models have more RF problems.
Ferrite toroids INSIDE the appliance housing can work wonders if the wiring harness has connectors in the AC line input, OR an external noise filter for the AC line cord of a washing machine can reduce RF spurs by 25 dB or more.
I. HVAC systems with variable speed blower control systems both cause RF noise and react badly to RF fields -- we believe adding torroids inside the unit on the power lines will work.
J. If you use a powered USB expansion hub, add a ferrite toroid on the cable coming from the USB power supply.
K. SignaLink -- You can ground the metal box shell by simply wrapping an 18ga wire (or use a small crimped ring or spade terminal) under the head of any of the screws holding the rear panel, then connect to your station RF ground.
The case is isolated from both USB and analog audio signal grounds, so this does not affect use of the USB shield isolators.
L. DC power supply -- both linear and switching -- READ THE PS MANUAL FIRST! This step may void some manufacturers' warranty and UL/CSA approvals.
Remove any jumpers between the DC negative output lead and PS chassis or line cord ground Add a .005 ufd cap from each DC output lead to chassis ground if not already there.
NOTE: Samlex DC outputs are already isolated and bypassed, but many others, including Astron, may randomly have the negative side grounded and no RF bypassing.
B through L may all need chokes.
#3 Free -- start unplugging devices around the house and see if there's one device that is acting as a bad source of RFI. This presupposes you can easily repeat the problem on your rig setup.
#4 Cheap -- Add some USB shield isolators (see my QRZ page). I use one on my SignaLink for example.
#5 Minimal $$ -- Good USB cables like this
#6 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.
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/
Newark also carries them https://newark.com/c/passive-components/emc-rfi-suppression/ferrites-ferrite-assortments?brand=fair-rite
On Wednesday, September 21, 2022 at 06:01:01 PM CDT, Bengt SM6MUY via groups.io <muy@...> wrote:
Also had this issue. Crashes all the time and the jt9 processing is
running. I had to downgrade to 2.5 but still have the issue with loosing
the CAT connection sometimes which I got when installed 2.6 for the
first time...Only PC reboot helps...
RIG: IC-7300, Win11 64 bit.
On 2022-09-21 17:20, Michael Black via groups.io wrote:
What rig do you have?
I notice QRZ doesn't know your callsign. You might want to add it.
On Wednesday, September 21, 2022 at 09:57:57 AM CDT, JH4VAJ / mit <jh4vaj@...> wrote:
WSJT-X 2.6.0-rc4 without CAT control rarely crashes.
The timing of the crash is when WSJT-X switches to transmit.
It does not crash while receiving.
After it crashes, the jt9.exe process remains running.
I have experienced this problem several times.
It does not crash when used with CAT control.
It also does not crash with 2.5.4 without CAT control.
I am using Windows 10 64-bit.