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 <billbarrett...@gmail.com> 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 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, 2021 at 10:32 PM Laurie, VK3AMA via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> >> >> 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 (127.0.0.1) and the other >> multicast (244.0.0.1). JTAlert when running in a multi-instance environment >> requires that all WSJT-X instances be set to use multicast. You need to >> change your unicast WSJT-X instance to multicast for the UDP server >> settings. >> >> de Laurie VK3AMA >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
