Hi Steve,
Very interesting! The model and received spectra are remarkably close
to identical. In fact, it's hard to see any differences as large as 5
dB, such as the spikes around 750 Hz in the top right plot.
I guess the fact that phase differences are mostly in the range +/- 45
deg (at
Hi all,
On 11/21/2016 3:46 PM, Alessandro Gorobey wrote:
> Hi Claude,
>
> I try the some at oct 16.
>
> ===> Ubuntu Xenial:
> At line 154 of file /home/sandro/jtsdk/src/wsjtx/lib/packjt.f90
> Fortran runtime error: Substring out of bounds: lower bound (-5) of 'c'
> is less than one
>
>
Hi Anders,
Yes, by all means please go ahead and release your draft of the Swedish
User's Guide for WSJT-X v1.6.0. I will be happy to post it on the WSJT
web site. Many thanks for your effort!
We hope to have v1.7.0 ready for release fairly soon, too.
-- Joe, K1JT
On 11/27/2016
Why would I want JTAlert to start a QSO?
On 11/22/2016 6:23 PM, Black Michael wrote:
> The change in r7329 to fix the Autoseq disables JTAlert's ability to
> start the QSO. Clicking in JTAlert will show the CQ message in the
> receive window but no longer enables "Enable Tx".
> r7328 works fine.
nd the reply packet causes WSJT-X to Enable Tx.
> Having an extra click to Enable Tx is an ergnomic pain.
>
> de Mike W9MDB
>
>
>
>
> ------------
> *From:* Joe Taylor <j...@princeton.edu>
> *To:* WSJT softwa
Terry --
N8JX wrote:
> Joe is it possible to fix tx2 in jt65 sends same message as tx1 example
> (shows tx2 UR0MC N8JX EN64 OOO but transmits UR0MC N8JX EN64)
> Tnx 73 Terry
The correct message was being sent, but the "OOO" report was
inadvertently omitted when the message was displayed in the
On 10/31/2016 7:10 PM, Black Michael wrote:
> Running r7273.
> What's up with "#*" modes?
#* ==> JT65 mode, normal sync achieved
## ==> JT65 mode, reverse sync ==> EME 'OOO' signal report.
It would appear that you have VHF features enabled ??
-- Joe, K1JT
Hi Mike,
On 10/31/2016 11:30 PM, Black Michael wrote:
>>> What's up with "#*" modes?
>>
>> #* ==> JT65 mode, normal sync achieved
>> ## ==> JT65 mode, reverse sync ==> EME 'OOO' signal report.
>>
>> It would appear that you have VHF features enabled ??
> Yup...that would be it...was testing a
On 11/2/2016 2:21 PM, Relu Jianu wrote:
> I'm sorry for stirring this up, I was more concerned with the usefulness of
> this file in the VLF and VHF/UHF and or EME modes where I would think (maybe
> naively) that priori would benefit a user giving the additional deep decode
> advantage.
> I
On 11/1/2016 6:54 PM, Relu Jianu wrote:
> Is there a mechanism of updating the call3.txt list?
>
> Thanks
> 73 Relu NJ9R
Everyone's working habits of band, mode, location, etc., are different.
The callsign database is best maintained by you, yourself, using the
"Add" button on the WSJT or
nterested in spotting one beacon
> who is to say what is too short?
>
>
>
> Bob Thornton
>
> G3WKW
>
>
>
> Date: Tue, 01 Nov 2016 19:05:37 -0400
> From: Joe Taylor <j...@princeton.edu <mailto:j...@princeton.edu>>
> Subject: Re: [wsjt-devel]
Hi Steve,
Sorry that you found the canned response accompanying rejection of your
post to wsjt-devel from an un-subscribed email address to be rude. As I
recall, that message simply says that posts are accepted only from
registered subscribers.
We have found this restriction to be necessary
On 11/2/2016 10:06 AM, Black Michael wrote:
> How does one turn on hinting? It's not in the Manual and I don't see it
> in the Settings anywhere.
> And if it's not appropriate on HF then disable it on HF if it's enabled.
> And give an educational message or link to the manual entry so people
>
Hi Rex and Bill,
Thanks for the corrections to the User Guide text concerning
*Allow Tx frequency changes while transmitting*. I should have caught
that... and will fix it.
-- Joe
--
The Command Line:
Hi Mike,
w9MDB wrote:
> Did you intend to expose all the controls for all modes now?
> Mode JT9 has a greyed out "Fast" -- a place holder I guess.
No changes here. JT9 has a *Fast* checkbox when VHF Features are
enabled. This has been true for a long time. It should be greyed out
when
Hi Wolfgang,
Thanks for reporting this -- your help is much appreciated! Additional
corrections have been made in revision 7175. Please continue your
careful checking of such things!
-- Joe
On 10/13/2016 1:18 PM, Wolfgang wrote:
> Hi,
>
> just a minor thing: if one clicks the
Hi all,
I've tried in r7165 to make arrangement of controls in the central part
of the main window look somewhat more polished, and also to be more
consistent with the actual needs of the different modes and the status
of "Enable VHF features". Please let us know if you find a need for
Bob --
K8VFV wrote:
> I welcome back the CW IDer. THANKS! But, it does not send the correct CW!
Sorry, but that's not a very useful message.
If there's a problem, we need to know exactly what you think the problem
is, and how to reproduce it. In what mode? With what T/R interval, and
Hi all,
Anders Rhodin, SM7VRZ, has completed a Swedish translation of the User's
Guide for WSJT-X version 1.6. I have posted it on the WSJT web site here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-1.6.0.se.html
Please help to spread the word of its availability to any who
Hi Jim,
On 12/15/2016 12:18 PM, Jim Brown wrote:
> If you can tell me where to find the .wav, I can send it, but I'm not
> sure if you would want it. I can't even find the file corresponding to
> the left display of decodes. :)
If you have checked *Save all* or *Save decoded*, .wav files are
Hi Jim,
On 12/15/2016 1:36 PM, Jim Brown wrote:
> Thanks. Do you WANT these files? If so, I'll send them. Otherwise I
> won't bother.
No need to send files.
-- Joe
--
Check out the vibrant tech community on
Hi Jim,
Without specifics and saved .wav files it's impossible to comment in any
detail on your false decodes.
When developing the two-pass decoder, we analyzed over a thousand .wav
files in crowded band conditions. The probability of false decodes was
higher for second-pass decodes than for
In JT9+JT65 mode the text window on the right-hand side displays
received messages at the selected Rx frequency. Your screen shot shows
your Rx (and Tx) frequency set at 553 Hz. The signal from NF3R is at
1165 Hz. Decodes of his signal therefore appear in your left ("Band
Activity" window
Relu --
On 12/15/2016 11:43 PM, Relu Jianu wrote:
> The worse part is when you think they actually call you. HI
> I got fooled on one instance, the call sign was correct so I tried replying.
> The locator seems right too but it's 160 and I am on a city lot so not likely.
> I'll try enabling
Hi Dmitry,
On 12/16/2016 5:01 AM, Дмитрий Гончар wrote:
> Hi! I have a problem with WSJT on XUBUNTU 14.04 LTS. WSJT Version 9.3 r2792
> from a native repository is established.
> The program works, but the figures which are responsible for audio in the
> lower left corner of a main window are
Hi Bill,
On 1/9/2017 5:28 PM, Bill Somerville wrote:
> I have just been looking at a problem with FeqCal when FTol>DF, I have a
> fix for that but I also noticed that, when I connect another WSJT-X
> instance as a tone generator back to back (digital loopback) with an
> instance running FreqCal,
Hi Edson,
On 1/10/2017 12:39 PM, Edson W. R. Pereira wrote:
> I got across this paper some time ago. The algorithm suggested could
> perhaps be applied to FreqCal.
>
> https://mgasior.web.cern.ch/mgasior/pap/FFT_resol_note.pdf
>
> 73, Edson PY2SDR
Thanks for the pointer to an excellent paper!
Hi Bill,
You might want to look at what I've done in MainWindow::freqCalStep(),
lines 6115 - 6127 of mainwindow.cpp in WSJT-X r7485. I think it works
correctly, but there is probably a better way to make use of your
m_frequency_list_fcal_iter iterator.
-- Joe
Hi all,
Gotta share my minor triumph of the day. :-)
Here are the first-ever decodes of QRA64 signals received by MAP65:
UTC S/N DT FreqMessage
--
0140 -23 2.3 480TNX JOE
0220 -25 2.5 322K1JT NJ2R EN82
0222 -24 2.5 321K1JT NJ2R R-26
Hi Bill,
On 1/12/2017 1:36 PM, Bill Somerville wrote:
> I was just looking at those changes. The iterator follows the pattern of
> C++ Standard Library iterators which model pointers. So using them as
> you might use a pointer is ok, I will check the usage.
>
> I note that the code to skip
Hi Charlie and all,
> It seems that if TX Delay in Advanced settings is set >1s it causes
> truncation of a QRA64 signal.
>
> I don’t know if this is of any consequence – it could cause loss of part
> of the first Costas array.
It will cause truncation of the first part of the Tx waveform in
Deal Colleagues,
Thanks to all coders, bug reporters, and testers for helping us to get
WSJT-X v1.7 into good shape for a third candidate release.
The following notice will be sent soon to the wsjtgroup reflector.
-- 73, Joe, K1JT
Mike --
Thanks for submitting this patch. The plan now is to release v1.7.0-rc3
very soon, maybe this weekend. A GA release of v1.7.0 may follow within
about a week. When that happens, the development branch will become the
"v1.8.0" branch.
Because your proposed changes are rather
On 12/30/2016 4:23 PM, Black Michael wrote:
> Fix geometry restore to correct for minimized main window after restart.
>
> https://www.dropbox.com/s/o6c76u8h3ym6z2c/geometry.patch?dl=1
>
> de Mike W9MDB
Part of this patch is committed in r7433. I did not remove these two
statements
Hi Charlie,
> Having used MSK144 now with a rather slow PC, it would be a ‘nice to
> have’ if some previous settings could be recalled on restarting the
> program in MSK144 or switching from another mode into MSK144.
>
> Specifically, the decode setting (in my case ‘fast’) and possibly Ftol.
>
Hi Charlie,
On 1/4/2017 10:50 AM, char...@sucklingfamily.free-online.co.uk wrote:
> I find either exiting the program from MSK144 or using a configuration
> doesn't seems to work, and the program returns to default 5 s period
> (which I forgot to mention), Deep decoding and Ftol of 200. I
Here's a brief update for those who may not be active on the VHF bands
or otherwise following the development of QRA64 and MSK144.
QRA64A QSOs are being made nightly on 160 m, of all places; and QRA64
activity on 2m EME is becoming significant, especially on weekends.
Last Friday evening I
With WSJT-X code revision r7467 the tools are in place to allow you to
determine calibration constants (Intercept A and Slope B) for your radio.
Builds using cmake will put the programs fmtave[.exe], fcal[.exe] and
fmeasure[.exe] in the .../install/bin directory along with wsjtx[.exe]
and the
Hi Bill,
Thanks for your additions to FreqCal mode committed in r7463. They are
just about what I had been planning, but you were one step ahead of me!
Before long I will provide some instructions for using this mode to
calibrate one's radio.
-- Joe, K1JT
Hi Bill (ND0B) and all,
I've been away most of the time since your post, and just now finding
time to respond. You gave us a long list of ideas, with no evident
prioritization. You mentioned to me that you were "in the process of
learning C++ and QT by immersion". Of course you're the best
On 1/2/2017 1:33 PM, Gordon Higgins wrote:
> What is the meaning of the tail nombers in msk155
> ie g3pxt dk9wi +01 1 8 -0.8
The first number is described in the WSJT-X User Guide, in a table found
here:
Andy --
K3WYC wrote:
> That assertion is simply not true. I keep v1.3 r3673 on my computer so I
> can check things like this. In r3673 pressing the lit "Enable Tx" button
> while transmitting a message does stop the message transmission!
WSJT-X v1.3 (r3673) was made more than three years ago.
Hi all,
Several users with good computer know-how have been helpful during the
roll-out phase of WSJT-X v1.7 (-rc1, -rc2, ...) by building successive
code revisions and making them available to other users. At such times
of incremental bug fixes and minor improvements, user feedback is a big
Dan --
On 12/20/2016 2:31 PM, Dan Bates N5TM wrote:
> Joe, 7405 seemed to have a major bug when trying to run QRA64. The Decode
> button would stick in "blue" and no decode would appear. I'm now testing
> 7412 and QRA seems ok.
Yes, you can get r7405 into the state you describe. Also 7412. I
Dear Colleagues,
Thanks to all for your many contributions to the development of WSJT-X,
Version 1.7. The following notice will be sent soon to the wsjtgroup
and Moon-Net reflectors.
-- 73, Joe, K1JT
To:
Noise blanking is best carried out well upstream of a reveiver's
demodulated audio output -- preferably at a point where bandwidth is
still relatively large.
On 12/16/2016 8:37 PM, David Tiller wrote:
> I'm currently suffering thru S9 arc noise at my QTH on 30m - 6m, but I
> figured I'd try to
Hi Jay,
On 12/19/2016 3:38 PM, Jay Hainline wrote:
> Since WSJT-X 1.7.0 has now been released for general availability, I would
> like to request WSPR-15 be added to the list of modes in WSJT-X. There are
> still a number of experimenters in the Lowfer community that still would
> like to use
On 12/22/2016 9:43 AM, Gordon Higgins wrote:
> hi joe i have used the early version with out any problem if i put in
> 7305 the clock runs fine on msk144 but when i try to use 7405 the clock
> is eratic
... because you did not read the manual at the place I directed you to.
-- Joe,
Josh --
You man need to -clean-first (or remove) your build tree before compiling.
-- Joe, K1JT
On 12/22/2016 4:52 PM, Josh Rovero wrote:
> Seeing the following under FC25 x86_64
>
> wsjtx_src/lib/decoder.f90:124:51:
>
>
Gordon --
On 12/22/2016 9:23 AM, Gordon Higgins G3PXT wrote:
> Hello using wsjt-x v1.7.0r7405
> on jt65 jt9 etc works fine when i sellect msk144 the clock does not
> tick evenly ie goes 48-49-50-55-8-10-14- sec etc ie missing tick any
> help have reloaded program go back to jt 65 clock
Hi all,
See the note below from ZL1LC, who lives in locator RF73.
-- Joe, K1JT
Forwarded Message
Subject: Re: Posting an issue with WSJT-X 1.7
Date: Tue, 28 Mar 2017 08:19:03 +1300
From: Jim Reed <jimree...@gmail.com>
To: Joe Taylor <j...@princeton.edu>
der if there is any GPL v3 violation here.
>
>
>
> On 4/10/2017 5:39 PM, Joe Taylor wrote:
>> On 4/10/2017 5:09 PM, James Shaver (N2ADV) wrote:
>>> Not necessarily WSJT-X related (but maybe?). I just saw a Facebook
>>> post touting "the new JT10 mode" w
Use the right-most slider to adjust the vertical position of the green line.
On 4/2/2017 5:22 AM, Claude Frantz wrote:
> Hi all,
>
> I'm using Rev: 7626 on a Linux system. As you can see on the attachment,
> the green signal line is not matching the window size and I ignore how I
> can change
On 4/2/2017 12:42 PM, Claude Frantz wrote:
> On 04/02/2017 01:38 PM, Joe Taylor wrote:
>
>> Use the right-most slider to adjust the vertical position of the green line.
>
> Thanks Joe ! In contrast to the picture in the user's guide, I have not
> slider in my window here. I
Hi Edson,
PY2SDR wrote:
> I have a few suggestions for polishing the lower part of the UI. I will
> enumerate them so that we can discuss each separately. I can implement
> the ones that Joe and the group give a thumbs up.
Thanks for your thought-provoking email with ideas for the WSJT-X user
Hi Edson,
On 3/3/2017 11:09 AM, Edson W. R. Pereira wrote:
> Hello Joe and Mike,
>
> Since I was the one who implemented the level meter, I have a
> suggestion: Please don't make the level meter change colors depending of
> the dB level. It makes it rather difficult to read for those of us with
On 3/3/2017 10:51 AM, Black Michael wrote:
> OK...I'll do it that way. So the idea is that the colors represent
> peak values then but the meter is noise. That works.
>
> 15dB peak value though is something like 5dB RMS on my system.
> Shouldn't that be a fair bit higher for a warning? Peak
the audio level
is simply not very critical.
-- Joe
On 3/3/2017 12:49 PM, Bill Somerville wrote:
> On 03/03/2017 15:38, Joe Taylor wrote:
>> 2. The slider should not affect the meter reading.
>>
> HI Joe & all,
>
> we have another enhancement possibili
Mike --
The file you posted as "signalmeter2.patch" appears not to be what you
intended. It's a diff (or possibly a fragment of a diff) taken from the
../wsjtx/doc directory ??
-- Joe, K1JT
On 3/4/2017 12:22 PM, Black Michael wrote:
> New signal meter shows 0-90dB -- no + anymore on
Kees --
You will need to be more explicit about your problem.
You can close the waterfall (I suppose you mean the "Wide Graph") simply
by clicking on the "X" at top right. Or you can minimize the window in
the usual way, by clicking the "-" button.
It's not clear, anyway, why you might want
Bill --
Thanks for catching and fixing my broken code with your commit r7971!
-- Joe
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
On 7/31/2017 12:28 AM, Black Michael via wsjt-devel wrote:
Couple of people on the HamApps mailing list mentioned their callsigns
don't workand I confirmed they are correct.
OT17L
VB7150
Why would you be surprised or consider this worthy of comment?
Anyone familiar with WSJT-X should
On 7/31/2017 9:12 AM, Black Michael via wsjt-devel wrote:
I think anytime users have questions about why WSJT-X doesn't do what it
says it's going to do that it's worthy of a comment and potentially a fix.
The whole point is that WSJT-X *does* do what it says it will do.
WSJT-X operates the
Hi Richard,
On 7/30/2017 7:07 AM, Richard Lamont wrote:
Looking at this a little further, in the 15 seconds before, on the same
Rx freq, AD5FW called CQ. So maybe the true message was "AD5FW VE3SMB
FN04" not "G4DYA VE3SMB FN04".
In the compressed 28-bit callsign field, how many bits are the
Hi all,
In preparation for a soon-to-come second candidate release of WSJT-X
Version 1.8, I committed a large number of updates to the WSJT-X User
Guide today.
The new user guide is posted here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.1-devel.html
If you are
Hi Jay,
Thanks for the feedback.
On 8/2/2017 5:01 PM, Jay Hainline KA9CFD wrote:
2 things I noticed about the User Guide.
1. In Section 16.2 Slow Modes, FT8 is listed. Should it be listed in the
Fast modes instead?
The X Fast modes in WSJT-X send their messages repeatedly in a single Tx
elaborate on why you think it does not.
As always, if you think you have uncovered a bug, it's best to provide a
series of steps that will reproduce the bug.
-- 73, Joe, K1JT
On 7/28/2017 1:33 PM, Joe Taylor wrote:
Hi all Beta Testers,
In code revision r7969 the WSJT-X development
Thanks Bob! -- Joe, K1JT
On 7/31/2017 5:53 AM, Bob Thornton via wsjt-devel wrote:
Using 1.7.1-Devel r7970
Help/Keyboard Shortcuts. F4 says "Clear DX Call, DX Grid, TX messages 1-5"
In practice Tx 5 is not being cleared. I suspect there is good reason for that,
if so the help needs update.
To: Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8
The planned protocol change in FT8 is now complete and tested. Effective
at UTC on July 8, 2017, you should stop using FT8 with any WSJT-X
code revision earlier than r7805.
If you
Correct. It's not yet UTC on July 8.
On 7/7/2017 1:27 PM, char...@sucklingfamily.free-online.co.uk wrote:
Hi Joe
I think the code in mainwindow.cpp still has the restriction on mycall, in
two places.
Program does not run unless mycall set to one of the test calls.
Charlie
To:
Hi Erik,
On 7/13/2017 11:19 AM, Erik EI4KF - wrote:
From version 7861, I get 2 stations decoded when that number respond on
the same DF. Presumably this results from the implementation of
Subtraction. Excellent.
When 3 stations answer on the same DF, none are decoded.
With signal
On 7/12/2017 10:07 PM, Gary McDuffie wrote:
On Jul 12, 2017, at 6:09 PM, George J Molnar wrote:
In any mode, select “Menus” OFF (unchecked).
Headers in Band Activity and RX Frequency windows disappear (as expected)
Open Preference pane
Close Preferences with OK
Band
Rick --
Thanks for the User Guide comments! -- Joe, K1JT
On 7/13/2017 9:34 AM, K5GZR - Rick wrote:
Did a quick read of the updated User Guide, and…
Section 1.1.New in Version 1.8: SWL option for third-partty (should be
party)
Section 4.6.Frequencies: Does not describe all of the options
Moreover: you can't Rx and Tx at the same time. If you're working
stations with FT8, often transmitting in two 15 s sequences during a UTC
minute, you can hardly expect to decode signals using one minute
transmissions.
On 7/13/2017 2:09 PM, Bill Somerville wrote:
On 13/07/2017 18:59, Gary
On 7/14/2017 10:04 AM, Raymond Montagne wrote:
To whom it may concern,
The ARRL Letter instructed that suggestions for use of the 3 extra bits
in FT8 be sent to this list. Toward that end, would you please consider
using these bits for providing a CQ DX capability?
Thank you.
Best
The WSJT Development Group is pleased to announce a candidate release of
WSJT-X Version 1.8.0. This is a beta release, already tested in the
field by around 160 alpha-test users. A short list of new features and
capabilities (including the new FT8 and FreqCal modes) can be found in
the
The WSJT Development Group is pleased to announce a candidate release of
WSJT-X Version 1.8.0. This is a beta release, already tested in the
field by around 160 alpha-test users. A short list of new features and
capabilities (including the new FT8 and FreqCal modes) can be found in
the
To: Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8
If you are building WSJT-X for yourself from source code, you may now
upgrade to r7812 and recompile. You will then have access to the latest
version of FT8 plus some new features for setting default
Hi all,
WSJT-X v1.8.0-rc1 includes an optional feature that is a significant
departure from all previous WSJT-related software.
When you call CQ in FT8 mode with both "Auto Seq" and "Call 1st"
checked, the program automatically selects the first decoded response to
your CQ and starts a QSO
Hi all,
For the auto 60Hz shift on answering CQs, I think this is a bad idea.
We have never considered anything like an "auto shift" of Tx frequency.
What we *might* do is provide an easy way to move your Tx frequency up
or down manually in increments of 60 Hz (or perhaps some other
On 7/10/2017 4:06 PM, David Tiller wrote:
Dear dev team,
FYI, this bug still exists in r7844, and happens any time you switch
into MSK144 mode from FT8, JT4, JT9, JT9+JT65, JT65, or QRA64. ISCAT and
WSPR seem ok. It sounds like the 'over' time isn't getting initialized
when entering MSK144
On 7/6/2017 5:23 PM, David Birnbaum wrote:
I know that there are a set of frequencies in the table and most of them
are useful. But local AM radio needs to be set for each station and not
all the time/frequency standard frequencies work for everyone all the time.
db
Delete the ones not
Hi all,
Thanks for all posted comments on WSJT-X r7812. I should have mentioned
that we knew about the "double display in right window" issue. I wasted
an hour or so, Friday afternoon, trying to identify the cause without
success. We'll fix it soon. Better two displays, rather than none!
Mike --
Thanks for submitting the patches! I have installed "menu.patch" and
"qsotime.patch". They appear to be OK, but please double-check to be
sure their functions are what's wanted.
I have left rigctld_setvfo.patch for Bill; I have no easy way to test
its functionality here.
Hi Wolfgang,
On 7/11/2017 12:22 PM, Wolfgang OE1MWW wrote:
If I have "TX even/1st" unchecked and I "Enable TX",
the transmission starts with CQ, disregarding the 15 sec. cycle time.
I checked that again, this can happen twice a minute, depends on the
setting and the activation of "Enable
FT8 (and other modes in WSJT) already support messages of the form
"CQ XX K1ABC FN42", where "XX" is any two letters. They have done so for some
considerable time. Obviously XX can be DX. So I do not understand what you are requesting.
Yes, but the grid square is not embedded in the call
Tnx John!
On 7/10/2017 10:15 AM, John Nelson wrote:
Hi Joe,
r7835 with revised Call 1st is working correctly..
— John G4KLA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites,
Hi all,
I had not intended the "Weak" checkbox to be visible, just yet. Its
function is not yet implemented.
Code revision 7835 is yet another attempt to get the "Call 1st" logic
just right. I think it should now do the following:
1. Decodes containing "MyCall" or falling within 10 Hz of
Mike --
We do NOT need reports about false decodes produced from development
code that is not released -- and use of which has been strongly
discouraged.
Such reports on "DO NOT USE" code only tend to give the mode or the
program a bad name. And they encourage others (who may not know any
Hi Bill,
On 7/18/2017 5:14 PM, Bill Somerville wrote:
I am reviewing handling of auto-sequencing and general responses to
messages by double-clicking them. I have a question about JT65 short
codes as used for EME QSOs.
There doesn't appear to be any automated way of moving from receiving an
Hi all,
From time to time it seems necessary to remind everyone of the two main
purposes of this "wsjt-devel" email reflector:
1. To facilitate communication among those contributing to the
development of WSJT and its sister programs.
2. To provide a forum for dedicated testers to convey
Hi David,
On 7/19/2017 11:42 AM, David Tiller wrote:
Using flatten for me results in a very angry red and yellow mess. I run
my input signal fairly hot, though. Around 60dB or so. It seems that
flatten can't handle high input levels.
Almost always, this behavior indicated that you have not
Hi Neil,
but doesn't that mean you have to redo the logic used by the double
click to change the current function from seeing RR73 as a grid, ...
The change in logic is minimal.
I'm also guessing that you would have to make this band specific so its
not used with MS/EME/etc modes which
On 7/15/2017 5:08 PM, roger stafford wrote:
hi thanks for the new mode I am also seeing the od bad decode
im running r7894 started 2 rev’s ago
cheers vk3fz
Did you read the commit log message for r7887?
The open beta release of WSJT-X is v1.8.0-rc1, r7847.
If you choose to build from code in
software version for each one; it will have been a recent dev
build (I suspect v1.8.0-rc2 r7924), but it's somewhat irrelevant because
this particular problem has been quite persistent through versions.
Regards, Mark
On 24/07/2017 22:27, Joe Taylor wrote:
Hi Mark,
On 7/24/2017 5:12 PM, Mark Turner
Hi Richard,
On 7/25/2017 4:58 PM, Richard Lamont G4DYA wrote:
On 25/07/17 00:17, Joe Taylor wrote:
Ubuntu MATE 16.04 amd64
1.7.1-devel r7939
Auto seq and call 1st enabled
Tried it and it looks as though FT8 now has a two-pass decoder, which is
nice.
Since you're providing feedback
Hi Mark,
On 7/24/2017 5:12 PM, Mark Turner EI3KD via wsjt-devel wrote:
I'm currently trying to capture some examples where the WSJT-X waterfall
appears to become corrupt with multiple images of signals, along with
multiple decodes - I see this fairly frequently when using FT8, and have
also
Hi Richard,
Richard G4DYA wrote:
Ubuntu MATE 16.04 amd64
1.7.1-devel r7939
Auto seq and call 1st enabled
Tried it and it looks as though FT8 now has a two-pass decoder, which is
nice.
Since you're providing feedback on development code, you should not need
to guess or make inferences
On 7/26/2017 12:01 PM, W9MDB Black Michael via wsjt-devel wrote:
What is "AP" decoding?
Decoding a message with aid of "a priori" information gathered
cumulatively during the progress of a QSO. It has been in WSJT-X for
about a year, in mode QRA64. It's now available in FT8.
--
Hi Alex,
We have already done most of what you suggest. Note, however, that
documenting the latest changes and additions in the WSJT-X User Guide is
still to be done.
-- Joe, K1JT
On 7/26/2017 12:54 PM, Alex, VE3NEA wrote:
The JT65 Communications Protocol document
601 - 700 of 1545 matches
Mail list logo