I'll mention that I'm working on a new program for hamlib I'm calling rigctlp
that will allow a virtual COM port passthru as a TS-2000 emulator.That way any
program (e.g. N1MM) can set up a TS-2000 on a virtual COM port...which in turn
can talk to FLRig for example which can handle multiple prog
Hi Greg,
Kubuntu has been largely trouble free for me in the shack, and I very much like
the visual attractiveness of the themes. I guess I am a little leery of
installing from debs though. I had one a couple of years back that for some
strange reason wanted to remove my KDE desktop as a conf
Bill,
with this setup on my TS-480, FT-450 and Flex 5000a, everything works great.
The problems showed up on a friends radio FT-847. It only is an issue on
UHF, thus not really a huge deal.
I questioned it to see if there was any ideas.
I have a work around I am going to try to test for him...
On 20/12/2018 01:00, Bill Frantz wrote:
On 12/20/18 at 4:08 PM, g4...@classdesign.com (Bill Somerville) wrote:
As far as I know the only way to run N1MM Logger+ and WSJT-X at the
same time is to disable CAT control in one of them. WSJT-X supports
several rig control server options but N1MM sup
On 12/20/18 at 4:08 PM, g4...@classdesign.com (Bill Somerville) wrote:
As far as I know the only way to run N1MM Logger+ and WSJT-X at
the same time is to disable CAT control in one of them. WSJT-X
supports several rig control server options but N1MM supports
none of them.
For some radios an
On 19/12/2018 21:06, Mike Maynard wrote:
Omni-rig is only running via WSJT. Both are shared against a serial
port splitter via VSPE.
There is something about how WSJT handles the control directly, that
it wont work (hangs up N1MM when set that way) but when you use
omni-rig on the WSJT side
Hi Bill,
I didn't think that could be the case since I have JTAlert set up to log to
ACLog. And it logged those test QSOs correctly to ACLog.
However, JTAlert has a thing called Last QSO API that is always on and does
log to the same (by default) port N1MM was looking for. So that's why the
QSOs we
George writes:
> Hello,
>
> I am running Mint Linux 18.2 & 18.3 (2 different computers) which are
> both long term support releases and are supported till 2021.
>
> When I attempt to install wsjtx 2.0.0 (amd64) it states that I need
> libc6 to be greater than 2.27 the version of libc6 that is
Omni-rig is only running via WSJT. Both are shared against a serial port
splitter via VSPE.
There is something about how WSJT handles the control directly, that it
wont work (hangs up N1MM when set that way) but when you use omni-rig on
the WSJT side things work ok.
Mike
On Wed, Dec 19, 2018 at
On 19/12/2018 18:14, Mike Maynard wrote:
Sorry, I guess I implied before... It works ok if you set the rig
direct in WSJT. Unfortunately we have to use Omni-Rig in order to get
WSJT and N1MM to play together on the CAT control.
Hi Mike,
that does tend to point to Omni-Rig being the issue, I
On 19/12/2018 18:11, Mike Maynard wrote:
It only happened on UHF though. Wouldnt the calibration fields effect
all frequencies? (although, I guess if they were skewed just right)
Hi Mike,
the frequency offset from the calibration slope adjustment increases
with frequency. The intercept
Furthermore, why would this effect it only when using Omni-rig for the
interface.
Sorry, I guess I implied before... It works ok if you set the rig direct in
WSJT. Unfortunately we have to use Omni-Rig in order to get WSJT and N1MM
to play together on the CAT control.
On Wed, Dec 19, 2018 at 1:1
Bill, that is something I am not sure about, we were working over the phone.
It only happened on UHF though. Wouldnt the calibration fields effect all
frequencies? (although, I guess if they were skewed just right)
Mike
On Wed, Dec 19, 2018 at 12:53 PM Bill Somerville
wrote:
> On 19/12/2
On 19/12/2018 17:23, Mike Maynard wrote:
Working with a friend of mine today to try and set his WSJT and N1MM
(and both have cat control together) we discovered an anomaly .
When using Omni-Rig inside WSJT for cat control, when you choose UHF
as your band (frequency - 432.500), upon initial s
Working with a friend of mine today to try and set his WSJT and N1MM (and
both have cat control together) we discovered an anomaly .
When using Omni-Rig inside WSJT for cat control, when you choose UHF as
your band (frequency - 432.500), upon initial selection it adds 10hz to the
frequency automa
> On December 18, 2018 at 7:14 PM Paul Bramscher wrote:
>
>
> On 12/18/2018 10:21 AM, Rich Griffiths wrote:
> > I'd like to chat with someone who has a working install of version 2.0.0
> > on Debian stretch. If you're interested, please contact me off-list at
> > rich-at-w2rg-dot-net.
> >
> >
Russ --
Obviously the bogus JT65 decodes you have seen are related to your use
of "Enable Averaging". You haven't answered my questions about optional
decoder settings and the contents of your CALL3.TXT file. Best of all
would be a sequence of *.wav files which, when opened in WSJT-X, would
Sorry, I forgot to change the subject on the previous message...
Russ
> -Original Message-
> From: Russ
> Sent: Wednesday, December 19, 2018 9:37 AM
> To: 'WSJT software development'
> Subject: Re: [wsjt-devel] Version 2.0 issues with JT65
>
> Hello all. I have discovered another issu
Hello all. I have discovered another issue with version 2.0. I do not know
if it existed in previous versions.
I use the feature called "Enable logged contact ADIF broadcast", with port
2333, to send contact information to my logging program (not N1MM). This
works very well, but I recently trie
Joe, Bill, Charles, and all. The problem I reported (many instances of old
contact information being shown as decodes and similar issues, in JT65) was
eliminated by unchecking the 'Enable Averaging' box under decoding. When I
re-enable averaging the problem returns after a bit of usage.
I have s
On Wed, Dec 19, 2018 at 7:22 AM Bill Somerville
wrote:
>
> Thanks again for the PPA updates so quickly after the v2.0.0, you and
> Richard, KF5OIM, are doing a great job making WSJT-X available as binary
> packages across many popular Linux distributions.
>
I'll keep supporting CentOS 7 as best
On 19/12/2018 04:52, Greg Beam wrote:
I have run into an error that may have
been discussed already. UB 14.04 (Trusty) is using Qt 5.2.1, while UB 16.04
(Xenial) and UB 18.04 (Bionic) are using 5.5.1 and 5.9.5 respectively.
Hi Greg,
as stated at the top of the WSJT-X source tarball INSTALL fil
On 19/12/2018 12:57, CHARLES LASH wrote:
Fortran runtime error: Index '1001' of dimension 1 of array 'c2fox'
above upper bound of 1000
Hi Charlie,
I don't know why using CRTL+C to copy WSJT-X message box text is not
working for you, it is fine here.
That issue is a known defect, thanks
The CTRL+C did not work but I finally got a copy of the whole error message. It
is attached as
> On December 18, 2018 at 8:27 PM Bill Somerville wrote:
>
> On 19/12/2018 01:23, CHARLES LASH wrote:
>
> > >
> > Please see the attached image of the error message in a Rich Te
On 19/12/2018 02:27, George wrote:
I am running Mint Linux 18.2 & 18.3 (2 different computers) which are
both long term support releases and are supported till 2021.
When I attempt to install wsjtx 2.0.0 (amd64) it states that I need
libc6 to be greater than 2.27 the version of libc6 that is
25 matches
Mail list logo
