On 4/11/2021 1:52 pm, Bill Barrett via wsjt-devel wrote:
Used TCP/IP connection and 224.0.0.1 and ethernet outgoing interface.
That works!
Bill W2PKY
That tells me you didn't have the "WSJT-X UDP Multicast on Loopback"
menu set in JTAlert which is needed if you have the WSJT-X UDP Server
On 4/11/2021 1:46 pm, Bill Barrett via wsjt-devel wrote:
Is it 244 or 224? either on does not work on the initial instance.
244 does not reveal the extra fields. 224 reveals the extra fields but
does not work.
see ??? for band data on initial instance and no decodes in Call Signs
window.
Hi Bill,
typo on my part, the UDP server value I use is: 224.0.0.0
[image: image.png]
I use this for Gridtracker and also the wsjt 'message_aggregator.exe'
program that shows what each of my many instances are doing.
Regards,
Peter, vk5pj
On Thu, Nov 4, 2021 at 1:21 PM Bill Barrett via
Hello Laurie-
Used TCP/IP connection and 224.0.0.1 and ethernet outgoing interface. That
works!
Bill W2PKY
On Wed, Nov 3, 2021 at 10:46 PM Bill Barrett
wrote:
> Hello Laurie-
> Is it 244 or 224? either on does not work on the initial instance.
> 244 does not reveal the extra fields. 224
Hello Laurie-
Is it 244 or 224? either on does not work on the initial instance.
244 does not reveal the extra fields. 224 reveals the extra fields but does
not work.
see ??? for band data on initial instance and no decodes in Call Signs
window.
Where am I going wrong?
Thanks;
Bill
On Wed, Nov 3,
Hello Peter-
Thanks, yes, if 224 and the extra fields are present and 127 is entered the
extra fields go away.
On Wed, Nov 3, 2021 at 10:08 PM Peter Sumner via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hello Bill,
> yes those displays are indeed different as on one you have
On 4/11/2021 12:43 pm, Bill Barrett via wsjt-devel wrote:
This is from 2.5.0, first and second instance on Win11
does anyone know why they are different?
Thanks;
Bill W2PKY
You're running multiple WSJT-X instances with incompatible udp server
settings. You have one instance running unicast
Hello Bill,
yes those displays are indeed different as on one you have defined a UDP
broadcast address of 244.0.0.1 which then prompts the WSJT software to
offer you a selection for an interface to apply this to. Ethrnet or
loopback normally, plus the multicast TTL, whereas the other version is
This is from 2.5.0, first and second instance on Win11
does anyone know why they are different?
Thanks;
Bill W2PKY
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
WSJT-X is a GREAT program and I tremendously enjoy it! However, one small
change in FT-4 and FT-8 (and potentially other modes) would make it easier to
pick out desired callsigns.
In the display of FT-4 and FT-8 signals, the callsign of the intended station
is shown first, as it should be,
Perhaps some do, perhaps I do.
However that in no way negates my reason for liking the DF axix(sic). It is
useful to me because of prior experience. Especially with weak signals which I
see a lot of on 50MHz and to some extent 432MHz where I will try with single
yagi 100W on Q65. I just find
Don’t most operators use split VFO tuning?
Sent from my iPad
> On Nov 3, 2021, at 7:34 AM, Conrad PA5Y via wsjt-devel
> wrote:
>
> Hello all.
>
> I really miss the DF axis on the waterfall when operating EME. I know that
> the doppler is shown in the Astronomical data window but my brain
On 03/11/2021 09:49, Ari Hyvonen via wsjt-devel wrote:
Hi,
WSJT-X 2.5.1 64 Bit, Windows 10.
I Saw this behaviour yesterday in the monthly 2m activity contest,
where EU VHF Contest mode is used.
DX Call Tx3 Message
OH6XXX R 530022 KP32
OH6XX R 530022 KP32E
OH6X R
Hello all.
I really miss the DF axis on the waterfall when operating EME. I know that the
doppler is shown in the Astronomical data window but my brain is tuned to
using DF in the waterfall, could it be added based upon my TX frequency? For
instance if I am using 1500Hz Q65-60B and I know
Hi,
WSJT-X 2.5.1 64 Bit, Windows 10.
I Saw this behaviour yesterday in the monthly 2m activity contest, where EU
VHF Contest mode is used.
DX Call Tx3 Message
OH6XXX R 530022 KP32
OH6XX R 530022 KP32E
OH6XR 530022 KP32EQ
Other TX messages were correct.
Switched back
15 matches
Mail list logo
