Date   

locked Re: Rig forced to VFO A by WSJT-X #Windows 10 #Cat_RigControl #Windows10 #WSJTX_config

Gilbert Baron
 

What a stupid restriction for a general use module. Unbelievable.

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Sunday, October 3, 2021 10:52
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Rig forced to VFO A by WSJT-X #Windows 10 #WSJT-X_Config #Cat_RigControl

On 03/10/2021 16:32, Ricky Gilliland via groups.io wrote:
Currently using WSJT-X version 2.3.0 oc42df. After upgrading to 2.5.0
the software pre-selects VFO-A at start up instead of VFO-B which the
rig is set to. Previous versions always read the rig correctly. When I
press Test Cat in settings the software switches back to VFO-A. Is
there a setting I need to change in this new version or is this a glitch?
Hi Ricky,

the Hamlib developers have decided that to use their library the rig must be on VFO A. I understand that this is a new restriction but I doubt that it will change. Is there any particular reason why selecting VFO B is important with your rig?

73
Bill
G4WJS.




--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


locked Re: Changed to new computer, no receive audio #Yaesu #signalink #Windows10 #AudioIssues

Wayne Rash
 

Hi Bill,

I just checked. Yes, WSJT-X is allowed access under the privacy settings. 

Wayne, N4HCR 


On Oct 3, 2021, at 4:25 AM, Bill Somerville <g4wjs@...> wrote:


On 03/10/2021 04:08, Wayne Rash wrote:

I just changed to a new computer for using with ham radio, and I’ve installed WSJT-X. It’s a Windows 10 computer, the radio is a Yaesu FT-920. I’m using a SignalLink USB for the external sound card. I have the current version of Log4OM installed and working. WSJT-X can see the radio, the CAT control appears to work properly. But the software isn’t hearing the incoming audio. I’ve checked that the device is set to USB Audio Codec. Log4OM is using Omnirig, which is installed, and appears to be working properly.

 

I know I’m missing something obvious. But I have no idea why it’s not working now. It worked properly on the previous computer.

 

Any thoughts would be appreciated.

 

Thanks

 

Wayne, N4HCR

Hi Wayne,

make sure that WSJT-X is allowed access to microphone devices in the Windows Camera and Microphone Privacy settings.

73
Bill
G4WJS.





locked Re: Rig forced to VFO A by WSJT-X #Windows 10 #Cat_RigControl #Windows10 #WSJTX_config

Bill Somerville
 

On 03/10/2021 16:32, Ricky Gilliland via groups.io wrote:
Currently using WSJT-X version 2.3.0 oc42df. After upgrading to 2.5.0 the software pre-selects VFO-A at start up instead of VFO-B which the rig is set to. Previous versions always read the rig correctly. When I press Test Cat in settings the software switches back to VFO-A. Is there a setting I need to change in this new version or is this a glitch?
Hi Ricky,

the Hamlib developers have decided that to use their library the rig must be on VFO A. I understand that this is a new restriction but I doubt that it will change. Is there any particular reason why selecting VFO B is important with your rig?

73
Bill
G4WJS.


locked Rig forced to VFO A by WSJT-X #Windows 10 #Cat_RigControl #Windows10 #WSJTX_config

Ricky Gilliland
 

Currently using WSJT-X version 2.3.0 oc42df. After upgrading to 2.5.0 the software pre-selects VFO-A at start up instead of VFO-B which the rig is set to. Previous versions always read the rig correctly. When I press Test Cat in settings the software switches back to VFO-A. Is there a setting I need to change in this new version or is this a glitch?


locked Re: Intermittent Decodes #adiFiles #decode

Luis F. Arango Arango
 

Are you running it in windows 10 and suffered  an update lately?
If so, try downloading  and running “DPC Latency Checker”. Run it before start WSJT-X and keep it running…

El El jue, 30 de sep. de 2021 a la(s) 1:42 a. m., Mike ZooLoo <aa0mz.usa@...> escribió:
I've suddenly found myself with a screen full of signals and very few decodes.  (If I received 10 signals I might get two decodes or none at all) Without going into the obvious (yes, the timing is right. No my computer is not over tasked with running other programs. No I am not receiving signals too strong.) I don't know why it has suddenly done this.  I am guessing someone has encountered something similar. I have been using WSJT for years so no settings have changed. I did upgrade to 2.5.0 but don't think that is the issue. Looking at the waterfall as solely a visual indicator it appears the signals are not as crisp as they once were (kinda distorted).  I've come to the point I might have to just delete everything and restart from scratch.  I hate to do that.  I've culled all previous comments regarding audio settings and no changes. I'm sure it is something simple and stupid. Any ideas on a simple solution would be appreciated. Rig is Icom 7300 and running HF USB-D.


--
Luis F. Arango


locked Re: Changed to new computer, no receive audio #Yaesu #signalink #Windows10 #AudioIssues

Bill Somerville
 

On 03/10/2021 04:08, Wayne Rash wrote:

I just changed to a new computer for using with ham radio, and I’ve installed WSJT-X. It’s a Windows 10 computer, the radio is a Yaesu FT-920. I’m using a SignalLink USB for the external sound card. I have the current version of Log4OM installed and working. WSJT-X can see the radio, the CAT control appears to work properly. But the software isn’t hearing the incoming audio. I’ve checked that the device is set to USB Audio Codec. Log4OM is using Omnirig, which is installed, and appears to be working properly.

 

I know I’m missing something obvious. But I have no idea why it’s not working now. It worked properly on the previous computer.

 

Any thoughts would be appreciated.

 

Thanks

 

Wayne, N4HCR

Hi Wayne,

make sure that WSJT-X is allowed access to microphone devices in the Windows Camera and Microphone Privacy settings.

73
Bill
G4WJS.


locked Changed to new computer, no receive audio #Yaesu #signalink #Windows10 #AudioIssues

Wayne Rash
 

I just changed to a new computer for using with ham radio, and I’ve installed WSJT-X. It’s a Windows 10 computer, the radio is a Yaesu FT-920. I’m using a SignalLink USB for the external sound card. I have the current version of Log4OM installed and working. WSJT-X can see the radio, the CAT control appears to work properly. But the software isn’t hearing the incoming audio. I’ve checked that the device is set to USB Audio Codec. Log4OM is using Omnirig, which is installed, and appears to be working properly.

 

I know I’m missing something obvious. But I have no idea why it’s not working now. It worked properly on the previous computer.

 

Any thoughts would be appreciated.

 

Thanks

 

Wayne, N4HCR


locked Re: Help with set up. #Icom #Cat_RigControl

vk4aac@...
 

Hi all,
Have had absolutely no luck with WSJTx, so changed to JTDX and no problem, working just fine. Have made many contacts.
Not sure why JTDX is working and WSJTx is not, but a good outcome for me at least.

Thanks to all responders.

73
Rob


locked Re: WSJT-X and 630 meters, a match made in heaven #FST4 #FST4W

Mark ~ AE2EA <mark.erdle@...>
 

Peter,
The SAC PC-1000 autocoupler is the real prize in my 630 meter station. My transmitter is a SAC SS-250C with only 25 watts output and the EIRP is estimated somewhere between 20 dbm and 26 dbm, so a more powerful amplifier is in my future, along with some antenna improvements. Still, I've made 3500 km JT9 contacts when conditions are good.

I've played around with the -900 and -1800 modes, but my FTDX-3000 has too much frequency drift over those time periods. I've been thinking of programming my GPSDO locked arbitrary waveform generator as a FST4W exciter. If I do I might give 2200 meters a shot.

I enjoyed reading your QRZ page and have downloaded your amplifier info for inspiration. Thanks.

73, Mark ~ AE2EA


locked Re: General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

Jim Brown
 

On 10/2/2021 1:23 PM, Bill, WB6JJJ wrote:
Maybe my location is extra quiet?
Hi Bill,

Signal reports in FT8 are signal to noise ratio, the differences you're seeing are usually the result of high noise levels on the other end. Another reason would be if the other station is using JTDX -- the current beta, which I'm using because it decodes some weak signals that WSJT-X misses (at least before the new 2.50 general release), is brain dead with respect to signal reports, giving very low ones.

73, Jim K9YC


locked Re: FT-1000MP frequency shift on transmit with FT-1000MP with SignaLink USB? #Yaesu #FT8

Mike KM2B
 

On Sat, Oct 2, 2021 at 12:53 PM, Bill Somerville wrote:
make sure you have the DELAY knob on the SignaLink USB interface set to minimum.
Bill, 

Bingo!!!!

I went down to the basement and the SignaLink USB delay was set half way between min and max (pointed straight up).

I rotated it completely counter clockwise to minimum and everything is back to working correctly without receive frequency shift with "fake it".

I cannot tell you how much I appreciate your input and thank you again.

Mike KM2B
 
--
Mike - KM2B


locked Re: Possible bug with tune button on 2.5.0 GA #IssueReport #Yaesu #Cat_RigControl #transmit

Jason B
 
Edited

I'll try that Jeff. It's the special formula W1ND3x right?


locked Re: Possible bug with tune button on 2.5.0 GA #IssueReport #Yaesu #Cat_RigControl #transmit

Jason B
 

No problem with regular transmissions, only with the tune button. Everything else seems to work fine except for every once in a while for some reason when I click to log a QSO it starts trying to contact someone else.


locked Re: FT-1000MP frequency shift on transmit with FT-1000MP with SignaLink USB? #Yaesu #FT8

Mike KM2B
 

Bill,

I will check that.   I may have been moved but generally that is where it is.   

Thank you again.

Mike
--
Mike - KM2B


locked Re: FT-1000MP frequency shift on transmit with FT-1000MP with SignaLink USB? #Yaesu #FT8

Mike KM2B
 

William,

Good thought!   Thanks.  I will check for RFI this evening or in the morning and let you know.

Appreciate your response
--
Mike - KM2B


locked Re: Command line decoding of wav files containing FST4W signals #FST4W

Rob Robinett
 

Hi Bill,

Magic!  Thanks so much!

Decodes now work on not only a single wav file, but also on a list of wav files which together contain the signal.

Can I find a description of the meaning of the spot line fields?

73,

Rob

rob@Robs-MBP:/Users/rob/jt9> cat decoded.txt
0000   0   27   0.4   1590.   0   WB7ABP CM88 27                        FST4
rob@Robs-MBP:/Users/rob/jt9> /Applications/wsjtx.app/Contents/MacOS/jt9  -W -p 120 -L 1400 -H 1600 -f 1500 -F 100  -d 3  20211002T035000Z_474200_usb.wav 20211002T035100Z_474200_usb.wav
 EOF on input file 20211002T035000Z_474200_usb.wav
0000  27  0.4 1590 `  WB7ABP CM88 27
<DecodeFinished>   0   1        0
 EOF on input file 20211002T035100Z_474200_usb.wav
<DecodeFinished>   0   0        0
rob@Robs-MBP:/Users/rob/jt9> cat decoded.txt
0000   0   27   0.4   1590.   0   WB7ABP CM88 27                        FST4
rob@Robs-MBP:/Users/rob/jt9>


On Sat, Oct 2, 2021 at 10:56 AM Bill Somerville <g4wjs@...> wrote:
Hi Rob,

here's an example of usage with the FST4W-1800 sample file that you can download with the WSJT-X v2.5.0 "Menu->Help->Download Samples ..." tool:
C:>\WSJT\wsjtx\bin\jt9 -W -p 1800 -L 1400 -H 1600 -f 1500 -F 100 -d 3 "%LocalAppData%\WSJT-X\save\samples\FST4+FST4W\201230_0300.wav"
0300 -44  0.3 1433 `  DL0HOT JO60 30
<DecodeFinished>   0   1        0
73
Bill
G4WJS.

On 02/10/2021 18:12, Rob Robinett wrote:
Ooops, I forgot the -F 20, but adding that doesn't affect the output:

jt9  -L 1400 -H 1600 -f 1500 -d 1 -F 20 -p 120 -W 211002_0350.wav
<DecodeFinished>   0   0        0


On Sat, Oct 2, 2021 at 10:10 AM Rob Robinett <rob@...> wrote:
Hi Bill,

Unfortunately, adding those flags doesn't affect the output:

jt9  -L 1400 -H 1600 -f 1500 -d 1 -p 120 -W 211002_0350.wav
<DecodeFinished>   0   0        0

Rob

On Sat, Oct 2, 2021 at 9:58 AM Bill Somerville <g4wjs@...> wrote:
On 02/10/2021 16:29, Rob Robinett wrote:
Hello,
 
I am trying to add FST4W support to version 3.0 of my wspedaemon service (https://github.com/rrobinett/wsprdaemon ) run by many of the top spotting sites worldwide. My goal is to encourage the adoption of FST4W by enabling dozens of sites worldwide to start listening for FST4W on all the appropriate bands 24/7/365, just as they currently do for WSPR transmissions.
 
For WSPR decoding I execute the 'wsprd' binary from the WSJT-x 2.5.0 giving it a 2 minute long wav file, e.g.:    /usr/bin/wsprd -c -C 500 -o 4 -d -f 1.8366 211002_1450.wav
 
However when I execute a similar jt9 command on a wav file from which WSJT-x displays signals, I get no spots:   
 
/usr/bin/jt9  -p 120 -W 211002_0350.wav
  0   0        0
 
I can see that a successful decode by WSJT-x of that file runs jt9 through a shared memory interface, but that would be awkward to use in my SW environment.
Ideally, I would like to give jt9 a list of 2 or more one minute long wav files which would optimize the use of disk space when attempting to decode all of the FST4W modes.
 
Thanks for any help.  73
 
Rob

Hi Rob,

you will need to set the frequency and decode depth arguments.

-L HERTZ
--lowest HERTZ
   Lowest frequency decoded (JT65), default HERTZ=200
-H HERTZ
--highest HERTZ
   Highest frequency decoded, default HERTZ=4007
-f HERTZ
--rx-frequency HERTZ
   Receive frequency offset, default HERTZ=1500
-F HERTZ
--freq-tolerance HERTZ
   Receive frequency tolerance, default HERTZ=20
-d DEPTH
--depth DEPTH
   Decoding depth (1-3), default DEPTH=1

73
Bill
G4WJS.







--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


locked Re: General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

Bill, WB6JJJ
 

Hmmm, my IC-7610 states more than 3500 Hz and does receive that entire bandwidth.  I have never restricted the width.  There are times that I receive similar TX and RX reports but they are rare.  Maybe my location is extra quiet?  I doubt it…

Bill
WB6JJJ 



On Oct 2, 2021, at 11:29 AM, Bill Somerville <g4wjs@...> wrote:


Hi Bill,

excessively optimistic signal reports are often due to restricted receiver bandwidth. The FT8 decoder relies on a reasonably flat receiver bandwidth across the displayed waterfall, and at least 2500 Hz wide. Narrower input data bandwidth will cause underestimation of the noise level.

73
Bill
G4WJS.

On 02/10/2021 19:24, Bill, WB6JJJ wrote:
I don’t feel so bad…. I have been giving +10 to +20 but receiving -15 to -20 dB.
Bill
WB6JJJ 


On Oct 2, 2021, at 9:09 AM, Joe Dz <joedzekevich@...> wrote:



I noticed a similar thing on the evening of 10/02 on 10m FT8.  There was a good opening from W1 land to LU and PY land, and I was getting -15 to +05 and I was giving out +20 and most around +10.  Interesting.

Joe, K1YOW

 


From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Geoff,G4FKA via groups.io
Sent: Saturday, October 02, 2021 11:43 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

 

Same here, v2.5.0 downloaded and installed perfectly. One thing I do notice is that there seem to be a much wider range of received signal strengths, with quite a few lower than they might have been with previous releases. Maybe WSJT-X, maybe recent Windows updates altering the CODEC settings. No problems operating, just rather disconcerting when I sent -01 to an N4 earlier and got +30 back! 






locked Re: General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

Bill Somerville
 

Hi Bill,

excessively optimistic signal reports are often due to restricted receiver bandwidth. The FT8 decoder relies on a reasonably flat receiver bandwidth across the displayed waterfall, and at least 2500 Hz wide. Narrower input data bandwidth will cause underestimation of the noise level.

73
Bill
G4WJS.

On 02/10/2021 19:24, Bill, WB6JJJ wrote:
I don’t feel so bad…. I have been giving +10 to +20 but receiving -15 to -20 dB.
Bill
WB6JJJ 


On Oct 2, 2021, at 9:09 AM, Joe Dz <joedzekevich@...> wrote:



I noticed a similar thing on the evening of 10/02 on 10m FT8.  There was a good opening from W1 land to LU and PY land, and I was getting -15 to +05 and I was giving out +20 and most around +10.  Interesting.

Joe, K1YOW

 


From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Geoff,G4FKA via groups.io
Sent: Saturday, October 02, 2021 11:43 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

 

Same here, v2.5.0 downloaded and installed perfectly. One thing I do notice is that there seem to be a much wider range of received signal strengths, with quite a few lower than they might have been with previous releases. Maybe WSJT-X, maybe recent Windows updates altering the CODEC settings. No problems operating, just rather disconcerting when I sent -01 to an N4 earlier and got +30 back! 



locked Re: General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

Bill, WB6JJJ
 

I don’t feel so bad…. I have been giving +10 to +20 but receiving -15 to -20 dB.
Bill
WB6JJJ 


On Oct 2, 2021, at 9:09 AM, Joe Dz <joedzekevich@...> wrote:



I noticed a similar thing on the evening of 10/02 on 10m FT8.  There was a good opening from W1 land to LU and PY land, and I was getting -15 to +05 and I was giving out +20 and most around +10.  Interesting.

Joe, K1YOW

 


From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Geoff,G4FKA via groups.io
Sent: Saturday, October 02, 2021 11:43 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

 

Same here, v2.5.0 downloaded and installed perfectly. One thing I do notice is that there seem to be a much wider range of received signal strengths, with quite a few lower than they might have been with previous releases. Maybe WSJT-X, maybe recent Windows updates altering the CODEC settings. No problems operating, just rather disconcerting when I sent -01 to an N4 earlier and got +30 back! 





locked Re: Command line decoding of wav files containing FST4W signals #FST4W

Bill Somerville
 

Hi Rob,

here's an example of usage with the FST4W-1800 sample file that you can download with the WSJT-X v2.5.0 "Menu->Help->Download Samples ..." tool:
C:>\WSJT\wsjtx\bin\jt9 -W -p 1800 -L 1400 -H 1600 -f 1500 -F 100 -d 3 "%LocalAppData%\WSJT-X\save\samples\FST4+FST4W\201230_0300.wav"
0300 -44  0.3 1433 `  DL0HOT JO60 30
<DecodeFinished>   0   1        0
73
Bill
G4WJS.

On 02/10/2021 18:12, Rob Robinett wrote:
Ooops, I forgot the -F 20, but adding that doesn't affect the output:

jt9  -L 1400 -H 1600 -f 1500 -d 1 -F 20 -p 120 -W 211002_0350.wav
<DecodeFinished>   0   0        0


On Sat, Oct 2, 2021 at 10:10 AM Rob Robinett <rob@...> wrote:
Hi Bill,

Unfortunately, adding those flags doesn't affect the output:

jt9  -L 1400 -H 1600 -f 1500 -d 1 -p 120 -W 211002_0350.wav
<DecodeFinished>   0   0        0

Rob

On Sat, Oct 2, 2021 at 9:58 AM Bill Somerville <g4wjs@...> wrote:
On 02/10/2021 16:29, Rob Robinett wrote:
Hello,
 
I am trying to add FST4W support to version 3.0 of my wspedaemon service (https://github.com/rrobinett/wsprdaemon ) run by many of the top spotting sites worldwide. My goal is to encourage the adoption of FST4W by enabling dozens of sites worldwide to start listening for FST4W on all the appropriate bands 24/7/365, just as they currently do for WSPR transmissions.
 
For WSPR decoding I execute the 'wsprd' binary from the WSJT-x 2.5.0 giving it a 2 minute long wav file, e.g.:    /usr/bin/wsprd -c -C 500 -o 4 -d -f 1.8366 211002_1450.wav
 
However when I execute a similar jt9 command on a wav file from which WSJT-x displays signals, I get no spots:   
 
/usr/bin/jt9  -p 120 -W 211002_0350.wav
  0   0        0
 
I can see that a successful decode by WSJT-x of that file runs jt9 through a shared memory interface, but that would be awkward to use in my SW environment.
Ideally, I would like to give jt9 a list of 2 or more one minute long wav files which would optimize the use of disk space when attempting to decode all of the FST4W modes.
 
Thanks for any help.  73
 
Rob

Hi Rob,

you will need to set the frequency and decode depth arguments.

-L HERTZ
--lowest HERTZ
   Lowest frequency decoded (JT65), default HERTZ=200
-H HERTZ
--highest HERTZ
   Highest frequency decoded, default HERTZ=4007
-f HERTZ
--rx-frequency HERTZ
   Receive frequency offset, default HERTZ=1500
-F HERTZ
--freq-tolerance HERTZ
   Receive frequency tolerance, default HERTZ=20
-d DEPTH
--depth DEPTH
   Decoding depth (1-3), default DEPTH=1

73
Bill
G4WJS.


6561 - 6580 of 35492