On 30/06/2018 1:01 AM, Black Michael via wsjt-devel wrote:
Still can't reproduce....
You'll find message_aggregator in the bin folder. It receives the UDP
packets too so should show what you see too.
If you're seeing bad info in what JTAlert receives than this should
show it too
I tested logging from the two VK* configs and it works as expected.
Inline image
de Mike W9MDB
Mike,
Thanks for the tests. Well I'm embarrassed!
I have my own version of Message Aggregator (.NET code) that I wrote to
exercise and test the different modules I'm coding for JTAlert V3
(especially the multicasting ;)). It agrees with the WSJT-X aggregator
and your observations. The problem was within the old JTAlert V2 code.
The UDP logged QSO handling was based on an older NetworkMessage.hpp
spec that didn't have My Grid and My Call defined so JTAlert was using
the values from the WSJT-X config read at startup and plugging those
into the Logged QSO record for JTAlert to process. That read of the
config was only happening once and didn't account for config switching,
thus the incorrect My Call value after switching configs.
An easy fix.
Sorry for the inconvenience.
de Laurie VK3AMA
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
