On 3/7/19 6:37 PM, Deisher, Michael wrote:
Thanks for the quick reply, Bill. Do you (or any others on the list)
have any recommendations for implementing this "below" wsjtx? In my
current setup, wsjtx seems to "lock" the serial device so that other
apps (e.g., flrig) cannot access it. It
On 08/03/2019 00:12, Bill Frantz wrote:
When printing decodes, I have frequently seen the "a1" on the right
side of the window. (The name of the location is forced beyond the
right margin of the Receive window.) I think having the "a1" appear
may be a bug, particularly since it forces the name
When printing decodes, I have frequently seen the "a1" on the
right side of the window. (The name of the location is forced
beyond the right margin of the Receive window.) I think having
the "a1" appear may be a bug, particularly since it forces the
name of the location out of the
Bill, do you know if this was the case with the posted 2.0.0 version
as well? My problems with audio over USB sound devices seem to have
completely gone away with this updated version - I thought they had
with 2.0.1 but within an hour or so things were slow again, and I
finally found that if I
Double-clicking on GW0TSM here does not work. Nothing happens.
de Mike W9MDB___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Mike (KK7ER)L
Select Hamlib NET rigctl from the rig menu, then launch rigctld (from the
WSJT-X package) in the background. WSJT-X listens on 4532 to anyone who wants
to send commands (R/W) to it.
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
Mike,
I've been using the free LP-Bridge software with my Windows 7 system for
many years with my Elecraft K3. The K3 is connected to LP-bridge which
creates multiple virtual ports. The K3 can simultaneously connect to
WSJT-X, N1MM, MMTTY, DX Lab suite's Launcher and Commander applications.
Thanks for the quick reply, Bill. Do you (or any others on the list) have any
recommendations for implementing this "below" wsjtx? In my current setup,
wsjtx seems to "lock" the serial device so that other apps (e.g., flrig) cannot
access it. It makes sense, but I remember reading about
On 07/03/2019 17:01, Deisher, Michael wrote:
Hi. I hope this is not beyond the scope of WSJT-X but since you have built-in
rig control features, here goes. In the interests of having all important
information on one screen is it possible to read the SWR during transmission
and have an alert
On 07/03/2019 17:01, Topher Petty wrote:
I'm not certain whether this is an OS limitation or a limitation in
the way WSJTX parses the /dev files, and, as I stated, I am able to
manually enter the symlink alias and get it working. I'm just bringing
this limitation to your attention in case
I've been trying to find a way around this issue for quite some time, but
to no avail.
I've got several USB->Serial port devices on my machine, including a
RIGblaster Advantage, and an Edgeport/8. I've got UDEV rules set up so that
it doesn't matter which order the devices come up; they're all
Original Message
From: John Bastin via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Wednesday, March 6, 2019, 7:52 PM
To: WSJT software development
Cc: John Bastin
Subject: [wsjt-devel] VFO-B behavior
> On 5Mar 2019, at 09:40, Marco Cali'stri wrote:
>
>> as
12 matches
Mail list logo
