I've been running 3 slices on a Flex 6600M 24/7 since August 2020. I
have it configured to use 4 slices, but use that 4th on the M model
Maestro display. I configured the DAX settings and TCP/COM settings,
then setup 4 different WSJT-X profiles with shortcuts on the desktop.
I'm also running a unique instance of JTAlert with each WSJT-X session.
It works quite well.
The only regular bug I have is it seems to lose connection with the
radio every few days, but closing SmartSDR and relaunching fixes that.
I have to click Retry on each WSJT-X session error and I'm good to go again.
If there's a specific problem you are facing that you'd like me to test
on my setup, let me know.
*Virgil K7VZ*
On 2/22/21 7:55 AM, Black Michael via wsjt-devel wrote:
Been seeing some discussion on the inability of handling slices well
with Flex rigs.
I'd like propose that WSJT-X add a new message when the window is
activated -- same logic as the watchdog timer does when you click on
the window. External apps could use that for many purposes like this.
The message would say the windows has been activated -- and maybe a
window handle for the OS or some other germane object? Any app could
use this info do things like set the active slice, adjust antennas,
tune, etc.
Could also add a new function in hamlib so WSJT-X could send a
set_conf("flex_slice", params.flex_slice.toLatin1 ().data ()););
I know this would require another parameter for the rig config window
-- and would only seem to apply to Flex TCP connections too....I still
have to get a Flex user to test the capability.
Better ideas for how to do this are more than welcome.
Mike W9MDB
_______________________________________________
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
