Ted, here's what I do to use N1MM Logger+ with wsjt-x:
I created a second, different shortcut to the N1MM Logger+ program that
starts N1MM Logger+ with a different .ini file, one that does NOT talk to
the radio. N1MM is really only used for logging, and the frequency and mode
information is provided by wsjt-x, so there's no reason for N1MM to even
talk to the radio.
To do this, I copied the my original "n1mm logger.ini" file in my
Documents\N1MM Logger+ folder to a file named "NoRadio.ini"
Then I copied the shortcut to N1MM Logger+, but edited it so that the
Target is "C:\Program Files(x86)\N1MM Logger+\N1MMLogger.net.exe"
Ini=NoRadio.ini
Then I started N1MM Logger+ with that shortcut (which uses the new
NoRadio.ini file), and went to the configuration dialog to get rid of the
radio.
I renamed the new shortcut to N1MM Logger+ NORADIO and when I use that
shortcut, I don't have CAT control, and wsjt-x works just fine.
When I exit wsjt-x and want to use N1MM Logger+ with another mode, I just
start it with the regular N1MM Logger+ shortcut.
-Brian N9ADG
On Thu, Mar 8, 2018 at 12:34 PM, Ted Gisske <gis...@offex.com> wrote:
> I am using 1.9-RC2. What I am trying to do is run N1MM+ and WSJT-X
> simultaneously to control the radio without having to reconfigure one or
> the other program to avoid CAT port conflicts. It gets to be pretty clumsy
> to switch programs, or have N1MM+ open to get UDP broadcasts.
>
>
>
> I see from some internet sleuthing that HamLib wants to have exclusive
> control of the radio, as it does not poll the radio to see if anything on
> the radio that the other program has changed has modified WSJT-X settings
> like mode or frequency.
>
>
>
> So, it appears that it won’t work unless some sort of context-switching
> layer is coded. It seems plausible to do this, but I don’t find it done
> anywhere and it would be a gnarly software project to write it. Covering
> all the possible interactions between all programs is a daunting project.
>
>
>
> Sigh…..
>
>
>
> *From:* Neil Zampella [mailto:ne...@techie.com]
> *Sent:* Thursday, March 08, 2018 2:18 PM
> *To:* wsjt-devel@lists.sourceforge.net
> *Subject:* Re: [wsjt-devel] VSPE issue
>
>
>
> Are you using version 1.9.0-RC2, as it interfaces directly with N1MM.
>
>
>
> On 3/8/2018 10:56 AM, Ted Gisske wrote:
>
> Has anyone had success using a VSPE splitter to direct both N1MM+ and
> WSJT-X to the same rig-control port (in my case a TS-990 on COM4). If so,
> I’d appreciate knowing how you got it done. The splitter seems to work OK
> with N1MM, but WSJT-X refuses to connect.
>
>
>
> Thanks!
>
> Ted
>
> K9IMM
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------
> ------------------
> 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
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
