Working great for me...made several contacts above 2000 Hz.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Tuesday, November 13, 2018, 10:45:36 AM EST, WB5JJJ
wrote:
If you read the release notes, support for legacy FT8 has been removed. Only
77bit operation is available.
On Tue, Nov 13,
by looking at them on the waterfall? I did notice that possibly the
signals I was not decoding didn't seem to have the same "cycle" time as FT8
but not sure. Any insight?
Don AA5AU
From: Ed Wilson via wsjt-devel
To: "wsjt-devel@lists.sourceforge.net"
Cc: Ed
Maijan,
It is possible that the strong signals that you could not decode were FT8Call
signals. The developer of this "experimental" application recommends 14.078 as
a default dial frequency just like WSJT-X 2.0 -rc1 with the 77 bit option. Both
applications also recommend using 7.078 on 40 meter
:25 PM EDT, Bill Somerville
wrote:
Hi Ed,
some comments in line below.
On 09/07/2018 16:59, Ed Wilson via wsjt-devel wrote:
I have enjoyed building and testing WSJT-X developmental releases over the
past few years and would like to continue to do so. I understand that the move
to
I have enjoyed building and testing WSJT-X developmental releases over the past
few years and would like to continue to do so. I understand that the move to
GitHub has required some changes to the JTSDK build process and I have followed
Greg Beam's excellent instructions and have successfully bu
Tom,
My understanding is that this is not a bug, but is by design. I would prefer
that Tx would be disabled in this situation, but others think just the
opposite. I believe that the reasoning is that if you continue to call a
station (off frequency), then you might be next in his queue when he w
I guess this is why I did not see a power increase since I have never changed
the default delay of 0.2 sec. I also used the “eyeball” method of observing the
signal in the time domain rather than an oscilloscope, so I probably missed the
initial spike in power.
> On Apr 5, 2018, at 6:43 PM, Bla
I built r8603 this morning and in a limited amount of operating FT8 on 80 and
30 meters, the output power seems to be rock solid. I run a Flex-6700 but that,
of course, should not matter..
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Thursday, April 5, 2018, 1:09:29 PM EDT, rjai...@gmail.com
Thanks, Joe...r8591 fixed this little "glitch".
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Thursday, March 29, 2018, 10:47:03 AM EDT, Ed Wilson via wsjt-devel
wrote:
I reverted back to r8576 and this anomaly did not appear.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Thurs
I reverted back to r8576 and this anomaly did not appear.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Thursday, March 29, 2018, 8:58:24 AM EDT, Ed Wilson via wsjt-devel
wrote:
I am currently running WSJT-X 1.9-rc3 r8590. I have set the option to have the
program prompt me to log a QSO
I am currently running WSJT-X 1.9-rc3 r8590. I have set the option to have the
program prompt me to log a QSO. I noticed this morning that upon a prompt, the
Report Rcvd field is blank and that I have to enter that value manually.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/-
I am currently testing r8164 but have noticed the following bug in previous
releases:
Lets say I am working G3XXX on FT8 and using Auto Seq. We get to the point in
the QSO where he sends me RRR and I send 73. He apparently does not decode my
73 and sends another RRR. I then manually move to Tx 5
Joe,
Although I have not yet tested r8148, I noticed that the "Tool Tip" needs
updated in r8146 on "Hold Tx Freq".
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Sunday, October 01, 2017 08:39:24 EDT, Joe Taylor
wrote:
Hi Erik,
Thanks for reporting this defect. I had left
I built r8044 this morning to test the double-click on call option and it
worked fine with my Flex-6700. I then changed configurations to one for my
Flex-5000, checked the box for the double-click on call option to test it with
this configuration and it failed to place Tx=Rx when I double-clicke
is Wideman via
wsjt-devel wrote:
This is where more and better filters would also be useful when the left
screen is full of calls that have nothing to do with your call or QSO. Hope you
get to feeling better Ed.73 Morris wa4mit
On Friday, September 29, 2017, 11:03:39 AM CDT, Ed Wilso
Gary,
I agree that people should notice the red line, but I think they tend to get
tuned-in to the right-hand window when looking for a response. I know that I
have missed a couple myself.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Friday, September 29, 2017, 2:37:26 PM EDT, Gary McDuffie
I have been using WSJT-X since its inception and JT65-HF before that. I was
always one of those "bad guys" who checked the Tx=Rx box unless I was trying to
contact a DX station where dozens of others were probably calling him or her
and it made sense to call off-frequency.
Over the past couple o
what version JTAlert are you using?
de Mike W9MDB
On Tuesday, September 26, 2017, 6:23:58 AM CDT, Ed Wilson via wsjt-devel
wrote:
I built r8123 this morning and was pleased to see that double-clicking on a
station calling CQ moves both the Tx and Rx frequencies to that of the caller.
Altho
o get on a "Q" list with the DX station.
Bill W2PKY
On Tue, Sep 26, 2017 at 7:30 AM, Ed Wilson via wsjt-devel
wrote:
Although it is not new to r8123, I have noticed that when I call a station and
someone else is also calling him or her and that calling station does not
answer me, Tx
manually.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Tuesday, September 26, 2017, 8:03:08 AM EDT, Hasan al-Basri
wrote:
That's a feature, not a bug, i.e., intentional73, N0AN
Hasan
On Tue, Sep 26, 2017 at 6:30 AM, Ed Wilson via wsjt-devel
wrote:
Although it is not new to r8123, I
Wolfgang,
I did not receive the UDP error message but I shut down both WSJT-X and JTAlert
several times as you suggested below and still do not have UDP communication
from JTAlert to WSJT-X. In fact, there was no communication from WSJT-X to
JTAlert until I restarted both several times.
Ed, K0KC
Although it is not new to r8123, I have noticed that when I call a station and
someone else is also calling him or her and that calling station does not
answer me, Tx is not disabled when the Tx frequency is offset from the receive
frequency. If the Tx and Rx frequencies are the same, Tx is disa
I built r8123 this morning and was pleased to see that double-clicking on a
station calling CQ moves both the Tx and Rx frequencies to that of the caller.
Although I can appreciate the comments of some of my colleagues suggesting that
only the Rx frequency be moved, I believe that moving both is
Understood Joe!
I guess I am just one of those people who likes to be on the cutting edge with
the understanding that I might suffer wounds occasionally.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Monday, September 25, 2017, 2:57:47 PM EDT, Joe Taylor
wrote:
Hi Ed, Charlie, Neil, and al
I built r8119 this morning and was surprised to find that with Lock Tx=Rx
unchecked, double-clicking on someone calling CQ (or otherwise calling another
station) just moves the Rx frequency to that of the station calling rather than
both the Tx and Rx frequency as before.
I have been trying to t
Morris,
Have you tried JTAlert? This software provides some of the same functionality
that you want from WSJT-X. Check-out:
http://hamapps.com/
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Monday, September 25, 2017, 8:16:13 AM EDT, Morris Wideman via
wsjt-devel wrote:
HelloI would like
I have been testing WSJT-X rc2 on FT8 over the past few days and noted that it
has the same defect that I reported earlier of the Tx5 line in the Standard
Messages seemingly randomly showing-up and transmitting blank. I built r7935
yesterday and noted today that the same issue continues to exist
I have been testing rc2 today. As I reported previously (when testing an
earlier release) there is an issue where Tx5 (the 73 line) appears blank on an
apparently random basis maybe 10% of the time. I have not been able to pin-down
if any particular sequence of events causes this problem. Mike
Dear Developers,
I was testing r7891 this morning on FT8 mode. I noticed that the "73" line in
the standard messages sometimes came-up blank when I double-clicked a call sign
to attempt a QSO. This happened on a random basis, perhaps 10% of the time. I
have now moved back to an earlier build. Ed
:14 AM, Ed Wilson via wsjt-devel wrote:
> I have been testing FT8 for the past week or so and today decided to
> try to make a JT65 contact on six meters. I am using r7836, which I
> built this morning. I made a contact with WB5TUF near Houston with -01
> at both ends and found an is
Re: [wsjt-devel] r 7836 Issue
This is fixed in 7838.
de Mike W9MDB
From: Ed Wilson via wsjt-devel
To: "wsjt-devel@lists.sourceforge.net"
Cc: Ed Wilson
Sent: Monday, July 10, 2017 12:15 PM
Subject: [wsjt-devel] r 7836 Issue
I have been testing FT8 for the past week or so
Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, July 10, 2017 1:16 PM
Subject: Re: [wsjt-devel] r 7836 Issue
On 10/07/2017 18:14, Ed Wilson via wsjt-devel wrote:
I have been testing FT8 for the past week or so and today decided to try to
make a JT65 contact on six mete
I have been testing FT8 for the past week or so and today decided to try to
make a JT65 contact on six meters. I am using r7836, which I built this
morning. I made a contact with WB5TUF near Houston with -01 at both ends and
found an issue with his transmissions NOT showing in the Rx Frequency w
suggestion is a fix. Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Sunday, July 9, 2017 12:16 PM
Subject: Re: [wsjt-devel] FT8 Issue
On 09/07/2017 16:44, Ed Wilson via wsjt-devel wrote:
> I am using a Flex-6700.
Hi Ed,
I believe is
Thanks for the suggestion, Bill...I will give it a try. Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Sunday, July 9, 2017 12:16 PM
Subject: Re: [wsjt-devel] FT8 Issue
On 09/07/2017 16:44, Ed Wilson via wsjt-devel wrote:
>
-X sending CAT QSY commands to
certain rigs that will not process them while transmitting. It is the reason
that you cannot move to another caller while you are transmitting and has been
so for a number of versions.
73
Bill
G4WJS.
On 09/07/2017 16:34, Ed Wilson via wsjt-devel wrote
George,
I really think that I am clicking soon enough, although I am definitely not a
gamer nor am I a teenager!. I was doing fine with FT8 for about 50 contacts and
then yesterday I started having problems. I will try testing again later today
before I draw any conclusions (good excuse to buy a
AM
Subject: Re: [wsjt-devel] FT8 Issue
Under Settings/General do you have "Double-click on call sets Tx enable"
checked?
de Mike W9MDB
From: Ed Wilson via wsjt-devel
To: "wsjt-devel@lists.sourceforge.net"
Cc: Ed Wilson
Sent: Sunday, July 9, 2017 7:29 AM
Subje
Ady,
That option is not checked. As far as I know, I have never operated with that
option checked when using WSJT-X.
Thanks for the suggestion. Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
From: Adrian Fabry
To: 'Ed Wilson' ; 'WSJT software development'
Sent: Sunday, July 9, 2017 8:34 AM
Su
I forgot to mention that I am using r7816...duh! Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
From: Ed Wilson
To: "wsjt-devel@lists.sourceforge.net"
Sent: Sunday, July 9, 2017 8:04 AM
Subject: FT8 Issue
Colleagues,
I have been testing FT8 since it was made available near the end of June.
Colleagues,
I have been testing FT8 since it was made available near the end of June. I
have made approximately 60 contacts with this mode and like it a lot. JT65/JT9
seems like slow motion now! As predicted from the simulations, it does appear
to be somewhat less sensitive than JT65/JT9, but I
41 matches
Mail list logo
