wsjt-devel — WSJT software development

Re: [wsjt-devel] Superfox MacOS

[Gary R. <cga...@gm...>]

I am decoding them on 10 right now with Mac M2 and OS 15.7.1 WSJT-X improved AL plus

> On Oct 18, 2025, at 1:49 PM, John Stengrevics via wsjt-devel <wsj...@li...> wrote:
> 
> Probably something specific to your situation.  I worked PJ6Y on 10m super fox this morning.  Running a MacBook Pro with M3 Max chip and Tahoe 26.0.1 operating system.
> 
> 73,
> 
> John
> WA1EAZ
> 
>> On Oct 18, 2025, at 1:40 PM, Michael Morgan via wsjt-devel <wsj...@li...> wrote:
>> 
>> I was just trying to decode and work 5K0UA on 10M using super fox and on my Mac it would never decode them.  I switched to my windows pc and it decoded fine and I was able to work them.  My time was good on my Mac.  I don’t typically use my windows machine but one I got the time synced on it, the decodes started working right away.  I am using WSJ-X Improved 250924 on both.  On my Mac I am using the M1 build.  I did also try the standard WSJT build as as well.  Not sure if it is just my situation or something may be up with the Mac builds of super fox.  All other functions work fine.  Here’s a screenshot showing both running.  I did grab an audio file but not sure that is necessary since it works fine on the Windows side.  
>> 
>> 73’s
>> 
>> Michael, AA5SH
>> 
>> https://www.aa5sh.com/pics/wsjt-sf.png_______________________________________________
>> wsjt-devel mailing list
>> wsj...@li...
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Superfox MacOS

[John S. <jst...@co...>]

Probably something specific to your situation.  I worked PJ6Y on 10m super fox this morning.  Running a MacBook Pro with M3 Max chip and Tahoe 26.0.1 operating system.

73,

John
WA1EAZ

> On Oct 18, 2025, at 1:40 PM, Michael Morgan via wsjt-devel <wsj...@li...> wrote:
> 
> I was just trying to decode and work 5K0UA on 10M using super fox and on my Mac it would never decode them.  I switched to my windows pc and it decoded fine and I was able to work them.  My time was good on my Mac.  I don’t typically use my windows machine but one I got the time synced on it, the decodes started working right away.  I am using WSJ-X Improved 250924 on both.  On my Mac I am using the M1 build.  I did also try the standard WSJT build as as well.  Not sure if it is just my situation or something may be up with the Mac builds of super fox.  All other functions work fine.  Here’s a screenshot showing both running.  I did grab an audio file but not sure that is necessary since it works fine on the Windows side.  
> 
> 73’s
> 
> Michael, AA5SH
> 
> https://www.aa5sh.com/pics/wsjt-sf.png_______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Superfox MacOS

[Michael M. <cmo...@gm...>]

I was just trying to decode and work 5K0UA on 10M using super fox and on my Mac it would never decode them.  I switched to my windows pc and it decoded fine and I was able to work them.  My time was good on my Mac.  I don’t typically use my windows machine but one I got the time synced on it, the decodes started working right away.  I am using WSJ-X Improved 250924 on both.  On my Mac I am using the M1 build.  I did also try the standard WSJT build as as well.  Not sure if it is just my situation or something may be up with the Mac builds of super fox.  All other functions work fine.  Here’s a screenshot showing both running.  I did grab an audio file but not sure that is necessary since it works fine on the Windows side.  

73’s

Michael, AA5SH

https://www.aa5sh.com/pics/wsjt-sf.png
wsjt-sf
PNG Image · 4.5 MB

Re: [wsjt-devel] Enforcing WSJT-X split mode

[John K. <joh...@gm...>]

Andy,

You know, I spent a fair amount of time as junior faculty working with
medical students and first year residents.  Things that were well known to
me were brand new to them and so at the start of every rotation I had to
lay out the basics all over again.  It wasn't a case of  stupidity or  bad
intent on their part.  There were just things they didn't know.  The good
news is the WSJT-X suite is a very popular application that gains more and
more users every week.  It isn't that they are not intelligent, it was just
that they didn't know or understand. In a different setting, a friend not
too long ago got chided for not doing something quite right.  Her
supervisor noted, "Well it was in a memo I sent around in 2023."
Problem was my friends started in 2024.. My point is some of the basics
need to be repeated over and over again.  So, yes, you could make rig split
or fake it mandatory.  But users might not know why it is mandatory.  Maybe
more importantly they understand the importance of a clean signal and the
role that rig  split/fake it plays  as a backup in case they get it wrong.

I am going to sign off for now.  Andy, it's a hobby and I think we should
always assume positive intent.

Peace,

John

On Mon, Oct 13, 2025 at 3:07 PM Andy Durbin via wsjt-devel <
wsj...@li...> wrote:

> "And unless I have a really good reason, I never go below 1500 Hz."
>
> Well, since you use split, you are imposing a meaningless and unnecessary
> restriction on your operating.  The requirement is not to never operate
> below DF 1500 Hz.  The requirement is not to use a modulation frequency
> below 1,500 Hz.
>
> If WSJT-X is controlling the rig correctly you cannot have a modulation
> frequency less that 1.500 Hz at any TX DF when split is in use.
>
> Andy, k3wyc
>
>
>
>
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Enforcing WSJT-X split mode

[Andy D. <a.d...@ms...>]

"And unless I have a really good reason, I never go below 1500 Hz."

Well, since you use split, you are imposing a meaningless and unnecessary restriction on your operating.  The requirement is not to never operate below DF 1500 Hz.  The requirement is not to use a modulation frequency below 1,500 Hz.

If WSJT-X is controlling the rig correctly you cannot have a modulation frequency less that 1.500 Hz at any TX DF when split is in use.

Andy, k3wyc

Re: [wsjt-devel] Hamlib new version fails on YAESU FT-100 VFO handling

[Marco C. <PY...@ou...>]

Well,

Since my issue persists and apparently nobody provided answers, I 
abandoned Hamlib NET option and I switched to Rig=YAESU FT-100: this is 
working under every situation!

73 de Marco, PY1ZRJ



Il 13/10/25 09:55, Marco Calistri via wsjt-devel ha scritto:
> *WRONG!
> *
> The issue is till present also in the new Hamlib!
>
> I need to manually switch off  the split operation in my FT-100, then 
> click again on the new band, otherwise VFOB keeps using the previous band!
>
> I use mode Rig in my WSJTX Radio Settings.
>
> Very dumb issue which was not present on the older Hamlib!
>
> Sorry for the wrong announcement!
>
> Regards!
>
> Marco, PY1ZRJ
>
> Il 13/10/25 08:19, Marco Calistri ha scritto:
>> Hello!
>>
>> Updating to
>>
>> *rigctld Hamlib 4.7~git 2025-10-10T14:52:54Z SHA=23710cf2d 64-bit*
>>
>> Has resolved the issue I spoken about in my previous message.
>>
>> So far, so good!
>>
>> Thanks,
>>
>>
>> ---
>> *73 de Marco, PY1ZRJ (former IK5BCU)*
>> **
>>
>>
>>
>> Il 30/09/25 11:57, Marco Calistri ha scritto:
>>> Hello,
>>>
>>> Hope someone of the Hamlib group being sneaking here.
>>>
>>> So far my rigctld command to drive my YAESU FT-100 CAT port has 
>>> worked flawlessly:
>>>
>>> /usr/local/bin/rigctld -m 1021 -r /dev/FT-100_USB1 -t 4532 -s 4800 
>>> *--vfo* &
>>>
>>> This by using older Hamlib version:
>>> rigctld --version: rigctld Hamlib 4.6~git 2023-07-20T21:59:57Z 
>>> SHA=aacf06 64-bit
>>>
>>> Now, using the new Hamlib version:
>>>
>>> rigctld --version: rigctld Hamlib 4.7~git 2025-09-27T16:16:32Z 
>>> SHA=0d122f6b1 64-bit
>>>
>>> One of the VFO stays on previous frequency when I switch band.
>>>
>>> For example: I start working on 10 meters band then VFOA tunes on 
>>> 28.074 and VFOB tunes on the same frequency minus or plus the audio 
>>> shift.
>>>
>>> When I switch band, for example to 17 meters, VFOA sets on 18.100, 
>>> whereas VFOB stays on 28.074!
>>>
>>> This is a really annoying behavior!
>>>
>>> I tried also without adding the *--vfo* parameter at rigctld without 
>>> success and obtaining a worst and slower switching from TX to RX.
>>>
>>> Thanks for any inputs you could provide.
>>>
>>> Marco, PY1ZRJ
>>> ---
>>> *73 de Marco, PY1ZRJ (former IK5BCU)*
>>> **
>>
>>
>
>
> ---
> *73 de Marco, PY1ZRJ (former IK5BCU)*
> **
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**

Re: [wsjt-devel] Enforcing WSJT-X split mode

[John K. <joh...@gm...>]

Andy,

Yes , indeed.  As we dig to the weeds on Rig Split versus Fake It and how
you know my only point was it is worth remembering why we got into this
discussion.   I must have read your paper or heard the talk because I have
from day one I have used Fake It.   And unless I have a really good reason,
I never go below 1500 Hz.

Point taken......"When you are up to your rear end in alligators it is
worth remembering why you got into the swamp!"

Cheers!

John

On Mon, Oct 13, 2025 at 1:46 PM Andy Durbin via wsjt-devel <
wsj...@li...> wrote:

> "I thought this all started with an observation that some people hit it
> way too hard and generate unwanted harmonics.  I have always thought the
> "cure" for that was to turn down the audio feed.  It is not clear to me how
> using rig split or Fake It solves that problem."
>
> When WSJT-X split mode is used the modulation frequency is always in the
> range 1,500 - 2,000 Hz.  The lowest frequency of the second harmonic is
> 3,000 Hz which is outside the TX passband of most transceivers.
>
> When WSJT-X split mode is not used the lowest modulating frequency is 200
> Hz. The harmonics of 200 Hz contaminate the normal WSJT-X operating
> frequency range.
>
> It is simply not possible to foul up the band with audio harmonics if
> split mode is used.  There is no protection against fouling the band if
> split mode is not used and transmission are made at the low end of the DF
> range.
>
> This is not new knowledge.  Long before WSJT-X was popular JT65 HF
> operating instructions cautioned against transmitting in the low DF range.
>
> Sure, if every operator set up their station to be free of audio
> harmonics, there would be no need for split mode.  You only have to look at
> the FT8 frequencies on any day of the week to know that isn't going to
> happen.
>
> I wrote a paper on this topic years ago.  It was intended for club use but
> I'll share it here - https://tinyurl.com/2err7nsz
>
> 73,
> Andy, k3wyc
>
>
>
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Enforcing WSJT-X split mode

[Andy D. <a.d...@ms...>]

"I thought this all started with an observation that some people hit it way too hard and generate unwanted harmonics.  I have always thought the "cure" for that was to turn down the audio feed.  It is not clear to me how using rig split or Fake It solves that problem."

When WSJT-X split mode is used the modulation frequency is always in the range 1,500 - 2,000 Hz.  The lowest frequency of the second harmonic is 3,000 Hz which is outside the TX passband of most transceivers.

When WSJT-X split mode is not used the lowest modulating frequency is 200 Hz. The harmonics of 200 Hz contaminate the normal WSJT-X operating frequency range.

It is simply not possible to foul up the band with audio harmonics if split mode is used.  There is no protection against fouling the band if split mode is not used and transmission are made at the low end of the DF range.

This is not new knowledge.  Long before WSJT-X was popular JT65 HF operating instructions cautioned against transmitting in the low DF range.

Sure, if every operator set up their station to be free of audio harmonics, there would be no need for split mode.  You only have to look at the FT8 frequencies on any day of the week to know that isn't going to happen.

I wrote a paper on this topic years ago.  It was intended for club use but I'll share it here - https://tinyurl.com/2err7nsz

73,
Andy, k3wyc

Re: [wsjt-devel] Enforcing WSJT-X split mode

[John K. <joh...@gm...>]

Lance,

Yes, as I said I recall that as the reason to stay above 1500 Hz.  I just
don't see how rig split or fake it solves the problem.  Or is it that
regardless of your DF, either of those modes *always* places you above 1500
Hz?

John

On Mon, Oct 13, 2025 at 12:45 PM Lance Collister, W7GJ via wsjt-devel <
wsj...@li...> wrote:

> Hi John,
>
> It IS important not to overdrive your audio stage, but that is not the
> biggest issue.
> The problem arises if the audio signals actually transmitted by the
> computer are
> under 1500 Hz...in that case, the audio harmonics can be passed through
> the filter in
> the transmitter and broadcast all across the spectrum.
>
> Before he passed away, W9MDB explained this on his website:
>
>
> https://www.dropbox.com/scl/fi/avq8nt3higd3evutjssv4/FT8Noise8.pdf?rlkey=xgfxw0bmtdik23h1psu7khz38&e=1&dl=0
>
> GL and VY 73, Lance
>
> On 10/13/2025 18:50:14, John Kludt via wsjt-devel wrote:
> > Guys,
> >
> > I thought this all started with an observation that some people hit it
> way too hard
> > and generate unwanted harmonics.  I have always thought the "cure" for
> that was to
> > turn down the audio feed.  It is not clear to me how using rig split or
> Fake It
> > solves that problem.  I always use Fake it - have for literally years.
> I thought
> > either method ,Rig Split or Fake It, was about keeping your signal more
> or less in
> > the center of the bandpass.   I do recall advice somewhere to run higher
> in the
> > bandpass rather than lower in the bandpass to move unwanted signals out
> of the
> > bandpass - is that why you all are discussing Fake It versus Rig Split?
> Isn't the
> > better answer to make sure you have a clean signal and in some cases
> maybe turn
> > down the power just a little bit?
> >
> > Just curious what I am missing.
> >
> > John K7SYS
> >
> > On Sun, Oct 12, 2025 at 11:57 PM Reino Talarmo via wsjt-devel
> > <wsj...@li...> wrote:
> >
> >     Hi Andy,
> >
> >     Your statement ‘Testing fake-it requires a transmission but rig
> split does
> >     not.’ without additional information makes no sense to me. Do you
> mean how an
> >     operator can see that he is transmitting at correct radio frequency?
> Most
> >     radios indicate the used VFO frequency, when commanded for
> transmission. In the
> >     fake-it operation the RX VFO (A) frequency changes and in the rig the
> >     transmission uses the TX VFO (B). For an indication both require a
> rig
> >     transmission activation.
> >
> >     If the Tune button is used for the activation, then there is output
> power in
> >     both cases. If the Test Cat button or the Test PTT button is used,
> then no
> >     audio will be transmitted, and no RF output will be sent. (If PTT
> method VOX is
> >     used, then the Test PTT don’t work and only the Tune button can be
> used.)
> >
> >     The change of the audio frequency is not presented to the user.
> >
> >     It would be much easier to help in the rig split operation, if at
> least you
> >     tell us the rig type and how CAT control is arranged.
> >
> >     73, Reino OH3mA
> >
> >     *From:*Andy Durbin via wsjt-devel <wsj...@li...>
> >     *Sent:* Monday, October 13, 2025 12:24 AM
> >     *To:* WSJT software development <wsj...@li...>
> >     *Cc:* Andy Durbin <a.d...@ms...>
> >     *Subject:* Re: [wsjt-devel] Enforcing WSJT-X split mode
> >
> >     "I provided a signal report with screen shots to one offending
> station and he
> >     improved his signal with audio drive adjustment.  He stated he was
> using rig
> >     split."
> >
> >     Correction - He stated he was using fake-it.  Testing fake-it
> requires a
> >     transmission but rig split does not.
> >
> >     Andy, k3wyc
> >
> >     _______________________________________________
> >     wsjt-devel mailing list
> >     wsj...@li...
> >     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
> >
> >
> > _______________________________________________
> > wsjt-devel mailing list
> > wsj...@li...
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> --
> Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX,
> 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ,
> S79GJ, FO/W7GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ)
> P.O. Box 73
> Frenchtown, MT   59834-0073
> USA
> TEL: (406) 626-5728
> QTH: DN27ub
> URL: http://www.bigskyspaces.com/w7gj
> Skype: lanceW7GJ
> 2m DXCC #11 - 6m DXCC #815 - FFMA #7
>
> Interested in 6m EME?  Ask me about subscribing to the new Magic Band EME
> email group, or just fill in the request box at the bottom of my web
> page (above)!
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Enforcing WSJT-X split mode

[Lance C. W. <w7...@bi...>]

Hi John,

It IS important not to overdrive your audio stage, but that is not the biggest issue. 
The problem arises if the audio signals actually transmitted by the computer are 
under 1500 Hz...in that case, the audio harmonics can be passed through the filter in 
the transmitter and broadcast all across the spectrum.

Before he passed away, W9MDB explained this on his website:

https://www.dropbox.com/scl/fi/avq8nt3higd3evutjssv4/FT8Noise8.pdf?rlkey=xgfxw0bmtdik23h1psu7khz38&e=1&dl=0

GL and VY 73, Lance

On 10/13/2025 18:50:14, John Kludt via wsjt-devel wrote:
> Guys,
>
> I thought this all started with an observation that some people hit it way too hard 
> and generate unwanted harmonics.  I have always thought the "cure" for that was to 
> turn down the audio feed.  It is not clear to me how using rig split or Fake It 
> solves that problem.  I always use Fake it - have for literally years.  I thought 
> either method ,Rig Split or Fake It, was about keeping your signal more or less in 
> the center of the bandpass.   I do recall advice somewhere to run higher in the 
> bandpass rather than lower in the bandpass to move unwanted signals out of the 
> bandpass - is that why you all are discussing Fake It versus Rig Split?  Isn't the 
> better answer to make sure you have a clean signal and in some cases maybe turn 
> down the power just a little bit?
>
> Just curious what I am missing.
>
> John K7SYS
>
> On Sun, Oct 12, 2025 at 11:57 PM Reino Talarmo via wsjt-devel 
> <wsj...@li...> wrote:
>
>     Hi Andy,
>
>     Your statement ‘Testing fake-it requires a transmission but rig split does
>     not.’ without additional information makes no sense to me. Do you mean how an
>     operator can see that he is transmitting at correct radio frequency? Most
>     radios indicate the used VFO frequency, when commanded for transmission. In the
>     fake-it operation the RX VFO (A) frequency changes and in the rig the
>     transmission uses the TX VFO (B). For an indication both require a rig
>     transmission activation.
>
>     If the Tune button is used for the activation, then there is output power in
>     both cases. If the Test Cat button or the Test PTT button is used, then no
>     audio will be transmitted, and no RF output will be sent. (If PTT method VOX is
>     used, then the Test PTT don’t work and only the Tune button can be used.)
>
>     The change of the audio frequency is not presented to the user.
>
>     It would be much easier to help in the rig split operation, if at least you
>     tell us the rig type and how CAT control is arranged.
>
>     73, Reino OH3mA
>
>     *From:*Andy Durbin via wsjt-devel <wsj...@li...>
>     *Sent:* Monday, October 13, 2025 12:24 AM
>     *To:* WSJT software development <wsj...@li...>
>     *Cc:* Andy Durbin <a.d...@ms...>
>     *Subject:* Re: [wsjt-devel] Enforcing WSJT-X split mode
>
>     "I provided a signal report with screen shots to one offending station and he
>     improved his signal with audio drive adjustment.  He stated he was using rig
>     split."
>
>     Correction - He stated he was using fake-it.  Testing fake-it requires a
>     transmission but rig split does not.
>
>     Andy, k3wyc
>
>     _______________________________________________
>     wsjt-devel mailing list
>     wsj...@li...
>     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

-- 
Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, FO/W7GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ)
P.O. Box 73
Frenchtown, MT   59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7

Interested in 6m EME?  Ask me about subscribing to the new Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!

Re: [wsjt-devel] Enforcing WSJT-X split mode

[John K. <joh...@gm...>]

Guys,

I thought this all started with an observation that some people hit it way
too hard and generate unwanted harmonics.  I have always thought the "cure"
for that was to turn down the audio feed.  It is not clear to me how using
rig split or Fake It solves that problem.  I always use Fake it - have for
literally years.  I thought either method ,Rig Split or Fake It, was about
keeping your signal more or less in the center of the bandpass.   I do
recall advice somewhere to run higher in the bandpass rather than lower in
the bandpass to move unwanted signals out of the bandpass - is that why you
all are discussing Fake It versus Rig Split?  Isn't the better answer to
make sure you have a clean signal and in some cases maybe turn down the
power just a little bit?

Just curious what I am missing.

John K7SYS

On Sun, Oct 12, 2025 at 11:57 PM Reino Talarmo via wsjt-devel <
wsj...@li...> wrote:

> Hi Andy,
>
> Your statement ‘Testing fake-it requires a transmission but rig split does
> not.’ without additional information makes no sense to me. Do you mean how
> an operator can see that he is transmitting at correct radio frequency?
> Most radios indicate the used VFO frequency, when commanded for
> transmission. In the fake-it operation the RX VFO (A) frequency changes and
> in the rig the transmission uses the TX VFO (B). For an indication both
> require a rig transmission activation.
>
> If the Tune button is used for the activation, then there is output power
> in both cases. If the Test Cat button or the Test PTT button is used, then
> no audio will be transmitted, and no RF output will be sent. (If PTT method
> VOX is used, then the Test PTT don’t work and only the Tune button can be
> used.)
>
>
>
> The change of the audio frequency is not presented to the user.
>
>
>
> It would be much easier to help in the rig split operation, if at least
> you tell us the rig type and how CAT control is arranged.
>
>
>
> 73, Reino OH3mA
>
>
>
> *From:* Andy Durbin via wsjt-devel <wsj...@li...>
> *Sent:* Monday, October 13, 2025 12:24 AM
> *To:* WSJT software development <wsj...@li...>
> *Cc:* Andy Durbin <a.d...@ms...>
> *Subject:* Re: [wsjt-devel] Enforcing WSJT-X split mode
>
>
>
> "I provided a signal report with screen shots to one offending station and
> he improved his signal with audio drive adjustment.  He stated he was using
> rig split."
>
>
>
> Correction - He stated he was using fake-it.  Testing fake-it requires a
> transmission but rig split does not.
>
>
>
> Andy, k3wyc
>
>
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Enforcing WSJT-X split mode

[Reino T. <rei...@ko...>]

Hi Andy,

 

Yes, thanks for pointing the real time indication in the
case of the Rig split operation. 

 

73, Reino OH3mA

 

From: Andy Durbin via wsjt-devel
<wsj...@li...> 
Sent: Monday, October 13, 2025 5:22 PM
To: WSJT software development
<wsj...@li...>
Cc: Andy Durbin <a.d...@ms...>
Subject: Re: [wsjt-devel] Enforcing WSJT-X split mode

 

"In the fake-it operation the X VFO (A) frequency
changes and in the rig the transmission uses the TX VFO
(B). For an indication both require a rig transmission
activation."

 

My TS-590S simultaneously displays VFO A and VFO B.  I
operate in rig split and there is no transmission
required to see the TX VFO frequency change when I move
the TX frequency cursor.

 

No all rigs work the same and some are more capable than
others.

 

73,

Andy, k3wyc

 

 

 

 

 

[wsjt-devel] decoder.f90 executable stack

[Jaroslav Š. <jsk...@re...>]

Hi,

linux distros are trying to harden with the noexecstack and the
execstack in decoder.f90 is causing problems. E.g. [1], [2]. It seems
the g++ linker doesn't allow combination of binaries with exec/noexec
stacks [1], so the whole binary needs to be compiled with the
execstack which may be unacceptable for some distros. The patch
proposed in [1] uses mprotect, should something similar be upstreamed?

Build failure of wsjtx-2.7.0 with the gcc-c++-15.2.1 in Fedora rawhide:
[81%] Building Fortran object
qmap/libqmap/CMakeFiles/qmap_impl.dir/f77_wisdom.f.o
cd /builddir/build/BUILD/wsjtx-2.7.0-build/wsjtx-2.7.0/wsjtx/redhat-linux-build/qmap/libqmap
&& /usr/bin/gfortran -DBIGSYM=1 -DBOOST_ALL_DYN_LINK
-DBOOST_ATOMIC_DYN_LINK -DBOOST_ATOMIC_NO_LIB -DBOOST_CHRONO_DYN_LINK
-DBOOST_CHRONO_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK
-DBOOST_FILESYSTEM_NO_LIB -DBOOST_LOG_DYN_LINK -DBOOST_LOG_NO_LIB
-DBOOST_LOG_SETUP_DYN_LINK -DBOOST_LOG_SETUP_NO_LIB
-DBOOST_REGEX_DYN_LINK -DBOOST_REGEX_NO_LIB -DBOOST_THREAD_DYN_LINK
-DBOOST_THREAD_NO_LIB -DCMAKE_BUILD -DFOX_OTP -DQT5 -DQT_CORE_LIB
-DQT_NO_DEBUG -DUNIX
-I/builddir/build/BUILD/wsjtx-2.7.0-build/wsjtx-2.7.0/wsjtx/redhat-linux-build/qmap/libqmap
-I/builddir/build/BUILD/wsjtx-2.7.0-build/wsjtx-2.7.0/wsjtx/qmap/libqmap
-I/builddir/build/BUILD/wsjtx-2.7.0-build/wsjtx-2.7.0/wsjtx/redhat-linux-build/qmap/libqmap/qmap_impl_autogen/include
-I/builddir/build/BUILD/wsjtx-2.7.0-build/wsjtx-2.7.0/wsjtx/redhat-linux-build
-I/usr/include -I/usr/include/qt5 -I/usr/include/qt5/QtCore
-I/usr/lib64/qt5/mkspecs/linux-g++ -O2  -fexceptions -g
-grecord-gcc-switches -pipe -Wall
-Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1
 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables
-fstack-clash-protection -fcf-protection -mtls-dialect=gnu2
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/lib64/gfortran/modules -DNDEBUG -fbounds-check
-funroll-all-loops -fno-f2c
-ffpe-summary=invalid,zero,overflow,underflow -Wall -Wno-conversion
-fno-second-underscore -fvisibility=hidden -fPIC -c
/builddir/build/BUILD/wsjtx-2.7.0-build/wsjtx-2.7.0/wsjtx/qmap/libqmap/f77_wisdom.f
-o CMakeFiles/qmap_impl.dir/f77_wisdom.f.o
[ 81%] Linking CXX executable ldpcsim240_74
/usr/bin/cmake -E cmake_link_script
CMakeFiles/ldpcsim240_74.dir/link.txt --verbose=1
/usr/bin/ld: error: decoder.f90.o: is triggering the generation of an
executable stack (because it has an executable .note.GNU-stack
section)
/usr/bin/ld: failed to set dynamic section sizes: no error
collect2: error: ld returned 1 exit status

thanks & regards

Jaroslav

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278939
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2385733

Re: [wsjt-devel] Enforcing WSJT-X split mode

[Andy D. <a.d...@ms...>]

"In the fake-it operation the X VFO (A) frequency changes and in the rig the transmission uses the TX VFO (B). For an indication both require a rig transmission activation."

My TS-590S simultaneously displays VFO A and VFO B.  I operate in rig split and there is no transmission required to see the TX VFO frequency change when I move the TX frequency cursor.

No all rigs work the same and some are more capable than others.

73,
Andy, k3wyc

Re: [wsjt-devel] Hamlib new version fails on YAESU FT-100 VFO handling

[Marco C. <PY...@ou...>]

*WRONG!
*
The issue is till present also in the new Hamlib!

I need to manually switch off  the split operation in my FT-100, then 
click again on the new band, otherwise VFOB keeps using the previous band!

I use mode Rig in my WSJTX Radio Settings.

Very dumb issue which was not present on the older Hamlib!

Sorry for the wrong announcement!

Regards!

Marco, PY1ZRJ

Il 13/10/25 08:19, Marco Calistri ha scritto:
> Hello!
>
> Updating to
>
> *rigctld Hamlib 4.7~git 2025-10-10T14:52:54Z SHA=23710cf2d 64-bit*
>
> Has resolved the issue I spoken about in my previous message.
>
> So far, so good!
>
> Thanks,
>
>
> ---
> *73 de Marco, PY1ZRJ (former IK5BCU)*
> **
>
>
>
> Il 30/09/25 11:57, Marco Calistri ha scritto:
>> Hello,
>>
>> Hope someone of the Hamlib group being sneaking here.
>>
>> So far my rigctld command to drive my YAESU FT-100 CAT port has 
>> worked flawlessly:
>>
>> /usr/local/bin/rigctld -m 1021 -r /dev/FT-100_USB1 -t 4532 -s 4800 
>> *--vfo* &
>>
>> This by using older Hamlib version:
>> rigctld --version: rigctld Hamlib 4.6~git 2023-07-20T21:59:57Z 
>> SHA=aacf06 64-bit
>>
>> Now, using the new Hamlib version:
>>
>> rigctld --version: rigctld Hamlib 4.7~git 2025-09-27T16:16:32Z 
>> SHA=0d122f6b1 64-bit
>>
>> One of the VFO stays on previous frequency when I switch band.
>>
>> For example: I start working on 10 meters band then VFOA tunes on 
>> 28.074 and VFOB tunes on the same frequency minus or plus the audio 
>> shift.
>>
>> When I switch band, for example to 17 meters, VFOA sets on 18.100, 
>> whereas VFOB stays on 28.074!
>>
>> This is a really annoying behavior!
>>
>> I tried also without adding the *--vfo* parameter at rigctld without 
>> success and obtaining a worst and slower switching from TX to RX.
>>
>> Thanks for any inputs you could provide.
>>
>> Marco, PY1ZRJ
>> ---
>> *73 de Marco, PY1ZRJ (former IK5BCU)*
>> **
>
>


---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**

Re: [wsjt-devel] Hamlib new version fails on YAESU FT-100 VFO handling

[Marco C. <PY...@ou...>]

Hello!

Updating to

*rigctld Hamlib 4.7~git 2025-10-10T14:52:54Z SHA=23710cf2d 64-bit*

Has resolved the issue I spoken about in my previous message.

So far, so good!

Thanks,


---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**



Il 30/09/25 11:57, Marco Calistri ha scritto:
> Hello,
>
> Hope someone of the Hamlib group being sneaking here.
>
> So far my rigctld command to drive my YAESU FT-100 CAT port has worked 
> flawlessly:
>
> /usr/local/bin/rigctld -m 1021 -r /dev/FT-100_USB1 -t 4532 -s 4800 
> *--vfo* &
>
> This by using older Hamlib version:
> rigctld --version: rigctld Hamlib 4.6~git 2023-07-20T21:59:57Z 
> SHA=aacf06 64-bit
>
> Now, using the new Hamlib version:
>
> rigctld --version: rigctld Hamlib 4.7~git 2025-09-27T16:16:32Z 
> SHA=0d122f6b1 64-bit
>
> One of the VFO stays on previous frequency when I switch band.
>
> For example: I start working on 10 meters band then VFOA tunes on 
> 28.074 and VFOB tunes on the same frequency minus or plus the audio shift.
>
> When I switch band, for example to 17 meters, VFOA sets on 18.100, 
> whereas VFOB stays on 28.074!
>
> This is a really annoying behavior!
>
> I tried also without adding the *--vfo* parameter at rigctld without 
> success and obtaining a worst and slower switching from TX to RX.
>
> Thanks for any inputs you could provide.
>
> Marco, PY1ZRJ
> ---
> *73 de Marco, PY1ZRJ (former IK5BCU)*
> **

Re: [wsjt-devel] Enforcing WSJT-X split mode

[Reino T. <rei...@ko...>]

Hi Andy,

Your statement 'Testing fake-it requires a transmission
but rig split does not.' without additional information
makes no sense to me. Do you mean how an operator can
see that he is transmitting at correct radio frequency?
Most radios indicate the used VFO frequency, when
commanded for transmission. In the fake-it operation the
RX VFO (A) frequency changes and in the rig the
transmission uses the TX VFO (B). For an indication both
require a rig transmission activation. 

If the Tune button is used for the activation, then
there is output power in both cases. If the Test Cat
button or the Test PTT button is used, then no audio
will be transmitted, and no RF output will be sent. (If
PTT method VOX is used, then the Test PTT don't work and
only the Tune button can be used.)

 

The change of the audio frequency is not presented to
the user. 

 

It would be much easier to help in the rig split
operation, if at least you tell us the rig type and how
CAT control is arranged. 

 

73, Reino OH3mA

 

From: Andy Durbin via wsjt-devel
<wsj...@li...> 
Sent: Monday, October 13, 2025 12:24 AM
To: WSJT software development
<wsj...@li...>
Cc: Andy Durbin <a.d...@ms...>
Subject: Re: [wsjt-devel] Enforcing WSJT-X split mode

 

"I provided a signal report with screen shots to one
offending station and he improved his signal with audio
drive adjustment.  He stated he was using rig split."

 

Correction - He stated he was using fake-it.  Testing
fake-it requires a transmission but rig split does not.

 

Andy, k3wyc

 

 

 

Re: [wsjt-devel] Enforcing WSJT-X split mode

[Andy D. <a.d...@ms...>]

"I provided a signal report with screen shots to one offending station and he improved his signal with audio drive adjustment.  He stated he was using rig split."

Correction - He stated he was using fake-it.  Testing fake-it requires a transmission but rig split does not.

Andy, k3wyc

Re: [wsjt-devel] Enforcing WSJT-X split mode

[Christoph B. <my...@de...>]

Re: Andy Durbin via wsjt-devel
> Would the developers please consider inhibiting transmission below DF 1500 unless rig split has been verified as operational.

I'm using wsjtx as input to a GNU Radio flowgraph where the whole TX
chain is fully SDR. No room for any audio harmonics in there even
without split. Please don't break that.

73,
Christoph DF7CB

[wsjt-devel] Enforcing WSJT-X split mode

[Andy D. <a.d...@ms...>]

There has been a recent increase in the HF FT8 frequencies being fouled by audio harmonics.  It is obvious that these stations are not using WSJT-X rig split or fake-it.

I provided a signal report with screen shots to one offending station and he improved his signal with audio drive adjustment.  He stated he was using rig split.   I asked him to run a simple test which confirmed the rig did not change frequency with 500 Hz step changes in the TX cursor position followed by Tune.  I still hope to get rig split working for him.

Would the developers please consider inhibiting transmission below DF 1500 unless rig split has been verified as operational.

Thanks and 73,
Andy, k3wyc

Re: [wsjt-devel] Partial loss of CAT radio control

[Marco C. <PY...@ou...>]

Today I installed WSJTX-v3.0.0-rc1 on my Windows 11 partition

(I already installed and used successfully this app on my Linux 
partition, that I use as my main system).

By selecting radio "Hamlib NET rigctl", I cannot control my RIG anymore, 
it is an old YAESU FT-100.

Note: _With previous WSJTX version this setup never failed!_

To keep my stubbornness up and strong 🙂, I insisted to use Hamlib to 
manage the radio CAT and I found a solution:

I created a bat file (named "start_rigctld.bat") containing:

@echo off
cls

REM start rigctld for FT-100
start C:\Programmi\hamlib-w64-4.6.5\bin\rigctld.exe -m 1021 -r COM4 -t 
4532 --vfo VFOA

And I put this file into the Automatic startup Menu of Windows (Windows 
key+R to open that location).

In this way, rigctld is started automatically any time system is started.

---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**

*Da:* Jonathan Welch via wsjt-devel <wsj...@li...>

*Inviata:* mercoledì 8 ottobre 2025 alle ore 1:54 PM UTC-3

*A:* wsj...@li...

*Cc:* Jonathan Welch <jh...@gm...>

*Oggetto:* RE: [wsjt-devel] Partial loss of CAT radio control


> This is a followup to my message from yesterday:
>
> If I reverse the order of which program starts first then WSJT-X can
> control the radio until I make a QSO, at which point the software
> cannot communicate with the radio.
>
> This is a show stopper; I hope it gets fixed before this becomes
> released as the next version.
>
> On Tue, Oct 7, 2025 at 7:55 PM Jonathan Welch<jh...@gm...> wrote:
>> I just upgraded to WSJT-X v3.0.0-rc1 250915 from WSJT-X 2.7
>>
>> Prior to this upgrade I would start Log4OM v 2.36.1.0 and then WSJT-X.
>>
>> I use OmniRig Rig 1.
>>
>> Now if I start the programs in that sequence WSJT-X cannot control the
>> radio; before the upgrade it could.
>>
>> If I reverse the startup order both programs work as expected.
>>
>> -Jonathan
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Partial loss of CAT radio control

[DX J. <ah...@ya...>]

 Jonathan,
Try taking Log4OM out of the string.  Keep it simple.  

         Danny         AH6FX/W4 - Virginia   AH6FX - Hawaii


    On Wednesday, October 8, 2025 at 12:57:09 PM EDT, Jonathan Welch via wsjt-devel <wsj...@li...> wrote:  
 
 This is a followup to my message from yesterday:

If I reverse the order of which program starts first then WSJT-X can
control the radio until I make a QSO, at which point the software
cannot communicate with the radio.

This is a show stopper; I hope it gets fixed before this becomes
released as the next version.

On Tue, Oct 7, 2025 at 7:55 PM Jonathan Welch <jh...@gm...> wrote:
>
> I just upgraded to WSJT-X v3.0.0-rc1 250915 from WSJT-X 2.7
>
> Prior to this upgrade I would start Log4OM v 2.36.1.0 and then WSJT-X.
>
> I use OmniRig Rig 1.
>
> Now if I start the programs in that sequence WSJT-X cannot control the
> radio; before the upgrade it could.
>
> If I reverse the startup order both programs work as expected.
>
> -Jonathan


_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  

Re: [wsjt-devel] Partial loss of CAT radio control

[Jonathan W. <jh...@gm...>]

This is a followup to my message from yesterday:

If I reverse the order of which program starts first then WSJT-X can
control the radio until I make a QSO, at which point the software
cannot communicate with the radio.

This is a show stopper; I hope it gets fixed before this becomes
released as the next version.

On Tue, Oct 7, 2025 at 7:55 PM Jonathan Welch <jh...@gm...> wrote:
>
> I just upgraded to WSJT-X v3.0.0-rc1 250915 from WSJT-X 2.7
>
> Prior to this upgrade I would start Log4OM v 2.36.1.0 and then WSJT-X.
>
> I use OmniRig Rig 1.
>
> Now if I start the programs in that sequence WSJT-X cannot control the
> radio; before the upgrade it could.
>
> If I reverse the startup order both programs work as expected.
>
> -Jonathan

[wsjt-devel] Partial loss of CAT radio control

[Jonathan W. <jh...@gm...>]

I just upgraded to WSJT-X v3.0.0-rc1 250915 from WSJT-X 2.7

Prior to this upgrade I would start Log4OM v 2.36.1.0 and then WSJT-X.

I use OmniRig Rig 1.

Now if I start the programs in that sequence WSJT-X cannot control the
radio; before the upgrade it could.

If I reverse the startup order both programs work as expected.

-Jonathan

[wsjt-devel] RX frequency change

[Ari L. <oh...@gm...>]

Hi

I'm running wsjt-x v 2.7.0 on both Ubuntu 22.04 and Debian 13. The problem
is that when changing the band e.g. from 14 MHz to 18 MHz the rx frequency
is changing to 5000. This does not happen in windows 11.
This did not appear when I was working wsjt-x in Ubuntu 20.04.

Radio is Icom IC-7300 and operated as remote over vpn.
Control software is WRC (web radio control) by finnish amateur OH3BHX. WRC
is running on Raspberry Pi 4 at the remote station.
All radio and sw settings are the same as in Ubuntu 20.04.


73
Ari Laine OH2BSF
Lohja
Finland