Date   

locked Re: After upgrade to WSJT-X 2.4.0, an IC-7600 no longer changes bands on SPE Expert 1K-FA power amplifier #Cat_RigControl

Frode Igland
 

This regrettably late reply responds to comments by Allan ZS1LS in Digest #2090 on 25 August 2021, and by Bill G4WJS and Mike W9MDB in Digest #2075 on 20 August 2021.

In our club station, we have now made more extensive examinations of the latest versions of WSJT-X and how they work with the IC-7600 and SPE Expert amplifiers.

The setup was:

  • Softwares: WSJT-X 2.3.1, WSJT-X 2.4.0, WSJT-X 2.5.0-rc5;
  • Radio: IC-7600 (firmware 2.0);
  • Amplifiers: SPE Expert 1K-FA and SPE Expert 1.3K-FA both set to “ICOM” Cat control.

The HP computer is connected to the radio via USB A-B cable. The radio is connected to the PA via the CI-V socket on the radio to the DB-15 CAT socket in the amplifier, as well phono plugs from the “Send” and “ALC” sockets on the radio to the “Relay”/”RY1” and “ALC”/”ALC1” sockets on the amplifiers.

First of all, some clarifications/reminders. The amplifiers are always connected to the TX VFO in use. If WSJT-X Settings – Radio – Split is set to “None”, VFO A is used for transmission as well as reception. VFO B is not in use. The same applies to “Fake it”, only VFO A is in use. In “Fake it”, the “split” effect is achieved by VFO A changing frequencies between the TX and RX sequences, if the audio frequency is outside the 1500-2000 Hz sweetspot. Only when Split is set to “Rig” does WSJT-X apply both VFOs, and then VFO A is used for RX only, whilst VFO B is the one used for transmission and thereby is the one to activate the amplifier.

WSJT-X 2.3.1 – All OK

We first tried with WSJT-X 2.3.1. No matter which Split setting we used, the radio and the PA immediately followed all band changes in WSJT-X. This has been our smooth experience for years, until version 2.4.0.

WSJT-X 2.4.0 – Radio VFO B changes band, the PA does not

We then tried with WSJT-X 2.4.0 (the current GA). With Split set to “None” or “Fake it”, VFO A followed the band changes in WSJT-X and the amplifier followed the VFO A. VFO B stayed in the previous band, which was as expected, as for “None” or “Fake it” VFO B is simply not in use.

With Split set to “Rig”, VFO A and VFO B followed the band change in WSJT-X, whilst the amplifier did not and stayed in the previous band, as previously described. As the amplifier follows the TX VFO, i.e. VFO B, it was to be expected that the amplifier changed bands when VFO B changed bands. The question here is: Why has VFO B stopped instructing the amplifier to change bands, or why has the amplifier stopped taking orders from VFO B? 

WSJT-X 2.5.0-rc5 – Neither the Radio VFO B nor the PA changes band

Finally, we tried WSJT-X 2.5.0-rc5, the release candidate at hand when the tests were conducted.

With Split set to “None” or “Fake it”, VFO A changed bands, but the amplifier did not follow. VFO B was unaffected, as expected, as it is not in use in “None” or “Fake it”.

With Split set to “Rig”, VFO A followed the band changes in WSJT-X, whilst VFO B as well as the amplifier stayed in the previous band. As the amplifier follows the TX VFO, i.e. VFO B, it was to be expected that the amplifier did not change when VFO B did not change.

The question now is: Why has WSJT-X stopped instructing VFO B to change bands? This time the PA can not be the one to blame (yet), as the PA does exactly as instructed by VFO B: Stay in the previous band.

CI-V Transceive and CI-V Output (for ANT) ON or OFF have no influence

All the exercises above were systematically conducted with all combinations of the radio’s SET – OTHERS – “CI-V Transceive” and SET – OTHERS – “CI-V Output (to ANT)” toggled between ON and OFF. These two settings made no difference in the results described above.

That it works with “CI-V Transceive” ON as well as OFF seems to be in line with the WSJT-X User Guide, section 16. Frequently Asked Questions, #4:

I occasionally get Rig Control Errors if I adjust my Icom rig’s VFO. What’s wrong?

By default, most Icom transceivers have *CI-V Transceive Mode" enabled. This will cause unsolicited CAT traffic from the rig that disrupts CAT control by a PC. Disable this option in the rig’s menu.

Expert 1.3K-FA and Expert 1K-FA give the same results

We have made the above tests on both our old Expert 1K-FA and our new Expert 1.3K-FA. The results are identical.

TX Audio frequency makes no difference

Trying several TX audio frequencies below, above and in the 1500-2000 Hz audio sweetspot made no difference.

N1MM Logger+ works smoothly with version 2.4.0

In the WW-DIGI Contest, I used the club station with WSJT-X 2.4.0 with N1MM Logger+ running the IC-7600 and the Expert 1.3K-FA. Everything worked smoothly, just like in version 2.3.1. As soon as I tried to operate version 2.4.0 standalone with no other changes made anywhere, the band change issue returned.

Is there any clue in the fact that version 2.4.0 does not change PA bands when operated standalone, whilst it works just fine when controlled by N1MM Logger+?

Summary

In version 2.3.1, everything works smoothly.

In version 2.4.0, VFO-B changes bands as instructed by WSJT-X, but the amplifier does not change bands. Version 2.4.0 works flawlessly when WSJT-X operates under N1MM Logger+.

In version 2.5.0-rc5, VFO B does not even change and then obviously not the amplifier.

The WSJT-X version number is the only identifiable variable that has an influence on the PA band changes.

That is why we think that the non-working PA band changes in WSJT-X 2.4.0 (standalone) and 2.5.0-rc5 have something to do with changes in the later versions of WSJT-X and/or it’s auxiliary CAT software.

73, Frode LA6VQ


locked A Pocket Sized FT Transceiver #decode #FT8 #transmit #Waterfall

Charles Hill
 

To All,

I have published another FT8 Transciever Project called Pocket_FT8 on github at https://github.com/chillmf/Pocket-FT8.

This project uses a Teensy 3.6 to send and receive FT8 messages on 17 meters. All you need to add is an antenna.

Source code and build instructions are included.

Regards,

Charley, W5BAA


locked Re: #IssueReport #WSPR #IssueReport #WSPR

Hasan Schiers N0AN
 

Kenwood TS-590sg, not using internal tuner. Only using the MFJ-998RT in the shack, 1500w autotuner.
Hasan


On Fri, Sep 10, 2021 at 3:29 AM Bill Somerville <g4wjs@...> wrote:
Hi Hasan,

which rig are you using? Are you using an auto-ATU built into your rig?

73
Bill
G4WJS.

On 08/09/2021 21:22, Hasan Schiers N0AN wrote:
Also RC6 here, although downloaded a few days ago. I think there was a hamlib fix since then, but have not downloaded since very early RC6.

73, N0AN
Hasan


On Wed, Sep 8, 2021 at 11:21 AM Bill Somerville <g4wjs@...> wrote:
Hi Hasan,

Steve, K9AN, and I are running WSPR band-hopping with a variety of bands set for Tune and Rx only. Neither of us are seeing this issue so far. I am using the latest 2.5.0 RC6 version.

73
Bill
G4WJS.

On 08/09/2021 15:00, Hasan Schiers N0AN wrote:
No, no errors at all, see an occasional audio stream error, nothing else

Hasan


On Wed, Sep 8, 2021 at 8:20 AM Bill Somerville <g4wjs@...> wrote:
Hi Hasan,

are there any Hamlib error messages in the WJST-X wsjtx_syslog.log file that correlate with the time of the issue?

73
Bill
G4WJS.

On 08/09/2021 01:09, Hasan Schiers N0AN wrote:
Bill,
I found the correlation I was looking for. 

If I tell WSPR Schedule to use the TUNE function (to make the autotuner adjust the antenna SWR on each band prior to transmitting), the ENABLE Tx light goes out in short order (next transmission or so).

If I uncheck the boxes on each band for Tune, and let the transmit signal itself actuate the auto-tuner, everything works normally.  

In reality, the TUNE function in the Scheduler is redundant, because the autotuner itself will auto-tune when RF is sent to it anyway, there is no need to 'pre-tune' things.

However, what I am reporting is undesirable and probably should be fixed, if it's a real malfunction.

73, N0AN
Hasan


On Sat, Sep 4, 2021 at 12:21 PM Bill Somerville <g4wjs@...> wrote:
On 04/09/2021 13:34, Hasan Schiers N0AN wrote:
WSJT-X 2.5.0 RC5
Mode WSPR
 
Issue:
 
When in Band Hopping Mode, with a proper schedule, the Enable Transmit button randomly goes dark and never lights up again.
 
This results in hours and hours of listening overnight with no transmitting. 
 
Is there an order effect or something that would cause this in terms of setup? It used to work perfectly with identical settings many versions ago.
 
Anyone else seen this?
 
TIA, 73, N0AN
Hasan

Hi Hasan,

that behaviour may be caused by a CAT error. Have a look in the wsjtx_syslog.log file (in the WSJT-X log files directory) for any Hamlib error messages around the time that the "Enable Tx" button resets.

73
Bill
G4WJS.






locked Re: JT65 #decode

Bill Somerville
 

On 10/09/2021 03:58, Jim Brown wrote:
On 9/9/2021 6:58 AM, Robert Woltag wrote:
  JT65 mode does not seem to decode anything.

Where are you looking for JT65? It's not a "random QSO" mode like FT8 and FT4, but more of a special purpose weak signal mode like MAP65, JT9, FST4 and Q65, and the newer of those modes, FST4 and Q65, are likely to replace JT65 and JT9.

73, Jim K9YC

Hi Jim,

a minor correction to thee above, MAP65 is not a mode, it is another data communications application designed to take advantage of wide-band I/Q input (it also supports base band audio and UDP data from Linrad) and dual polarization aerial systems. It supports JT65 and Q65-60* modes, and is used for VHF and UHF EME where adaptive polarization can give significant decode sensitivity advantages.

73
Bill
G4WJS.


locked Re: #IssueReport #WSPR #IssueReport #WSPR

Bill Somerville
 

Hi Hasan,

which rig are you using? Are you using an auto-ATU built into your rig?

73
Bill
G4WJS.

On 08/09/2021 21:22, Hasan Schiers N0AN wrote:

Also RC6 here, although downloaded a few days ago. I think there was a hamlib fix since then, but have not downloaded since very early RC6.

73, N0AN
Hasan


On Wed, Sep 8, 2021 at 11:21 AM Bill Somerville <g4wjs@...> wrote:
Hi Hasan,

Steve, K9AN, and I are running WSPR band-hopping with a variety of bands set for Tune and Rx only. Neither of us are seeing this issue so far. I am using the latest 2.5.0 RC6 version.

73
Bill
G4WJS.

On 08/09/2021 15:00, Hasan Schiers N0AN wrote:
No, no errors at all, see an occasional audio stream error, nothing else

Hasan


On Wed, Sep 8, 2021 at 8:20 AM Bill Somerville <g4wjs@...> wrote:
Hi Hasan,

are there any Hamlib error messages in the WJST-X wsjtx_syslog.log file that correlate with the time of the issue?

73
Bill
G4WJS.

On 08/09/2021 01:09, Hasan Schiers N0AN wrote:
Bill,
I found the correlation I was looking for. 

If I tell WSPR Schedule to use the TUNE function (to make the autotuner adjust the antenna SWR on each band prior to transmitting), the ENABLE Tx light goes out in short order (next transmission or so).

If I uncheck the boxes on each band for Tune, and let the transmit signal itself actuate the auto-tuner, everything works normally.  

In reality, the TUNE function in the Scheduler is redundant, because the autotuner itself will auto-tune when RF is sent to it anyway, there is no need to 'pre-tune' things.

However, what I am reporting is undesirable and probably should be fixed, if it's a real malfunction.

73, N0AN
Hasan


On Sat, Sep 4, 2021 at 12:21 PM Bill Somerville <g4wjs@...> wrote:
On 04/09/2021 13:34, Hasan Schiers N0AN wrote:
WSJT-X 2.5.0 RC5
Mode WSPR
 
Issue:
 
When in Band Hopping Mode, with a proper schedule, the Enable Transmit button randomly goes dark and never lights up again.
 
This results in hours and hours of listening overnight with no transmitting. 
 
Is there an order effect or something that would cause this in terms of setup? It used to work perfectly with identical settings many versions ago.
 
Anyone else seen this?
 
TIA, 73, N0AN
Hasan

Hi Hasan,

that behaviour may be caused by a CAT error. Have a look in the wsjtx_syslog.log file (in the WSJT-X log files directory) for any Hamlib error messages around the time that the "Enable Tx" button resets.

73
Bill
G4WJS.



locked Re: "Error in Sound Input" (message box) Circle w/ RED X ---- my WSJT is "BRICKED" #AudioIssues #Windows10 #Elecraft

Alan G4ZFQ
 

*THE FIX IS IN* !!!   I found a Windows privacy setting changed.
Bill,

Yes this has been known for quite a while.
In fact a week ago someone pointed you to a link describing this and showing how to change it.
So far it has not changed on my system.

Glad you are running again.

73 Alan G4ZFQ


locked Re: #txaudio #linux WSJT-X No TX audio issue #txaudio #linux

Steve K4RVA
 

Well, how about this for a coincidence.. I've been futzing around with this for the last two days, and not making any progress. Tonight I received several updates on Linux Mint, which included the kernel and 'alsa-ucm-conf'. I thought I would give it another try and - behold! WSJT-X is now sending audio!

FYI, I have the 'alsa_input...' and 'alsa_output..." audio devices selected in the configuration menu.

Cheers,
Steve K4RVA


locked Re: JT65 #decode

Jim Brown
 

On 9/9/2021 6:58 AM, Robert Woltag wrote:
 JT65 mode does not seem to decode anything.
Where are you looking for JT65? It's not a "random QSO" mode like FT8 and FT4, but more of a special purpose weak signal mode like MAP65, JT9, FST4 and Q65, and the newer of those modes, FST4 and Q65, are likely to replace JT65 and JT9.

73, Jim K9YC


locked Re: JT65 #decode

Lloyd Korb
 

Are you sure you have JT65B selected?

Lloyd  K8DIO

On Thu, Sep 9, 2021 at 5:22 PM Robert Woltag <rwoltag@...> wrote:
Hi, I am running WSJT-X v2.4.0.  FT8, FT4 etc seem to decode and transmit fine.  JT65 mode does not seem to decode anything.  Any suggestions?  Thanks Rob W1AFP



locked Re: Font too big #IssueReport

Chuck Freeman
 

Thanks Bill I will give it a shot!


locked Re: "Error in Sound Input" (message box) Circle w/ RED X ---- my WSJT is "BRICKED" #AudioIssues #Windows10 #Elecraft

Bill
 
Edited

RESOLVED: Microsoft  in   their quest for an infinitely configurable machine decided to allow users to mute the microphone on any and ail apps, those designed, and those yet to be designed like WSJT-X,  They grouped LINE IN as a MICROPHONE  under a single mute button.  So, if suddenly your green monitor bar quits showing signal, it could have been muted in the following settings: SYSTEM | PRIVACY | MICROPHONE


locked Re: "Error in Sound Input" (message box) Circle w/ RED X ---- my WSJT is "BRICKED" #AudioIssues #Windows10 #Elecraft

Bill
 

On Thu, Sep 9, 2021 at 02:11 AM, <bill333@...> wrote:
Microsoft in their quest for an infinitely configurable machine decided to allow users to mute the microphone on any and ail apps, those designed, and those yet to be designed like WSJT-X,  They groped LINE IN as a MICROPHONE  under a single mute button.  So, if suddenly your green monitor bar quits showing signal, it could have been muted in the following settings: SYSTEM | PRIVACY | MICROPHONE


locked Re: Font too big #IssueReport

Bill Somerville
 

On 09/09/2021 20:27, Chuck Freeman via groups.io wrote:
I installed Wsjtx on my laptop. I changed the font size in the settings menu but now the font is so big that I am not able to go back to the settings menu to change the font size and click on the OK button. The OK button is not visible. I tried thg o uninstall wsjtx and reinstalled the program but the font size stayed the same large size. Anyone have any ideas?

Hi Chuck,

the OK button should be the default button, hitting ENTER should accept the changes. Otherwise you can edit the WSJT-X.ini file and remove the lines starting:

Font=

and

DecodedTextFont=

73
Bill
G4WJS.


locked Font too big #IssueReport

Chuck Freeman
 

I installed Wsjtx on my laptop. I changed the font size in the settings menu but now the font is so big that I am not able to go back to the settings menu to change the font size and click on the OK button. The OK button is not visible. I tried thg o uninstall wsjtx and reinstalled the program but the font size stayed the same large size. Anyone have any ideas?


locked Re: #txaudio #linux WSJT-X No TX audio issue #txaudio #linux

Steve K4RVA
 

Sorry, I don't mean to hijack your thread, but I am having the same (or similar) issue.

I installed wsjtx_2.4.0_amd64.deb on a very fresh install of Linux Mint 20.2 Cinnamon on a laptop with integrated audio. Audio input and FT8 decoding works fine. CAT control (Kenwood TS-570D) and PTT via CAT are working.

But when I click either 'Tune' or 'Enable TX', the button will turn red but I do not get any audio out, and the 'wsjtx' process goes straight to 100% CPU utilization. At this point, the waterfall freezes, the audio input level meter goes blank (the green vertical bar disappears), and new decoded messages no longer appear in the Band Activity window. The interface stills responds, ie. I can open any menu items, click the Tune button, but the application is no longer functioning.

When I close WSJT-X (either by clicking the 'X' or via File->Exit), the application windows go away but the 'wsjtx' process is still running at 100% CPU. I can kill it easily with a Ctrl-C from the terminal where I started it, or with a SIGTERM from inside 'top'.

I tried installing it on a different PC, also with Linux Mint 20.2, also with integrated/on-board audio and I got the exact same results.
I tried selecting several of the various audio output devices on both PCs (default, jack, oss, pulse, front, and several others with long cryptic names) and I got the same results.
I looked through ~/.local/share/WSJT-X/*.log and /var/log/syslog, but nothing was immediately apparent. Not exactly sure what to look for, though.
Fldigi outputs audio on both PCs.
It looks like pulseaudio is the audio server being used, but I don't know which other ones to look for in case there is a conflict or something.

Does anyone have any suggestion on where to look next? Is anyone else running 2.4.0 on Linux Mint (or another Ubuntu/Debian variety) successfully?

Cheers,
Steve K4RVA


locked Re: AO-100 Sat #IssueReport #FT8

Carlos
 

Hi to all,

Fortunately is this not my signal, but I heard this wave issue today and also sometimes ago on the satellite AO-100 in the mode FT8.

It sounds like RTTY. I enclose the wav file.

Some weeks ago I also asked for this strange issue, but didn't get any answer yet

Please give me any ideas.

Thanks a lot , Karl OE3JAG
My rig is: raspberry, buster; wsjtx 2.4.0, FT847, DXpatrol Up- and Down-converter, 1m dish


Robert Woltag
 

Hi, I am running WSJT-X v2.4.0.  FT8, FT4 etc seem to decode and transmit fine.  JT65 mode does not seem to decode anything.  Any suggestions?  Thanks Rob W1AFP


locked Re: WSJT-X shuts down unexpectedly (Raspberry Pi Raspian OS) #wsjt-x-crashing

Heikki Pisilä
 

i think you could start from this v2.3.0 installation works 100% when you follow the instructions.

https://photobyte.org/raspberry-pi-update-to-wsjt-x-2-3-0/

73

Heikki/oh8gkp



Bill Somerville9.9.2021 klo 20:14:

On 09/09/2021 18:00, S Johnson wrote:
Is there a bug repository where I can file this for (hamlib/wsjtx) developers? I can also offer to test any potential code fix on my Pi to help develop a solution.

OM,

have you tried the WSJT-X v2.5.0 RC6 release?

73
Bill
G4WJS.





locked Re: WSJT-X shuts down unexpectedly (Raspberry Pi Raspian OS) #wsjt-x-crashing

Bill Somerville
 

On 09/09/2021 18:00, S Johnson wrote:
Is there a bug repository where I can file this for (hamlib/wsjtx) developers? I can also offer to test any potential code fix on my Pi to help develop a solution.
OM,

have you tried the WSJT-X v2.5.0 RC6 release?

73
Bill
G4WJS.


locked Re: WSJT-X shuts down unexpectedly (Raspberry Pi Raspian OS) #wsjt-x-crashing

Steve Johnson
 

Is there a bug repository where I can file this for (hamlib/wsjtx) developers? I can also offer to test any potential code fix on my Pi to help develop a solution. 

11661 - 11680 of 40041