Date   

locked #Cabrillo Contest Log Window #ContestMode

David Ross
 

While it is possible to sort any of the Cabrillo Contest log column headers, can the sort be added to the contact number header. As the log is filled after the window is filled it is not possible to see how many contacts are in the log without scrolling down the log. Adding this sort to the Cabrillo Contest log column headers would be best OR add the total contacts somewhere in the main WSJTX window so it is visible during any of the contest in the Advanced settings.


David VA3MJR
--


locked Re: #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

W4JBB
 

Fred,

At this point, the only suggestion I can make is to try the USB cable I recommended previously. Otherwise, I’m out of suggestions.

Thanks,
Joel, W4JBB


locked Re: Bug that Tx5 is not sent #FT8 #IssueReport

 

This has been discussed so many times before, but I’ll add my twopennorth. If I receive a repeated R+sig, I’ll repeat the RR73, if I don’t I’ll assume they’ve received it. It doesn’t matter to me, as I’m not a diploma chaser, if they are I assume they’ve got me if they don’t ask again. I upload to eQSL.cc, LotW and Clublog all QSOs I think are complete. If they disagree, I don’t care. I occasionally get an e-mail via eSL.com, “Please remove me from your log”, why? I worked you, you just haven’t confirmed it – work me again if you want to. Sorry it’s ended like my sixpennyworth of opinion.

 

73 Phil GM3ZZA.

 

Sent from Mail for Windows 10

 

From: K0LUZ -- Gary Red Letchford
Sent: 26 June 2021 19:02
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Bug that Tx5 is not sent #FT8 #wsft-x #BugReport

 


Just because you sent RR73 does not mean that the other station rcvd RR73.  I still have that nagging feeling that the qso is not complete.  So I like to see the 73 as an assurance that all was received.  I understand it is not required,  but it's a nice gesture.

73 Red  K0LUZ


On 6/26/2021 10:07 AM, Dave Garber wrote:

if you sent the rr73, what is the need to send 73 of any kind again....  I have never sent 73, after the rr73.  just thought it was normal

Dave Garber

VE3WEJ / VE3IE

 

 

On Sat, Jun 26, 2021 at 7:21 AM kiyo <ja9hwd@...> wrote:

hello!

There is a bug in WSJT-X v2.3.1 or later.
When "TU NEWBAND 73" is set to Tx5 immediately after the start of QSO, QSO ends without sending the message of Tx5 at the end, and the dialog for writing the log is displayed. The QSO partner does not exit QSO because Tx5 is not sent. I cannot return to 73 messages by pressing the "Generate standard message" button.
However, a bug that does not occur when Tx4 is "RR73".
To reproduce this bug, set Tx4 to "RRR". And start QSO by CQ without calling other stations.
To work around this bug, set Tx4 to "RR73". And I have to give up sending the nifty 73 messages.

If possible, I would like to see the bugs fixed as soon as possible.
--
kiyo



 
 
 

 

 

Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



 


--
73 Phil GM3ZZA


locked WSJT-X locking up #general

Brian Bowers G0VAX
 

Hi All,
Has anyone had version 2.4 lock up when trying to go into settings?
I wish to edit frequencies and WSJT-x locks up when entering settings

Brian G0VAX


locked #FT8 and processor speed #FT8

John Geiger AF5CC <af5cc2@...>
 

I apologize if this topic has been covered before, I looked through the archives and couldn't find anything that seemed to be discussing exactly this topic.

For the past 3 years I have been running FT8 using WSJT-X on a Lenevo Thinkpad which uses an AMD E1-7500 AMU processor running at 1.4GHZ and has 4GB of RAM.  It was acting up the other day so I decided to do a full reset on it, wiping the hard drive and reinstalling Windows 10.  This ended up taking a while so I hooked up my other laptop to see what was going on on FT8.  It is a HP Elitebook with an Intel I5-5300U processor running at 2.4GHZ and has 8 GB of RAM.  I immediately noticed that the decoded lines filled up the screen much quicker on the Elitebook.

So, is having a faster, more powerful processor like the Intel I5 likely to lead to more stations decoded on FT8 than I would get with the slower processor?  I kind of prefer to take the Elitebook traveling with me, but if it will lead to significantly better decoding, I will leave it in the shack running remotely and take the Lenevo with me when traveling.

73 John AF5CC


locked Re: Bug that Tx5 is not sent #FT8 #IssueReport

K0LUZ -- Gary "Red" Letchford
 


Just because you sent RR73 does not mean that the other station rcvd RR73.  I still have that nagging feeling that the qso is not complete.  So I like to see the 73 as an assurance that all was received.  I understand it is not required,  but it's a nice gesture.

73 Red  K0LUZ



On 6/26/2021 10:07 AM, Dave Garber wrote:
if you sent the rr73, what is the need to send 73 of any kind again....  I have never sent 73, after the rr73.  just thought it was normal
Dave Garber
VE3WEJ / VE3IE


On Sat, Jun 26, 2021 at 7:21 AM kiyo <ja9hwd@...> wrote:
hello!

There is a bug in WSJT-X v2.3.1 or later.
When "TU NEWBAND 73" is set to Tx5 immediately after the start of QSO, QSO ends without sending the message of Tx5 at the end, and the dialog for writing the log is displayed. The QSO partner does not exit QSO because Tx5 is not sent. I cannot return to 73 messages by pressing the "Generate standard message" button.
However, a bug that does not occur when Tx4 is "RR73".
To reproduce this bug, set Tx4 to "RRR". And start QSO by CQ without calling other stations.
To work around this bug, set Tx4 to "RR73". And I have to give up sending the nifty 73 messages.

If possible, I would like to see the bugs fixed as soon as possible.
--
kiyo









Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Re: #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

Frederick Kent
 
Edited

Hi Joel, tnx fer the dog park info which leads me back to my initial problem post (#25962) in that having the IC-7300 which has a SiLab USB to UART device that I need the SiLab CP210X driver. So I tried to delete as many of the SiLab driver attempts before that I could from the iMac and reloaded the CP210X ver. 6.0.1. It successfully loaded into the extensions as advertised (ref. attached photo) which was taken after I connected the radio and rebooted the computer.
Prior to the radio connection and reboot it did state it was loaded, now after reboot its not loaded. When I look at the WSJTx config. it is the same as in my (#26007) post. Also the radio does not show of in the iMac USB list.I tried reloading the driver again and it showed up as loaded in the extensions, so I connected radio without reboot and it stayed loaded but didn't show up in IC-7300 WSJTx config. It needs to be in terminal ( ls /dev. ). And far as working before, I only recently attempted to use WSJTx. However I did have it working somewhat  3 or 4 years ago before a series of events led to me  losing it and not trying to use  using WSJTx. And in that previous episode 3 years ago it was the same difficulties in getting it to work. 
  So I'm just the spinning my wheels and going nowhere.


locked Re: Where I can download WSJT-X 2.9.x? #wsjt-x #IssueReport

Pietro Molina
 

I' sorry: yes, I intend 2.3.x, I had downloaded the 2.3.1 and all is OK. 

yes, I tried without the flag about the freq. changes during transmit, but nothing changed.

Pietro I2OIM


locked Re: Bug that Tx5 is not sent #FT8 #IssueReport

Dave Garber
 

if you sent the rr73, what is the need to send 73 of any kind again....  I have never sent 73, after the rr73.  just thought it was normal
Dave Garber
VE3WEJ / VE3IE


On Sat, Jun 26, 2021 at 7:21 AM kiyo <ja9hwd@...> wrote:
hello!

There is a bug in WSJT-X v2.3.1 or later.
When "TU NEWBAND 73" is set to Tx5 immediately after the start of QSO, QSO ends without sending the message of Tx5 at the end, and the dialog for writing the log is displayed. The QSO partner does not exit QSO because Tx5 is not sent. I cannot return to 73 messages by pressing the "Generate standard message" button.
However, a bug that does not occur when Tx4 is "RR73".
To reproduce this bug, set Tx4 to "RRR". And start QSO by CQ without calling other stations.
To work around this bug, set Tx4 to "RR73". And I have to give up sending the nifty 73 messages.

If possible, I would like to see the bugs fixed as soon as possible.
--
kiyo



locked Bug that Tx5 is not sent #FT8 #IssueReport

kiyo
 

hello!

There is a bug in WSJT-X v2.3.1 or later.
When "TU NEWBAND 73" is set to Tx5 immediately after the start of QSO, QSO ends without sending the message of Tx5 at the end, and the dialog for writing the log is displayed. The QSO partner does not exit QSO because Tx5 is not sent. I cannot return to 73 messages by pressing the "Generate standard message" button.
However, a bug that does not occur when Tx4 is "RR73".
To reproduce this bug, set Tx4 to "RRR". And start QSO by CQ without calling other stations.
To work around this bug, set Tx4 to "RR73". And I have to give up sending the nifty 73 messages.

If possible, I would like to see the bugs fixed as soon as possible.
--
kiyo


locked VS: [WSJTX] Lost cat (Old problem new to me) #FT8 #Cat_RigControl #WSJTX_config

Reino Talarmo
 

Hi Dennis,

 

Have you checked that your rig is actually using COM1 as port number? I don’t remember, whether you told us which rig you are using and how it is connected to your computer for the CAT control. In some rig the COM port driver presents to you two port numbers and you should select the Enhanced one.

 

Just another observation, if your rig support CAT control, then you should use for spilt either Rig or Fake It.

 

73, Reino OH3mA


locked Re: Lost cat (Old problem new to me) #FT8 #Cat_RigControl #WSJTX_config

Dennis Jacobson
 

Finally got a screenshot of what happens when I try to Tune in WSJTX.   Maybe it will help..
Dennis N6NG


locked Re: 2m FT8 Interference. Change frequency #FT8

Roger
 

On 25/06/2021 17:26, Amos Sobel 4X4MF wrote:
We have a non stop interference on the 2m FT8 allocated frequency of 144.174 Mhz. See below. It can spread to Europe and America by   TROPO and Sporadic-E and interfere with your best DX chances on 2m.
Please consider changing the default frequency of FT8 on 2m. There is plenty of space on 2m.
Amos 4X4MF
Other countries will have interference on other 2m frequencies. Moving the default frequency is more than likely to cause problems elsewhere.

Surely a more sensible course of action is to force your administration to deal with it?

73
Roger
G#4HZA


locked Special Frequencies for Field Day 2021? #ContestMode #FT8

Eric Hansen
 

Anyone know where I can find if we're supposed to use special frequencies for FT8 on Field Day? I've only been able to find references to 2019 Field Day frequencies for FT8


locked Re: Where I can download WSJT-X 2.9.x? #wsjt-x #IssueReport

Ron W3RJW
 

On Fri, Jun 25, 2021 at 09:04 AM, Pietro Molina wrote:
Thanks! 
2.9.x means any of the 2.9 releases...
What we are trying to tell you is there are no 2.9.x releases. The current GA release is 2.4.0.  Do you mean 2.3.0 ?
OH2GGC gave you a complete list of releases.
Did you even try what G4WJS suggested ?
 
--
73
Ron  W3RJW

FTdx-5000, Timewave Navigator, WSJT-x Improved 2.5.0 rc1, JTAlert 2.50.2, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Re: 2m FT8 Interference. Change frequency #FT8

 

What’s causing it Amos? It’s definitely a modulated carrier on 144.175 – looking like some form of FM. Is 144-146 an amateur-only allocation in Israel? Though all countries’ military ignore allocations.

Report it to IARU intruder watch.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Amos Sobel 4X4MF
Sent: 25 June 2021 18:30
To: main@WSJTX.groups.io
Subject: [WSJTX] 2m FT8 Interference. Change frequency #FT8 #FT8

 

We have a non stop interference on the 2m FT8 allocated frequency of 144.174 Mhz. See below. It can spread to Europe and America by   TROPO and Sporadic-E and interfere with your best DX chances on 2m.



Please consider changing the default frequency of FT8 on 2m. There is plenty of space on 2m.

Amos 4X4MF

 


--
73 Phil GM3ZZA


locked Re: 2m FT8 Interference. Change frequency #FT8

Buddy Morgan
 

I think 144.174 is pretty well cast in concrete. Here in the United States, we can only work CW, below 144.100. We work Q65 terrestrial, on 144.170. MSK144, on 144.150 and surrounding frequencies. Throw in a few EME skeds and there is not a whole lot of room, left, on 2M. We have been using xxxx.174 MHz, on the bands 2M and higher in frequency, for FT8, for several years, now. Personally, I think it has worked out well.

Buddy WB4OMG EL 98 


locked Re: #WSJTX_config -- USB vs DATA-USB Modes #WSJTX_config

Charles Albert
 

Thanks for the info, Dave.

The numbers and settings look similar, but I'll have to look at them in detail.

I was able to get my FT991A/Linux/FLDIGI/WSJTX system to work. I simply copied the various filter settings from the SSB group to the DATA group, and the "deafness" went away. Made several 600+ mile contacts on FT8 at 6m yesterday with this setup.

I'm very tempted to just leave it alone now, though I am curious why in looking at about a dozen different HOW TO docs there are the same number of "...these are the only settings that will work..." statements. And that includes the docs for both FLDIGI and WSJTX.

Take Care & 73



On Fri, Jun 25, 2021 at 5:25 AM Dave KD2SGM <dfreeswick@...> wrote:
Hi Charles,

I have a Yaesu FTDX 3000 so I’m not sure if these settings will help. I spent a long time searching the internet and it took a while to get it right as everyone seems to have that one little change that makes it all work for them. I use Win4YaesuSuite to control everything so again, this may or may not fix your situation.

FTDX 3000 Menu Settings
#40 CAT RTS - Disable
#65 PC KEYING - Off
#67 DATA MODE - OTHERS
#69 OTHER DSP - 0
#75 DATA IN - USB
#76 DATA MIC GAIN - MCVR
#77 DATA OUT LEVEL - 50
MIC GAIN -20

WSJT-X Settings
Radio - FTDX 3000
Serial Port - COM 10 (COM0COM virtual port)
Baud Rate - 38400 (same as radio)
Data Bits - Default
Stop Bits - Default
Handshake - Default
PTT Method - CAT
Mode - Data/ Pkt
Split - Fake It

Good Luck,
Dave, KD2SGM



locked 2m FT8 Interference. Change frequency #FT8

Amos Sobel 4X4MF
 

We have a non stop interference on the 2m FT8 allocated frequency of 144.174 Mhz. See below. It can spread to Europe and America by   TROPO and Sporadic-E and interfere with your best DX chances on 2m.



Please consider changing the default frequency of FT8 on 2m. There is plenty of space on 2m.

Amos 4X4MF


locked Re: (K)Ubuntu's slow UI response #linux #wsjt-x

Hans Fong
 

Hello Bill,

It's a Kubuntu thing. I installed DragonOS today which is Lubuntu 20.04 and WSJT-X worked fine. When I switched from Lubuntu to Kubuntu with tasksel it slowed down WSJT-X. I played around with LXQT tonight and liked it, so I'll be switching from KDE/Plasme to LXQT. Problem avoided, not solved, but equally happy. Cheers,

Hans

BX2ABT.com

On 6/23/21 5:44 AM, Bill Somerville wrote:
On 22/06/2021 14:16, Hans Fong wrote:
Compiled WSJT-X from the latest source code on a Kubuntu 20.04 machine, connected to my (for me new) TS-2000. Everything works, except for the delay when e.g. double clicking a call in the band activity column, saving a log entry, selecting an audio device, etc. The entire WSJT-X window freezes for at least a couple of seocnds after which operation resumes as normal. Delay times differ from 2 seconds (FT-4) to 7.5 seconds (FT-8), 9.5 seconds (saving a log entry). I don't have the impression that the program stops working, it's just a delay in the UI.

I also tried other versions, like the stock one from the Kubuntu 20.04 (2.1.12), the lastest deb 2.4.0 and some of the beta versions, but they all suffer from the same delay. So I guess it is a (K)Ubuntu thing, but what? The command line doesn't give me any verbose messages.

Any hints or tips welcome. Been searching the web, but it seems no one has this problem, as I haven't been able to find any reference to this phenomenon.
73 de Hans
BX2ABT.com

Hi Hans,

you are the first to report that issue as far as I know. Other than making sure your distribution packages are all up to date I don't have any suggestions.

73
Bill
G4WJS.




--
73 de Hans
BX2ABT.com

9541 - 9560 of 35420