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! 

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! 

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.

On Oct 2, 2021, at 12:14 PM, mike s <mike.km2b@...> wrote:

Bill,

Thank you. Thank you for the clarification of the frequency shift.

Yes, I have been using "fake it" to split the transceiver transmit frequency from the receive frequency for about two years with zero problems.

Two days ago, however, both the receive frequency and the transmit frequency began to move. By the third transmission in a sequence during a QSO, I can no longer hear any of the FT8 signals in the passband anymore and I have lost the contact I was making......without fail.

On the video I posted you can see the receive frequency stepping away from its first setting which is where I started after setting the frequency for 80m using wsjt-x.

Something disabling and different is happening and any other thoughts you might have would be great. I completely understand fake it moves the transmit frequency around to manage where in the passband transmit occurs.

But, the receive frequency, my perception, never changed before. It stayed on the frequency set by wsjt-x.

Thank you again.


--
Mike - KM2B

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!