Re: [wsjt-devel] wsjt-devel Digest, Vol 112, Issue 11
Since you were asking about the IC705, I loaded the new dll and tried it with my X6100. It worked as it should from 6m > 160m and back with no problems. It also worked fine with my ANAN running Thetis. I will leave the new dll installed and let you know if something shows later. BTW, I did notice the X6100 saves ATT, PRE, and ATU settings by VFO. So, if using ATI in split operation, you do need to tune the ATU while in each VFO. I suspect most other transceivers save preamp/attenuation and ATU tuning by band therefor avoiding this. I will post it to the Xiegu suggestion/bug site. Al Pawlowski Los Osos, CA USA > On Jun 11, 2023, at 11:26, wsjt-devel-requ...@lists.sourceforge.net wrote: > > Send wsjt-devel mailing list submissions to > wsjt-devel@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > or, via email, send a message with subject or body 'help' to > wsjt-devel-requ...@lists.sourceforge.net > > You can reach the person managing the list at > wsjt-devel-ow...@lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of wsjt-devel digest..." > > > Today's Topics: > > 1. Re: Hamlib testing -Testing IC-7300/IC-705, IC-7610 Results > (Gene Hinkle) > 2. Re: Hamlib testing -Testing IC-7300/IC-705, IC-7610 Results > (Black Michael) > 3. Re: Hamlib testing -Testing IC-7300/IC-705, IC-7610 Results > (Gene Hinkle) > > > -- > > Message: 1 > Date: Sun, 11 Jun 2023 09:04:53 -0500 > From: Gene Hinkle > To: Black Michael via wsjt-devel > Subject: Re: [wsjt-devel] Hamlib testing -Testing IC-7300/IC-705, > IC-7610 Results > Message-ID: > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > *_Testing IC-7300/IC-705, IC-7610 Results_* > > Mike, on the IC-7610 so far the new *libhamlib-4.dll* seems to work. > > On the IC-705 and the IC-7300 however: > > The WSJT-X program /*crashes */if I start either radio from 7.074 MHz or > higher and THEN change the band setting drop down to 80m e.g., 3.573 MHz > or lower and do a TUNE transmit. It works OK at on 7.074 MHz and above > frequencies but when I then drop to 3.573 MHz or the 1.840 MHz band and > TUNE for Transmit it will crash and I have to then restart the program > which then immediately crashes and a second restart operates correctly > works unless I repeat the sequence I state above. > > I should note that in both radio test cases, they are being operated > from different computers, in fact all radios have their own computers. > > I will be out most of the morning to church but back in the afternoon CDST. > > 73, Gene, K5PA > > > > > > > On 6/10/2023 10:18 PM, Black Michael via wsjt-devel wrote: >> Need people to test the latest Hamlib please >> >> https://n0nb.users.sourceforge.net/ >> >> #1 Backwards compatibility with WSJT-X has been fixed. >> #2 Notable speedups for Windows operations >> Here's an FT-991 comparison >> Old: >> ?1:rig_get_freq: elapsed=16ms >> ?1:rig_get_freq: elapsed=17ms >> ?1:rig_get_split_vfo: elapsed=30ms >> ?1:rig_get_mode: elapsed=47ms >> ?1:rig_get_ptt: elapsed=17ms >> New: >> ?1:rig_get_freq: elapsed=6ms >> ?1:rig_get_freq: elapsed=6ms >> ?1:rig_get_split_vfo: elapsed=14ms >> ?1:rig_get_mode: elapsed=13ms >> ?1:rig_get_ptt: elapsed=4ms >> >> Mike W9MDB >> >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > -- > -- Gene > -- next part -- > An HTML attachment was scrubbed... > > -- > > Message: 2 > Date: Sun, 11 Jun 2023 15:03:46 + (UTC) > From: Black Michael > To: Gene Hinkle via wsjt-devel > Subject: Re: [wsjt-devel] Hamlib testing -Testing IC-7300/IC-705, > IC-7610 Results > Message-ID: <715399477.1421189.1686495826...@mail.yahoo.com> > Content-Type: text/plain; charset=UTF-8 > > Sounds like RFI Problems due to noise on the USB cable > > > Tests > 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 > > > RFI Fixes: > #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
Re: [wsjt-devel] Hamlib testing -Testing IC-7300/IC-705, IC-7610 Results
Both were connected to dummy loads, not antenna. I just repeated now with Multi- Control knob setting power to zero watts output on both the IC-7300 and the IC-705 radios with same results. Question for you, was I to use the WSJT-X v2.7.0-rc1 as originally released or was there another version of it that we should have installed? The testing I did was with the originally released candidate WSJT-X but with your updated libhamlib-4.dll installed per your email. Gene > On Jun 11, 2023, at 10:11 AM, Black Michael via wsjt-devel > wrote: > > Sounds like RFI Problems due to noise on the USB cable > > > Tests > 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 > > > RFI Fixes: > #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 solutions: > 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. > http://www.k9yc.com/GroundingAndAudio.pdf > #3 Free -- start unplugging devices around the house and see if there's > one device that is acting as a bad
Re: [wsjt-devel] Hamlib testing -Testing IC-7300/IC-705, IC-7610 Results
Sounds like RFI Problems due to noise on the USB cable Tests 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 RFI Fixes: #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 solutions: 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. http://www.k9yc.com/GroundingAndAudio.pdf #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 https://www.amazon.ca/Tripp-U023-006-Device-Ferrite-Chokes/dp/B003MQ29B2/ref=sr_1_5?crid=11YRNPWDVWGCU=usb+cable+with+choke=1658187349=usb+cable+with+choke%2Caps%2C139=8-5 #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 --
Re: [wsjt-devel] Hamlib testing -Testing IC-7300/IC-705, IC-7610 Results
*_Testing IC-7300/IC-705, IC-7610 Results_* Mike, on the IC-7610 so far the new *libhamlib-4.dll* seems to work. On the IC-705 and the IC-7300 however: The WSJT-X program /*crashes */if I start either radio from 7.074 MHz or higher and THEN change the band setting drop down to 80m e.g., 3.573 MHz or lower and do a TUNE transmit. It works OK at on 7.074 MHz and above frequencies but when I then drop to 3.573 MHz or the 1.840 MHz band and TUNE for Transmit it will crash and I have to then restart the program which then immediately crashes and a second restart operates correctly works unless I repeat the sequence I state above. I should note that in both radio test cases, they are being operated from different computers, in fact all radios have their own computers. I will be out most of the morning to church but back in the afternoon CDST. 73, Gene, K5PA On 6/10/2023 10:18 PM, Black Michael via wsjt-devel wrote: Need people to test the latest Hamlib please https://n0nb.users.sourceforge.net/ #1 Backwards compatibility with WSJT-X has been fixed. #2 Notable speedups for Windows operations Here's an FT-991 comparison Old: 1:rig_get_freq: elapsed=16ms 1:rig_get_freq: elapsed=17ms 1:rig_get_split_vfo: elapsed=30ms 1:rig_get_mode: elapsed=47ms 1:rig_get_ptt: elapsed=17ms New: 1:rig_get_freq: elapsed=6ms 1:rig_get_freq: elapsed=6ms 1:rig_get_split_vfo: elapsed=14ms 1:rig_get_mode: elapsed=13ms 1:rig_get_ptt: elapsed=4ms Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- -- Gene ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
