I duplicated your problem.It's the -f at fault.
First off, it's an offset, not a raw frequency. But it still errors even with
a correct offset.
So this worksC:\Users\mike\Downloads>\wsjt\wsjtxrc7\bin\jt9 -5
190604_100622.wav EOF on input file 190604_100622.wav
on rc7 trying to use jt9.exe to decode a wav works on the 32bit version but
fails on the 64bit version. It throws
At line 58 of file C:\Users\bill\src\k1jt\wsjtx\lib\readwav.f90
Fortran runtime error: Inquire statement identifies an internal file
73 Alan M0NNB
MacOS 10.13. WSJT-X 2.1.0-rc7 working well on FT4. No problems
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Mike,
it looks like it is a problem with any of the arguments that take a
parameter.
73 Alan M0NNB
On Tue, Jun 4, 2019 at 12:46 PM Black Michael wrote:
> I duplicated your problem.
> It's the -f at fault.
>
> First off, it's an offset, not a raw frequency. But it still errors even
> with a
On 04/06/2019 09:33, Richard Lamont wrote:
Hi all,
I see that whereas rc5 logged an FT4 QSO as "FT4", rc7 is
logging it as "MFSK FT4".
I assume this is intentional and ADIFically correct, but it has confused
CQRlog 2.3.0 which is logging the QSO as MFSK. (Yes, I have added FT4 in
CQRlog
FYI...64-bit version behaves OK on Linux with the arguments
jt9 -5 -f 1000 190604_100622.wav which jt9 EOF on input file 190604_100622.wav
Yes, I did that - after I saw the doubles. Hopefully, I will catch it again.
73 de W8NET Miles / “Gene”
Secretary, Portage County Amateur Radio Service (PCARS)
3905 Century Club - Master #47
DV2/W8NET in the Philippines
Licensed since 1974
> On Jun 4, 2019, at 12:43 PM, Joe Taylor wrote:
>
>
Hi Gene,
I have seen nothing like the duplicate decodes you report. Please send
us the .wav file for one or two of your examples, and tell us something
about your computer setup.
-- 73, Joe, K1JT
On 6/4/2019 11:39, Gene Marsh via wsjt-devel wrote:
FT4: I have seen 7-8 times, double
Mike,
My ALC is ~25% @80W. But, I have no issues with transmit. Only observing the
double decode. Everything else is good.
73 de W8NET Miles / “Gene”
Secretary, Portage County Amateur Radio Service (PCARS)
3905 Century Club - Master #47
DV2/W8NET in the Philippines
Licensed since 1974
> On
Gene --
Remember that release candidates are intended for test purposes. When
running any -rc# version, you should always run with "Save All"
selected. It's easy enough to delete all those unwanted files, later.
-- Joe, K1JT
On 6/4/2019 12:39, Gene Marsh via wsjt-devel wrote:
Hi Al,
Please verify that you were running the latest rc7 release?
Assuming that you are running rc7, it would be helpful if you could send a
saved wav file that reproduces this error.
Thanks!
Steve k9an
> On Jun 4, 2019, at 11:03 AM, Al wrote:
>
> I left while monitoring FT4 on 20m, When
Hi Alan,
On 6/4/2019 6:44 AM, Alan Hopper wrote:
on rc7 trying to use jt9.exe to decode a wav works on the 32bit version
but fails on the 64bit version. It throws
At line 58 of file C:\Users\bill\src\k1jt\wsjtx\lib\readwav.f90
Fortran runtime error: Inquire statement identifies an internal
If you reduce power from WSJT-X (not from the rig) does your ALC drop? If
so...that's too much audio.
Mike
On Tuesday, June 4, 2019, 11:57:44 AM CDT, Gene Marsh wrote:
Mike,
My ALC is ~25% @80W. But, I have no issues with transmit. Only observing the
double decode. Everything
Ok
I called IZ0CUV
He responded with -13
I didn’t decode his report
He didn’t hear his response
His next transmission I heard was his CQ - and was GREEN.
No 73 or RR73. No log entry.
???
73 de W8NET Miles / “Gene”
Secretary, Portage County Amateur Radio Service (PCARS)
3905 Century
On 6/4/2019 15:59, Adriaan Koopman wrote:
Dear OM,
Audio goes by 64bits *Candidate Release/WSJT-X 2.1.0-rc7 /*/still to
100%./*/
/*
*/73, Adriaan PE2K/*
Read before download: Known Issues:
https://physics.princeton.edu/pulsar/k1jt/Known_issues.txt
Essentially if everyone sets up some time sync process to a time standard then
the issues will be minimized.
Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca
> On Jun 4, 2019, at 15:14, Bill Frantz wrote:
>
>> On 6/3/19 at 4:56 AM, slotter+w3...@gmail.com (Dave Slotter)
On 04/06/2019 18:50, Al wrote:
Steve,
Yes it was rc7 on Win10 1809.. I don't know exactly when the error
occurred. Sometime between last contact at 1357z and when I posted the
message at 1603z. There are tons of wav files during that time period
the first of which is 1450:30z. Assuming
On 6/3/19 at 4:56 AM, slotter+w3...@gmail.com (Dave Slotter) wrote:
It doesn't do much good to be "in-your-face" about clock synchronization
issues to the receivers of signals which are off by too high a delta,
because it's the sender that needs their clock adjusted, not the receiver.
However,
Known bug...32-bit version does not have the problem. Will be fixed in the
final release of 2.1.0 with a new version of Qt that should be out shortly.
https://physics.princeton.edu/pulsar/k1jt/Known_issues.txt
de Mike W9MDB
On Tuesday, June 4, 2019, 3:04:54 PM CDT, Adriaan Koopman
Hello Richard.
Also using CQRLOG this way, v. 2.3.0 (216), and at my side logging of
FT4 is working fine. Gets logged in CQRLOG as FT4, and in the
wsjtx_log.adi as MFSK FT4.
I have also added FT4 to the "user defined digital mode" setting on the
Modes tab under Preferences.
I'm using the
Dear OM,
Audio goes by 64bits *Candidate Release/WSJT-X 2.1.0-rc7 /*/still to
100%./*/
/*
*/73, Adriaan PE2K/*
*/
/*
*///
/*
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Well, the FT4 mode in WSJT-X 2.1.0-rc7 worked great at the K1HTV QTH in
the mock RU test. There were plenty of participants. Here are the totals:
189 QSOs (156 on 20M, 33 on 40M)
26 countries
29 States
4 VE provinces
TX: K3 (70W)
Antennas: A3S at 70ft and ZS6BKW antenna for 40M.
I just had an instance of the 'invalid QSO data' popup, but mine was caused by
the "Best S+P" mode pouncing on a non-RTTY Roundup CQ caller.
Would it be possible to limit the S+P mode to only those in the contest when a
particular contest is selected? That is, when I'm in RTTY RU mode, only
Joe,
Ramblings from Kent, Ohio:
- as this was a “mock contest”, I think was a: 1) good indication of
functionality, and 2) not a good indicator of contest conditions. Because we
had a small sample of stations for “congestion” in a contest, we need more real
life contest conditions.
I had the same issue once - invalid QSO date. Filled in the one missing data
box - left side - and logged ok.
Quit and restarted app with no further issues.
Logged over 40 QSOs when I was on and off the rig.
Kudos development team .
Frank
Regards and 73s
VE3FBZ
London Amateur Radio Club
Same problem here, after the first 2-3 QSO's were logged the small error
logging window from WSJT-X popped up with an error about invalid QSO data
as my send rpt+exchange did not appear in the QSO data to be saved. Almost
every QSO thereafter I had to enter my send report and state/serial nr to
(I re-posted this from the correct email address.)
I participated in the FT4 mock contest a bit today and made 68 contacts.
Most QSOs went quickly and smoothly. I have some feedback and questions.
Sometimes when I was between QSOs I enabled "Best S+P". This is a handy
feature.
[1]
On 04/06/2019 07:15, Christoph Berg wrote:
Re: Bill Somerville
2019-06-03
It's segfaulting for me (amd64 Debian buster, Debian packaging):
can you try the attached patch please?
The patch fixes the problem, thanks!
Christoph
Hi Christoph,
thanks for the update. Note that we have released
RC7
Is RC7 still a beta development!!
Ken.. G0ORH - FT4 rc5
Sent from my iPad
> On 3 Jun 2019, at 23:50, VE3FBZ wrote:
>
> Downloaded RC7 Win 10 64 bit version
> Works great.
> QSOs On 14.080
> Working with JTALERT 12.13.7 ok.
> Logging ok.
> Response great.
> Thanks a million
On 04/06/2019 06:45, Tom Ramberg via wsjt-devel wrote:
I’ve installed the WIN64OpenSSL_Light-1_0_2s, but the the lotw user activity
file won’t load. Se error message
Hi Tom,
please read he instructions for the 32-bit OpenSSL installation in the
WSJT-X v2.0.1 User Guide, there are follow up
Re: Bill Somerville 2019-06-03
> > It's segfaulting for me (amd64 Debian buster, Debian packaging):
>
> can you try the attached patch please?
The patch fixes the problem, thanks!
Christoph
___
wsjt-devel mailing list
Hi Tom,
I had the same issue here with my 64-bit version of WSJT-X. Just installed the
following 64-bit version of OpenSSL, and "Fetch now" now works fine:
https://slproweb.com/download/Win64OpenSSL_Light-1_0_2s.exe
Restart WSJT-X after installation.
73 de Uwe, DG2YCB
-Ursprüngliche
Re: Bill Somerville 2019-06-04
<1accb949-2c9d-cecb-faa5-1cda815bd...@classdesign.com>
> thanks for the update. Note that we have released WSJT-X v2.1.0 RC7 which
> includes that patch so it is now obsolete.
Yeah, I noticed just after applying the patch, but figured reporting
back success would
Hi all,
I see that whereas rc5 logged an FT4 QSO as "FT4", rc7 is
logging it as "MFSK FT4".
I assume this is intentional and ADIFically correct, but it has confused
CQRlog 2.3.0 which is logging the QSO as MFSK. (Yes, I have added FT4 in
CQRlog preferences.)
I have reported this to the CQRlog
That did the trick. Thanks!
Made 20 qsos this morning mostly on 20. No problems encountered so far. Kudos
to the developers!
73 de Tom OH6VDA @ OH2K club station
Sendt fra min iPhone
> 4. jun. 2019 kl. 11:31 skrev DG2YCB, Uwe :
>
> Hi Tom,
>
> I had the same issue here with my 64-bit
35 matches
Mail list logo
