Thanks, Bill! -- Joe
On 6/3/2016 7:43 PM, Bill Somerville wrote:
> On 04/06/2016 00:18, Joe Taylor wrote:
>> I thought I did the right things when adding mode "MSK144" to v1.7. All
>> seems OK, with one exception: when I right-click in the Working
>> Frequencies
Hi George,
On 6/5/2016 11:44 AM, George J Molnar wrote:
> Haven't had much luck with any of the versions including MSK144 on my Mac.
When and if MSK144 becomes a supported mode in WSJT-X, we'll let
everyone know what it is, what it's good for, and how to use it. In the
meantime, it's best to s
Hi Dave,
>I have been using Various WSJT packages for several years.
> WSJT-X V 1.6.1 is terrific but there are a couple additions that could
> make it even better ( in my humble opinion).
Actually we're 'way beyond v1.6.1 now. Version 1.7 has many features
not in v1.6.x. We have yet prepa
Hi Bob,
I'm not aware that anyone else has observed the strange behavior shown
in your screen shots. Certainly I haven't seen it here.
It might be helpful to set about diagnosing your own problem. Your
screen shots suggest that you have an unusually large number of programs
running, and perh
Hi all,
In WSJT-X r6739 if you have Monitor stopped and then switch mode to
JT65, JT9+JT65, or WSPR, Monitor is turned on. Switching to JT4, JT9,
ISCAT, JTMSK, or MSK144 does not turn Monitor on. This seems illogical.
Was there a good reason that I've somehow forgotten?
-- Joe, K1J
Bill --
Thanks... and yes, please look into it!
-- Joe
On 6/8/2016 5:06 PM, Bill Somerville wrote:
> On 08/06/2016 21:43, Joe Taylor wrote:
>> In WSJT-X r6739 if you have Monitor stopped and then switch mode to
>> JT65, JT9+JT65, or WSPR, Monitor is turned on. Switch
Hi all,
On 6/10/2016 10:18 AM, Black Michael wrote:
> I can't think of a reason to not start monitor...but shouldn't it
> be consistent across mode changes then? I would think any change
> from mode-to-mode should behave the same. Maybe Joe has a reason
> to not want to start it since he brought
Hi Bill,
I think I see it the way Mike does: just leave monitor alone, let it
stay the way it was set when doing a band change.
-- Joe
On 6/10/2016 11:01 AM, Bill Somerville wrote:
> On 10/06/2016 15:40, Joe Taylor wrote:
>> I frequently run with Monitor off at startup, most
Hi Bill,
Thanks for making the GPL URL in the "About" window a live link, and
adding the GPL logo.
Here's a related suggestion. Would it be reasonably easy to add our own
WSJT-X logo alongside the GPL logo, say to its left? The juxtaposed
images would help to convey the cooperative, synergis
Dear Colleagues,
FYI, I have copied below a message to be sent to the "wsjtgroup"
reflector. Its intent is to bring users up-to-date on our recent and
planned development work.
-- Joe, K1JT
###
From: Joe Ta
Wolfgang --
Revision 6841 compiles OK with Qt 5.5, but not with Qt 5.2. Perhaps
Bill will modify the new calls to QTimer::singleShot() so as to be
compatible with Qt 5.2; or perhaps we will decide that it's time to
insist on using Qt 5.5...
-- Joe
On 7/1/2016 9:00 AM, Wolfgang wrote:
Hi Mike and all,
On 7/22/2016 5:40 PM, Black Michael wrote:
> I'm curiousWhat's the status and todo list for releasing 1.7?
> de Mike W9MDB
Version 1.7 could have been released many weeks ago if we had stopped
making enhancements and adding features.
As it is, we've made considerable progre
Tnx Mike :-)
On 7/26/2016 1:43 PM, Black Michael wrote:
> MIssed adding a file?
>
> -- Configuring doneCMake Error at CMakeLists.txt:987 (add_library): Cannot
> find source file:
> lib/spec64.f90
> de Mike W9MDB
>
>
>
> -
Hi OM,
On 8/1/2016 9:13 AM, f5...@free.fr wrote:
> Hello all,
> Is there a way to use a special callsign of 7 characters TM11FAJ
> here? Text 1 the message is truncated (no locator) which is not
> very serious against by not sending the rst. example: ZZ0ZZZ
> TM11FAJ only, no RST is sent.
>
> Woul
Hi Pino,
On 8/3/2016 7:58 AM, Pino Zollo wrote:
> Please can you tell the differences in performance in usinh WSJT-X 1.7.0
> on EME versus WSJT 10.0 ?
>
> At present I can only use WSJT-X what do I miss ?
The trend is toward using WSJT-X for all propagation modes, EME
included. Simulation
Dear Colleagues,
With many recent enhancements to the experimental modes QRA64 and MSK144
and some cleanup of certain GUI features, we are almost ready to make an
open Alpha Release of WSJT-X v1.7.
It could be based on code revision r7002 (or perhaps slightly later, if
we find any problems in
Hi Jim,
On 8/4/2016 4:19 PM, Jim Brown wrote:
> Those of us wanting to use your modes for E-skip would really appreciate
> the inclusion of short-cycle versions of the relevant protocols like ISCAT.
Not sure what you might mean.
Short-cycle options for all of the fast modes (JT9E-H "fast", ISCAT
Hi Steve,
Sorry about this oversight. Working too quickly, today...
-- Joe
On 8/4/2016 5:59 PM, Steven Franke wrote:
> Hi George -
> I just made a change to address an issue that I found on OS X. You might try
> it to see if it fixes your problem.
> Steve k9an
>
>> On Aug 4, 2016, at 4
e "-devel" code revisions.
-- Joe, K1JT
On 8/4/2016 5:13 PM, Jim Brown wrote:
> On Thu,8/4/2016 1:50 PM, Joe Taylor wrote:
>> Hi Jim,
>>
>> On 8/4/2016 4:19 PM, Jim Brown wrote:
>>> Those of us wanting to use your modes for E-skip would really appreciate
&g
George --
I can't test in OS X, so in principle your reports could be especially
useful.
You are building the program yourself. For diagnostic purposes you
should build the "Debug" version, not the "Release" version. Can you
start it from a command-prompt window, or run it under gdb? That s
George --
You are building the program yourself, so you need to do some diagnosis
yourself when you find a problem.
Some things that would be installed automatically from the distribution
package may not be in the correct place after your builds.
If I infer correctly what you must be doing, th
Hi John,
On 8/5/2016 7:55 AM, John Nelson wrote:
> Hi Joe,
>
> Clarification point: I am running r7004 on 2m listening to a beacon
> (GB3VHF) 150 miles away on the back of the antenna which is not raised.
> Decoding JT65B -22 to -24db; clear trace on waterfall.
>
> But no decode for QRA64 wi
Hi all,
I have posted a Windows installation package for an Alpha Release of
WSJT-X Version 1.7 r7005 here:
http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.7.0-alpha-1-win32.exe
You can read about new features in v1.7 (relative to v1.6) here:
http://physics.princeton.edu/pulsar/k1jt/v1.7_Feat
Hi Mike and all,
On 8/5/2016 1:15 PM, Black Michael wrote:
> It appears the splash screen is still interfering with JTAlert
> docking and such.Maybe make it a one-time display if it really
> needs to be there?
> 73 Mike W9MDB
As you will have seen, I implemented the change that Wolfgang, OE1MWW,
Wolfgang --
The program's present behavior is exactly what you asked for. Is that
not right?
The splash screen is shown exactly once, on program startup, after the
main window is displayed.
If you are building the program for yourself, of course you may modify
it as you wish. But in that ca
George --
On 8/5/2016 5:31 PM, George J Molnar wrote:
> At the end of a valid decode cycle (where a signal is present)
> QRA64 crashes for
> me. Transmission is fine. If no signal is present, no crash occurs.
For your report to be useful you need to tell us more.
Have you saved a .wav file, as a
Hi Claude,
On 8/6/2016 10:38 AM, Claude Frantz wrote:
> Hi,
>
> Please look at the attached image file (QRA64 mode):
>
> What is the red figure in the spectrum at the bottom ?
As stated in the Release Notes, QRA64 is designed primarily for EME.
EME users of JT65 are familiar with its single-deco
Hi all,
It's OK to play with and test QRA64 at HF, if you wish. Some of our
earliest tests of the mode were done on the 20m and 30m bands.
But Greg is right: the mode is intended for EME, where every dB of
sensitivity matters a lot. We do not recommend any large-scale shift
from JT65 to QRA64
Hi Bill, Rex, and all,
I will not have time to work on this before leaving in two days for the
EME Conference in Venice, but I will just say that there is certainly
nothing inherent in the QRA64 mode that should prevent its use in
Windows XP. I do not think it should take us very long to track
Hi Jay and all,
That certainly looks like a bug -- thanks for catching and reporting it.
It leaves me wondering why I've never seen it here.
I hope you had "Save all" checked during this run, and can retrieve and
send us one of the files that produced truncated output. (If not, could
you pl
it to?
>
> Jay KA9CFD
>
> -Original Message-
> From: Joe Taylor [mailto:j...@princeton.edu]
> Sent: August 16, 2016 12:47
> To: WSJT software development
> Subject: Re: [wsjt-devel] Grid square last digit being cut off in msk144
>
> Hi Jay and all,
>
> Tha
Hi Mike,
Thanks for the bug fix. In the end I changed "40" to "43", to allow for
a max-length message like this:
131415 -4 11.2 1501 & R+00
Using msg0.length() would make it always use length=80, causing a minor
waste of space downstream.
-- Joe, K1JT
On 8/16/2016 3:02 PM, Black M
error
> check before the call to ensure it's NOT longer than 43?
>
> Not that WSJT-X ever changes...:-)
>
> de Mike W9MDB
>
> --------
> *From:* Joe Taylor
> *To:* WSJT software development
> *Sent:*
Hi Mike,
> Does the input gain slider actually affect anything other than the level
> readout? I recall Joe saying that the decoder always uses the raw PCM
> data. Though I don't know fortran very well skimming the symspec routine
> suggests that only the readout is affected.
The gain slider does
Hi Jay,
KA9CFD wrote:
> Using WSJT-X v1.7.0-rc1 r7036 this morning on msk144.
>
> Noticed that the az/el calculator will not work if I enter a DX grid square
> that happens to be in my grid field EN. I am located in EN40. If I try and
> work a station in an EN grid field, the AZ and miles show up
; Jay KA9CFD
>
> -Original Message-
> From: Joe Taylor [mailto:j...@princeton.edu]
> Sent: August 29, 2016 13:50
> To: WSJT software development
> Subject: Re: [wsjt-devel] Azimuth/Elevation calculator in WSJT-X
>
> Hi Jay,
>
> KA9CFD wrote:
>
>> U
Mike --
On 8/29/2016 12:59 PM, Black Michael wrote:
> Actually the calculation for lat/lon was incorrect.
No, there's nothing wrong with grid2deg.f90.
Your patch would be approximately OK, except that its longitudes have
the opposite sign convention to that used elsewhere in the program.
Hi Bill,
On 9/2/2016 7:44 PM, Bill Somerville wrote:
> On 03/09/2016 00:29, Steven Franke wrote:
>> With the recent wspr changes (probably as of r7042) I find that I am now
>> transmitting the hash/6-digit locator messages. I’ve searched the
>> preferences tabs and I don’t find any option to t
Hi Jay,
KA9CFD wrote:
> Using WSJT-X 1.7.0-rc1 r7054 today. I have been watching 20 meters in
> JT9+JT65 modes using 4 khz bandwidth from my Flex 6500. I counted at one
> sequence, 22 stations decoded in my passband. That is a heck of an
> achievement and I just wanted to congratulate the developm
Hi all,
I'm happy to report that the two annoying and hard-to-diagnose bugs in
WSJT-X v1.7 have been fixed. One caused unpredictable frequency jumps
in MSK144 mode; the other caused crashes when decoding was attempted in
QRA64 mode. Both affected only some users.
Meanwhile, Steve has made se
Yes
On 9/8/2016 10:04 AM, IK1WVQ Mauro wrote:
> Hi Joe,
>
> have you plans for porting the QRA mode into the MAP65 SW ???
>
> best regards .
>
> 73 de Mauro IK1WVQ
>
>
>
> At 15:19 08/09/2016, Joe Taylor wrote:
>> Hi all,
>>
>> I'm happy t
Another thought concerning a pending -rc2 release.
I suspect it is time to permanently retire the JTMSK mode and remove it
from WSJT-X. It has been superseded by MSK144, which I consider
superior in every meaningful way.
Do I hear any disagreement ?
-- Joe, K1JT
-
Hi all,
I've made some progress on updating the WSJT-X User Guide for Version
1.7. Intermediate results have been committed to SourceForge, and the
updated guide (as it now stands) is posted here for user access:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.0-rc1.html
Hi all,
I've made some progress on updating the WSJT-X User Guide for Version
1.7. Intermediate results have been committed to SourceForge, and the
updated guide (as it now stands) is posted here for user access:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.0-rc1.html
C
to me is the outdated pictures of the settings
> tabs. The advanced tab is missing and no mention of it. Maybe that's
> intentional. :-)
>
> 73 Jay KA9CFD
>
> -----Original Message-
> From: Joe Taylor [mailto:j...@princeton.edu]
> Sent: September 8, 2016 17:11
> T
Tnx Sandro -- will do.
-- Joe, K1JT
On 9/8/2016 3:26 PM, Alessandro Gorobey wrote:
> Hi Joe,
>
> File --> Measure Reference Spectrum
> is not so obvious
>
> Also "wide graph" current, cumulative, linear avg, but "reference" ?
>
> Exceptional work
>
-
Hi Rex,
Thanks for your suggestions.
VK7MO wrote:
> Prior to the next candidate release I think it would be worth considering:
>
> a. The introduction of filtering to improve QRA with spreading
>
> b. Some work to see if you can resolve the reasons for ftol not working
> properly and whether if y
Hi Claude,
On 9/9/2016 10:05 AM, Claude Frantz wrote:
> On 09/08/2016 07:10 PM, Joe Taylor wrote:
>
>> Please let me know of things you think need to be added, deleted,
>> improved, or ???
>
> Hi Joe,
>
> I would be grateful to see the ability to generate the documen
I don't consider the splash screen as a permanent feature of WSJT-X. In
fact, I find it rather annoying. It was added to an alpha release to
point users, gently but firmly, toward the "Release Notes". These were
needed in order to document (even though very briefly) a number of
features not
Hi David,
> I noticed the following on r7072 (Running under OSX 10.9.5):
>
> 1) Given a constant audio level input with the JT65 level adjusted
> to 30 dB, I see the correct 30dB audio reading using JT9, JT65,
> JT9+JT65, JT4, QRA64, and WSPR2. Switching to ISCAT, JTMSK or
> MSK144 results in a 5d
Hi Gary,
Because this reponse to your email may be useful to others, I am copying
it to the wsjt-devel ("WSJT Developers") email list.
AG0N wrote:
> If I am interpreting what I've done in testing correctly, the MSK144 tones
> center around 1500. Again, from what I've seen, if you double click a
Hi Gary and all,
My earlier message was wrong about one thing:
> At present, any decode in MSK144 mode (whether or not you double-click
> on the decode) will set the "Rx Freq" spinner control to the frequency
> of the received signal. Tx Freq always stays fixed at 1500 Hz. In code
> revision 7076
Hi Dan,
> I have also added QRA to the psk reporter.
>
> How should I share the code patches?
Has this item fallen through the cracks? If so, send me the patch and
I'll commit it.
-- Joe, K1JT
--
_
Hi Jay,
I don't understand your comment. It seems to me that in MSK144 mode, as
in all others, double-clicking on a line of decoded text does set the
proper Tx sequence for calling that station.
I do not understand why this might not be working for you. Please
elaborate.
-- Joe, K1J
Hi Victor,
On 9/19/2016 5:37 PM, Victor Batchelor wrote:
> Hi Joe and all developers.
> Are there plans to release the FMT group of programs in 1.7.0?
> An updated version with the option to update the frequency
> settings would in my opinion be very useful.
Yes, an adaptation of the FMT ("fmtest
Hi Pino,
On 10/3/2016 11:07 AM, Pino Zollo ZP4KFX wrote:
>
> Developers might be interested in this sequence of JT65 signal received
> in GG14hq trough Trans Equatorial Propagation on 6m band using a 10 el
> antenna 16m o.g.
>
> http://cloud5.tcpsas.com/index.php/s/nImEyGUQD2B5zmy
>
> Signals are
Wed, 5 Oct 2016 09:57:29 -0400
From: Joe Taylor j...@princeton.edu [wsjtgroup]
Reply-To: Joe Taylor
To: n...@mtcmobile.com.na, WSJT Group
Dear Pieter V51PJ,
I do not in any way wish to throw cold water on your attempts at
trans-Atlantic communication on 2 meters, but I would like
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 Submod
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
furthe
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 'Enable
Hi all,
1. Is there any objection to my removing the checkbox labeled
"dB reports to comments" from the Settings -> Reporting tab?
I introduced this way back when I was using a logging program that would
accept only RST ("599")-style reports. My guess is that nobody uses it.
2. A brief reminder
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
other
hairman Adviser
>
> Email - K8VFV at ARRL dot NET
> Web Site - http://www.k8vfv.com
> Outgoing email checked by MSE
> In GOD we trust
>
> On 17 Oct 16 10:54 AM, Joe Taylor wrote:
>> Bob --
>>
>> K8VFV wrote:
>>> I welcome back the CW IDer. THANKS! But, it
Hi Sandro,
Thanks for finding and reporting those typos!
-- Joe, K1JT
On 10/23/2016 1:27 PM, Alessandro Gorobey wrote:
> Hi All,
>
> reading the new manual I found some typos.
> I also noticed that some of the JT9 (B,C,D) modes disappear from the
> tables.
>
> Compliments for the big wor
Hi all,
Slowly but surely, a respectable User Guide for WSJT-X v1.7 has been
taking shape. Much material has been added over the past week or so --
and quite a bit more, even today.
If you have not referred to the User Guide recently, please give it a
careful look. A fresh copy is available
Mike --
Could you explain the rationale behind this suggested feature?
Why might I want WSJT-X to remember particular power output settings on
a band-by-band basis?
Why would I (in general) want to adjust my power output by using the
slider on the WSJT-X screen, rather than by making an adjust
OK Mike -- Revision 7230 now includes your patch implementing
save/restore of Pwr settings. Thanks!
-- Joe, K1JT
--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you
Hi Mike and all,
W9MDB wrote:
> #2 To prevent what happened to me...where I blew out the finals on my
> rig when I was operating remotely on 15M because the SWR was too high
> and so was the power level from WSJT-X. Unfortunately rig wasn't smart
> enough to curb power (it's in the shop now). I ha
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: Reinvent
Hi Charlie,
Thanks for catching this.
> Mystery solved re non decode of JT4 examples.
>
> They decode fine if decode at 52s is *not* checked.
>
> Given JT4 is intended for EME, it may be better to choose files that work
> with decode at 52s checked.
Better still, find out why the files don't wor
Hi Charlie,
> Mystery solved re non decode of JT4 examples.
>
> They decode fine if decode at 52s is *not* checked.
>
> Given JT4 is intended for EME, it may be better to choose files that work
> with decode at 52s checked.
This anomaly is fixed in revision 7236.
-- Joe
Hi Charlie,
> The two JT4 files are reported by Windows as 52s in length, compared to
> others that are 59s. Also at a lower bitrate (maybe WSJT10 recordings?).
Correct. This has now been taken care of.
> Are you updating online user guide as you go (at the URL you gave out), or
> are the edits
Many thanks to all those providing suggestions for improvements to the
WSJT-X User Guide. Your comments are greatly appreciated!
-- Joe, K1JT
--
The Command Line: Reinvented for Modern Developers
Did the resurge
Mike --
On 10/26/2016 5:27 PM, Black Michael wrote:
> In reference to the RRR patch that was previously disapprovedwhat
> about making this an option with "Prompt me to log QSO" as a tristate
> checkbox?
>
> If I make such a patch would it be considered for inclusion? Otherwise
> I won't wast
Patrick F1EBK wrote:
> Does the WSJT-X outputs an AZEL.DAT file to control both, the antenna
> control and the compensation of the doppler shift ?
>
> If the answer is yes, in which directory could it be found ?
Why not consult the WSJT-X User Guide?
You'll find the answer here:
http://www.physi
Hi Bill,
On 10/28/2016 11:08 AM, Bill Somerville wrote:
> The layout was still broken. It is a bit complicated getting a handle on
> how to build a UI using layout managers and widgets.
Thanks for cleaning up the Audio tab layout, once again. Those
shortcomings were mine, at least as much as M
Deal Colleagues,
Thanks to all coders, bug reporters, and testers for helping us to get
WSJT-X v1.7 into good shape! The program still has a few known
shortcomings, but they are relatively minor. The time seems right for a
second candidate release.
The following notice will be sent soon to t
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 bug
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 WSJT
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 i
if I was only interested 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 mailto:j...@princeton.edu>>
> Subject: Re: [wsjt-devel] call3.txt
>
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
> ca
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 k
Hi all,
With code revision 7289 I have implemented support for messages of the
form "CQ AA" through "CQ ZZ". They are encoded by sending "E9AA"
through "E9ZZ" for the first callsign. Upon reception these calls are
converted back to the form "CQ AA" through "CQ ZZ".
For consistency, "CQ DX" i
Hi Sandro,
Thanks for the suggestion about using the ISO 8601 format for Date/Time
labels in ALL.TXT. I have made this change in code revision 7312.
-- Joe, K1JT
On 11/8/2016 4:12 PM, Alessandro Gorobey wrote:
> Hi Claude and All,
>
> ALL.TXT is borne to dump all the lines in receive w
Hi all,
Regular readers of this list will know there has been much recent
development work on the experimental mode QRA64.
In the current code revision, r7322, QRA64 uses a wider spacing between
tones in its thrice-replicated Costas 7x7 sync pattern. Sync tones are
now transmitted at tone num
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 f
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
>
> Interesting
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.
>
JTAlert and 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
> *To:* WSJT software devel
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 le
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 10:5
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 any
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 extensive
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
###
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 bu
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 mi
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
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 sav
1301 - 1400 of 1593 matches
Mail list logo
