Locked No decode on 40m, Band Activity blank #FT8


KG2RG
 

New to digital, but I’m having an issue on 40m only. There is a lot of signals on 7.077 on the waterfalls but nothing is decoding into the band activity box. Transmit also works fine.

This issue is only on 40m. I have made many contacts and the band activity fills up fast with station traffic. Crazy thing is that 40m is my strongest band with a quality ant. I’ve checked all of the filters and I’m listening 3K wide.


Chuck Gelm
 

On 7/13/22 02:54, KG2RG wrote:
New to digital, but I’m having an issue on 40m only. There is a lot of signals on 7.077 on the waterfalls but nothing is decoding into the band activity box. Transmit also works fine.

This issue is only on 40m. I have made many contacts and the band activity fills up fast with station traffic. Crazy thing is that 40m is my strongest band with a quality ant. I’ve checked all of the filters and I’m listening 3K wide.
I think...
You should be on USB and dial 7074 kHz.
If your receiver is on 7077 LSB, WSJT-X will not decode but the waterfall will look 'normal'.
Your bandpass should be about 7074.2 through 7077 kHz.
IOW, your receiver should be passing audio tones from ~200 to ~3000 Hz to WSJT-X.

Hope this helps,
Chuck


Kevin k5vp
 

7.077 is where JT65 is or was.

FT8 on 40m is on 7.074. Look there for FT8.

Best regards,

*Kevin Potter *
*k5vp*

On Wed, Jul 13, 2022 at 1:42 AM KG2RG <justinandyazny@...> wrote:

New to digital, but I’m having an issue on 40m only. There is a lot of
signals on 7.077 on the waterfalls but nothing is decoding into the band
activity box. Transmit also works fine.

This issue is only on 40m. I have made many contacts and the band activity
fills up fast with station traffic. Crazy thing is that 40m is my
strongest band with a quality ant. I’ve checked all of the filters and I’m
listening 3K wide.






Tim Dawson
 

Are you correctly set to USB?

On July 13, 2022 2:54:24 AM EDT, KG2RG <justinandyazny@...> wrote:
New to digital, but I’m having an issue on 40m only. There is a lot of signals on 7.077 on the waterfalls but nothing is decoding into the band activity box. Transmit also works fine.

This issue is only on 40m. I have made many contacts and the band activity fills up fast with station traffic. Crazy thing is that 40m is my strongest band with a quality ant. I’ve checked all of the filters and I’m listening 3K wide.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


alanbeal@...
 

I am experiencing the same thing right now. Windows 11, WSJT-X v2.5.4, Yaesu FTDX10. 20 meters (14.074) is fine, 40 meters (7.074) no decoding. It used to work. Set to LSB on 40 meters, USB on 20 meters. I have an ICOM 7300 and I will try it on 40 meters tonight.


Larry Banks
 

It is USB everywhere!

Larry / W1DYJ

On 7/13/2022 14:06, alanbeal@... wrote:
I am experiencing the same thing right now. Windows 11, WSJT-X v2.5.4, Yaesu FTDX10. 20 meters (14.074) is fine, 40 meters (7.074) no decoding. It used to work. Set to LSB on 40 meters, USB on 20 meters. I have an ICOM 7300 and I will try it on 40 meters tonight.




Pietro Molina
 

this is the solution. if you don't have a dig mode, you MUST set USB also
in 40 and 80 meters.

Pietro I2OIM

Il giorno mer 13 lug 2022 alle ore 21:09 Larry Banks via groups.io
<larryb.w1dyj@...> ha scritto:

It is USB everywhere!

Larry / W1DYJ



On 7/13/2022 14:06, alanbeal@... wrote:
I am experiencing the same thing right now. Windows 11, WSJT-X v2.5.4,
Yaesu FTDX10. 20 meters (14.074) is fine, 40 meters (7.074) no decoding.
It used to work. Set to LSB on 40 meters, USB on 20 meters. I have an
ICOM 7300 and I will try it on 40 meters tonight.









Andy Talbot
 

Too many peo-ple are mixing up
USB - Universal Serial Bus
USB - Upper SideBand

Use USB on all bands for data modes
Does no one read the manual - it says it quite clearly in there.
*Use UpperSideBand*


Andy
www.g4jnt.com


fritz1000@...
 

I don't see anywhere that this was suggested. Open WSJT-X. Set operation to 40m. Go to the WSJT-X "MODE" drop down menu. Verify that FT8 has a check next to it.


Jim Shorney
 

Second line in section 5 of the WSJT-X User Guide:

Be sure your transceiver is set to USB (or USB Data) mode.

73

-Jim
NU0C

On Wed, 13 Jul 2022 16:30:13 -0700
"fritz1000 via groups.io" <fritz1000@...> wrote:

I don't see anywhere that this was suggested. Open WSJT-X. Set operation to 40m. Go to the WSJT-X "MODE" drop down menu. Verify that FT8 has a check next to it.





alanbeal@...
 

One reader of this group sent me an email about FT8 being USB on all bands. I tried USB on 40 meters and decoding started working again. I thought my configuration was broken but as it turns out, my mistake was setting the radio to LSB on 40 meters. I made the mistake of assuming the mode was the same as SSB on that band. The funny thing is I had used FT8 on 40 meters on that radio in the past and it worked, but I had not noticed the radio was in USB mode. Thanks for the help.


VE3KTN
 

I'm seeing a similar kind of problem where WSJT-X (v2.4.0) will stop decoding if the setup is left untouched for a few hours and is only doing Monitoring. It happens regardless of band. At first I thought it might be something funny coming from JTAlert as I only started using it a few days ago, but with only WSJT-X running, it still stops decoding after sitting untouched for a few hours. Signals are on the waterfall and it's falling normally, the cycle timer is running, the DECODE indicator flashes at the right time but nothing shows in the Band Activity window and nothing shows up on JTAlert. If WSJT-X is decoding, it's not releasing the results.

This does not happen if I'm operating fairly regularly for several hours, e.g. it worked without a hitch over Field Day but now, if I leave the computer and radio alone, WSJT-X will stop releasing decodes after a while. It's lilke some user action on the computer is needed to reset a watchdog timer (I've got the TX watchdog set to Disable).

Now, I know I'm using an older release of WSJT-X, but it works fine for me and I probably won't be upgrading until 2.6.0 is released. Nevertheless, I think there have been other posts here reporting the same problem with 2.5.0 and maybe also RC2.6.

This is NOT a USB/LSB issue. I know what sideband to use for FT4/8. The only way to get things going again is to close WSJT-X and launch it again.

Anyone in the know have any ideas?

73,

Hugo, ve3ktn.


Kevin k5vp
 

Clock drifting?

Best regards,

*Kevin Potter *
*k5vp*

On Mon, Jul 18, 2022 at 7:25 PM VE3KTN <hal9k@...> wrote:

I'm seeing a similar kind of problem where WSJT-X (v2.4.0) will stop
decoding if the setup is left untouched for a few hours and is only doing
Monitoring. It happens regardless of band. At first I thought it might be
something funny coming from JTAlert as I only started using it a few days
ago, but with only WSJT-X running, it still stops decoding after sitting
untouched for a few hours. Signals are on the waterfall and it's falling
normally, the cycle timer is running, the DECODE indicator flashes at the
right time but nothing shows in the Band Activity window and nothing shows
up on JTAlert. If WSJT-X is decoding, it's not releasing the results.

This does not happen if I'm operating fairly regularly for several hours,
e.g. it worked without a hitch over Field Day but now, if I leave the
computer and radio alone, WSJT-X will stop releasing decodes after a
while. It's lilke some user action on the computer is needed to reset a
watchdog timer (I've got the TX watchdog set to Disable).

Now, I know I'm using an older release of WSJT-X, but it works fine for me
and I probably won't be upgrading until 2.6.0 is released. Nevertheless, I
think there have been other posts here reporting the same problem with
2.5.0 and maybe also RC2.6.

This is NOT a USB/LSB issue. I know what sideband to use for FT4/8. The
only way to get things going again is to close WSJT-X and launch it again.

Anyone in the know have any ideas?

73,

Hugo, ve3ktn.






Mike Black
 

When that happens check http://time.is and see if you clock is correct (i.e. the site will say "exact").

Mike W9MDB

On Monday, July 18, 2022 at 09:25:30 PM CDT, VE3KTN <hal9k@...> wrote:





I'm seeing a similar kind of problem where WSJT-X (v2.4.0) will stop decoding if the setup is left untouched for a few hours and is only doing Monitoring.  It happens regardless of band.  At first I thought it might be something funny coming from JTAlert as I only started using it a few days ago, but with only WSJT-X running, it still stops decoding after sitting untouched for a few hours.  Signals are on the waterfall and it's falling normally, the cycle timer is running, the DECODE indicator flashes at the right time but nothing shows in the Band Activity window and nothing shows up on JTAlert.  If WSJT-X is decoding, it's not releasing the results.

This does not happen if I'm operating fairly regularly for several hours, e.g. it worked without a hitch over Field Day but now, if I leave the computer and radio alone, WSJT-X will stop releasing decodes after a while.  It's lilke some user action on the computer is needed to reset a watchdog timer (I've got the TX watchdog set to Disable).

Now, I know I'm using an older release of WSJT-X, but it works fine for me and I probably won't be upgrading until 2.6.0 is released.  Nevertheless, I think there have been other posts here reporting the same problem with 2.5.0 and maybe also RC2.6.

This is NOT a USB/LSB issue.  I know what sideband to use for FT4/8.  The only way to get things going again is to close WSJT-X and launch it again.

Anyone in the know have any ideas?

73,

Hugo, ve3ktn.


Reino Talarmo
 

Hi Hugo,

There is one known issue at least in older versions of WSJT-X that may be a reason for "non-decoding". Do you have in General tab in the Display section activated the Start new period decodes at top? I have been running WSJT-X without it now almost two years 24/7 and have had no problem. At least earlier the display stopped after an extended period, but the decodes were there and could be seen by rolling the display. I had to erase the display now and then to keep it working.

I don't have JTAlert in use, so don't know how it behaves in that situation.

73, Reino OH3mA


 

I had the same problem, but it stopped when I upgraded to the latest WSJTX.
Kerry WB7AKE

On Jul 18, 2022, at 10:42 PM, Reino Talarmo <reino.talarmo@...> wrote:

Hi Hugo,

There is one known issue at least in older versions of WSJT-X that may be a reason for "non-decoding". Do you have in General tab in the Display section activated the Start new period decodes at top? I have been running WSJT-X without it now almost two years 24/7 and have had no problem. At least earlier the display stopped after an extended period, but the decodes were there and could be seen by rolling the display. I had to erase the display now and then to keep it working.

I don't have JTAlert in use, so don't know how it behaves in that situation.

73, Reino OH3mA






Dave Garber <ve3wej@...>
 

I have had this issue for a couple of versions, but mostly since I have
been including Slice Master. if I restart either wsjt or SM , audio returns

Dave Garber
VE3WEJ / VE3IE

On Mon, Jul 18, 2022 at 10:25 PM VE3KTN <hal9k@...> wrote:

I'm seeing a similar kind of problem where WSJT-X (v2.4.0) will stop
decoding if the setup is left untouched for a few hours and is only doing
Monitoring. It happens regardless of band. At first I thought it might be
something funny coming from JTAlert as I only started using it a few days
ago, but with only WSJT-X running, it still stops decoding after sitting
untouched for a few hours. Signals are on the waterfall and it's falling
normally, the cycle timer is running, the DECODE indicator flashes at the
right time but nothing shows in the Band Activity window and nothing shows
up on JTAlert. If WSJT-X is decoding, it's not releasing the results.

This does not happen if I'm operating fairly regularly for several hours,
e.g. it worked without a hitch over Field Day but now, if I leave the
computer and radio alone, WSJT-X will stop releasing decodes after a
while. It's lilke some user action on the computer is needed to reset a
watchdog timer (I've got the TX watchdog set to Disable).

Now, I know I'm using an older release of WSJT-X, but it works fine for me
and I probably won't be upgrading until 2.6.0 is released. Nevertheless, I
think there have been other posts here reporting the same problem with
2.5.0 and maybe also RC2.6.

This is NOT a USB/LSB issue. I know what sideband to use for FT4/8. The
only way to get things going again is to close WSJT-X and launch it again.

Anyone in the know have any ideas?

73,

Hugo, ve3ktn.