search

K1DBO / slice-master-6000

Additional slice controls for your Flex 6000 series radio
33 stars 20 forks source link

No WSJT-X Spots #22

Closed imagesafari closed 1 year ago

imagesafari commented 1 year ago

I'm launching WSJT-X and it all works, but I'm not getting any spots, either on the panadapter or via the telnet aggregation server.

WSJT-X is configured to report via multicast, to support JT Alert & GridTracker, etc.

Where is SliceMaster looking to get its spots from WSJT-X? Could enabling multicast be breaking that?

Thanks & 73

K1DBO commented 1 year ago

Slice Master looks to the ALL.txt file for spot information. The network settings shouldnt matter. Send an email to the address you see when Slice Master starts up. Please check the end of the README for instructions on including your log files in the email.

imagesafari commented 1 year ago

Looks like that was it. I'm not sure if this is a WSJT-X Improved-only feature or if it is in the mainline WSJT-X now too, but on the latest release candidate, I've got this option selected - so it is writing to a file named 2023-ALL.txt not ALL.txt - I tried changing the setting, and spots appeared.

172-238-max

K1DBO commented 1 year ago

Ok, that makes sense. In earlier releases (I think) it used to be on by default.

imagesafari commented 1 year ago

Maybe a feature request to specify the name of the ALL.txt file to watch for spots?

On Fri, Jul 21, 2023 at 8:42 AM K1DBO @.***> wrote:

Ok, that makes sense. In earlier releases (I think) it used to be on by default.

— Reply to this email directly, view it on GitHub https://github.com/K1DBO/slice-master-6000/issues/22#issuecomment-1645523254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADAVQKELXKGSDFB43FGAE3XRJ2KBANCNFSM6AAAAAA2RULSHI . You are receiving this because you authored the thread.Message ID: @.***>

K1DBO commented 1 year ago

I think the best option here is to have Slice Master determine which file WSJTx is writing to and to read from that one.