Hi Joe, Bill, and all,
I thought you’d be interested in seeing an encouraging result from our tests
the other day. Hopefully, a screenshot will be attached to this, showing two
receive cycles that I recorded while you both (Joe and Bill) were deliberately
transmitting CQs on nearly the same
Just had a contact with VK6KXW on FT8 his sig -14 and mine
-13.works well
73 DAVID VK4BDJ
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
HI...i would suggest that 14.078 where JT9 would be might be a better
frequency for FT8 than 14.079.in VK I know other ops would get
curious as to what they are seeing and may be come interested in
learning about FT8
73 David VK4BDJ
Bill,
I've been using DX Commander with my KX3, and prior to that IC-715 for 4
or 5 years. I really would not want to give that up as it fully
integrates with the rest of the DXLab suite. Is there anything that
Dave can do to adjust Commander ??
Neil, KN3ILZ
On 6/30/2017 8:32 PM,
FWIW ... there has been at least >> 4 << different code releases today
alone. I ran the JTSDK build at 3:00 EDT and built v7752. At 8:50 EDT
or so, I built v7756. The updates are flying as fast as the development
team can test and update. This is one of the reasons why the development
team
Thanks David. Got that done and in the process found there is an updated
TQSL 2.3.1.
From: David Tiller [mailto:dtil...@captechconsulting.com]
Sent: Friday, June 30, 2017 8:05 PM
To: WSJT software development
Subject: Re: [wsjt-devel] K4SHQ FT8 Notes
In
>>>AA6YQ comments below
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Friday, June 30, 2017 8:33 PM
To: WSJT software development
Subject: [wsjt-devel] WSJT-X: Important, [please read if you use an external PA
with WSJT-X
>snip<
There is a notable
Thanks David. Log4OM does indeed use TQSL under the hood. Just where in
TQSL do enter FT8-->DATA?
BTW I have found that QRZ will accept FT8.
From: David Tiller [mailto:dtil...@captechconsulting.com]
Sent: Friday, June 30, 2017 7:47 PM
To: WSJT software development
Re: the second part of item #2: You still can’t upload to eQSL or LoTW with FT8.
If Log4OM is anything like the macOS software I use, it actually uses TSQL
under the covers to do the digital signing and upload. At least in my case, if
you add the FT8 --> DATA mapping in TSQL, the upload works.
1. Log4OM can be made to accept FT8 as a mode. But while it accepts
it as a mode, RST reports are set '59'.
2. Reference #1 above. Making Log4OM accept FT8 is trivial but moot.
You still can't upload to eQSL or LoTW with FT8.
3. Log4OM also does not auto upload to eQSL when
Hi All,
along with the new FT8 mode we reduced the built in delay between PTT
and audio starting. It was such that audio started at the beginning of
the next second. This meant that PTT was asserted soon after the
beginning of a transmit period and audio started at the beginning of the
next
FT8 sounds promising. Joe wrote:
*Three extra bits are available in the message payload, with uses yet to
be **defined. We have in mind special message formats that might be used
in **contests, and the like. Your considered suggestions for use of these
bits **are very welcome!*
1. VHF
On 30/06/17 23:20, Richard Lamont wrote:
> FT8 spots received by me don't seem to be appearing on PSK reporter.
As others have noted, this is fixed in r7755.
73,
Richard G4DYA
--
Check out the vibrant tech community
Hello All,
Just to completeness; I've not used Ubuntu 14.04 in some time. I fired it
up; did a quick package update; rebuilt Hamlib3, then WSJT-X r7755. No
errors or warnings of consequence to end-users. Currently monitoring 20m
FT8.
I am working with Llyod offline to get his issue resolved.
I miss a way to notify a distortion on the emitted signal.
e.g. see the attached image with 4 or more decoding spectra.
I have seen other types of distortions:
2nd an 3rd harmonics all decoding
2n and 3rd harmonic do not decode because the spectrum is X2 or X3 wide.
A shadow spectrum on the
Hi Edfel,
Thanks for your comments. We tend not to increment our version number
until we're ready (or nearly ready) to make an official release. This
will likely be very soon!
-- Joe, K1JT
On 6/30/2017 6:00 PM, Edfel Rivera wrote:
Hi:
Just an observation.
Hi
Builds OK on linux Mint 18.1 64 bit ,which uses the same libs as ubuntu 16.04
On Fri, 30 Jun 2017 16:10:06 -0600
"Greg Beam" wrote:
> Hi Llyod,
>
> You can contact me off-line to keep the traffic on the mailing-dist down a
> bit.
>
> Couple question to answer in the
Hi Joe,
That is a great approach. For some other products the developers seem to want
the average user to debug the software for them, and they release multiple
versions of their product over a very short period of time. The net result is
there are a lot of very unstable products floating
Hi Llyod,
You can contact me off-line to keep the traffic on the mailing-dist down a
bit.
Couple question to answer in the offline email:
* What Linux distro are you using?
* How did you install JTSDK-Nix?
73's
Greg, KI7MT
-Original Message-
From: Lloyd Kirk [mailto:ll...@gcis.biz]
Hi:
Just an observation. FT8 mode addressed an answer to a 'issue' among JT65
and users regarding long time for QSO. I want to congratulate the WSJTX
development team. Thats why I prefer to stick with the 'source' and not
try forks!
IMO, WSJTX versioning should move some numbers up to reflect
We are well aware that displayed values of S/N are unreliable. This
will be fixed soon.
-- Joe, K1JT
On 6/30/2017 5:28 PM, Adrian Fabry wrote:
Hi all,
I saw also this problem.
For example, two signals, one very strong @ 806Hz -15 dB and one weak
@1254 Hz -17dB:
The wav file
Hi Dani,
Thanks for your comments.
As far as I am concerned, a more important reason than possible
licensing issues is the simple fact that when we deem a development
version ready (or nearly ready) for general use, we post "official"
installation packages.
Until that time, we're in
Hello,
Can someone contact me perhaps directly if needed to answer a couple of
questions? I had JTSDK 2.0.21 installed on ubuntu 14.04 and it was
working but would not update the devel wsjtx to current, so I removed it
and re-installed. I have built hamlib, when I try to build the latest
El 30/06/17 a las 19:06, Joe Taylor escribió:
> Anyone is welcome to build WSJT-X from source code, and use the results
> on the air. But please DO NOT post your pre-built binaries for others
> to download. This causes needless support problems for us. We have no
> way of knowing exactly what
To me leaving split completely out of the name is going to prompt questions of
"why did my rig go into split mode".
It actually does a frequency split just like all splits do. It's just that
WSJT-X then adjusts the audio to maintain the reception offset during transmit
instead of you having to
As of right now the function keys won't work menu's when the menu is disabled.
It should be possible to intercept the key and do it anyways.
Since I made the CTLR-M patch I'll take a look at still processing functions
keys when menu is disabled.
de MIke W9MDB
From: Edfel Rivera
eQSL is unlikely to put FT8 or JT10 on until the ADIF specs are updated to
reflect it.I've posted the request to the ADIF group.
de Mike W9MDB
From: Gordon Higgins
To: WSJT software development
Sent: Friday, June 30, 2017 1:07 PM
Hit F3 to see a list of keyboard shortcuts, and look at the entry for
CTRL+M.
On 6/30/2017 2:40 PM, Edfel Rivera wrote:
Hi:
I am not sure what I did but I am not able to access configuration.
Also, can not change band. I tried building new but no fix.
Previously used 1.7.1 with out any
Hi:
I am not sure what I did but I am not able to access configuration. Also,
can not change band. I tried building new but no fix.
Previously used 1.7.1 with out any problem.
Thanks.
Edfel
KP4AJ
--
Check out the
Hi All,
FT8 working nice here, a big thanks to Joe and Steve.
I have collected about 150 FT8 wav files from 20m and 6m (tropo, MS, ES).
Some of them no decode, maybe useful to analyze.
S/N from -19 to +2dB.
https://www.dropbox.com/sh/busdna76pjavht7/AAAXLDcC1sOfarmeLWsMU5vBa?dl=0
Hello!
I am trying to connect my IC 7000 to the WSJT-X, but I only get the message:
"hamlib error: Communication bus error while getting current frequency"
Can you help?
I have downloaded the latest version of your program; v.1.7.0 r7405 and
I have Windows 10 on my computer.
Hope you can
have been using FT8 today on 20m 18 qso in log 14dxcc eqsl will not exept
mode ?
like mode very quick no faults exept eqsl
On 30 June 2017 at 18:55, Dan Malcolm wrote:
> FYI. I just tried the “split” mode in WSJT-X for an FT8 QSO. My Apache
> 100D seems to like it
FYI. I just tried the “split” mode in WSJT-X for an FT8 QSO. My Apache 100D
seems to like it just fine.
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Friday, June 30, 2017 12:04 PM
To: WSJT software development
Cc:
I'd like to weigh in on the "what to call it" discussion. Not that I have
anything really better, but since we already have a well understood "split
mode", called this a split confuses one function with another. Can we say
something like "Audio Purity Offset"?
I have not used it before I'm
David, Jay, and others --
We have been through this here before.
Anyone is welcome to build WSJT-X from source code, and use the results
on the air. But please DO NOT post your pre-built binaries for others
to download. This causes needless support problems for us. We have no
way of
What if we just named that box "Audio Split Operation" and improve the tooltips?
Tooltip on groupbox: Special split ops for cleaner audio -- see help
fileTooltip on None: No splitTooltip on Rig: Use rig split capabilityTooltip
on FakeIt:Split occurs on VFOA during transmit
Might have to
Hi George,
On 6/30/2017 12:38 PM, George J Molnar wrote:
The nut here seems to be with the use of the term “split.” It implies
two different frequencies are being used for the contact. This threw me,
and probably some others.
Yes, I understood what you took to be the meaning of "split".
The
Just some food for thought.
Some of these development builds could be compiled into a exe install
package once in a while and made available from the sourceforge site or
maybe a link from the WSJT home page or wsjtx.net for those who want to try
the new mode but are intimidated at installing
(Sorry Joe - posted this to you instead of the group - apologies for the double
message)
Hi Joe,
I was just about to send an “amen” to Mike’s comments - he hit it on the head.
The nut here seems to be with the use of the term “split.” It implies two
different frequencies are being used for
What rig are you having split problems with?I'm always interested in fixing
hamlib problems like that.
de Mike W9MDB
From: Jordan Sherer
To: WSJT software development
Sent: Friday, June 30, 2017 11:30 AM
Subject: Re:
More recent gcc versions now detect indentation inconsistencies.
A minor fix for qra64.c
https://www.dropbox.com/s/n67v5kg1tltj1fv/qra64_patch.txt?dl=1
I'd recommend developers get into the habit of ALWAYS adding bracesI found
one error in hamlib due to this and this patch "fixes" what is
Thanks Bill,
Yep. This was the issue. It looks like my rig doesn't like custom offsets
for split mode over CAT. Haven't researched it much yet. But, swapping over
to "Fake It" worked like a charm, no issue.
Thanks again!
Best,
Jordan
KN4CRD
On Fri, Jun 30, 2017 at 10:45 AM, Bill Somerville
Hi George,
Still feel like the way this is being implemented is counter-intuitive
for most operators. After your explanation, I get it. That said, I’ve
made 10,000 JT-mode QSOs and it never occurred to me when I saw this. I
think we might see a fair number of folks fall into the same
Can you can think of a better thing to call it? I agree that for newbies it's
not intuitive as there have been quite a few who have questioned what it's for.
Did you read the help and find it inadequate? We either need to name it
something other than split (maybe call it purity or some such
Hi George
Simple solution here is to select rig as 'none' and tune manually.
Just had my first QSO on 20m. All looks very good.
73
Charlie
_
From: George J Molnar [mailto:geo...@molnar.com]
Sent: 30 June 2017 17:08
To: WSJT software development
Subject: Re:
Thanks, Mike and Bill, for the clarification.
Still feel like the way this is being implemented is counter-intuitive for most
operators. After your explanation, I get it. That said, I’ve made 10,000
JT-mode QSOs and it never occurred to me when I saw this. I think we might see
a fair number of
Hi all,
tomorrow I try RX in the new mode and seem to be simple fantastic!!
I do some local QSO for practice on autosequence.
If try to search in pskreporter all QSO in 24h on any band any callsign
mode=FT8 it report only 1 QSO.
Is this wanted?
Thank you all for the new gift
--
73
Joe,
OK.
osd can only be successful if it is given candidates. I’m noticing now that the
current sync threshold is high enough where bp probably doesn’t fail all that
often. In any case, more candidates fed to osd would only increase the fraction
of time spent in that routine. It doesn’t
On 30/06/2017 15:37, Jordan Sherer wrote:
Jumping in here since it's sort of relevant to the discussion.
One oddity I found this morning while operating split:
0. I load up WSJTX on 20m
1. I have enabled FT8 mode with rig ctl split
2. VFO is at 14.079.000, transmit offset at 800Hz
3. Tx cycle
HI Joe & Steve,
one quick win might be to implement a more CPU intensive decode at the
Rx DF +/- a few Hertz when clicking the "Decode" button or double
clicking the waterfall. I believe most of the logic to drive this is
already in place.
73
Bill
G4WJS.
On 30/06/2017 15:34, Steven Franke
Jumping in here since it's sort of relevant to the discussion.
One oddity I found this morning while operating split:
0. I load up WSJTX on 20m
1. I have enabled FT8 mode with rig ctl split
2. VFO is at 14.079.000, transmit offset at 800Hz
3. Tx cycle correctly adjusts split to 14.078.500
4. I
On 30/06/2017 15:25, Bill Somerville wrote:
one of us is misunderstanding the situation. There is no "split" of
the on-air signals, stations using split are transmitting exactly
where the red cursor is placed on the waterfall which is exactly the
rig's dial frequency plus the Rx DF.
Sorry, I
Joe,
Were these results obtained with 40 iterations for bp and norder = 3 for
signals at or within 10 Hz of nfqso? If so, it might be interesting to see how
the numbers would change if you dropped back to norder=2 for all signals.
Steve
> On Jun 30, 2017, at 9:25 AM, Joe Taylor
Mike,
msk144sd is just a development routine - it is not used in WSJT-X.
Steve
> On Jun 30, 2017, at 8:15 AM, Black Michael via wsjt-devel
> wrote:
>
> Looking at some of the compilation warningstframe pops out as
> uninitialized...and appears to not be
You misunderstand how split works with WSJT-X. It's not like the split you're
used to on other modes.Technically, it is "split" as two your transmit/receive
are different.
But nobody even knows you're doing split but you. WSJT-X adjusts the audio on
the carrier to stay at your offset.
On 30/06/2017 15:21, George J Molnar wrote:
Good morning/afternoon, Bill.
Don’t think anything is going wrong. Clearly, it’s working the way
it’s written.
My concern is that, in a crowded band situation, as stations spread
out, having the software automatically “split” TX and RX in the name
Hi all,
Thanks for a busy ~20 hours of many people testing FT8. I now have
accumulated a directory with 527 *.wav files, each of which has at least
one visible FT8 signal. The files were recorded at K1JT at either
14.079 or 50.313 MHz.
Running the r7753 stand-alone slow-mode decoder
Good morning/afternoon, Bill.
Don’t think anything is going wrong. Clearly, it’s working the way it’s written.
My concern is that, in a crowded band situation, as stations spread out, having
the software automatically “split” TX and RX in the name of spectral purity
could lead to unintended
Hi George,
please explain in detail what you think is going wrong? The behaviour
Erik described is normal and correct behaviour and allows you to
transmit at *any* DF plus it helps to keep your transmit signal as clean
as possible.
73
Bill
G4WJS.
On 30/06/2017 14:12, George J Molnar wrote:
Hi Joe, Steve and Bill,
FT8 busy on 20m this afternoon. r7752 operational on Mac OSX 10.11 without
problems…
— John G4KLA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites,
Mike --
A large number of such "development routines" are presently listed in
CMakeLists.txt and compiled in a standard CMake-driven build, but not
actually used in wsjtx[.exe]. We're discussing, after all, the
Development Branch. In due course, "code cleanups" of the sort you
suggest will
Perhaps we should remove it from the compile chain then?
de Mike W9MDB
From: Steven Franke
To: Black Michael ; Joe Taylor
Sent: Friday, June 30, 2017 8:28 AM
Subject: Re: [wsjt-devel] msk144sd.f90 problem?
Looking at some of the compilation warningstframe pops out as
uninitialized...and appears to not be used at all.
Line 136 of lib/msk144sd.f90
if(ndecodesuccess .gt. 0) then
tdec=tsec+xmc(iavg)*tframe fest=fo+(fest-fc)/32.0
If I understand FORTRAN default
I see the same, and suggest it not be continued as the normal behavior. In a
multi signal environment, it will likely lead to confusion.
Using a configuration for FT8 that turns off split capability is a workaround
for now, it seems.
George J Molnar, KF2T
Nevada, USA
> On Jun 30, 2017, at
One FT8 record in pskreporter (RA9HO heard by I3RGH). Hopefully the
first of many!
Congratulations.
Philip
On 29/06/2017 21:58, Tim Carlson wrote:
I just made my first FT8 QSO with WB4KDI as well. I agree - very cool.
-Tim - KD0GYG
On Jun 29, 2017, at 6:43 PM, C. Gary Rogers
Hey Bill,
Deps are up to date and there are no dist upgrades available. I restarted
the app and haven't had another issue yet...just an empty band here. I'll
let you know if I find a reproducible test case.
73
Jordan
KN4CRD
On Fri, Jun 30, 2017 at 8:12 AM, Bill Somerville
On 30/06/2017 13:06, Jordan Sherer wrote:
I'm a new comer to the wsjt-devel list. Software engineer by day. Ham
by night.
I was able to get a build of WSJTX r7752 running on my Ubuntu box this
morning. I tried calling a few CQs on 20m a few minutes ago and had a
segfault. Attached is a copy
Howdy All!
I'm a new comer to the wsjt-devel list. Software engineer by day. Ham by
night.
I was able to get a build of WSJTX r7752 running on my Ubuntu box this
morning. I tried calling a few CQs on 20m a few minutes ago and had a
segfault. Attached is a copy of the core dump.
Happy to help
On 30/06/2017 08:18, Erik Icket wrote:
I successfully operate latest build 7752, and in the last 12 hours, I
was able to copy on 14079 the following stations :
OE1MWW, F1ABL, CT1FBK, I3VJW, KB3MOW, AK1P, VA3VF, K9AN, K4DET, WB4KDI
There is however one anomaly with my rig control (ICOM 7100
On 30/06/2017 02:29, Takehiko Tsutsumi wrote:
Would you change the section of FrequencyList.cpp on 80m to be
operable for JA stations as follow?
{357, Modes::JT65},
{3572000, Modes::JT9},
{3573000, Modes::FT8},
{3572600, Modes::WSPR},
Current frequencies are used for Government Use and
On 30/06/2017 02:24, Roger Rehr W3SZ wrote:
Bill G4WJS had given a warning on June 9 to "Beware if building from
development sources" with revisions later than r7703, due to some
transmission modulation issues.
Given the recommendations for us to try JT8 and the great enthusiasm
being shown
...build went like a breeze, just did an svn co and followed
instructions in INSTALL. (Revision 7752)
I might be able to try the new mode tonight around 2230 UTC
Cheers,
Tamas HA5FTL
2017-06-29 20:47 keltezéssel, Tamás Fábián írta:
I'm going to try and compile it on Ubuntu 17.04 "zesty"
I successfully operate latest build 7752, and in the last 12 hours, I was
able to copy on 14079 the following stations :
OE1MWW, F1ABL, CT1FBK, I3VJW, KB3MOW, AK1P, VA3VF, K9AN, K4DET, WB4KDI
There is however one anomaly with my rig control (ICOM 7100 in SPLIT mode) :
When I PTT
73 matches
Mail list logo