No. That's it.
73
Tom OH6VDA
Sendt fra min iPad Air 2
> 10. jun. 2020 kl. 16:20 skrev Bill Somerville :
>
>
> On 10/06/2020 14:11, Bill Somerville wrote:
>> On 10/06/2020 14:01, Tom Ramberg wrote:
>>> First it happens when I set the Com port In the radio tab WSJT-X settings
>>> (in this case
The rig is Yaesu FTdx3000 connected with a Microham II keyer. I suppose that is
what I am trying, yes. And when I disconnect N1MM+, WSJT-X works fine with both
COM4 and COM5.
The problem is that I am trying to set this up in a club, where most of the
users are new licencees, and I want to make
It sounds like you're trying to do port sharing. I'm don't believe the
microham supports that. I believe it does support PTT on one com port and CAT
on another. And it can also echo CAT responses to another COM port for
monitoring...but not CAT control.
So if you turn off N1MM and connect WSJ
>
> I have just updated to WSJT-X 2.2.1 and have a problem with some items on
> the menu being in Spanish instead of English
>
> In preferences only the options at the bottom are Cancelar and Aceptar
> everything else is OK
>
> On the main program heading under WSJT-X all items
> Fine to learn how it should work, but here, there is always the same crash,
> even in 2.2.1, trying to decode FT8 on the air or from a wav file. In
> contrast, FT4 decodes well.
Claude,
Please try this change to line 48 in gen_ft8wave.f90 and let me know if it
fixes your problem:
$ git dif
On 10/06/2020 14:11, Bill Somerville wrote:
On 10/06/2020 14:01, Tom Ramberg wrote:
First it happens when I set the Com port In the radio tab WSJT-X
settings (in this case COM5) and press the "Test CAT" button. It
turns red, and a pop up window appears with the message "Rig
Failiure. Hamlib er
On 10/06/2020 14:01, Tom Ramberg wrote:
First it happens when I set the Com port In the radio tab WSJT-X settings (in this case COM5) and
press the "Test CAT" button. It turns red, and a pop up window appears with the message
"Rig Failiure. Hamlib error: I/O error while opening connection to ri
FLDigi and FLRig do not do anything close to what WSJT-X does with rig
control.FLDigi does notSet VFOA freq/modeSet VFOB freq/modeSet SplitTransmit
And it does it all within milliseconds.
It's kind of like saying "The noise my car makes doesn't happen going less than
10MPH".
Mike W9MDB
O
On 10/06/2020 13:23, Richard Shaw wrote:
It doesn't seem to cause a problem (unlike on MythTv, which I also
maintain), but a user reported the following terminal output when
running 2.1.2:
"qt.qpa.wayland: Wayland does not support QWindow::requestActivate()"
Thanks,
Richard
KF5OIM
Hi Richar
It doesn't seem to cause a problem (unlike on MythTv, which I also
maintain), but a user reported the following terminal output when running
2.1.2:
"qt.qpa.wayland: Wayland does not support QWindow::requestActivate()"
Thanks,
Richard
KF5OIM
___
wsjt-dev
I have only seen this behavior with WSJT-X, and only when changing bands
via ci-v/cat. I have been unable to reproduce this in FLDigi or FLRig.
SKCClogger only reads freq and does not provide for any form of rig
control.
73 de AI8W, Chris
On Wed, Jun 10, 2020, 00:06 Black Michael via wsjt-devel <
On 10/06/2020 07:45, Tom Ramberg via wsjt-devel wrote:
Starting WSJT-X with FTdx3000 and using 2nd CAT port in MicroHams device router
gives Hamlib error.
de OH6VDA TOM
Hi Tom,
what is the full error message, including details, please? When does it
happen?
73
Bill
G4WJS.
__
12 matches
Mail list logo
