Hi Russell
We can't test every possible rig in advance, so we depend on reports
like yours. Most of the rig-control issues are being handled by Bill,
G4WJS, and usually he can fix such problems fairly quickly. I am
copying this brief reply to the wsjt-devel list. You will probably hear
from
On 10/21/2014 10:02 PM, Joe Taylor wrote:
Hi Rusty,
>> Using version 1.4.0-rc2 r4400, I cannot seem to get the radio to respond
>> to transmit. I have checked, double checked, and triple checked my
>> settings to make sure everything matched and nothing. Had a friend of
>> mine who works in the I
Running windows 8.1, ham radio deluxe v 6.2.8.330, kenwood ts-590s
The major problem is the software gets confused when running split. Sometimes
it will go the VFO b (the split frequency) when opening. Sometimes it sets VFO
a = VFO b. Sometimes it drops vfo b completely.
The small problem - T
...snip...
When you say it sets VFO A equal to VFO B, do you mean when you start
the program or do you mean at some point during operating when your Tx
DF is outside of 1500Hz - 2000Hz?
Can you clarify what you mean by "drops the vfo b completely"?
...snip...
If I close the program with the tx/r
On 17/02/2015 19:16, fly...@yahoo.com wrote:
Hi Jeff,
Running windows 8.1, ham radio deluxe v 6.2.8.330, kenwood ts-590s
The major problem is the software gets confused when running split.
Sometimes it will go the VFO b (the split frequency) when opening.
Sometimes it sets VFO a = VFO b. S
The problem is that the "MR" (memory read) icon/indicator (used only to set
up 60m operation) on the FT-950 extinguishes after the end of a transmission
and resets back to "VFO Mode", whether it is a "tune" mode or a "QSO" mode
and then has to be manually reset time after time. The frequency also
On 08/02/2017 21:43, Neil Mayes wrote:
The problem is that the "MR" (memory read) icon/indicator (used only
to set up 60m operation) on the FT-950 extinguishes after the end of a
transmission and resets back to "VFO Mode", whether it is a "tune"
mode or a "QSO" mode and then has to be manually
ncy manually
deselects the Memory Read function and then "NO TRANSMIT"!
Thoughts?
73's, Neil K7IPP
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Wednesday, February 08, 2017 3:03 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Problem with WSJ
Hello,
I had been using the previous version successfully on a MacBook Pro (Intel not
M1), OS Big Sur 12.2.2.
Today, I downloaded Mac version 2.4.0-rc2.
When running Q65 on 6 meters, T/R = 30 seconds, Submode A, the program
continues to transmit after the 30 second period is complete, for 60
Same apparent CAT problem as WA1EAZ reports. But it seems resolved at the
moment.
Running Flex 6600, Mac mini with Big Sur (11.2.2) and SmartSDR for Mac 1.4.34.
Had been okay for a while monitoring, then the transmit problem crept in.
Normal sequence transmit, but the PTT issues and delays repo
Why did you run the clone to test FT8 .. .wouldn't it be a better idea
to see if WSJT-X worked correctly, then reported the issue? Using the
clone does not give the same information as the WSJT-X RC versions often
have Hamlib updates that other programs don't.
Neil, KN3ILZ
On 3/5/2021 1:10 PM
Neil,
Fair enough. I was hesitant to use WSJT-X 2.4.0-rc2 because of the problems I
encountered (which blew up a preamp).
Nevertheless, I just tried the FT8 mode on 2.4.0-rc2 and it appears to work
fine.
Thus, the problem seems to be isolated to Q65. No Hamlib here.
73,
John
WA1EAZ
> On
FWIW ... Hamlib is built-in to WSJT-X.
Neil, KN3ILZ
On 3/5/2021 9:23 PM, John Stengrevics wrote:
Neil,
Fair enough. I was hesitant to use WSJT-X 2.4.0-rc2 because of the problems I
encountered (which blew up a preamp).
Nevertheless, I just tried the FT8 mode on 2.4.0-rc2 and it appears to w
I decided to test out the RC3 release and everything comes up fine but as
soon as I try to change TX frequency in the waterfall or make a contact I
get something like this:
Rig Control Error
Hamlib error: Content-length: 168
xml_parse2: value returned=''
xml_parse2: xml='
'
flrig_transacti
This is my first post to this mailing list so please excuse me if it’s already
been asked:
Sometimes I find that WSJT-X isn’t fully decoding messages in the background
after a few minutes. Sometimes this doesn’t happen for days but lately this
has been happening to me everyday. I’ve spent abo
What rig? For some reason that call is not returning any value for your rig
when getting the current mode.
Mike W9MDB
On Sunday, January 28, 2024 at 07:37:38 PM CST, Richard Shaw via wsjt-devel
wrote:
I decided to test out the RC3 release and everything comes up fine but as soon
On Sun, Jan 28, 2024 at 10:16 PM Black Michael wrote:
> What rig? For some reason that call is not returning any value for your
> rig when getting the current mode.
>
FT-991A
Thanks,
Richard
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.ne
Assuming this is repeatable we now need to see FLRig debug data to see why mode
is not being read correctly.
So Config/Setup/Trace and turn on all the checkboxes.
Duplicate the problem. Then find the trace.txt file in flrig.files and send it
to me.
Mike W9MDB
On Monday, January 29,
Dave just posted a new alpha, I'll test with it first to see if it's
resolved.
Thanks,
Richard
KF5OIM
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Alex,
Why not disable App Nap completely:
defaults write NSGlobalDomain NSAppSleepDisabled -bool YES
To re-enable it try:
defaults delete NSGlobalDomain NSAppSleepDisabled
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-d
Hi John,
Thanks for the suggestion. I wish I could only turn off App Nap for WSJT-X
because I have a ton of other apps running and want the benefit of better
battery life and better foreground app performance.
Apps that support App Nap can be individually disabled by going to Finder's Get
Inf
Just to follow up on this- I think I might have found a solution that I’m
testing now with 2.4.0 on MacOSX 11.1.
John G4KLA suggested using the NSAppSleepDisabled key globally which got me to
thinking I could use it locally, so I added:
NSAppSleepDisabled
to the app’s Info.plist file an
On 22/06/2021 02:48, Alex Lelievre wrote:
Just to follow up on this- I think I might have found a solution that
I’m testing now with 2.4.0 on MacOSX 11.1.
John G4KLA suggested using the NSAppSleepDisabled key globally which
got me to thinking I could use it locally, so I added:
NSAppSleepDi
Hi Bill,
Thanks for offering to update the Info.plist file but unfortunately that hack
didn’t work. It could be because I modified the app after it was signed- or
simply that it isn’t supported. I’ve been trying to build WSJT-X on my Mac but
have run into some issues with gfortran complainin
HI Alex and Bill,
I am trying this scheme (NSAppSleepDisable) as well, using a local rather than
Global domain. It is not clear that this will will survive a reboot, but some
further checks are in progress.
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
__
Hi John,
Thanks for helping to test this fix.
You can read the settings back using:
defaults read org.k1jt.wsjtx
I just rebooted and checked they were still there. Also, I'd like to report
that I haven’t seen the app nap yet. :)
alex K6LOT
> On Jun 23, 2021, at 12:18 PM, John Nelson via wsjt
Hi Alex,
I also use Activity Monitor to check whether the system really does have sleep
disabled. This is where I have noticed that after a reboot the answer is
often no. I have yet to find a consistent way of doing this which will stick…
— John G4KLA
smime.p7s
Description: S/MIME cryptogr
27 matches
Mail list logo
