Date   

locked Re: Tail ending my signal #FT8

Austin 2E0MNV
 

On Sat, Jan 30, 2021 at 02:11 PM, Williams, G (af8c) wrote:
So what will happen when near the height of sunspot cycle 25 when on, say, 20m the FT8 waterfall is jammed full with three callers on each slot   (FT8 is decoded "three" times in deep decode per manual) and there's no clear slot?
FT8 is a weak signal mode.  At the height of the Sun spot cycle when all the fun starts, I'll be moving to SSB and some of the other digital modes where you can actually talk to people.  I enjoy FT8 by prowling the bands around greyline times or e-openings for DX.  I don't enjoy FT8 when the band is absolutely jam packed with stations I can talk to SSB just by picking up the mic.  When the bands are packed with FT8, that's the time when I switch over to other modes.
 
--
Austin
2E0MNV


locked Re: WSJT Log Problem #WSJTX_config #FT8

Reino Talarmo
 

Hi Woody,

WSJT-X reads only log files  named WSJTX_LOG.ADI. The “X” is relevant, case is irrelevant. Try to rename it and all should work again!

73, Reino OH3mA

 

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Woody
Sent: 30. tammikuuta 2021 17:45
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT Log Problem #FT8 #WSJTX_config

 

Hi Bill,
TNX for the hint but the log file is named wsjt_log.adi and is located in C:>users>woody>appdata>local>WSJT-X which I believe is the correct name and location.
Must be something else....????
Woody


locked Re: Tail ending my signal #FT8

K8BL BOB LIDDY <k8bl@...>
 

Jon,

I fully agree.

In my experience, WSJT-X runs best with all Filters turned OFF
and the Noise Reduction and Noise Blanker turned OFF. 

Also, I often run into situations where I call someone numerous
times with no response until I land exactly on their frequency. I
have no idea why, but it happens way too often. It bothers me
because it is bad form to call on someone's CQ frequency. But,
I'll do it if nothing else works. WFWL

GL/73,   Bob  K8BL


On Saturday, January 30, 2021, 10:31:05 AM EST, Jon KM8V <perlguy9@...> wrote:


I think a lot of ops think running narrow filters is a good idea. I can't tell you how often I call and call someone, or someone is CQing into the wind and now answering, and only when I move close to or on to their freq suddenly they answer.

Don't run narrow filters people!

73 de KM8V Jon




locked Re: F/H mode malfunction or operator error? #FoxAndHound

ve3ki
 

Perhaps the other stations were not using WSJT-X; maybe they were using MSHV, for example.

73,
Rich VE3KI


On Sat, Jan 30, 2021 at 10:23 AM, John, K9MM wrote:
Hi Jim,

No, that is not the way F/H works. It is supposed to QSY you automatically!

73,

John, K9MM


locked Re: WSJT Log Problem #WSJTX_config #FT8

Woody <woody@...>
 

Hi Bill,
TNX for the hint but the log file is named wsjt_log.adi and is located in C:>users>woody>appdata>local>WSJT-X which I believe is the correct name and location.
Must be something else....????
Woody


locked Band hopping in other modes #Cat_RigControl #FT8 #Timesync

Don Melcher
 

Greeting. I joined seeking a solution to the WSPR band hopping error - and found it!

But the reason I did was because of a new RX only system I’m playing with consisting of a spare Pi 3B+ (does a 4 decode better?), an Icom R-75 (I have three that are unemployed) and a Pixel loop that was also unemployed. A CI-V converter, a USB>Audio dongle and a 1/8” mini patch cord later and I was in business. Cool. So, now to check out performance/propagation, especially on 136 & 472.2 kKz. Crash!!! Here we are!

So, it occurred to me (before looking at WSPR and finding band hopping) that such a function would be fun for other modes.

An SWL mode for logging would be a nice touch well.  
--
Don
W6CZ/W6ZB
DM07bk


locked Re: F/H mode malfunction or operator error? #FoxAndHound

Jim Shorney
 

Yes, I understand that. But in every test I have done you can QSY manually if need be. In fact I recommend that every op learn how to use the software manually because someday your automation will fail you.

73

-Jim
NU0C

On Sat, 30 Jan 2021 07:23:15 -0800
"John, K9MM" <johnb3030@...> wrote:

Hi Jim,

No, that is not the way F/H works. It is supposed to QSY you automatically!

73,

John, K9MM


locked Re: Tail ending my signal #FT8

Jon KM8V
 

I think a lot of ops think running narrow filters is a good idea. I can't tell you how often I call and call someone, or someone is CQing into the wind and now answering, and only when I move close to or on to their freq suddenly they answer.

Don't run narrow filters people!

73 de KM8V Jon


locked Re: F/H mode malfunction or operator error? #FoxAndHound

John, K9MM
 

Hi Jim,

No, that is not the way F/H works. It is supposed to QSY you automatically!

73,

John, K9MM


locked Re: F/H mode malfunction or operator error? #FoxAndHound

John, K9MM
 

Hi Bill,

I'm not seeing any problem with my CAT control. I made about 65 QSOs yesterday on FT8 and FT4. The only issue with one of my QSOs was the F/H attempt with the J28.

The issue with 4U1UN was affecting many people other than me.

73,

John, K9MM


locked Re: Tail ending my signal #FT8

Tony Collett
 

Another explanation is the use of MSHV instead of WSJT-X.

It comes with the ability to restrict the bandwidth the decoder uses to look for signals - Seems it can be set rather narrow and I believe it is set as the default.

Unfortunately while WSJT-X has sensible features they are not all implemented in other variants.

Whilst WSJT stops the TX if you do call Co-channel and the station responds to somebody else it seems other variants manage to keep transmitting every period until they do get answered.

Also several stations are using the multi streaming variant on normal FT8 channels instead of moving to a discrete frequency, something which thankfully you can't do with F&H.....

Cheers
Tony


locked Re: Tail ending my signal #FT8

Tony Collett
 

Hopefully majority of us will be able to make lots of phone contacts and actually talk to each other?

Alternatively use FT4 if you really must use Data - FT modes are wonderful things at the bottom of the cycle (I've certainly worked way more than I thought possible) but when signals are strong there are other watering holes to be investigated.

Regards
Tony G4NBS


locked Re: Tail ending my signal #FT8

Larry Banks
 

We will all be spread out on other, higher bands and using CW and SSB as FT8 will not be needed as much!

73 -- Larry -- W1DYJ

 
Sent: Saturday, January 30, 2021 9:11
Subject: Re: [WSJTX] Tail ending my signal
 
So what will happen when near the height of sunspot cycle 25 when on, say, 20m the FT8 waterfall is jammed full with three callers on each slot   (FT8 is decoded "three" times in deep decode per manual) and there's no clear slot?

2.2.0-rc1 " A second processing step starts at 13.5 s, and the final one at 14.7 s."

--73, Glenn, AF8C

On 1/29/2021 11:47 PM, Jim Shorney via groups.io wrote:
From the WSJT-X online manual:

"To avoid QRM from competing callers, it is usually best to answer a CQ on a different frequency from that of the CQing station. The same is true when you tail-end another QSO. Choose a Tx frequency that appears to be not in use. You might want to check the box Hold Tx Freq. "

From the Hinson document linked from same:

“The CQing station doesn’t need to say up 3 or anything else.  He will decode all stations in the audio spectrum.  You can call him at 300Hz or 2300Hz and it won’t make any difference.  They all display.  You don’t have to (and don’t want to) move to his frequency.  If there is more than one station calling him, they will hopefully be spread all over the audio spectrum, not causing QRM to the station trying to make a QSO or each other.  If a bunch call on his frequency, they just QRM each other and the guy CQing will be working those who are split.  Additionally, if he starts a QSO with someone close to your transmit frequency, your transmitter will be disabled so you don’t cause him QRM.  If you are transmitting further away, you can keep calling him and he should pick you up as he works through the list of callers.”

73

-Jim
NU0C

On Sat, 30 Jan 2021 03:47:00 +0000 (UTC)
"mchenryproj via groups.io" mailto:mchenryproj@... wrote:

I haven't "obviously" missed anything.  Because it can be used that way doesn't make it intended to be used that way not is it the correct thing to do just because one can.
I am done with the subject. Do as you will and clutter the band. I will continue on and make my contacts as will everyone else.
Sean is the nameKB8JNE is the call

Spell checked by the NSA. 
 
  On Fri, Jan 29, 2021 at 8:48 PM, Jim Shorneymailto:jshorney@... wrote:   
You obviously missed the point that this is the way the software is intended to be used. In a time division multiplexing scenario it is expected that a clear slot is available for transmit use by anyone not using that slot for RX. It is the strict timing that makes it possible,

73

-Jim
NU0C

On Fri, 29 Jan 2021 15:46:46 +0000 (UTC)
"mchenryproj via groups.io" mailto:mchenryproj@... wrote:

I still politely disagree.





Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com







locked Re: #FT8 decodes #FT8

Jacques Pecourt
 

Thank you Bill for the alternative to solve the issue. .  I like to use the "blank line between decoding periods" as the listing appears as a clear refresh rather than a continuous list..  Both ways work perfectly.

73's  Jacques W2/F2YS

On Fri, 29 Jan 2021 at 12:28, Bill Somerville <g4wjs@...> wrote:
Hi Jacques,

rather than disabling a feature you like, you can simply erase the "Band Activity" decodes window periodically before the issue occurs.

73
Bill
G4WJS.

On 29/01/2021 17:21, Jacques Pecourt wrote:
Thank you for your answer Reino. Yes, I do use "start new period decoded at top". Have been using this for a long time, kind of like seeing  a new list of decodes every cycle.. I am removing this check mark in the settings. Hopefully the solution I missed. Will let you know if this issue is resolved.
73's  Jacques W2/F2YS

On Fri, 29 Jan 2021 at 12:04, Reino Talarmo <reino.talarmo@...> wrote:

A phenomenon I cannot understand. For some unknown raisons my screen “band activity” will become blank at random times. However, decodes continue to appear on the Waterfall and on the “RX Frequency” screen window. I suspected the TX watchdog (set by default at 6) was the culprit and I changed it eventually to the ridiculous value of 99. The occurrence continues to appear randomly every 10 - 20 minutes or whatever.  The only way to recover is to turn OFF and ON WSJT-X. I also noticed that, just prior to the blank activity, the number of decodes  goes suddenly down from 25 or 30 to just 4 or 5 entries. The Task manager normally shows CPU usage of 5 to 15% during normal cycles. There are no other functions or background activities connected to the computer. I have all possible “hibernate USB functions” turned OFF. I am still using v2.1.2 0068f9 since I am using a new 590G. I did not want to introduce  too many changes at once. Any help on this issue? Thank you.

 

Hi Jacques,

Obviously you are using ”Start new period decoded at top”. There is a known ”feature” with that the Band activity stops displaying decodes. Decodes are still there, you need to scroll down to see decodes. Best way is to now and then Erase both windows double click Erase button, or just the Band activity Right click there and select Erase.

73, Reino OH3mA






locked Re: F/H mode malfunction or operator error? #FoxAndHound

Jim Shorney
 

Aside from what is causing the problem, the alert op should notice what is going on and QSY down manually.

73

-Jim
NU0C

On Sat, 30 Jan 2021 06:34:43 -0600
"John, K9MM" <johnb3030@...> wrote:

I am currently using WSJT-X v2.2.2. I updated to this version on
6/26/2020. The computer is running Windows 10 Pro v20H2.

With the dearth of DXpeditions due to Covid-19, it has been months since
I last used F/H mode.

Yesterday, J28PJ was using F/H on 17M. When he responded to my call, my
transmit frequency stayed above +1000 instead of moving down to his
frequency. I was unable to complete the QSO. I was definitely in Hound
mode. Later, he was on FT4 and I had a complete QSO.

Last evening, 4U1UN had many calling him on 40M FT8, so he announced he
was switching to F/H mode on 7056. He had about a dozen strong callers
from NA, SA, and EU, but was making few QSOs and sending many reports
repeatedly. After awhile, I stopped calling and just watched what was
going on in both even and odd time slots. In many cases, he would give
someone a report and they would reply, but their transmit frequency did
NOT shift down to his. The QSO would not be completed, and soon the
station would be calling him again. Occasionally there would be a QSO
attempt where F/H correctly shifted the caller's transmit frequency and
the QSO would complete, but this was less common.

Is it possible that there is an F/H incompatibility conflict between
v2.2.2 and v2.3.0-rc4? Or are there this many operators who have
something wrong in their setup? Strange!

73,

John, K9MM


locked Re: Tail ending my signal #FT8

Williams, G (af8c) <af8c@...>
 

So what will happen when near the height of sunspot cycle 25 when on, say, 20m the FT8 waterfall is jammed full with three callers on each slot   (FT8 is decoded "three" times in deep decode per manual) and there's no clear slot?

2.2.0-rc1 " A second processing step starts at 13.5 s, and the final one at 14.7 s."

--73, Glenn, AF8C

On 1/29/2021 11:47 PM, Jim Shorney via groups.io wrote:
From the WSJT-X online manual:

"To avoid QRM from competing callers, it is usually best to answer a CQ on a different frequency from that of the CQing station. The same is true when you tail-end another QSO. Choose a Tx frequency that appears to be not in use. You might want to check the box Hold Tx Freq. "

From the Hinson document linked from same:

“The CQing station doesn’t need to say up 3 or anything else.  He will decode all stations in the audio spectrum.  You can call him at 300Hz or 2300Hz and it won’t make any difference.  They all display.  You don’t have to (and don’t want to) move to his frequency.  If there is more than one station calling him, they will hopefully be spread all over the audio spectrum, not causing QRM to the station trying to make a QSO or each other.  If a bunch call on his frequency, they just QRM each other and the guy CQing will be working those who are split.  Additionally, if he starts a QSO with someone close to your transmit frequency, your transmitter will be disabled so you don’t cause him QRM.  If you are transmitting further away, you can keep calling him and he should pick you up as he works through the list of callers.”

73

-Jim
NU0C

On Sat, 30 Jan 2021 03:47:00 +0000 (UTC)
"mchenryproj via groups.io" <mchenryproj@...> wrote:

I haven't "obviously" missed anything.  Because it can be used that way doesn't make it intended to be used that way not is it the correct thing to do just because one can.
I am done with the subject. Do as you will and clutter the band. I will continue on and make my contacts as will everyone else.
Sean is the nameKB8JNE is the call

Spell checked by the NSA. 
 
  On Fri, Jan 29, 2021 at 8:48 PM, Jim Shorney<jshorney@...> wrote:   
You obviously missed the point that this is the way the software is intended to be used. In a time division multiplexing scenario it is expected that a clear slot is available for transmit use by anyone not using that slot for RX. It is the strict timing that makes it possible,

73

-Jim
NU0C

On Fri, 29 Jan 2021 15:46:46 +0000 (UTC)
"mchenryproj via groups.io" <mchenryproj@...> wrote:

I still politely disagree.  
  






Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Re: Class C PA on FT8? #FT8

Chuck K4RGN
 

As to relevance, discussion of the internals of non-linear PAs may indeed be OT. But the OP's question was an interesting one. VHF/UHF operators occasionally see non-linear PAs for sale that were meant for FM but could be useful for some digital modes at lower prices than linear PAs.  

73 Chuck K4RGN


locked Re: wsjtx mchf and linux #AudioIssues #linux #WSJTX_config

PFA
 

Hi Bill
... :) ...


On Sat, Jan 30, 2021 at 02:13 PM, Bill Somerville wrote:

is the libqt5multimedia5-plugins package installed on your system?

 

Thanks it solve, now rig is connected amd wsjtx is controlling it.

 thanks a lot
--
73 paolo IU2OMT


locked Re: F/H mode malfunction or operator error? #FoxAndHound

Bill Somerville
 

On 30/01/2021 12:34, John, K9MM wrote:
I am currently using WSJT-X v2.2.2. I updated to this version on 6/26/2020. The computer is running Windows 10 Pro v20H2.

With the dearth of DXpeditions due to Covid-19, it has been months since I last used F/H mode.

Yesterday, J28PJ was using F/H on 17M. When he responded to my call, my transmit frequency stayed above +1000 instead of moving down to his frequency. I was unable to complete the QSO. I was definitely in Hound mode. Later, he was on FT4 and I had a complete QSO.

Last evening, 4U1UN had many calling him on 40M FT8, so he announced he was switching to F/H mode on 7056. He had about a dozen strong callers from NA, SA, and EU, but was making few QSOs and sending many reports repeatedly. After awhile, I stopped calling and just watched what was going on in both even and odd time slots. In many cases, he would give someone a report and they would reply, but their transmit frequency did NOT shift down to his. The QSO would not be completed, and soon the station would be calling him again. Occasionally there would be a QSO attempt where F/H correctly shifted the caller's transmit frequency and the QSO would complete, but this was less common.

Is it possible that there is an F/H incompatibility conflict between v2.2.2 and v2.3.0-rc4? Or are there this many operators who have something wrong in their setup? Strange!

73,

John, K9MM
Hi John,

is your CAT control working correctly?

73
Bill
G4WJS.


locked Re: wsjtx mchf and linux #AudioIssues #linux #WSJTX_config

Bill Somerville
 

On 30/01/2021 11:27, PFA wrote:
Hi all,
I'm try to use digital mode with my mchf.

Just download and build wsjtx v2.2.2 (last stable).
I run WSJTX then I'm trying to configure the rig.
I set Yaesu FT-817, /dev/ttyAM0, ptt on CAT, but I'm not able to select the audio interface (list is empty).

Linux detects the MCHF sound card and I'm able to hear and record the mchf audio signals. 
Running a previous version of WSJTX (2.0.0) I was able to see the sound interfaces, but CAT was failing

Any suggestion ?

some data on setup
mcHF:
hw 0.6.3
sw UHSDR 2.11.93
output DIG EXT

Linux kernel :
Linux version 5.4.0-64-generic (buildd@lgw01-amd64-030) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #72~18.04.1-Ubuntu SMP Fri Jan 15 14:06:34 UTC 2021

lsusb report
Bus 001 Device 006: ID 0483:5732 STMicroelectronics
Device Descriptor:
../..
  idVendor           0x0483 STMicroelectronics
  idProduct          0x5732
  bcdDevice            2.00
  iManufacturer           1 UHSDR Community (based on STM Drivers)
  iProduct                2 USB Interface mchf
../..


--
73 paolo IU2OMT

Hi Paolo,

is the libqt5multimedia5-plugins package installed on your system?

73
Bill
G4WJS.

18881 - 18900 of 40086