subject:"\[wsjt\-devel\] Hamlib testing"

Re: [wsjt-devel] Hamlib testing

2023-06-12 Thread Marco Calistri via wsjt-devel


Will do it Mike,

I will do it when radio is still cold, in order to avoid to have the 
thermal drift as a possible cause, since I think the reason is another.


Regards,

---
*73 de Marco, PY1ZRJ (former IK5BCU)*



**
Il 12/06/23 17:27, Black Michael ha scritto:

Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0


 C:\Users\[username]\AppData\Local\WSJT-X
 The WSJT-X_Rigcontrol.log file will be in the same location


For Linux put it in
 ~/.config
 The WSJT-X_Rigcontrol.log file will be here:
 ~/.local/share/WSJT-X


For MacOS put it in
 /Users/[username]/Library/Preferences
  
Restart WSJT-X and duplicate the problem.

Shut down WSJT-X


Then send me the WSJT-X_RigControl.log file
Mike W9MDB



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing

2023-06-12 Thread Daniele Forsi via wsjt-devel

Black Michael wrote:

> Need people to test the latest Hamlib please

it works fine for me with an FT-991 on Debian 12

-- 
73 de IU5HKX Daniele


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing

2023-06-12 Thread Black Michael via wsjt-devel

Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0


C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location


For Linux put it in  
~/.config
The WSJT-X_Rigcontrol.log file will be here:
~/.local/share/WSJT-X


For MacOS put it in
/Users/[username]/Library/Preferences
 
Restart WSJT-X and duplicate the problem.
Shut down WSJT-X


Then send me the WSJT-X_RigControl.log file
Mike W9MDB



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing

2023-06-12 Thread Marco Calistri via wsjt-devel

Tested new version compiled from git repository and on my old YAESU 
FT-100 I see same behavior I saw with previous Hamlib versions.


I use WSJT-X 2.7.0 RC1 with settings Split=RIG and Mode= Data Packet and 
at the very beginning of the operation, the VFO A (Transmitter) and VFO 
B (Receiver) behave in this way:


I make the first CQ, VFO A transmit 1 KHz below, so VFO B then moves 1 
KHz below its original frequency, at second CQ VFO B is then 2 KHz below 
the starting frequency.


I have to correct manually this behavior by clicking again on the band 
frequency I was using and have to do it two or three times, until the 
radio finally stabilize and then the shift keeps constant among VFO A 
and B of the value which depends by the TX audio I selected, I.E. if I 
use 777 Hz, the SPLIT shift between VFO's is 1 KHz and it remains stable.


This is not a major issue for me but I would like to report it here.

Best regards,

---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**

Il 11/06/23 00:18, Black Michael via wsjt-devel ha scritto:

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


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing -Testing IC-7300/IC-705, IC-7610 Results

2023-06-11 Thread Gene Hinkle via wsjt-devel

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

2023-06-11 Thread Black Michael via wsjt-devel

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 --

44 matches

Mail list logo