Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location
Here's a youtube video showing Windows users howto --
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location
Here's a youtube video showing Windows users howto --
Depend on what you are trying to seperate -- sounds like the GUI FFT processing
is you concern perhaps the decoding too?
Here's the flow
RigAudio -> PC -> GUI (both fft and collect for decoder -> wav file -> decoder
(e.g. JT9.EXE) -> GUI
And you are talking aboutRigAudio -> PicoITX -> GUIWhere
I think you can put those values in the qt.conf file also that you'll find in
the bin directory.
Did you try the wsjtx.exe I sent youi?
Mike W9MDB
On Sunday, February 11, 2024 at 03:18:03 PM CST, Laurie, VK3AMA via
wsjt-devel wrote:
On 10/02/2024 4:46 pm, Alan McDonald via
Try this executable -- not sure this is the fix but it may be.
https://www.dropbox.com/scl/fi/988papncf8o0wtuy56urw/wsjtx.exe?rlkey=nrkyyw7nerl21oatqlyhs27uz=0
On Saturday, February 10, 2024 at 07:04:04 PM CST, Laurie, VK3AMA via
wsjt-devel wrote:
On 11/02/2024 5:06 am, Black
Are you using more than 100% scaling?
Mike W9MDB
On Friday, February 9, 2024 at 05:35:27 PM CST, Laurie, VK3AMA via wsjt-devel
wrote:
This defect has been present in all recent release candidates and the 2.6.1 GA
release since the mode selection buttons were first introduced.
If the new machine is a Dell look for "WAV" services in the services manager
and disable them.
Mike W9MDB
On Tuesday, January 30, 2024 at 06:28:24 AM CST, Nic Sears via wsjt-devel
wrote:
Hi there, Nic G3YEG here.
I have been using wsjt for quite a few years both ft8 (hf, vhf and
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,
What version of Hamlib are you running? There's currently no way to disable
polling.
rigctl-wsjtx --version
FT747 behavior was supposedly fixed Aug 2022.
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
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
I don't see the 240202 update at your "find it here" link.
It points to
https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.7.1/
Mike W9MDB
On Saturday, January 27, 2024 at 04:14:00 AM CST, Uwe, DG2YCB via wsjt-devel
wrote:
Hi all,
Short information: Although I
Should be able to use this instead. Your call always has a space before/after.
contains(" " + m_baseCall +" "))
Mike W9MDB
On Saturday, January 27, 2024 at 04:14:00 AM CST, Uwe, DG2YCB via wsjt-devel
wrote:
Hi all,
Short information: Although I could not reproduce this unwanted
Actually CW operators use apriori operation all the time.
When you're in a poor signal CW QSO with a dxepedition or such all you listen
for is your call sign -- not theirs. You assume (apriori) that they are the
ones responding and you have a sequence you follow so you just continue.
Mike
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location
Here's a youtube video showing Windows users howto --
#1 That's a false decode (detectable as a funky message)
#2 Not on the Fox offsets. Fox never transmitted at 474
Mike W9MDB
On Friday, January 26, 2024 at 11:19:40 AM CST, Glenn Williams via wsjt-devel
wrote:
I am reporting here another issue with my TX5S QSO and the FT8 windows
No...it just appends the file. Size doesn't matter as the saying goes...
Mike W9MDB
On Friday, January 26, 2024 at 11:10:08 AM CST, Glenn Williams via wsjt-devel
wrote:
So,
Once upon a time I asked a question and the gurus had an answer (V2.2.2
I think).
My question was about
Perhaps when the fox offset for your callsign changes?
I think I've seen that.
On Friday, January 26, 2024 at 09:15:37 AM CST, Uwe, DG2YCB via wsjt-devel
wrote:
Hi Rich,
Last night I ran some tests with our good old standard WSJT-X (latest code)
using three instances all
You must have old source code in your system somewhere and it's picking up and
old yaesu.h file.
That is defined in ft9000.c
Hamlib/rigs/yaesu# grep ft9000Old_caps *.c *.hft9000.c:struct rig_caps
ft9000Old_caps =yaesu.c: rig_register(_caps);yaesu.h:extern struct
rig_caps ft9000Old_caps;
So I see a Behringer sound card.
Does this setup work or not?
Mike W9MDB
On Monday, January 8, 2024 at 09:04:58 PM CST, JP3EXR
wrote:
Hi Mike and the wsjt development team.
Thank you for supporting me.
Sorry I was unable to send two attached picture of my result because my
For the most part all but one of your "no good" involve the Sound Blaster on an
Input channel.
So two suggestions.
#1 Put a choke on the audio lines for all your sound lines into the Sound
Blaster. Possible RFI into the computer might be locking up the card.#2
Replace the Sound Blaster with
When it freezes check Task Manager and see if the jt9.exe process is using any
CPU time.
We need to know if the jt9.exe process is stuck or the user interface is just
not disabling the decode button.
There have a been other reports of the Decode button getting stuck.
Mike W9MDB
Please confirm what you mean by "freezing".
>From the last pictures you sent it looks like the "Decode" button is still
>enabled when the decoding stops?
Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
There is a checkbox you need to turn off in the Windows Sound Control Panel.
You can go direct to this control panel by typing "mmsys.cpl" in the search bar
in Windows.
Right-click your audio device (do this for both Playback and Record).
Select Properties
Advanced tab
Uncheck "Allow
Your time looks off by quite a bit. Is your waterfall still working and just
not decoding?
Check here http://time.is
And you can use Meinberg NTP to keep your time in sync.
Just be careful when installing. Easy to miss the configuration setup right
after it shows the installation files
How much memory do you have in your computer?
Mike W9MDB
On Thursday, January 4, 2024 at 03:51:24 AM CST, JP3EXR via wsjt-devel
wrote:
Hi wsjtx development team.
Thank you for helping me with my trouble.
Sorry I forgot to send you about my trouble situation.
Please check the
Exclude all of your ham software folders and data locations.
The antivirus programs are interfering with all sorts of ham stuff including
logging QSOs. I helped one of the DXpeditions a couple years ago when they
were losing QSOs in the log due to antivirus scanning of the log file for
Can you show the command line you are using to start each of the two JT65B
programs?
Mike W9MDB
On Tuesday, January 2, 2024 at 07:36:17 AM CST, JP3EXR via wsjt-devel
wrote:
Hello WSJT software development team.
Sorry I asked you about in my problem of I run two JT65B of
Look for openssl here
https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.6.1.html
Mike W9MDB
On Monday, January 1, 2024 at 12:20:11 PM CST, lktenpas--- via wsjt-devel
wrote:
One very minor observation.
I tried to updated the hamlib, 64 bit version. I have several
radios/instances
That's correct -- you cannot do two compound calls like that. It's a known
limitation of the message format.
There is an option for "full call in..." options but they don't seem to
honored. I'm still seeing full call transmitted in all messages.
Would be more than nice if WSJT-X could call
What version of WSJT-X?
This message seems to encode OK as a standard message. Is it possible your
decode window isn't wide enough to see the R+11??
C:\WSJT\wsjtx\bin>ft8code "WB0GAG R+11" Message
Decoded Err
No...that particular fork was created when Hamlib was not getting updated.
Mike W9MDB
On Sunday, December 10, 2023 at 02:27:28 PM CST, Daniel Uppström
wrote:
Oh, that's unfortunate.
I thought this particular fork was necessary for WSJT-X and not the main branch
of Hamlib?
Since Bill is silent key that repository has been removed.
The permanent home of Hamlib is here:
https://github.com/Hamlib/Hamlib
Mike W9MDB
On Saturday, December 9, 2023 at 02:33:42 PM CST, Daniel Uppström via
wsjt-devel wrote:
Hi,
When trying to build WSJT-X from source these
Since Bill is silent key that repository has been removed.
The permanent home of Hamlib is here:
https://github.com/Hamlib/Hamlib
Mike W9MDB
On Saturday, December 9, 2023 at 02:33:42 PM CST, Daniel Uppström via
wsjt-devel wrote:
Hi,When trying to build WSJT-X from source these days
There are several programs that will log to QRZ.
JTAlertLog4omDXKeeperHam Radio Deluxe
And others that can chime in with their fav'.
Mike W9MDB
On Thursday, December 7, 2023 at 03:40:01 PM CST, Marty Wayne via
wsjt-devel wrote:
Is there a way to use UDP or other method to
I take it you are running two receivers? Seems to me a software solution is
possible.
Do we need to do any more than just average the two? In your example doesn't
look like time delays are needed for steering.
Mike W9MDB
On Tuesday, December 5, 2023 at 09:18:28 AM CST, robert evans
Check your time
http://time.is
Mike W9MDB
On Monday, December 4, 2023 at 03:57:05 PM CST, robert evans LAST_NAME via
wsjt-devel wrote:
Using a IC-705 over the weekend and after
installing the usb drivers in a asus win11
i9 laptop i started WSJT-X 2.7.0-rc2.
The rig
Actually the strongest is not indicative at all of current conditions. You can
have momentary band conditions either way.
What matters is what signal you heard them at. e.g. "I initially received you
at XXdB". If a user wants to see band conditions for their callsign they can
use
That sourceforge link is no good anymore since Bill is SK.
Here is the master repo https://github.com/Hamlib/Hamlib
And here are the packages -- https://n0nb.users.sourceforge.net/
Mike W9MDB
> On Nov 7, 2023, at 4:27 PM, Matt Melling via wsjt-devel
> wrote:
>
> Hi,
>
> I am hacking on the
The one thing I have noticed on every dxpedition I've worked over the last year
so
WSJTX Fox mode bill on an 300Hz offset for channel 1.MSHV will normally be
above 500Hz.
You'll also see MSHV work people calling below 1000Hz.
I can always tell the difference.
And you don't really need Hound
It's not a waste of time
Here's why (especially on weak signals or when the band is flaky or QRM).
.start of QSOW9MDB W0YK R-13W0YK W9MDB RR73 -- band goes flaky but I'm
supposed to think the QSO is done...but you don't decode the RR73.W9MDB W0YK
R-13 -- you repeat because you didn't
Fox/Hound
For dxpeditions...see the Help
Mike W9MDB
On Saturday, October 21, 2023 at 11:24:46 PM CDT, sdegroff via wsjt-devel
wrote:
What is F/H mode ?
Sent from my Verizon, Samsung Galaxy smartphone
Original message From: sdegroff via wsjt-devel
Date: 10/21/23
Search the Help file for "a4" or "a3".
Mike W9MDB
On Saturday, October 21, 2023 at 07:26:27 AM CDT, Glenn Williams via
wsjt-devel wrote:
Hi,
The following line of text is found once in my huge ALL.TXT file. Note
the "a4" far to the right.
V2.6.1 Windows 10 USB-USB to TS590SG
What version of WSJT-X?
Mike W9MDB
On Tuesday, October 17, 2023 at 06:23:56 AM CDT, Erik Icket via wsjt-devel
wrote:
Dear developers,
The following Fortran runtime error occurred a number of times in MAP65.exe
:
Running: C:\WSJT\wsjtx\bin\m65 -s
At line 13 of file
I got some more info from the HamSCI group. So if you could maintain one band
for the duration of the SEQP that would be best.
>From W2NAF
The SEQP is going to run for 10 hours from 1200-2200 UTC. See
https://hamsci.org/seqp-rules
What we actually analyze will depend on the quality of
If you have a recent version of WSJTX (like RC2) we would appreciate you
turning on PSKReporter to support the upcoming solar eclipse Oct 14th. If you
can turn on PSKReporter now and keep it on until at least Oct 16th it would be
appreciated.
We implemented special PSKReporter ability in
lower than 1500 Hz.
They insist that they have checked their audio and it is not overdriving their
amp...
GL and VY 73, Lance
On 5 Sept 2023 11:48, Black Michael via wsjt-devel wrote:
No -- the target is not good quality of signals -- that's misleading
tooit's all about
No -- the target is not good quality of signals -- that's misleading
tooit's all about shifting the audio (actually shifting the suppressed
carrier).
#1 Avoid transmit band edges (rigs can actually transmit outside of their
bandpass)#2 Avoid harmonics#3 Avoid non-linear power behavior (some
of the text seems a bit
less sharp, but it does fix the problem and I like the overall effect better.
I very much appreciate your response.
--Mark, N7YD
From: Black Michael via wsjt-devel
Sent: Friday, September 1, 2023 9:25 AM
To: WSJT software development
Cc: Black Michael
things, and some of the text seems a bit
less sharp, but it does fix the problem and I like the overall effect better.
I very much appreciate your response.
--Mark, N7YD
From: Black Michael via wsjt-devel
Sent: Friday, September 1, 2023 9:25 AM
To: WSJT software
Try this to replace the qt.conf in your bin directory
[Paths]Plugins = ../plugins
[Platforms]WindowsArguments = dpiawareness=0
Mike W9MDB
On Thursday, August 31, 2023 at 10:43:43 PM CDT, Laurie, VK3AMA via
wsjt-devel wrote:
On 01/09/2023 8:15 am, Mark Galbraith via wsjt-devel wrote:
sent me. I may find a solution there.
I'll keep you informed.
Thanks in advance.
ON4CKT Rudy
- Oorspronkelijk bericht -
Van: "Black Michael via wsjt-devel"
Aan: "on4ckt--- via wsjt-devel"
Cc: "Black Michael"
Verzonden: Maandag 28 augustus 2023 23:08
That makes it sound like it's the wrong port.
You should have two COM ports -- the Extended port is the one you want.
Mike W9MDB
On Monday, August 28, 2023 at 10:07:56 AM CDT, on4ckt--- via wsjt-devel
wrote:
Hello, today I tried to install WSJT-X v2.7.0-rc2 on my laptop
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
I can duplicate the behavior here with my Apache 7000 and Thetis.
Using RC2 here.
Both the Tune button and Enable Tx follow the 500hz offsets.
Both Fake It and Rig Split behave this way.
Split=None works correctly.
Mike W9MDB
On Thursday, August 3, 2023 at 03:13:30 PM CDT, Andreas
No...Yaesu rigs do not have CI-V transceive.
Mike W9MDB
On Thursday, July 20, 2023 at 03:21:36 PM CDT, Marco Calistri
wrote:
Il 20/07/23 16:07, Christoph Berg ha scritto:
Check if CIV Transceive is off.
Christoph DF7CB
What is it? CIV...
Are you sure that Yaesu
the 1 Khz shift: 28074 RX and 28073 TX.
This is not a blocking issue to me but it is a bit annoying having to correct
manually.
Regards,
Marco, PY1ZRJ
Inviato da Outlook per AndroidFrom: Black Michael via wsjt-devel
Sent: Thursday, July 20, 2023 10:42:39 AM
To: wsjt-devel@lists.sourceforge.net
Cc
Inviato da Outlook per AndroidFrom: Black Michael via wsjt-devel
Sent: Thursday, July 20, 2023 10:42:39 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] VFO readout on FT8 shutdown That's what you get when
you start smooshing buttons.
Here's what happened.
You
That's what you get when you start smooshing buttons.
Here's what happened.
You swap VFOs -- WSJT-X doesn't care.You exit -- WSJT-X saves the VFOB
frequency as the "last frequency" used.You start again -- if you have "Monitor
returns to last used frequency" it will then load VFOB's frequency
why anyone would run an outdated firmware on a radio.In
DXLog.ne we simply do not support outdated firmwares.
Björn
On Fri, Jul 14, 2023 at 12:13 AM Black Michael via wsjt-devel
wrote:
Also what firmware version are you running?I made some changes which SHOULD be
both forward/backward com
eve why anyone would run an outdated firmware on a radio.In
DXLog.ne we simply do not support outdated firmwares.
Björn
On Fri, Jul 14, 2023 at 12:13 AM Black Michael via wsjt-devel
wrote:
Also what firmware version are you running?I made some changes which SHOULD be
both forward/backward com
M 7300; Win10 on dedicated Celeron J4125 with 16GB RAM;
(J4125 has Cores. 4 ; Threads. 4 ; Burst 2.70 GHz ; Processor Base 2.00 GHz ;
Cache. 4 MB).
Regret I don't have comparable CPU data for 2.6.0 but will install it if that
helps.
73,
Roger (K7GXB)
-Original Message-
From: Black Michae
, Jul 12, 2023 at 3:20 PM Black Michael via wsjt-devel
wrote:
Save this into a file called "hamlib_settings.json" and place in the same
folder as WSJT-X.ini
Should improve things until I get this fixed.
{
"config": {
"async": "0"
}
}
ted Celeron J4125 with 16GB RAM;
(J4125 has Cores. 4 ; Threads. 4 ; Burst 2.70 GHz ; Processor Base 2.00 GHz ;
Cache. 4 MB).
Regret I don't have comparable CPU data for 2.6.0 but will install it if that
helps.
73,
Roger (K7GXB)
-Original Message-
From: Black Michael via wsjt-devel
This is a problem on Windows with the async routine enabled. With async
enabled Windows uses 100% of 1 core. Async disabled runs at 1.6% of 1 core.
It really should be closer to zero than the 1.6% but Windows has a problem with
timing.
Linux doesn't have this problem.
I'm working on a
es at less than 2%.
Drew K9CW
On 7/11/2023 11:52 AM, Black Michael via wsjt-devel wrote:
> It's fixedhad a new send_morse routine (now takes up to 1023 chars to
>transmit) and missed putting a sleep in the main loop.
> With 32 cores here the 3% usage didn't really pop out at me.
OH3mA
> -----Original Message-----
> From: Black Michael via wsjt-devel [mailto:wsjt-
> de...@lists.sourceforge.net]
> Sent: tiistai 11. heinäkuuta 2023 19.53
> To: wsjt-devel@lists.sourceforge.net
> Cc: Black Michael
> Subject: Re: [wsjt-devel] High CPU load with 2.7.0-rc2
&
at 32% usage which is essentially the
same as the earlier "4.6~git Jun 28" version. The older libhamlib-4.dll v4.5.4
idles at less than 2%.
Drew K9CW
On 7/11/2023 11:52 AM, Black Michael via wsjt-devel wrote:
> It's fixedhad a new send_morse routine (now takes up to 1023 chars
It's fixedhad a new send_morse routine (now takes up to 1023 chars to
transmit) and missed putting a sleep in the main loop.
With 32 cores here the 3% usage didn't really pop out at me.
New 64-bit DLL
https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0
New Linux shared library
I can duplicate the problem herewill be fixed ASAP.
Mike W9MDB
On Tuesday, July 11, 2023 at 10:35:20 AM CDT, Brian Morrison via wsjt-devel
wrote:
On Tue, 11 Jul 2023 15:12:00 +0100
Brian Morrison via wsjt-devel wrote:
> Running on Linux under Fedora 38 I am seeing the latest
Calistri via wsjt-devel
wrote:
Il 08/07/23 12:16, Black Michael via wsjt-devel ha scritto:
I guess you must be compiling the latest hamlib from github.
Please pull the latest and try again. It should be fixed.
Mike W9MDB
Hello,
Are there any oddities in my thoughts
I guess you must be compiling the latest hamlib from github.
Please pull the latest and try again. It should be fixed.
Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Try this 64-bit DLL
https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0
Mike W9MDB
On Saturday, July 8, 2023 at 01:39:11 AM CDT, jarmo via wsjt-devel
wrote:
Fri, 7 Jul 2023 11:50:06 -0400
Joe Taylor via wsjt-devel kirjoitti:
> Dear WSJT-X Users,
>
> We are pleased
The 7610/7600 will behave better (if it's the latest firmware) with the more
current version of Hamlib than Uwe said he was going to use.
Icom decided to add the 0x25 0x26 command but did it differently than all other
Icoms (actually they did it the "right" for the 76xx IMHO).
Mike W9MDB
I would recommend that WSJT-X save a dated copy of the file during the closing
of the Settings dialog where it checks for changes.So...if something changed
save the current config with MMDDHHMMSS which would end up showing when
the change took place
Mike W9MDB
On Wednesday, June
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location
For Linux put it in
~/.config
The WSJT-X_Rigcontrol.log file will
from
different computers, in fact all radios have their own computers.
I will be out most of the morning to church but back in the afternoon CDST.
73, Gene, K5PA
On 6/10/2023 10:18 PM, Black Michael via wsjt-devel wrote:
> Need people to test the latest Hamlib please
>
&
Need people to test the latest Hamlib please
https://n0nb.users.sourceforge.net/
#1 Backwards compatibility with WSJT-X has been fixed.
#2 Notable speedups for Windows operations
Here's an FT-991 comparison
Old:
1:rig_get_freq: elapsed=16ms
1:rig_get_freq: elapsed=17ms
1:rig_get_split_vfo:
Two things to do -- try the latest hamlib and if that doesn't solve the problem
I need some debug.
ew 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
Would this paper relate to WSJT-X's method?
https://ieeexplore.ieee.org/document/6349716
Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
You would run tcpdump on the PI. You cannot watch one computer's network
traffic from another computer using wireshark. Everybody uses a switch now
and the cheap switches do not have a monitoring capability (sometimes referred
to as an aggregation port). You can only see your own traffic.
Turns out Task Manager shows different memory usage then the System Informer I
use and also Process Explorer.
System Informer says 444MB but Task Manager says 44MB on a clean config (no rig
selected or anything done).
Process Explorer shows 450MB.
So I don't believe Task Manager is correct at
2.6.1 gives me the same 450MB on a clean AppData\Local\WJST-X setup.
Mike W9MDB
On Friday, May 26, 2023 at 08:30:02 AM CDT, Fred Price via wsjt-devel
wrote:
I started 2.7.0-rc1 Windows 11 Ryzen 5 task manager shows 473mb for WSJT.exe.
I then closed 2.7.0-Tx1 and opened 2.6.1 task
I don't see a memory leak -- but do see a large chunk of memory being
used...over 400MB by both 32-bit and 64-bit Windows versions. Others have
mentioned this too.
330MB of that is the main wsjtx.exe program and not the DLLs.
I was able to compile a debug version and put a break point in
So I need a debug file from rigtctld and from WSJT_X.
For rigctld add this "-v -Z >log.txt 2>&1"
And for WSJT-X please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X
The
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location
For Linux put it in
~/.config
The WSJT-X_Rigcontrol.log file will
Fixed it -- will be in tonight's build 20230520
https://n0nb.users.sourceforge.net/
Mike W9MDB
On Friday, May 19, 2023 at 04:25:07 PM CDT, Sam W2JDB wrote:
Hi Mike,
Saw this thread, decided to look at the log.
[SYSLOG][2023-05-19 18:26:29.239145][00:00:00.000273][info]
You have to decode them once when they do NOT get their callsign in brackets.
A lot of people like to skip TX1 which causes this problem.
Mike W9MDB
On Monday, May 15, 2023 at 03:02:58 PM CDT, Bo Nilsson FJE via wsjt-devel
wrote:
Hi Gents,
This msg has hit me a couple
BTW -- The community would appreciate everybody turning on PSKReporter. We
have put changes in WSJT-X to support the HamSCI community doing analysis on
solar eclipses where the spotting will increase +/- 6 hours around a solar
eclipse event.
By default WSJT-X removes duplicate spots now
What do you mean "it does not find my Hamlib net rigctld," -- is there some
error message?
Mike W9MDB
On Saturday, May 13, 2023 at 09:41:27 AM CDT, jarmo wrote:
Sat, 13 May 2023 12:42:20 +0000 (UTC)
Black Michael via wsjt-devel
kirjoitti:
Hi Mike &
No,
Looks for any errors at all during startup or normal operations.
In particular using Fake It or Rig Split
Mike W9MDB
On Saturday, May 13, 2023 at 09:35:42 AM CDT, Hisashi T Fujinaka via wsjt-devel
wrote:
I have an Elecraft K3 and an Elecraft K4 and I'm running MacOS.
I could test
Do you have an old libhamlib sitting around? Did you uninstall the hamlib
package?
Mike W9MDB
On Saturday, May 13, 2023 at 04:35:41 AM CDT, jarmo via wsjt-devel
wrote:
Just started trying compile hamlib in Fedora 38.
Got error
make[1]: Siirrytään hakemistoon
I have been writing simulators but they do not have the nuances that the rigs
do. There's all sorts of oddities.
Butthe plan is to eventually incorporate those simulators in the "make
test" in Hamlib that should catch big mistakes.
It's on my to-do list but don't hold your breath...it's a
, and
rebooted the computer, but I am still getting the error.
So, then I tried re-installing 2.7.0-rc1, and rebooting the computer
again, I still have the error.
Sorry.
73 de WA3ZSC - Jerry
On 5/12/2023 13:07, Black Michael via wsjt-devel wrote:
> Direct link
>
> https://www.drop
. Even tried
again with a clean install.
Greg, NC7B
> On May 12, 2023, at 9:57 AM, Black Michael via wsjt-devel
> wrote:
>
> Please try this DLL
>
> https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0
>
> Mike W9MDB
>
>
>
>
>
>
&
Direct link
https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=1
Mike W9MDB
On Friday, May 12, 2023 at 12:01:57 PM CDT, Black Michael via wsjt-devel
wrote:
Please try this DLL
https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0
Mike W9MDB
On Friday
Please try this DLL
https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0
Mike W9MDB
On Friday, May 12, 2023 at 11:55:54 AM CDT, Gerald Smith via wsjt-devel
wrote:
Hi Joe,
Sorry, but I get this error with WSJT-X 2.7.0-rc1.
Radio IC-7700, interface -
And ya'll are confusing the purpose of split with the rig split function.
We have 3 choices
#1 Fake It#2 Rig#3 None
The all refer to split -- not to any reason for using it. You are trying to
put the reason as the title.
Mike W9MDB
On Monday, May 8, 2023 at 10:51:17 AM CDT, Adrian via
I don't see what the problem is.
When you click "Rig" your rig goes into Split mode -- why would want to confuse
people now with asking "why does my rig go into split mode when I click Rig in
audio optimization".
Fake It is running split on just one VFO.
What we're missing in WSJT-X is the
vel
wrote:
Fair enough, they come with keeping the transmit audio frequency centered in
the passband.
"Use optimal transmit audio frequency" then?
Given the huge and often uninformed debates (not only here), avoiding the
s-word would have a lot of value.
Björn SM7IUN
On Mon, May 8, 20
#1 It allows you to transmit outside your passband.#2 It avoids roll off of
power at band edges.#3 It avoids non-linearities in the audio digitization.
Mike W9MDB
On Monday, May 8, 2023 at 09:13:02 AM CDT, Björn Ekelund via wsjt-devel
wrote:
So what more does it do?
Björn SM7IUN
On
1 - 100 of 1442 matches
Mail list logo
