Hi Steve and Bill:
FYI, I get a similar error when changing to MSK144 mode. My terminal listing:
iMac:MacOS mcquiggi$ ./wsjtx
At line 2 of file /Users/bill/wsjtx-prefix/src/lib/hspec.f90
Fortran runtime error: Actual string length is shorter than the declared one
for dummy argument 'mycall' (-
Great tip, Laurie.
This is a good technique if one can reasonably assume that the majority of
QSO partners sending a signal report will not complete the QSO, or log it,
if the contester only sends a Grid Square.
IOW, if a contester set to NA VHF Contest mode connects up with a
"non-contester" set
On 22/07/2019 7:16 am, Jim Brown wrote:
so I quickly switched out of contest mode to work him. :)
What I WOULD like is to able to do this without going to Settings
Advanced. All those clicks loses a TX cycle.
73, Jim K9YC
Simple and only requires a single mouse click. Setup two configurati
Hi Andy.
What if you did receive a signal report from a station participating in the
contest? Would you then be ambivalent to whether your QSO partner was "in
the contest" or not?
For example, if your QSO partner is in contest mode but also had the ability
to manually initiate a SNR messag
On 21/07/2019 19:44, Steven Franke via wsjt-devel wrote:
On Jul 21, 2019, at 12:58 PM, John Nelson via
wsjt-devel wrote:
Hi Bill,
I managed to get someone to run the code from a Terminal window. It exits with:
“At line 1 of file /Users/bill/wsjtx-prefix/src/lib/gen65.f90
Fortran runtime err
On 7/21/2019 10:17 AM, Andy Durbin wrote:
I chose not to participate in the RTTY contest but still wished to make
FT8 QSO on 6 meters. I called CQ K3WYC DM33 thus indicating I was not
in the contest. Multiple stations answered me and replied to my report
with "R grid". Since these stations p
Relating to Kevin VE7DS's issue with MSK144 selection on OS X (my machine
is running Mojave 10.14.4)
iMac:~ adamb$ /Applications/wsjtx.app/Contents/MacOS/wsjtx
At line 2 of file /Users/bill/wsjtx-prefix/src/lib/hspec.f90
Fortran runtime error: Actual string length is shorter than the declared
one
> On Jul 21, 2019, at 12:58 PM, John Nelson via wsjt-devel
> wrote:
>
> Hi Bill,
>
> I managed to get someone to run the code from a Terminal window. It exits
> with:
>
> “At line 1 of file /Users/bill/wsjtx-prefix/src/lib/gen65.f90
> Fortran runtime error: Actual string length is shorter th
What are you using for CAT control? The Signalink only handles audio and PTT.
George J Molnar
Arlington, Virginia USA
Office: (202) 618-1077
Mobile: (702) 767-5420
> On Jul 21, 2019, at 1:34 PM, Robert Anthony
> wrote:
>
>
> Anyone using the above and getting it to work? I can't get them
I have a ft2000 and it works also, but the 857D is or has been a problem.TNX
for your reply maybe someone will have a answer for me W8om Bob Sent from my
Galaxy Tab® A
Original message From: Tom Ramberg via wsjt-devel
Date: 7/21/19 1:44 PM (GMT-05:00) To: WSJT
software devel
Hi Bill,
I managed to get someone to run the code from a Terminal window. It exits with:
“At line 1 of file /Users/bill/wsjtx-prefix/src/lib/gen65.f90
Fortran runtime error: Actual string length is shorter than the declared on for
dummy argument ‘msgsent’ (-216172782113783786/22)”
— John G4KLA
I chose not to participate in the RTTY contest but still wished to make FT8 QSO
on 6 meters. I called CQ K3WYC DM33 thus indicating I was not in the contest.
Multiple stations answered me and replied to my report with "R grid". Since
these stations provided no report they were not logged.
T
For what it's worth, at OH2K club station we use Signalink, FT1000MP (I realise
it's a different rig) and Windows 7 64 bit, and have had no problem with F/H.
This isn't very helpful, I suppose.
OH6VDA Tom
> 21. jul. 2019 kl. 20:32 skrev Robert Anthony :
>
> Anyone using the above and getting it
Anyone using ft857d, signalink, and Windows 7 and getting them to work? I can't
use f/h mode get a error message. W8om Bob Anthony Sent from my Galaxy Tab® A
Original message From: George Molnar Date:
7/21/19 7:33 AM (GMT-05:00) To: WSJT software development
Subject: Re: [ws
Anyone using the above and getting it to work? I can't get them to work in the
f/h mode. Get a error message. W8om Bob Anthony Sent from my Galaxy Tab® A___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/list
Hi Kevin,
I did see your report of this issue, I have yet to reproduce it. Several
macOS WSJT-X v2.1.0 users have reported crashes that do not generate a
crash report and only leave a trace in the console log of launchd with
exit code 2. Exit code 2 is normally a file not found error but I don
wsjt-x-aa5au01.jpg
The entry in wsjtx_log.adi seems correct.
KK6NTL DM95 FT8 -07
20190721 160830 20190721
160930 6m 50.315022 AA5AU
EL49XU
Don AA5AU
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.source
Bill, thanks for this info!
The crashes I have seen are related to selection of MSK144 mode. This
invariably causes the app to crash. Sometimes MSK144 mode will “come up” in
the UI, but in that case any interaction with the UI elements will cause the
app to crash. I submitted a report about
ct.
KK6NTL DM95 FT8
-07 20190721 160830
20190721 160930 6m
50.315022 AA5AU EL49XU
Don AA5AU
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
ontest log and
it won't allow me to edit it to the correct time and date. It will allow me
to edit it, but it doesn't change the entry.
wsjt-x-aa5au01.jpg
The entry in wsjtx_log.adi seems correct.
KK6NTL DM95 FT8 -07
20190721 160830 20190721
160930 6m 50.315022 AA5AU
E
pg
The entry in wsjtx_log.adi seems correct.
KK6NTL DM95 FT8 -07
20190721 160830 20190721
160930 6m 50.315022 AA5AU
EL49XU
Don AA5AU
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
There's an inconsistency in double-clicking Tx4 selector.I assume txb4 should
be same as txrb4 for the FT4 RR73 settings.
void MainWindow::on_txrb4_doubleClicked (){ // RR73 only allowed if not a type
2 compound callsign auto const& my_callsign = m_config.my_callsign (); auto
is_compound = my
On 21/07/2019 12:33, George Molnar wrote:
Thanks for the effort, Bill. Unfortunately, no change on MacOS
Catalina beta. Still crash on launch.
73
*George J Molnar*
Arlington, Virginia, USA
Hi George,
the crash with macOS 10.15 beta is a different one. For that I will wait
until 10.15 goes
Thanks for the effort, Bill. Unfortunately, no change on MacOS Catalina beta.
Still crash on launch.
73
George J Molnar
Arlington, Virginia, USA
> On Jul 21, 2019, at 6:34 AM, Bill Somerville wrote:
>
> Hi all,
>
> some of you have reported a crash on startup, thanks to those who have
Hi all,
some of you have reported a crash on startup, thanks to those who have
provided the crash report.
I can confirm there is a defect which appears to be in the underlying Qt
library we use for cross platform portability. The issue is fixed in Qt
v5.11 but using that will entail dropping
25 matches
Mail list logo
