On 31/05/2018 21:43, Richard Shaw wrote:
While trying to build wsjtx 1.9.1 I got a build error. It looks like
the long depreciated qt5_use_modules macro has been removed from the
release of qt5 in Fedora Rawhide.
I made some simple changes as recommended[1], here's an example snippet:
@@ -134
It's a typowsjtx_status.txt
%TEMP%\WSJT-X\wsjtx_status.txt
de Mike W9MDB
On Thursday, May 31, 2018, 4:12:59 PM CDT, Pino Zollo
wrote:
I am running th 1.9.1 since a couple of days, but I can not locate the file
wsjt_status.txt
as stated in http://physics.princeton.edu/pulsar/k1j
I am running th 1.9.1 since a couple of days, but I can not locate the file
wsjt_status.txt
as stated in http://physics.princeton.edu/pulsar/k1jt/New_Features_1.9.1.txt
- DX grid locator sent to wsjt_status.txt, for use by applications
like PstRotatorAZ
73 Pino ZP4KFX
--
On 5/31/2018 9:43 AM, Joe Taylor wrote:
Of course this could be done in FT8. But as I emphasized in a previous
email, we did not want to use a different solution for FT8 and MSK144.
As currently implemented, MSK144 has no spare bits.
Two thoughts. First, aren't FT8 and MSK144 designed for ver
While trying to build wsjtx 1.9.1 I got a build error. It looks like the
long depreciated qt5_use_modules macro has been removed from the release of
qt5 in Fedora Rawhide.
I made some simple changes as recommended[1], here's an example snippet:
@@ -1343,7 +1343,8 @@ else ()
)
endif ()
According to my LOTW account it's the start time being recorded in the
QSO...not the end time.
On Thursday, May 31, 2018, 12:17:40 PM CDT, Tom Melvin
wrote:
Hi
I much prefer the start time - if it takes me 30 mins to work a station I am
‘on the air’ for 30 mins - a) I need to log
LoTW allows a mismatch of up to 30 minutes.
This issue bit me yesterday during the 6 meter JA opening:
- Called a station, no response.
- Took a 30 minute break, without working another station.
- Called the same station, worked him.
Was very surprised to see the QSO time reported to N1MM+ as t
On 31/05/2018 19:13, Ted Gisske wrote:
In the midst of all of the pondering about what to do with the >1mi QSO's (nb. I made one to JA
last night. Quite a thrill!) is it possible to make the contents of the "Hold TX Frequency"
checkbox sticky when changing from FT8 DXpedition mode or from M
In the midst of all of the pondering about what to do with the >1mi QSO's
(nb. I made one to JA last night. Quite a thrill!) is it possible to make the
contents of the "Hold TX Frequency" checkbox sticky when changing from FT8
DXpedition mode or from MSK144 back to "normal" FT8?
I find mys
On 5/31/2018 1:16 PM, George Molnar wrote:
Would a unique CQ message for contest mode work, or is that asking for
confusion?
Normal mode: CQ KF2T FM18
Contest mode: CX KF2T FM18
The contest community is smaller than the general population, so it
might be an easier “sell."
*George J Molnar*
On 31/05/2018 16:36, Steve London wrote:
Version 1.9.0
When making a difficult QSO, many minutes can pass between the time
the QSO was initiated and the QSO was completed. These are identified
in the log screen as "Start Time" and "End Time". Currently, when a
QSO is logged, the Start Time is
I think that might be a good solution Bill as NA contest mode is pretty much a
"VHF/UHF/Microwave feature".
73 Jay. KA9CFD
Sent from my U.S.Cellular© Smartphone
Original message From: Bill Somerville
Date: 5/31/18 12:08 (GMT-06:00) To: wsjt-devel@lists.sourceforge.net Subje
Would a unique CQ message for contest mode work, or is that asking for
confusion?
Normal mode: CQ KF2T FM18
Contest mode: CX KF2T FM18
The contest community is smaller than the general population, so it might be an
easier “sell."
George J Molnar
Arlington, Virginia, USA
KF2T - FM18lv
Hi
I much prefer the start time - if it takes me 30 mins to work a station I am
‘on the air’ for 30 mins - a) I need to log this to stay legal and b) it allows
me to see historically how long QSO;s take.
73’s
Tom
GM8MJV
On 31 May 2018, at 16:36, Steve London wrote:
> Version 1.9.0
>
> Whe
On 05/31/2018 05:36 PM, Steve London wrote:
Hi Steve & All,
> When making a difficult QSO, many minutes can pass between the time the
> QSO was initiated and the QSO was completed. These are identified in the
> log screen as "Start Time" and "End Time". Currently, when a QSO is
> logged, the Star
On 31/05/2018 17:43, Joe Taylor wrote:
On 5/31/2018 12:22 PM, Jay Hainline wrote:
Joe, is it possible to use one of the extra FT8 bits as a flag that
you are transmitting in contest mode or not? Would that be useful to
keep the program on the receiving end from being confused?
73 Jay KA9CFD
On 5/31/2018 12:22 PM, Jay Hainline wrote:
Joe, is it possible to use one of the extra FT8 bits as a flag that you
are transmitting in contest mode or not? Would that be useful to keep
the program on the receiving end from being confused?
73 Jay KA9CFD
Of course this could be done in FT8. B
Joe, is it possible to use one of the extra FT8 bits as a flag that you are
transmitting in contest mode or not? Would that be useful to keep the program
on the receiving end from being confused?
73 Jay KA9CFD
Sent from my U.S.Cellular© Smartphone
Original message From: Joe Ta
Joe
On 5/31/2018 3:34 PM, Joe Taylor wrote:
When you're lucky enough to be working East Asia on 6m, using WSJT-X
v1.9, just hit "No" when asked if you should be in contest mode.
Just so you know, my screen was littered with windows for all sorts of
prop monitoring tools during the event. I n
Version 1.9.0
When making a difficult QSO, many minutes can pass between the time the QSO was
initiated and the QSO was completed. These are identified in the log screen as
"Start Time" and "End Time". Currently, when a QSO is logged, the Start Time is
placed in the ADIF file, and sent to clie
Ned & Jim,
Using WSJT-X V 1.9.1 v8747, to activate the "NA VHF Contest" check box hit F2
(File/Settings) and
click the 'General' tab. check the "Enable VHF/UHF/Microwave" features" box.
After you click 'OK',
the "NA VHF Contest" box will appear on the main WSJT-X screen under the 'Hold
Tx Freq'
Hi Jay, Ned, and all,
On 5/30/2018 8:57 PM, Jay Hainline KA9CFD wrote:
We had a big opening to JA today on 6m. Some of the contacts were over
10,000 km and I have heard some ops report their WSJT-X software would hang
up asking if they want to switch to contest mode. Apparently the program
sees
Great work Joe and team. I found one minor bug when upgrading to 1.9.1
from 1.8 on Windows 10. When I first opened WSJT-X after installing 1.9.1
it defaulted to DXpedition mode Hound in FT8. I was not using DXpedition
mode in the previous version so it was not carried over from there.
On Thu, M
On 31/05/2018 15:15, Black Michael via wsjt-devel wrote:
Is this the current development branch? It's build 1.9.1 as of
now...it was building 1.10.0 on 5/28
http://svn.code.sf.net/p/wsjt/wsjt/wsjtx/trunk/
Also interesting it says rev 8745 on "svn info" and "svn log" but the
"svn update" and t
Using WSJT-X v1.9.1 r8747
Windows 10
I was in a qso on 17m with JA1NCZ. All was going as expected until he gave up
and gave a report to RU3DK. My MM5AGM JA1NCZ R+02 then changed to me calling
him - JA1NCZ MM5AGM IO85.
142245 Tx 1934 ~ CQ MM5AGM IO85
142300 7 0.1 1934 ~ MM5AGM JA1NCZ -22
142
Is this the current development branch? It's build 1.9.1 as of now...it was
building 1.10.0 on 5/28http://svn.code.sf.net/p/wsjt/wsjt/wsjtx/trunk/
Also interesting it says rev 8745 on "svn info" and "svn log" but the "svn
update" and the website says 8747.
Working Copy Root Path: C:\JTSDK\src\w
WSJT-X Version 1.9.1 is now available for download. This version
corrects a flaw in Version 1.9.0 that unintentionally restricted the
full use of FT8 DXpedition Mode by "Fox" stations.
New features and enhancements to WSJT-X since Version 1.8.0 are
summarized here:
http://physics.princeton.e
27 matches
Mail list logo
