Those options should have been removed for the F/H mode. Perhaps, they
triggered this by accident.
On Mon, Oct 22, 2018 at 9:41 AM Sam W2JDB via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Ctrl-E - Turns on TX Even
> Shift-E - Turns off TX Even
>
> good luck
>
> Sam W2JDB
>
>
>
>
Ctrl-E - Turns on TX Even
Shift-E - Turns off TX Even
good luck
Sam W2JDB
-Original Message-
From: WB5JJJ
To: wsjt-devel
Sent: Mon, Oct 22, 2018 10:32 am
Subject: Re: [wsjt-devel] VP6D on wrong time slot
Yes, you are correct.
I think what we are seeing is a glitch in
Clicking on their (odd sequence) CQ does put my Hound into TX first, and seems
to work okay. The checkbox IS greyed out, so I can’t manually change it.
Ver 1.9.1 running Mac OS.
George J Molnar
Arlington, Virginia, USA
KF2T - FM18lv
> On Oct 22, 2018, at 10:46 AM, WB5JJJ
Ok, ctrl-E, it works, BUT!
Why did they started with odd?
Jarmo, oh1mrr
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi!
It is VP6D, not casual Fox.
Yes, I tried for some time but give up: VP6D was -17 at best, so 20 minutes is
enough.
And they faded out.
For people in wrong TS (or correct one), I've seen it all:
- people calling below 1 kHz
- people calling with TX2, obviously not F/H mode
- people not
Yes, you are correct.
I think what we are seeing is a glitch in the software on their end, which
was an occurrence even I experienced where I was not able to UNCHECK the
EVEN box as it was grayed out. Restarting WSJTx solved the problem and
it's never returned. But how are so many guys
Right now on 20m (14.090) VP6D is transmitting on the ODD time slot. About
half of the callers are on EVEN and the others on ODD. How is the
happening? He's using DX Fox according to what I'm seeing from him.
--
George Cotton, WB5JJJ
___
wsjt-devel
He is using V1.9.1. You are likely using V2.0 RCx. Reinstall V1.9.1 and all
will be well.
73,
Ted
K9IMM
From: WB5JJJ [mailto:wb5...@gmail.com]
Sent: Monday, October 22, 2018 9:02 AM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] VP6D on wrong time slot
Right now on 20m
Il 21/10/18 07:22, Adam Schaible ha scritto:
> Good morning Linux WSJT-X fans,
>
> Awesome discussion going on in this thread, using all the feedback so far
> I've gone and hacked up some build scripts for RC3 on a couple different
> Linux distros (Debian and Solus). First some banter and
Nope. They said they were using v1.9.1 and that's what I'm running.
The option to transmit on EVEN is grayed out since v1.9.0 rc2 ( I just
reloaded all previous versions to see ). In v1.8.x, the F/H option is not
there yet.
I see there is a code that allows CTRL-E and SHIFT-E to switch time
If you try CTL-E or Shift-E, it will toggle the time slot even when grayed
out. This should have been removed in F/H mode, but was not.
On Mon, Oct 22, 2018 at 10:12 AM jarmo wrote:
> Mon, 22 Oct 2018 09:36:05 -0500
> "Ted Gisske" kirjoitti:
>
> > He is using V1.9.1. You are likely using V2.0
Mon, 22 Oct 2018 10:14:29 -0500
WB5JJJ kirjoitti:
> If you try CTL-E or Shift-E, it will toggle the time slot even when
> grayed out. This should have been removed in F/H mode, but was not.
But most funniest thing is,that half world calling wrong period. Don't
watch what's happening on band
Mon, 22 Oct 2018 09:36:05 -0500
"Ted Gisske" kirjoitti:
> He is using V1.9.1. You are likely using V2.0 RCx. Reinstall V1.9.1
> and all will be well.
I have 1.9.1 and impossible work hound, tx even..
Jarmo, oh1mrr
___
wsjt-devel mailing list
I am seeing this too George as of 1415z on 14090. I remember where this could
happened in an earlier version but thought it had been fixed.
Jay KA9CFD
Sent from my U.S.Cellular© Smartphone
Original message From: WB5JJJ Date:
10/22/18 09:01 (GMT-06:00) To:
Weird, worked VP6D on 40M and 20M FT8 today. Received a +03 report,
Gave them a R+xx report, AND received their RR73 but I'm not appearing
in their DXA log!! While others are.
--
Dave, WB5NHL
5BDXCC, 307 countries confirmed
@dkjellqu
___
I just worked him on 40M, George, and he was transmitting on EVEN. I’m
assuming there’s only one operator and he’s running two stations.
John W7CD
From: WB5JJJ [mailto:wb5...@gmail.com]
Sent: Monday, October 22, 2018 7:02 AM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel]
Noticing a few operators calling TX1 below 1000.Is that now blocked in V2.0?
Or should it be? At best they are wasting their time and at worst causing
interference to others.
>From the guide for those that aren't aware:
Hounds make initial calls anywhere in the range 1000 – 4000 Hz.
Fox
Tom --
Your problem has been described a number of times already on this email
list. The work-around solution is simple: run the program from a
command-prompt window.
-- 73, Joe, K1JT
On 10/22/2018 5:40 PM, Tom Harson wrote:
Hello
I am experiencing a program crash with RC3 (*This
Hello.
Since communication between WSJT-X and 3rd-party software like JTalert
are sent by udp packets, could it perhaps be that during the hours of
unattended monitoring, your computer puts the network interface to sleep
(power saving), and thus preventing these udp packets getting trough,
On 22/10/2018 23:38, Anders LA9NKA wrote:
Since communication between WSJT-X and 3rd-party software like JTalert
are sent by udp packets, could it perhaps be that during the hours of
unattended monitoring, your computer puts the network interface to
sleep (power saving), and thus preventing
Buonasera Marco,
OpenSUSE Tumbleweed you say? Sure I can handle that. Here is a tested and
working script to build WSJT-X 2.0.0 RC3 on that distro.
First, disclaimers/notes and then, the script:
1) I am NOT a WSJT-X developer, I am just a regular ham radio operator who
loves Linux. (I did
Hello
I am experiencing a program crash with RC3 (*This does not happen in RC2*)
Also this does not happen when running wsjt alone.
System / Operating information
Using Mint linux ver. 19.0
wsjtx ver. 2.0.0-rc3_amd64.deb
Logging Program - CQRLOG
The program crashes upon DECODE
Here's
Hi all,
...DXA really gives reason to worry. My definite QSO never showed up... along with some
others while I was watching the system. It reminds me of earlier pitfalls with this
system... .
By the way: It was unbelievable to see how many callers did not realize that they were in
the wrong
On Mon, Oct 22, 2018 at 9:15 AM David Kjellquist wrote:
>
> Weird,worked VP6D on 40M and 20M FT8 today. Received a +03 report,
> Gave them a R+xx report, AND received their RR73 but I'm not appearing
> in their DXA log!! While others are.
Same here. Just a wild guess .. maybe DXA can't
On Mon, Oct 22, 2018 at 9:09 AM Iztok Saje wrote:
> It is VP6D, not casual Fox.
> Yes, I tried for some time but give up: VP6D was -17 at best, so 20 minutes
> is enough.
> And they faded out.
>
> For people in wrong TS (or correct one), I've seen it all:
> - people calling below 1 kHz
> -
Also another problem is LOTW fails with Rc3. Downgraded and now all
works well.
/*73’s Rod KI8A*/
/*Cell: 517-404-6554*/
/*Fax: 888-371-0292*/
On 10/22/2018 6:44 PM, Bill Somerville wrote:
On 22/10/2018 23:38, Anders LA9NKA wrote:
Since communication between WSJT-X and 3rd-party software
26 matches
Mail list logo
