New hamlib for installation directions
#1 Shut down WSJTX
#2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX -- hopefully your browser doesn't block it but may warn you multiple
times.
If you can do a "Save As" you can save it directly in the appropriate WSJTX
When using Shift-click on the waterfall to set the TX frequency, the "Rig
Control Error" popup is displayed. Clicking the "Show Details..." button shows
the following error information:
Hamlib error: port_wait_for_data_direct(733): timeout=1,0
port_wait_for_data_direct(742): timeout=1,0
in a grounded system.
From: David Tiller
Date: Monday, May 9, 2022 at 10:33 AM
To: WSJT software development
Cc: W2JDM
Subject: Re: [wsjt-devel] Bug Report
Jason,
This sounds like a textbook example of RFI getting into your computer or USB
cable. I had a similar issue on 80m
are grounded. Proves that RF
can leak in even in a grounded system.
From: David Tiller
Date: Monday, May 9, 2022 at 10:33 AM
To: WSJT software development
Cc: W2JDM
Subject: Re: [wsjt-devel] Bug Report
Jason,
This sounds like a textbook example of RFI getting into your computer or USB
cable. I had
That’s a question of RFI !
Op ma 9 mei 2022 om 17:03 schreef David Tiller via wsjt-devel <
wsjt-devel@lists.sourceforge.net>
> Jason,
>
> This sounds like a textbook example of RFI getting into your computer or
> USB cable. I had a similar issue on 80m and found that a few well-placed
> ferrites
Jason,
This sounds like a textbook example of RFI getting into your computer or USB
cable. I had a similar issue on 80m and found that a few well-placed ferrites
on my USB cable fixed the issue.
Search for "FT8 RFI" for other folks advice.
To verify, try transmitting into a dummy load or at
WSJTX Version: 2.5.4
OS – Mac Monterey 12.3.1
Radio – Yaesu 991A
SiliconLabs Driver – 6.0.2 for Mac
When tuned to 40m (and only 40m), using FT8, the software loses CAT control
shortly after transmitting. The symptoms are that it will hold the transmit
too long and eventually show ORANGE
Hi Marco,
thanks for the update, glad you are up and running correctly now.
73
Bill
G4WJS.
On 14/10/2021 19:23, Marco Monari via wsjt-devel wrote:
Problem solved overwriting with the new libhamlib-4.dll, many thanks!
73
Marco
IK4PLZ
On 14/10/2021 16:34, Bill Somerville via wsjt-devel wrote:
Problem solved overwriting with the new libhamlib-4.dll, many thanks!
73
Marco
IK4PLZ
On 14/10/2021 16:34, Bill Somerville via wsjt-devel wrote:
On 14/10/2021 14:25, Marco Monari via wsjt-devel wrote:
Version 2.4.0 and 2.5.0
OS: Windows 10 64 bit
All versions previous 2.4.0 work perfectly,
On 14/10/2021 14:25, Marco Monari via wsjt-devel wrote:
Version 2.4.0 and 2.5.0
OS: Windows 10 64 bit
All versions previous 2.4.0 work perfectly, 2.4.0 and also latest
2.5.0 both show this problem.
Conditions: FT8 mode with a Kenwood TS-590SG
Switching between bands VFO RX frequency change
Version 2.4.0 and 2.5.0
OS: Windows 10 64 bit
All versions previous 2.4.0 work perfectly, 2.4.0 and also latest 2.5.0
both show this problem.
Conditions: FT8 mode with a Kenwood TS-590SG
Switching between bands VFO RX frequency change correctly but TX
frequency in VFO radio doesn't change.
On 11.8.2021 13.51, Jose Montano via wsjt-devel wrote:
Hi
this problem is still present, have you been able to duplicate it?
Jose, for the 'lowercase X" issue see my reply:
https://sourceforge.net/p/wsjt/mailman/message/37326983/
Have you contacted the translator???
IIRC your second issue
Hi
this problem is still present, have you been able to duplicate it?
Mensaje reenviado
Asunto: Bug Report
Fecha: Tue, 27 Jul 2021 19:37:10 -0300
De: Jose Montano
Para: wsjt-devel@lists.sourceforge.net
-WSJT-X 2.5.0-rc5 4030b0
-OS GNU/Linux Debian testing
Hi Jose,
you did not tell us your callsign, but from the screenshot I assume you
are using Spanish.
TxN buttons
This seems to be an translation issue.
In file "wsjtx_es.ts" we can see that the translator has translated TxN
to TXN...
line="1850"/> Tx 2 TX
2
Hi Jose,
Interesting, how you did it?
73, Reino OH3mA
>El 27/7/21 a las 19:46, Bill Somerville via wsjt-devel escribió:
>> TxN buttons
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
El 27/7/21 a las 19:46, Bill Somerville via wsjt-devel escribió:
TxN buttons
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On 27/07/2021 23:37, Jose Montano via wsjt-devel wrote:
-WSJT-X 2.4.0+repack-1 (experimental branch)
-OS GNU/Linux Debian testing
-In the button "TX1" the letter "X" is lowercase.
-When I call CQ, and someone answers me, for example with a dB-19
signal, the software responds giving the
-WSJT-X 2.4.0+repack-1 (experimental branch)
-OS GNU/Linux Debian testing
-In the button "TX1" the letter "X" is lowercase.
-When I call CQ, and someone answers me, for example with a dB-19
signal, the software responds giving the report -19, but if for some
reason, the station does not
Thanks Mike. I’ll install it, play with it and get back to you some time
tomorrow.
73,
Mike Cizek W0VTT
From: Black Michael via wsjt-devel
Sent: Saturday, 20 March, 2021 16:19
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s Freq Control
Hi Mike,
thanks Mike, I asked because the K3 series have known issues with getting
confused if they have multiple PTT sources.
Please try "Settings->Radio->Split Opera
le
> Sent: Thursday, 18 March, 2021 15:56
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s Freq Control
>
> Hi Mike,
>
> thanks Mike, I asked because the K3 series have known issues with getting
> confused if they have multi
G4WJS - Found a local to test with on MSK144. The CQ 266 seems to work OK, but
I still see the freq display on the K3s flicker when switching from transmit to
receive.
W9MDB - Installed the version you sent me. I’m calling it rc3b. Split
Operation > Fake It. FT8 50.313, call CQ tx dF 2100
On 18/03/2021 22:25, Joe Taylor wrote:
Hi Mike,
On 3/18/2021 5:55 PM, Mike Cizek W0VTT wrote:
Using Split Operating > Rig seems to work fine on FT8. I can’t find
anyone on meteors right now to test it split on MSK144.
"Split" is not used (and not relevant) in MS144 mode.
-- Joe, K1JT
Hi Mike,
On 3/18/2021 5:55 PM, Mike Cizek W0VTT wrote:
Using Split Operating > Rig seems to work fine on FT8. I can’t find
anyone on meteors right now to test it split on MSK144.
"Split" is not used (and not relevant) in MS144 mode.
-- Joe, K1JT
day, 18 March, 2021 15:56
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s Freq Control
Hi Mike,
thanks Mike, I asked because the K3 series have known issues with getting
confused if they have multiple PTT sources.
Please try "Settings->R
, 2021 11:05
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s Freq Control
Mike,
it is certainly possible, but there need be no doubt. When you K3s is
in USB DATA A mode is the VOX indicator showing on the K3s display panel?
73
Bill
G4WJS.
On 18/03
Hello Bill,
No, there is no VOX. PTT is provided via the USB cable.
73,
Mike Cizek W0VTT
From: Bill Somerville
Sent: Thursday, 18 March, 2021 11:05
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s Freq Control
Mike
the rig
and computer is all digital; sound card is built in to the radio. As
noted, v2.3.0 and earlier all worked fine.
73,
Mike Cizek W0VTT
*From:* Bill Somerville
*Sent:* Thursday, 18 March, 2021 10:49
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] Bug Report v2.4.0
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s Freq Control
Hi Mike,
thanks for that. Could the K3s be getting PTT from another source as well, DATA
VOX enabled for example?
73
Bill
G4WJS.
On 18/03/2021 15:44, Mike Cizek W0VTT wrote:
Hello
PTT Method : CAT
Mode: Data/Pkt
Split Operation: Fake It
73,
Mike Cizek W0VTT
*From:* Bill Somerville
*Sent:* Thursday, 18 March, 2021 10:19
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s Freq Control
On 18/03/2021 15:15, Mike Cizek W0VTT
@lists.sourceforge.net
Subject: Re: [wsjt-devel] Bug Report v2.4.0 rc3 K3s Freq Control
On 18/03/2021 15:15, Mike Cizek W0VTT wrote:
Greetings,
Frequency control problems in v2.4.0 rc2 and rc3. (did not try rc1) v2.3.0 and
earlier worked fine.
FT8 or Q65 – when transmitting at audio dF
On 18/03/2021 15:15, Mike Cizek W0VTT wrote:
Greetings,
Frequency control problems in v2.4.0 rc2 and rc3. (did not try rc1)
v2.3.0 and earlier worked fine.
FT8 or Q65 – when transmitting at audio dF that requires shifting the
transmit freq (df 2000Hz), WSJT will move the radio up 500 Hz,
Greetings,
Frequency control problems in v2.4.0 rc2 and rc3. (did not try rc1) v2.3.0 and
earlier worked fine.
FT8 or Q65 – when transmitting at audio dF that requires shifting the transmit
freq (df 2000Hz), WSJT will move the radio up 500 Hz, but does not always
return to the original
On 04/02/2021 13:25, David Schmocker wrote:
Good morning:
Operating system: Mac OS Mojave 10.14.6
Software version: WSJT-X v 2.4.0 rc1
Issue/behavior: Program self closes (all windows) and
Unable to move outside of 15 second
periods for this mode
Steps
On 01/02/2021 15:49, kb8u vhf wrote:
Hello, I have noticed a bug while operating FST4. I am currently
running v2.3.0-rc4 ef3630
To reproduce:
Make a QSO with auto sequencing enabled and RR73 configured to be
sent. While RR73 is being sent, select CQ Next checkbox (expecting to
receive 73
Hello, I have noticed a bug while operating FST4. I am currently running
v2.3.0-rc4 ef3630
To reproduce:
Make a QSO with auto sequencing enabled and RR73 configured to be sent. While
RR73 is being sent, select CQ Next checkbox (expecting to receive 73 from the
other station).
After 73 is
Just downloaded and installed V.2.2.2, made a contact and checked my wsjtx_log
file.It had the correct (WSJT-X ADIF Export) header. No problem?Al, N4AB,
73
In a message dated 6/24/2020 15:18:44 Eastern Standard Time,
g4...@classdesign.com writes:
On 24/06/2020 19:17, Joe WA6AXE wrote:
> I
@lists.sourceforge.net
Subject: Re: [wsjt-devel] BUG Report for WSJT-X Ver 2.2.2 - 64 bit
On 24/06/2020 19:17, Joe WA6AXE wrote:
> I need to report a BUG in the newest ver 2.2.2. (64 bit) ...
>
> When the program MAKES the wsjtx_log.adi file .. There is an ERROR in the
> beginning of the adi file ..
&
On 24/06/2020 19:17, Joe WA6AXE wrote:
I need to report a BUG in the newest ver 2.2.2. (64 bit) ...
When the program MAKES the wsjtx_log.adi file .. There is an ERROR in the
beginning of the adi file ..
The current version 2.2.2 writes:
WSJT-X ADIF Export
it SHOULD be written as:
WSJT-X ADIF
I need to report a BUG in the newest ver 2.2.2. (64 bit) ...
When the program MAKES the wsjtx_log.adi file .. There is an ERROR in the
beginning of the adi file ..
The current version 2.2.2 writes:
WSJT-X ADIF Export
it SHOULD be written as:
WSJT-X ADIF Export
The is currently shown as
This
Hi Onno,
On 6/19/2020 3:53 PM, Onno Benschop VK6FLAB wrote:
Frankly that makes no sense.
All the JT modes have evolved over time. Even WSPR has evolved. Compound
callsigns were introduced with WSPR 2.00 (r1714) Nov 19, 2009 -
http://physics.princeton.edu/pulsar/K1JT/WSPR_Changelog.TXT
Just
Frankly that makes no sense.
All the JT modes have evolved over time. Even WSPR has evolved. Compound
callsigns were introduced with WSPR 2.00 (r1714) Nov 19, 2009 -
http://physics.princeton.edu/pulsar/K1JT/WSPR_Changelog.TXT
Just because it wasn't designed with a four character suffix callsign
Onno,
There is nothing wrong with your call sign of four characters in the
suffix. It is just too long to fit within the restrictions of WSJT-X if you
want to use WSJT-X in the standard way. Mind you, you can still use
WSJT-X, just not in the standard way.
WSJT-X was never created to work
Hi Onno,
I was enquiring about this in February this year too -
https://sourceforge.net/p/wsjt/mailman/message/36929030/
> With various tests, I can hear my WSPR transmissions away from my station
and WSJT-X can even decode my transmissions. However the decoding only
occurs on transmissions
Today I attempted to TX using WSPR and learned that my callsign (VK6FLAB)
which I've held for nearly a decade isn't considered a "standard" callsign
- this format was introduced in 2005.
According to the ITU[1], my callsign is a perfectly legal callsign (and has
been since 2003) (*emphasis*
Problem: WSJT-X Tx audio disconnects from Flex DAX after sitting idle
Current software configuration: WSJT-x v 2.2.0, Flex DAX v 2.6.2.50, Windows 10
Pro v 1909.
FlexRadio 6600M transceiver running v 2.6.2.50 software.
After WSJT-x in FT8 mode sits in a receive/monitor condition for several
Hi Bruce,
On 5/25/2020 5:44 PM, Bruce H. Bern K3NQ wrote:
Program version: (beta) WSJT-X 2.2.0-rc3; My system: Win 10 Pro X64; Intel
Core i7-3930K; CPU@3.2 GHz; RAM=24Gb; Radio Kenwood TS-990, Baud rate:
115,200; data bits, stop bits, handshake all default
Precis of problem: If a transmit
Hi Bruce,
On 5/25/2020 2:53 PM, Bruce H. Bern K3NQ wrote:
Using latest Win-10, if attempting to place the transmit frequency below
200 Hz, the display crashes
I can't reproduce the effect you describe.
If it's reproducible for you, please follow instructions for bug reports
here in the User
Using latest Win-10, if attempting to place the transmit frequency below 200
Hz, the display crashes
Thanks,
Bruce K3NQ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi Joe
Thank you.
I am glad to hear that.
73
Yukio JG1APX
On Sat, 23 May 2020 09:11:20 -0400
Joe Taylor wrote:
> Hi Yukio-san,
>
> Thanks for alerting us to the omission of a mode-label color definition for
> FT4, and the typo. They will be corrected in the next release!
>
> --
Hi Yukio-san,
Thanks for alerting us to the omission of a mode-label color definition
for FT4, and the typo. They will be corrected in the next release!
-- Joe, K1JT
On 5/22/2020 8:52 PM, Yukio JG1APX wrote:
Hello all
I have noticed minor things in mainwindow.cpp source code. If
Hello all
I have noticed minor things in mainwindow.cpp source code. If they are
already known, sorry about this.
v2.2.0 rc1 mainwindow.cpp :
1. FT4 background color of mode lable depends on previous mode.
The background color difinition is missing in setup_status_bar
(bool vhf) at line
Thank you Joe, glad to help, if even with a little-used mode.
As others have said, we have a small group of ISCAT users here in the west, so
we may have further info for you as time progresses.
We need to thanks James K7KQA for this as he is the driver out here for getting
people to try out
Hi Kevin,
On 5/22/2020 10:45 AM, Kevin McQuiggin VE7ZD/KN7Q wrote:
In ISCAT mode, if one double-clicks a message in the left hand RX signals pane
this presents a dialog box “Double clicking is not supported in ISCAT mode”.
When this dialog box is dismissed, the app crashes.
Many tThanks
Hi All:
In ISCAT mode, if one double-clicks a message in the left hand RX signals pane
this presents a dialog box “Double clicking is not supported in ISCAT mode”.
When this dialog box is dismissed, the app crashes.
I am running rc1 on MacOS version 10.14.6 Mojave.
If you need further info
On 13/05/2020 00:44, Dave Anderson, K4SV via wsjt-devel wrote:
Hi Everyone,
I am new to the group here and not sure where to make a bug report
other than what the WSJTX site suggests, which is here.
Overall software runs very well. Using it for 630 meter WSPR at the
moment.
Bug
After
Hi Everyone,
I am new to the group here and not sure where to make a bug report other than
what the WSJTX site suggests, which is here.
Overall software runs very well. Using it for 630 meter WSPR at the moment.
BugAfter setting the transmit power level it transmits correctly but if the
Hi WSJT-X Developers.
I am Yoshi JH7WNV.
Thanks for all. and I enjoy using WSJT-X every day.
When I creating log(ALL.TXT) file analyze tool, I found a bug in WSJT-X log
file.
Please check this problem. and fix.
•Program version
WSJT-X v2.1.0 x64
•Operating system
OS: Windows 7 x64
CPU:
New to the list...I couldn't find a bug tracker online so I will report
this here for now.
WSJT-X version 2.0.1 (GA Release)
Windows 10 Pro 64-bit
Issue: Even when Save->None is selected the app continues to accumulate
large numbers of WAV files in ...\AppData\Local\WSJT-X\save (SaveDir)
This
Oh, also running W10 1809 and WSJT-X 2.1.0 RC7.
On 6/16/2019 04:01, Jim Nuytens via wsjt-devel wrote:
I'm not a programmer or developer, but I'd like to know the precise
hardware configuration of those having this issue. Down to the minute
details of motherboard, sound interface, etc.
I do
I'm not a programmer or developer, but I'd like to know the precise
hardware configuration of those having this issue. Down to the minute
details of motherboard, sound interface, etc.
I do not see anything like this at all, and my system runs for days at a
time. Sometimes the system runs for
Check your Windows 10 updates first. I had the same issue. Now, no problem.
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 15, 2019, at 6:41 PM, Tom M0LTE wrote:
>
>
This happens to me from time to time.
On Sat, 15 Jun 2019 at 22:43, Steve Masticola via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Program version: 2.0.1 7ddcb7
>
> Operating system: Windows 10, ver. 1809 (OS Build 17763.503)
>
> Description: After sitting idle with Monitor on for
Program version: 2.0.1 7ddcb7
Operating system: Windows 10, ver. 1809 (OS Build 17763.503)
Description: After sitting idle with Monitor on for several minutes, WSJT-X
will key the transceiver on Tune or transmit, but does not generate sound to
the soundcard. I have confirmed that the issue is in
On 02/06/2019 21:50, DG2YCB wrote:
WSJT-X v2.1.0 RC6 32-bit version starts normal on my Windows 10 64 bit
computer. Only issue there was that CAT connection to my Ft-991 (via
OmniRig) got lost at least ten times within three minutes. I didn't
have such issues with all earlier versions
It appears to me that the problem with rc6 failing to start is related
to an existing wsjt_log.adi..
delete or rename the wsjt_adi.log file and try again..
AL, K0VM
On 6/2/2019 4:52 PM, Hasan al-Basri wrote:
Same here, 64 bit win won't start and does not show up as an installed
program. The
v2.1.0-RC6 also crashes on my Ubuntu 18.04.2 64bit installation.
I have uploaded the Ubuntu crash report to my dropbox:
https://www.dropbox.com/s/ocaibp3dfbajdyh/_usr_bin_wsjtx.1001.crash?dl=0
If starting the program with the -r parameter (wstjx -r test) everything
starts fine. Starting with
Same here, 64 bit win won't start and does not show up as an installed
program. The files are in the install directory, but it neither starts, nor
does is show up in the start program list.
N0AN
Hasan
On Sun, Jun 2, 2019 at 2:00 PM Jari A wrote:
> win 7 64 bit
>
> Does not start, reboot does
Hi Bill,
RC6 32 bit came with:
Problem signature:
Problem Event Name: APPCRASH
Application Name: wsjtx.exe
Application Version: 0.0.0.0
Application Timestamp: 07211a30
Fault Module Name: wsjtx.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 07211a30
Exception Code:
On 02/06/2019 21:50, DG2YCB wrote:
Hi Bill,
WSJT-X v2.1.0 RC6 32-bit version starts normal on my Windows 10 64 bit
computer. Only issue there was that CAT connection to my Ft-991 (via
OmniRig) got lost at least ten times within three minutes. I didn't
have such issues with all earlier
Ubuntu MATE 18.04 LTS amd64
rc6 segfaults at startup.
It's OK if I start from shell using --test-mode
73,
Richard G4DYA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
.
wsjtx -r test
de Mike W9MDB
On Sunday, June 2, 2019, 3:11:48 PM CDT, DG2YCB, Uwe wrote:
Same here. Win 10 64 bit version not starting.
73 de Uwe, DG2YCB
Von: Jari A [mailto:oh2...@gmail.com]
Gesendet: Sonntag, 2. Juni 2019 20:55
An: WSJT software development
Betreff: [wsjt-devel] Bug
better for you?
73
Bill
G4WJS.
On 02/06/2019 21:07, DG2YCB, Uwe wrote:
Same here. Win 10 64 bit version not starting.
73 de Uwe, DG2YCB
*Von:*Jari A [mailto:oh2...@gmail.com]
*Gesendet:* Sonntag, 2. Juni 2019 20:55
*An:* WSJT software development
*Betreff:* [wsjt-devel] Bug report
win 7 64
:
Same here. Win 10 64 bit version not starting.
73 de Uwe, DG2YCB
Von: Jari A [mailto:oh2...@gmail.com]
Gesendet: Sonntag, 2. Juni 2019 20:55
An: WSJT software development
Betreff: [wsjt-devel] Bug report
win 7 64 bit
Does not start, reboot does not help.
FYI
Best rgds
development
Betreff: [wsjt-devel] Bug report
win 7 64 bit
Does not start, reboot does not help.
FYI
Best rgds,
:Jari / oh2fqv
---
Problem signature:
Problem Event Name: APPCRASH
Application Name: wsjtx.exe
Application Version: 0.0.0.0
Application Timestamp
*Von:*Jari A [mailto:oh2...@gmail.com]
*Gesendet:* Sonntag, 2. Juni 2019 20:55
*An:* WSJT software development
*Betreff:* [wsjt-devel] Bug report
win 7 64 bit
Does not start, reboot does not help.
FYI
Best rgds,
:Jari / oh2fqv
___
wsjt-devel mailing
: Jari A [mailto:oh2...@gmail.com]
Gesendet: Sonntag, 2. Juni 2019 20:55
An: WSJT software development
Betreff: [wsjt-devel] Bug report
win 7 64 bit
Does not start, reboot does not help.
FYI
Best rgds,
:Jari / oh2fqv
---
Problem signature:
Problem Event
win 7 64 bit
Does not start, reboot does not help.
FYI
Best rgds,
:Jari / oh2fqv
---
Problem signature:
Problem Event Name: APPCRASH
Application Name: wsjtx.exe
Application Version: 0.0.0.0
Application Timestamp: 5cf07e87
Fault Module Name: wsjtx.exe
Fault Module Version:
On 03/05/2019 01:27, Morris Wideman via wsjt-devel wrote:
Why would I want to call another station on top of someone else. If
the TX/RX freqs are suppose to locked together thats what they should
do, I do sometimes operate split but I try not to get on top of
another station. 73 WA4MIT Morris
Why would I want to call another station on top of someone else. If the TX/RX
freqs are suppose to locked together thats what they should do, I do sometimes
operate split but I try not to get on top of another station. 73 WA4MIT Morris
On Thursday, May 2, 2019, 5:44:44 PM CDT, Ron Koenig
Why would you want to TX on his frequency ?
On Thu, 2 May 2019 at 15:30, Morris Wideman via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Many thanks to the development team for sharing FT4 with us all. This
> faster FT should really help the DXpeditions and Contesters I think it
>
Hi Mike
Thanks again for your rapid reply, and for the information ..I suspected this
would be corrected in the next release.
Take care
Lorin
> On Jan 23, 2019, at 12:11 PM, Black Michael via wsjt-devel
> wrote:
>
> It's a bug in the 2.0.0 version where the "Retain" checkbox is not being
It's a bug in the 2.0.0 version where the "Retain" checkbox is not being
honored.
It's been fixed for the next version.
de Mike W9MDB
On Wednesday, January 23, 2019, 2:07:38 PM CST, Lorin Hollander
wrote:
Hi Bill, Mike and the others who kindly answered my question and addressed
On 23/01/2019 20:02, Lorin Hollander wrote:
Please, can you help me address the other issue? It is about the
empty Comment and Power fields in the "Log QSO” pop-up window,
Although the windows is now configured differently in vs/ 2.0., is
thee a way to autofill these two fields, fields that
Hi Bill, Mike and the others who kindly answered my question and addressed
this issues so well. Thank you all for your time and care, it means a lot.
I have returned to the practice of sending CQ DX WA1PGB CM88, and that is
working fine. Thank you again.
Please, can you help me address
On 23/01/2019 16:24, Lorin Hollander wrote:
When sending a CQ DX from the drop down entry box No 5 where I have
previously entered my call in F2 “Settings “, as the compound WA1PGB/6
Hi Lorin, sorry clicked "Send" prematurely. Let's try again:
the way non-standard callsigns are handled in
On 23/01/2019 16:24, Lorin Hollander wrote:
When sending a CQ DX from the drop down entry box No 5 where I have
previously entered my call in F2 “Settings “, as the compound WA1PGB/6
Hi Lorin,
the way non-standard callsigns are handled in WSJT-X for the new 77-bit
FT8 and MSK144 modes has
On 1/23/19 5:46 PM, Roy Gould wrote:
Hi Roy & all,
This happens to me once in a while. I don't know what call sign was
supposed to be there so I delete the whole record and save the file and
then everything seems to be OK.
When you reread an ADIF file, it should not contain obvious errors,
I can confirm "CQ DX WA1PGB/6" works in 1.9.1 but not 2.0.0...you're solution
right now is to drop the "DX" and the grid. The grid doesn't work either and
drops the suffix. In 1.9.1 it dropped the grid and kept the suffix.
C:\WSJT\wsjtx\bin>ft8code.exe "CQ WA1PGB/6 EM49" Message
It appears that was just one record where you didn't have the callsign in the
"DX Call" box in WSJT-X.
That first field is your QSO partner's callsign.
Mike
On Wednesday, January 23, 2019, 10:31:26 AM CST, Lorin Hollander
wrote:
Many thanks Mike for this information and advice.
And
Many thanks Mike for this information and advice.
And as to where I should enter station snd personal information so that this
will be included as autofill in the Log Window fields? Where do I enter that
data?
Thanks again
Lorin
Sent from my iPhone
> On Jan 23, 2019, at 7:45 AM, Black
Hello,
I have been successfully using FT-8 in vs 1.9 for several months with no
problems or issues. I have now been using vs. 2.0 in the latest iteration, I
believe, and have run into what seems like a bug, although I cannot be sure.
I am running WSJT-X 2.0 on a MacBook Pro with OS X High
The error tells you -- that record has no call sign. Edit the log file and
remove the record.
The ADIF parsing has been relaxed for the next version but not sure what it
will do a record like this.
Perhaps Bill knows.
de Mike W9MDB
On Wednesday, January 23, 2019, 9:40:35 AM CST, Lorin
Hello,
I am a new member of this group.
I receive the following error (see screenshot below) when starting WSJT-X FT8
vs 2.0 in Windows 10.What is the process to correct this. Also, the
previous versions always autofilled most of the fields in the Log Contact
window (Power - etc.) and
Known bug. Already fixed in next version.
de Mike W9MDB
On Thursday, December 27, 2018, 6:36:41 AM CST, VE3FBZ
wrote:
Begin forwarded message:
From: VE3FBZ
Date: December 26, 2018 at 12:50:54 PM EST
To: wsjtgr...@yahoogroups.com
Subject: Bug report - non urgent- WSJT-X V2.0.0
Begin forwarded message:
> From: VE3FBZ
> Date: December 26, 2018 at 12:50:54 PM EST
> To: wsjtgr...@yahoogroups.com
> Subject: Bug report - non urgent- WSJT-X V2.0.0 build 784f75 - comments and
> power not sticky.
>
> I have found both comments and power level shown on logging window are
On 20/12/2018 14:23, Gene H wrote:
A friend of mine also has same issue with his ICOM IC-7600 using Fake
It. He went back to Split to get around the issue.
73 Gene K5PA
Hi Gene,
problems with Icom CAT control are often due to not disabling "CI-V
Transceive Mode" on the rig.
73
Bill
A friend of mine also has same issue with his ICOM IC-7600 using Fake
It. He went back to Split to get around the issue.
73 Gene K5PA
On 12/20/2018 8:15 AM, Steven Greer wrote:
Hey bill last time we touched base on this was right after release and
you mentions you could send me a build with
On 20/12/2018 14:15, Steven Greer wrote:
I tried to enable a mirror to see what was passing however wsjtx won't
connect to the radio because it's not responding fast enough.
Hi Steven,
some emulators use a device with a built in bootloader that is active
for a second or two after a chip
Hey bill last time we touched base on this was right after release and
you mentions you could send me a build with CAT trace enabled, if you
could that would be great. I did notice that another user was using
ft-857d interface and had the same problem. I have been able to connect
directly to
1 - 100 of 199 matches
Mail list logo
