Elecraft

WSJT-X K3/K3s hanging as Tx

Classic

List

Threaded

32 messages Options

Gary Smith-2

Re: WSJT-X K3/K3s hanging as Tx

Folks,

I seem to have ignited a fire-storm that
was not at all what I was trying to
accomplish, I was just stating an issue
and asking if others had experienced this
and it seems like the topic has taken on
legs.

I am a novice at WSJT-X but I can't help
but feel that it is a program that is
genius but immature. I say this expressly
because I run N1MM, MMTTY, logic 9 and my
GPSDO all with LP bridge but WSJT-X wants
to have total dominion over the operating
system as far as the ports go.

I have found a way to finagle it to work
with LP bridge but not because WSJT-X has
any interest in that being the case.
Considering how many people are having
trouble with ports and that program, it
seems like the problem to me is within the
program itself and how it approaches using
ports. If the other programs can use the
virtual ports without issue, it doesn't
make sense that WSJT-X has to have
dominion. I'm sure that after enough
complaints and enough time, that the
authors will attend to this problem.

It is only when I use WSJT-X that I have
the issue that I mentioned in my initial
post which is hanging of the transmit
function without sending RF out the
antenna. No other program or situation
causes this to happen, only WSJT-X so as
far as I'm concerned it is a buggy program
but a genius program at the same time,
what it does is amazing and it is free no
less. My only interest in posting was to
find if somebody has found a way of
getting around this bug.

When it comes to the idea of RF getting
back in the shack, I never get any RF back
in the shack to disturb anything when I
use my antennas that are almost 400 feet
from the house using 1 inch hardline get
to them. The only time I ever have any
issue with RF in the shack is if I use the
tri-band on top of the house and I rarely
use that because of RFI in the
neighborhood.

For this transmit-state issue to happen
when I am running barefoot to an antenna
almost 400 feet away which is tuned
beautifully and I need no transmatch and
me running barefoot... it is not RFI in
the shack causing this problem. I do lay
it squarely on the shoulders of the WSJT-X
software for it never ever happens at any
other time then when I am running this
specific software.

I really don't want this topic to run to
the point that it becomes something Eric
has to shut down so maybe it's best just
to leave it and I will keep pushing a
button on the front panel to unlock the
transmit condition when it engages when
WSJT-X goes rogue.

The only way I can reproduce the problem
every time ( And FWIW, PTT-Key is set to
off-off) is to go into the WSJT-X
settings, select Radio, click on test PTT
and it creates this exact condition. If I
exit settings without clicking on Test PTT
again to shut the state off, the K3s is
then left in this transmit state with no
RF being made.

The solution is to tap a button on the K3s
front panel and all is fine again.

The problem appears to me to be a still
buggy WSJT-X issue that the authors have
not yet become interested in attending to.
I would just like to know how to have a
workaround to get around this error until
they fix it. As it is it has become
tiresome.

73,

Gary
KA1J

> For those using WSJT-X, sometimes I find
> the K3s is locked as transmit but there is
> no RF being sent and no Rx from the K3.
>
> Looking at the P3 I see a jitter on the
> upper half of the screen as if there was a
> tiny output but no Rf is seen on any of
> the three SWR meters in line (K3s, AP3 &
> LP-100A).
>
> I couldn't get WSJT to receive, looked at
> the settings, all were correct and as is
> sometimes needed with WSJT-X, I rebooted
> to get it to work properly but it still
> did not lock onto the K3s frequency.
> Rebooted again and then I realized the K3s
> was in that TX condition with both the red
> & yellow LEDs lit and that jitter on the
> P3 upper screen.
>
> This happens every so often and what I
> have to do is touch any of the buttons on
> the K3s and it disengages this situation.
> I did that to deal with the issue I
> mentioned above. I could restart the K3s
> but then I'd have to restart LP-Bridge and
> wait, so I use the quick fix.
>
> Anyone experience this and figure out how
> to prevent it?
>
> Thanks!
>
> 73,
>
> Gary
> KA1J
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

tomb18

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Gary Smith-2

Hi,
Just hooked up a sniffer to WSJT and the PTT CAT commands are correct,
putting it into transmit when appropriate and out as well. (Unless there is
an intermittent bug).
If the radio menu for PPT-KEY is OFF-OFF it cannot get put into transmit via
hardware. So, DTR signals do nothing. There will be no issue when you
power up your PC etc.

Since the K3 will go into transmit anyways, the most likely item then is
LPBridge (which the OP said he was using) OR VOX is enabled on the line-in
in the rear and the sensitivity is just too high.

73 Tom

-----Original Message-----
From: Gary Smith
Sent: Monday, November 13, 2017 2:12 PM
To: [hidden email]
Subject: [Elecraft] WSJT-X K3/K3s hanging as Tx

For those using WSJT-X, sometimes I find
the K3s is locked as transmit but there is
no RF being sent and no Rx from the K3.

Looking at the P3 I see a jitter on the
upper half of the screen as if there was a
tiny output but no Rf is seen on any of
the three SWR meters in line (K3s, AP3 &
LP-100A).

I couldn't get WSJT to receive, looked at
the settings, all were correct and as is
sometimes needed with WSJT-X, I rebooted
to get it to work properly but it still
did not lock onto the K3s frequency.
Rebooted again and then I realized the K3s
was in that TX condition with both the red
& yellow LEDs lit and that jitter on the
P3 upper screen.

This happens every so often and what I
have to do is touch any of the buttons on
the K3s and it disengages this situation.
I did that to deal with the issue I
mentioned above. I could restart the K3s
but then I'd have to restart LP-Bridge and
wait, so I use the quick fix.

Anyone experience this and figure out how
to prevent it?

Thanks!

73,

Gary
KA1J

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Joe Subich, W4TV-4

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Gary Smith-2

On 11/13/2017 9:01 PM, Gary Smith wrote:
>
> The only way I can reproduce the problem
> every time ( And FWIW, PTT-Key is set to
> off-off) is to go into the WSJT-X
> settings, select Radio, click on test PTT
> and it creates this exact condition. If I
> exit settings without clicking on Test PTT
> again to shut the state off, the K3s is
> then left in this transmit state with no
> RF being made.

That's because "Test PTT" in WSJT-X is a *TOGGLE*
exactly like the XMIT button on the front of the
K3. By clicking "Test PTT" only once, you are
placing the K3 into transmit and *NEVER* switching
it back to receive! WSTJ-X and the K3 are both
doing *exactly* what you told it to do.

> The problem appears to me to be a still
> buggy WSJT-X issue that the authors have
> not yet become interested in attending to.

WSJT-X is not buggy. The radio control interface
does not handle asynchronous data and it was not
designed to do so. That means you *must* disable
AI1; (set AI0;) in the K3 command (no automatic
information reports) and *MUST NOT* share control
of the K3 with any other software - where that
software will poll the K3 and cause it to generate
any unexpected data to hamlib (the WSJT-X control
module).

Your complaint really belongs on the WSJT-X list
and not the Elecraft list.

73,

... Joe, W4TV

On 11/13/2017 9:01 PM, Gary Smith wrote:

> Folks,
>
> I seem to have ignited a fire-storm that
> was not at all what I was trying to
> accomplish, I was just stating an issue
> and asking if others had experienced this
> and it seems like the topic has taken on
> legs.
>
> I am a novice at WSJT-X but I can't help
> but feel that it is a program that is
> genius but immature. I say this expressly
> because I run N1MM, MMTTY, logic 9 and my
> GPSDO all with LP bridge but WSJT-X wants
> to have total dominion over the operating
> system as far as the ports go.
>
> I have found a way to finagle it to work
> with LP bridge but not because WSJT-X has
> any interest in that being the case.
> Considering how many people are having
> trouble with ports and that program, it
> seems like the problem to me is within the
> program itself and how it approaches using
> ports. If the other programs can use the
> virtual ports without issue, it doesn't
> make sense that WSJT-X has to have
> dominion. I'm sure that after enough
> complaints and enough time, that the
> authors will attend to this problem.
>
> It is only when I use WSJT-X that I have
> the issue that I mentioned in my initial
> post which is hanging of the transmit
> function without sending RF out the
> antenna. No other program or situation
> causes this to happen, only WSJT-X so as
> far as I'm concerned it is a buggy program
> but a genius program at the same time,
> what it does is amazing and it is free no
> less. My only interest in posting was to
> find if somebody has found a way of
> getting around this bug.
>
> When it comes to the idea of RF getting
> back in the shack, I never get any RF back
> in the shack to disturb anything when I
> use my antennas that are almost 400 feet
> from the house using 1 inch hardline get
> to them. The only time I ever have any
> issue with RF in the shack is if I use the
> tri-band on top of the house and I rarely
> use that because of RFI in the
> neighborhood.
>
> For this transmit-state issue to happen
> when I am running barefoot to an antenna
> almost 400 feet away which is tuned
> beautifully and I need no transmatch and
> me running barefoot... it is not RFI in
> the shack causing this problem. I do lay
> it squarely on the shoulders of the WSJT-X
> software for it never ever happens at any
> other time then when I am running this
> specific software.
>
> I really don't want this topic to run to
> the point that it becomes something Eric
> has to shut down so maybe it's best just
> to leave it and I will keep pushing a
> button on the front panel to unlock the
> transmit condition when it engages when
> WSJT-X goes rogue.
>
> The only way I can reproduce the problem
> every time ( And FWIW, PTT-Key is set to
> off-off) is to go into the WSJT-X
> settings, select Radio, click on test PTT
> and it creates this exact condition. If I
> exit settings without clicking on Test PTT
> again to shut the state off, the K3s is
> then left in this transmit state with no
> RF being made.
>
> The solution is to tap a button on the K3s
> front panel and all is fine again.
>
> The problem appears to me to be a still
> buggy WSJT-X issue that the authors have
> not yet become interested in attending to.
> I would just like to know how to have a
> workaround to get around this error until
> they fix it. As it is it has become
> tiresome.
>
> 73,
>
> Gary
> KA1J
>
>> For those using WSJT-X, sometimes I find
>> the K3s is locked as transmit but there is
>> no RF being sent and no Rx from the K3.
>>
>> Looking at the P3 I see a jitter on the
>> upper half of the screen as if there was a
>> tiny output but no Rf is seen on any of
>> the three SWR meters in line (K3s, AP3 &
>> LP-100A).
>>
>> I couldn't get WSJT to receive, looked at
>> the settings, all were correct and as is
>> sometimes needed with WSJT-X, I rebooted
>> to get it to work properly but it still
>> did not lock onto the K3s frequency.
>> Rebooted again and then I realized the K3s
>> was in that TX condition with both the red
>> & yellow LEDs lit and that jitter on the
>> P3 upper screen.
>>
>> This happens every so often and what I
>> have to do is touch any of the buttons on
>> the K3s and it disengages this situation.
>> I did that to deal with the issue I
>> mentioned above. I could restart the K3s
>> but then I'd have to restart LP-Bridge and
>> wait, so I use the quick fix.
>>
>> Anyone experience this and figure out how
>> to prevent it?
>>
>> Thanks!
>>
>> 73,
>>
>> Gary
>> KA1J
>>
>> ______________________________________________________________
>> Elecraft mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:[hidden email]
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>> Message delivered to [hidden email]
>>
>
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Gary Smith-2

Re: WSJT-X K3/K3s hanging as Tx

Hi Joe,

>
>
> On 11/13/2017 9:01 PM, Gary Smith wrote:
> >
> > The only way I can reproduce the problem
> > every time ( And FWIW, PTT-Key is set to
> > off-off) is to go into the WSJT-X
> > settings, select Radio, click on test PTT
> > and it creates this exact condition. If I
> > exit settings without clicking on Test PTT
> > again to shut the state off, the K3s is
> > then left in this transmit state with no
> > RF being made.
>
> That's because "Test PTT" in WSJT-X is a *TOGGLE*
> exactly like the XMIT button on the front of the
> K3. By clicking "Test PTT" only once, you are
> placing the K3 into transmit and *NEVER* switching
> it back to receive! WSTJ-X and the K3 are both
> doing *exactly* what you told it to do.

### I used that as an example of the state
I find sometimes find the K3s in. There is
something unique to WSJT-X that no other
software does that makes this happen, I
only find it randomly if I am using
WSJT-X. Never experienced it before WSJT-X
and never with any other
situation/software.

>
> > The problem appears to me to be a still
> > buggy WSJT-X issue that the authors have
> > not yet become interested in attending to.
>
> WSJT-X is not buggy. The radio control interface
> does not handle asynchronous data and it was not
> designed to do so. That means you *must* disable
> AI1; (set AI0;) in the K3 command (no automatic
> information reports) and *MUST NOT* share control
> of the K3 with any other software - where that
> software will poll the K3 and cause it to generate
> any unexpected data to hamlib (the WSJT-X control
> module).

### WSJT-X is the only software I use that
does this. The others share control as in
N1MM and MMTTY, Logic & FLDigi working
fine together. Logic runs beautifully with
N1MM and MMTTY, no conflicts of any kind.
If they can do this flawlessly, it is not
unreasonable to expect WSJT-X to play nice
as well.

>
> Your complaint really belongs on the WSJT-X list
> and not the Elecraft list.

### I disagree. As is so often the
situation when someone has an issue with
Company A's product and Company B's
product is being used and there is a
conflict... the stock answer is that
problem belongs to the other company, ask
them what to do. It's an old saw and in
this case, I'm told I should ask on the
other list. Everyone feels it's the other
guy's fault and that question belongs
elsewhere. Ask there and they tell you how
the K3 is non standard and to ask on the
Elecraft list. The person in the middle
gets trashed on both sides. I've
experienced this for so long I've come to
like trash.

As I said in the words below, I was asking
on the Elecraft list if others had
experienced this problem. My original
statement was: "Anyone experience this and
figure out how to prevent it?"

Where better to ask than a place devoted
to this type of radio if others have the
problem and if so, how to resolve it.

When I first started with WSJT-X I asked
on the WSJT-X reflector and was told quite
clearly if I want to use it, I had to run
it directly to the port for the K3, no
other control software should be running
at the same time and if I wanted to use
logging I had to use JT Alert and have my
logging done via that. I was also told
virtual ports are nothing but trouble, not
to use them with WSJT-X and there is no
help for those that use them. It seems to
me there's a lot of attitude on that list.

FWIW, I did find I can use a virtual port
with it # "10" If I assign any other
numerical value it will not work. Won't
work with Win 7, I tried for hours but
with this computer & Win 10, WSJT-X works
on virtual port 10. All the other software
works on whatever virtual port I tell it
to work on. WSJT-X is not yet user
friendly, I suspect it will become more so
over time.

If I had the skills I would be happy to
help make that so. My skills lie in other
areas; want someone to help keep you alive
following a traumatic injury? I can do
that. Write software? I can't do that.

73,
Gary
KA1J

>
> 73,
>
> ... Joe, W4TV
>
>
> On 11/13/2017 9:01 PM, Gary Smith wrote:
> > Folks,
> >
> > I seem to have ignited a fire-storm that
> > was not at all what I was trying to
> > accomplish, I was just stating an issue
> > and asking if others had experienced this
> > and it seems like the topic has taken on
> > legs.
> >
> > I am a novice at WSJT-X but I can't help
> > but feel that it is a program that is
> > genius but immature. I say this expressly
> > because I run N1MM, MMTTY, logic 9 and my
> > GPSDO all with LP bridge but WSJT-X wants
> > to have total dominion over the operating
> > system as far as the ports go.
> >
> > I have found a way to finagle it to work
> > with LP bridge but not because WSJT-X has
> > any interest in that being the case.
> > Considering how many people are having
> > trouble with ports and that program, it
> > seems like the problem to me is within the
> > program itself and how it approaches using
> > ports. If the other programs can use the
> > virtual ports without issue, it doesn't
> > make sense that WSJT-X has to have
> > dominion. I'm sure that after enough
> > complaints and enough time, that the
> > authors will attend to this problem.
> >
> > It is only when I use WSJT-X that I have
> > the issue that I mentioned in my initial
> > post which is hanging of the transmit
> > function without sending RF out the
> > antenna. No other program or situation
> > causes this to happen, only WSJT-X so as
> > far as I'm concerned it is a buggy program
> > but a genius program at the same time,
> > what it does is amazing and it is free no
> > less. My only interest in posting was to
> > find if somebody has found a way of
> > getting around this bug.
> >
> > When it comes to the idea of RF getting
> > back in the shack, I never get any RF back
> > in the shack to disturb anything when I
> > use my antennas that are almost 400 feet
> > from the house using 1 inch hardline get
> > to them. The only time I ever have any
> > issue with RF in the shack is if I use the
> > tri-band on top of the house and I rarely
> > use that because of RFI in the
> > neighborhood.
> >
> > For this transmit-state issue to happen
> > when I am running barefoot to an antenna
> > almost 400 feet away which is tuned
> > beautifully and I need no transmatch and
> > me running barefoot... it is not RFI in
> > the shack causing this problem. I do lay
> > it squarely on the shoulders of the WSJT-X
> > software for it never ever happens at any
> > other time then when I am running this
> > specific software.
> >
> > I really don't want this topic to run to
> > the point that it becomes something Eric
> > has to shut down so maybe it's best just
> > to leave it and I will keep pushing a
> > button on the front panel to unlock the
> > transmit condition when it engages when
> > WSJT-X goes rogue.
> >
> > The only way I can reproduce the problem
> > every time ( And FWIW, PTT-Key is set to
> > off-off) is to go into the WSJT-X
> > settings, select Radio, click on test PTT
> > and it creates this exact condition. If I
> > exit settings without clicking on Test PTT
> > again to shut the state off, the K3s is
> > then left in this transmit state with no
> > RF being made.
> >
> > The solution is to tap a button on the K3s
> > front panel and all is fine again.
> >
> > The problem appears to me to be a still
> > buggy WSJT-X issue that the authors have
> > not yet become interested in attending to.
> > I would just like to know how to have a
> > workaround to get around this error until
> > they fix it. As it is it has become
> > tiresome.
> >
> > 73,
> >
> > Gary
> > KA1J
> >
> >> For those using WSJT-X, sometimes I find
> >> the K3s is locked as transmit but there is
> >> no RF being sent and no Rx from the K3.
> >>
> >> Looking at the P3 I see a jitter on the
> >> upper half of the screen as if there was a
> >> tiny output but no Rf is seen on any of
> >> the three SWR meters in line (K3s, AP3 &
> >> LP-100A).
> >>
> >> I couldn't get WSJT to receive, looked at
> >> the settings, all were correct and as is
> >> sometimes needed with WSJT-X, I rebooted
> >> to get it to work properly but it still
> >> did not lock onto the K3s frequency.
> >> Rebooted again and then I realized the K3s
> >> was in that TX condition with both the red
> >> & yellow LEDs lit and that jitter on the
> >> P3 upper screen.
> >>
> >> This happens every so often and what I
> >> have to do is touch any of the buttons on
> >> the K3s and it disengages this situation.
> >> I did that to deal with the issue I
> >> mentioned above. I could restart the K3s
> >> but then I'd have to restart LP-Bridge and
> >> wait, so I use the quick fix.
> >>
> >> Anyone experience this and figure out how
> >> to prevent it?
> >>
> >> Thanks!
> >>
> >> 73,
> >>
> >> Gary
> >> KA1J
> >>
> >> ______________________________________________________________
> >> Elecraft mailing list Home:
> >> http://mailman.qth.net/mailman/listinfo/elecraft Help:
> >> http://mailman.qth.net/mmfaq.htm Post:
> >> mailto:[hidden email]
> >>
> >> This list hosted by: http://www.qsl.net
> >> Please help support this email list: http://www.qsl.net/donate.html
> >> Message delivered to [hidden email]
> >>
> >
> >
> >
> > ______________________________________________________________
> > Elecraft mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/elecraft
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:[hidden email]
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
> > Message delivered to [hidden email]
> >
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Richard Lamont

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Don Wilhelm

On 13/11/17 23:10, Don Wilhelm wrote:

> The proper place to cure "RF in the shack" problems is in your antenna
> system. A good common mode choke (many call it a balun) in the antenna
> feedline and running the feedline at right angles to the radiator
> (assuming a dipole) to keep the feedline from picking up radiation from
> the radiator. If that physical configuration cannot be avoided, then an
> additional common mode choke at the shack entry point can help.

I agree and have done all that. I have a doublet, centre-fed with 300
ohm ladder line dropping vertically to a DX Engineering choke balun
(which contains three binocular ferrite chokes in series). For good
measure, I have a Fair-Rite #31 clamp-on ferrite on the co-ax next to
it. The co-ax then runs in a duct buried about 350mm deep to the house,
where it goes up the external wall and then through it about 4m above
ground level into the (upstairs) shack, where there's another #31
clamp-on ferrite.

> With effective common mode chokes on the antenna and feedline, you
> should not have to use ferrites on every cable in the shack

Well, my experience disproves your hypothesis.

While common-mode current on the feedline is often a problem, it isn't
necessarily the only problem.

The problem here is radiated RF, not conducted RF, being picked up by
the USB cables. It's only to be expected when the shack is in the
antenna's near field.

73,
Richard G4DYA

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Joe Subich, W4TV-4

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Gary Smith-2

On 11/13/2017 11:21 PM, Gary Smith wrote:

> When I first started with WSJT-X I asked
> on the WSJT-X reflector and was told quite
> clearly if I want to use it, I had to run
> it directly to the port for the K3, no
> other control software should be running
> at the same time and if I wanted to use
> logging I had to use JT Alert and have my
> logging done via that.

Well, you got the best advice from the WSJT-X list - from the developers
of that software. Why do you think the developers of the K3 and K3
users are going to tell you something different or fix a basic design
decision in the WSJT-X software?

*If you don't like the way WSJT-X operates, DON'T USE IT!*

> I was also told
> virtual ports are nothing but trouble, not
> to use them with WSJT-X and there is no
> help for those that use them.

In the language of the WSJT-X list, "virtual ports" means port splitting
software - not USB derived serial ports. Most port splitting software
is a problem because it is nothing more than a software "Y" connection
which causes exactly the kind of "unanticipated data" errors that crash
the WSJT-X radio control.

> It seems to me there's a lot of attitude on that list.

The WSJT-X project has some of the smartest developers you will ever
encounter. They have their own vision of the project and have no use
for those who complain about the direction of that project unless the
complainers are willing to contribute to the development *write code*
of the features they seek.

WSJT-X had its beginnings in WSJT which had no rig control and used
only serial port RTS (or VOX) for T/R switching. CAT is present for
only three purposes - 1) to shift TX frequency in order to center the
TX tones; 2) for band hopping/scanning WSPR and 3) for split frequency
meteor scatter work. None of those functions require cooperating with
a logging program.

What you want would turn a bicycle into a semi ...

> ### WSJT-X is the only software I use that
> does this. The others share control as in
> N1MM and MMTTY, Logic & FLDigi working
> fine together. Logic runs beautifully with
> N1MM and MMTTY, no conflicts of any kind.

N1MM & MTTY do not share radio control. Logic never polls the K3 and
relies entirely on the auto-information or reading the data polled by
other software. Logic & Fldigi (or other active control software)
will bomb spectacularly with older Yaesu gear because both will try
to poll simultaneously. Similarly, unless a logger makes provision
to use MMTTY as a "RTTY engine" and MMTTY is configured to *NOT* do
any control of the radio frequency or software PTT, MMTTY and most
loggers will not coexist either.

73,

... Joe, W4TV

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Gordon LaPoint

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Bert Garcia N8NN

Bert,
I also have the problem, and it IS NOT rf getting into the shack.
It will happen with 1 watt. It is a function of wsjt-x and may be
related to using split. I have never seen the problem when NOT using
split. The problem usually appears when clicking on a new station to
answer a CQ, and the split has to change.
The systems will return to normal in the next 15 second segment if
nothing else is touched, or somtimes will return to normal sooner if the
"halt tx" button is clicked on.
I also see the problem when using other radios than the K3, I have
an IC-7000 and ANAN-10E that also get used for wsjt-x.
The problem has occured in wsjt-x versions 1.8 rc2, rc3 and release
1.8 I not remember seeing the problem before version 1.8 rc2, but can
not be sure.
I now have about 1,500 FT8 contacts in the log, so I use FT8 a lot.
Gordon - N1MGO

On 11/13/2017 07:00 PM, Bert Garcia N8NN wrote:

> The CAT and PTT are on different COM ports, per the installation instructions for the microKEYER II when using WSTJ-X. And it's not a stray RF problem as I have all the equipment bonded together, ferrite cores on the audio and control lines, a line isolator in the feedline where it enters the house, and line isolators between the rig and amp and between the amp and antenna tuner. The lockup happens when running only 30 watts with FT8. It never happens when running a KW on many other modes. I run RTTY, PSK and other digital modes with no problems.
>
> Thus, I suspect the issue is associated with the WSRJ-X software as the same issue occurs with various transceivers in multiple locations.
>
> Bert N8NN
>
> -----Original Message-----
> From: Don Wilhelm [mailto:[hidden email]]
> Sent: Monday, November 13, 2017 3:17 PM
> To: [hidden email]; [hidden email]; [hidden email]
> Subject: Re: [Elecraft] WSJT-X K3/K3s hanging as Tx
>
> Bert and Gary,
>
> Have you looked for a computer problem? Such as having both PTT via command and via an RS-232 signal line? Do you have both VOX on and another means of keying the transceiver?
>
> 73,
> Don W3FPR
>
> On 11/13/2017 3:07 PM, Bert Garcia N8NN wrote:
>> This problem is not unique to the K3. My Yaesu FT-1000mp does the
>> same thing -- locks up in transmit mode with no RF output and I have
>> to turn it off to regain control. The lock up is intermittent, and
>> some days it never happens. Rebooting everything works for a while,
>> but when I least expect it, the lockups will start again.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]

--
Gordon - N1MGO

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Gordon LaPoint

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Don Wilhelm

To add to my previous post-

I have the problem, home made interface for serial port ptt. This
problem is NOT a MicroHam problem, or Elecraft problem.
I have had the problem on my IC-7000 and ANAN-10E (which I no longer use
split on, not needed there) I have not seen the problem when NOT using
split.
The problem *IS NOT* rf in the shack, it happens even with 1 watt out,
and nothing else happens even when the KPA-500 is on at full power, any
mode!
Please - this *IS NOT* a ptt contention problem or rf in the shack problem.
Gordon - N1MGO

On 11/13/2017 07:08 PM, Don Wilhelm wrote:

> Bert and all,
>
> Use software PTT in the applications while W4TV figures out what is
> going on with the MicorHam gear.
> Are all those having a similar problem using MicroHam something? or
> does it occur with other interfaces.
>
> 73,
> Don W3FPR
>
> On 11/13/2017 7:00 PM, Bert Garcia N8NN wrote:
>> The CAT and PTT are on different COM ports, per the installation
>> instructions for the microKEYER II when using WSTJ-X. And it's not a
>> stray RF problem as I have all the equipment bonded together, ferrite
>> cores on the audio and control lines, a line isolator in the feedline
>> where it enters the house, and line isolators between the rig and amp
>> and between the amp and antenna tuner. The lockup happens when
>> running only 30 watts with FT8. It never happens when running a KW
>> on many other modes. I run RTTY, PSK and other digital modes with no
>> problems.
>>
>> Thus, I suspect the issue is associated with the WSRJ-X software as
>> the same issue occurs with various transceivers in multiple locations.
>>
>>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]

David Bunte

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Gordon LaPoint

I won't take a lot of time weighing in on this thread. I am a newbie to
FT8, with only a little over 100 Qs. I am using my K3 with a DigiKeyer II,
and have never experienced the problem.
Dave - K9FN

On Tue, Nov 14, 2017 at 8:58 AM, Gordon LaPoint <[hidden email]>
wrote:

> Bert,
> I also have the problem, and it IS NOT rf getting into the shack. It
> will happen with 1 watt. It is a function of wsjt-x and may be related to
> using split. I have never seen the problem when NOT using split. The
> problem usually appears when clicking on a new station to answer a CQ, and
> the split has to change.
> The systems will return to normal in the next 15 second segment if
> nothing else is touched, or somtimes will return to normal sooner if the
> "halt tx" button is clicked on.
> I also see the problem when using other radios than the K3, I have an
> IC-7000 and ANAN-10E that also get used for wsjt-x.
> The problem has occured in wsjt-x versions 1.8 rc2, rc3 and release
> 1.8 I not remember seeing the problem before version 1.8 rc2, but can not
> be sure.
> I now have about 1,500 FT8 contacts in the log, so I use FT8 a lot.
> Gordon - N1MGO
>
> On 11/13/2017 07:00 PM, Bert Garcia N8NN wrote:
>
>> The CAT and PTT are on different COM ports, per the installation
>> instructions for the microKEYER II when using WSTJ-X. And it's not a stray
>> RF problem as I have all the equipment bonded together, ferrite cores on
>> the audio and control lines, a line isolator in the feedline where it
>> enters the house, and line isolators between the rig and amp and between
>> the amp and antenna tuner. The lockup happens when running only 30 watts
>> with FT8. It never happens when running a KW on many other modes. I run
>> RTTY, PSK and other digital modes with no problems.
>>
>> Thus, I suspect the issue is associated with the WSRJ-X software as the
>> same issue occurs with various transceivers in multiple locations.
>>
>> Bert N8NN
>>
>> -----Original Message-----
>> From: Don Wilhelm [mailto:[hidden email]]
>> Sent: Monday, November 13, 2017 3:17 PM
>> To: [hidden email]; [hidden email]; [hidden email]
>> Subject: Re: [Elecraft] WSJT-X K3/K3s hanging as Tx
>>
>> Bert and Gary,
>>
>> Have you looked for a computer problem? Such as having both PTT via
>> command and via an RS-232 signal line? Do you have both VOX on and another
>> means of keying the transceiver?
>>
>> 73,
>> Don W3FPR
>>
>> On 11/13/2017 3:07 PM, Bert Garcia N8NN wrote:
>>
>>> This problem is not unique to the K3. My Yaesu FT-1000mp does the
>>> same thing -- locks up in transmit mode with no RF output and I have
>>> to turn it off to regain control. The lock up is intermittent, and
>>> some days it never happens. Rebooting everything works for a while,
>>> but when I least expect it, the lockups will start again.
>>>
>> ______________________________________________________________
>> Elecraft mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:[hidden email]
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>> Message delivered to [hidden email]
>>
>
>
> --
> Gordon - N1MGO
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Matt Murphy

Re: WSJT-X K3/K3s hanging as Tx

I'd experienced this problem, also not due to RF in the shack, and since I
switched to using PTT via RTS or DTR the problem has not recurred. The
problem began when I had been using RCForb and a virtual serial port with
CAT control of PTT for WSJT-X, so the explanation Joe offers makes sense
based on my experience.

Unless WSJT-X had some provision for reviewing all state changes to the K3
that might occur "unexpectedly" due to other CAT "clients" of the K3, it
would not be able to guarantee that its own state matched that of the K3,
which could seemingly result in the sort of behavior being experienced.

73,
Matt NQ6N

On Tue, Nov 14, 2017 at 8:07 AM, David Bunte <[hidden email]> wrote:

> I won't take a lot of time weighing in on this thread. I am a newbie to
> FT8, with only a little over 100 Qs. I am using my K3 with a DigiKeyer II,
> and have never experienced the problem.
> Dave - K9FN
>
> On Tue, Nov 14, 2017 at 8:58 AM, Gordon LaPoint <[hidden email]>
> wrote:
>
> > Bert,
> > I also have the problem, and it IS NOT rf getting into the shack. It
> > will happen with 1 watt. It is a function of wsjt-x and may be related
> to
> > using split. I have never seen the problem when NOT using split. The
> > problem usually appears when clicking on a new station to answer a CQ,
> and
> > the split has to change.
> > The systems will return to normal in the next 15 second segment if
> > nothing else is touched, or somtimes will return to normal sooner if the
> > "halt tx" button is clicked on.
> > I also see the problem when using other radios than the K3, I have an
> > IC-7000 and ANAN-10E that also get used for wsjt-x.
> > The problem has occured in wsjt-x versions 1.8 rc2, rc3 and release
> > 1.8 I not remember seeing the problem before version 1.8 rc2, but can
> not
> > be sure.
> > I now have about 1,500 FT8 contacts in the log, so I use FT8 a lot.
> > Gordon - N1MGO
> >
> > On 11/13/2017 07:00 PM, Bert Garcia N8NN wrote:
> >
> >> The CAT and PTT are on different COM ports, per the installation
> >> instructions for the microKEYER II when using WSTJ-X. And it's not a
> stray
> >> RF problem as I have all the equipment bonded together, ferrite cores on
> >> the audio and control lines, a line isolator in the feedline where it
> >> enters the house, and line isolators between the rig and amp and between
> >> the amp and antenna tuner. The lockup happens when running only 30
> watts
> >> with FT8. It never happens when running a KW on many other modes. I
> run
> >> RTTY, PSK and other digital modes with no problems.
> >>
> >> Thus, I suspect the issue is associated with the WSRJ-X software as the
> >> same issue occurs with various transceivers in multiple locations.
> >>
> >> Bert N8NN
> >>
> >> -----Original Message-----
> >> From: Don Wilhelm [mailto:[hidden email]]
> >> Sent: Monday, November 13, 2017 3:17 PM
> >> To: [hidden email]; [hidden email]; [hidden email]
> >> Subject: Re: [Elecraft] WSJT-X K3/K3s hanging as Tx
> >>
> >> Bert and Gary,
> >>
> >> Have you looked for a computer problem? Such as having both PTT via
> >> command and via an RS-232 signal line? Do you have both VOX on and
> another
> >> means of keying the transceiver?
> >>
> >> 73,
> >> Don W3FPR
> >>
> >> On 11/13/2017 3:07 PM, Bert Garcia N8NN wrote:
> >>
> >>> This problem is not unique to the K3. My Yaesu FT-1000mp does the
> >>> same thing -- locks up in transmit mode with no RF output and I have
> >>> to turn it off to regain control. The lock up is intermittent, and
> >>> some days it never happens. Rebooting everything works for a while,
> >>> but when I least expect it, the lockups will start again.
> >>>
> >> ______________________________________________________________
> >> Elecraft mailing list
> >> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> >> Help: http://mailman.qth.net/mmfaq.htm
> >> Post: mailto:[hidden email]
> >>
> >> This list hosted by: http://www.qsl.net
> >> Please help support this email list: http://www.qsl.net/donate.html
> >> Message delivered to [hidden email]
> >>
> >
> >
> > --
> > Gordon - N1MGO
> >
> > ______________________________________________________________
> > Elecraft mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/elecraft
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:[hidden email]
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
> > Message delivered to [hidden email]
> >
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Edward R Cole

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Gary Smith-2

Without getting into the middle of this, I would make one
suggestion. Download WSJT-10 and see if your problems go away.

WSJT-X is Joe Taylor's (with other developers) attempt to make WSJT
usable for all bands and uses; it is fairly new and being revised to
solve issues, so if you are a user (esp having problems) you might
keep track if new versions have been released.

HFer's esp seem to want to run all these loging and special control
programs simultaneous with WSJT-X so should not be big surprise when
they collide. I still run WSJT-10 for eme as its simpler and not
trying to be all things to all users. I have downloaded WSJT-X and
have it running on my K3 using audio line in/out and USB/RS232
adapter cable for computer I/F. I run two external soundcards which
makes setting audio levels easier (has knobs instead of sliders).

For VHF contests and eme paper logs is fine, and it gets transferred
to a excel log (very simple chart), then I convert it to pdf. for
posting on my website. I guess when you are working hundreds of
stations per hour automation is handy.

Recently MAP65 had a new upgrade which I downloaded before the recent
EME Contest but I ran into a couple problems with very slow decoding
and one window not opening (probably bugs which eventually will get
fixed). I reverted to my earlier version to run the contest. I'm
using an old XP32-SP3 computer so might be its being overloaded with
the new sw applications (which expect you to run a Cray-4 or
something). Adding some more memory might help me. Absolutely not
upgrading to later OS newer hdwr as that will render much of my
equipment obsolete (no drivers). A topic for another thread.

One thing I see is that JT65 use on HF is very different than how its
used on EME. Lends to "Beta-Max vs VHS like" compatibility issues.
PS: several eme'rs are also having issues making WSJT-X work. "new
tricks for old dogs"?

Nov. 11, I celebrated 59th anniversary of my first ham license. "old
dog" indeed: 1958-KN8MWA, 1959-K8MWA, 1982-AL7EB, 2005-KL7UW

73, Ed - KL7UW
http://www.kl7uw.com
Dubus-NA Business mail:
[hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

gt-i

Re: WSJT-X K3/K3s hanging as Tx

In reply to this post by Gary Smith-2

> FWIW, I did find I can use a virtual port
> with it # "10" If I assign any other
> numerical value it will not work. Won't
> work with Win 7, I tried for hours but
> with this computer & Win 10, WSJT-X works
> on virtual port 10. All the other software
> works on whatever virtual port I tell it
> to work on. WSJT-X is not yet user
> friendly, I suspect it will become more so
> over time.
>

Gary,
In Windows, all COM-Port notation above COM9 must be written in UNC-Format.
See:
https://support.microsoft.com/en-us/help/115831/howto-specify-serial-ports-larger-than-com9
A good software takes care of it by itself, no need for the user to
know about it.
So, COM9 is internally "COM9" but COM10 is "\\.\COM10".
Don't know if the SW will accept that. If not you can forward this info
to the developers.
73 Gernot DF5RF

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]