Charlie, thanks for the reply.
I actually remember this feature, but I'd like to know if the loop only
occurs between different versions, or this feature needs to be enabled
somehow through the software (e.g., wsjtx configuration)?
Tnx
73 de IU3BSY Federico
Il 23/06/2026 22:21, Charles Suckling via wsjt-devel ha scritto:
Hi Federico
Some time ago WSJT-X -improved announced a new feature whereby it is
possible for two non-standard callsigns to make a QSO, but only if
those stations were both using the new version.
In the case where two stations with non-standard callsigns , one of
whom does not have that new version, attempt a QSO an infinite loop
situation was predicted. Apparently this new feature has migrated to
some early releases of other program versions based on WSJT-X.
This may have been what you were observing.
73
Charlie DL3WDG
On Tue, 23 Jun 2026 at 19:46, IU3BSY via wsjt-devel
<[email protected]> wrote:
Hello everyone,
I've searched the posts for a similar issue but haven't found
anything.
I'm currently participating in an award using a special 7-character
callsign. I've noticed, and I'm not the only one, that if I try to
complete a QSO (in standard mode with version 3.0.2) with another
callsign of 7 or more characters, an infinite loop begins because my
system responds without sending a signal report. So, I'm wondering if
this is a bug, an incorrect setting, or a protocol limitation.
Thanks for your help.
--
73 de IU3BSY Federico
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
73 de IU3BSY Federico
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
