Hi Marty,
Lets start from beginning. How is your CAT communication signaling built in
your system? Do you have a USB to RS-232 converted cable or direct RS-232 to
RS-232 cable between PC and your FT-1000MP?
To me it seems a simple loss of that connection for some reason. Even just the
bit
You mean lots of dropped audio?
What model Mac?
Can you raise the process priority?
Mike W9MDB
On Friday, July 22, 2022 at 11:02:29 PM CDT, Hisashi T Fujinaka
wrote:
On Fri, 22 Jul 2022, Black Michael via wsjt-devel wrote:
> I'd appreciate if users could check their
That's a pretty consistent bunch of dropped audio samples.
As I asked another user have you tried raising the priority of WSJT-X to see if
making it real-time improves things?
Mike W9MDB
On Friday, July 22, 2022 at 07:17:20 PM CDT, Dennis Younker NE6I via wsjt-devel
wrote:
Here
I can’t even get the radio and wsjt-x to communicate. I misspoke when I said
that the Hamlib error happened while using FT8. Actually, I had taken a short
break. I believe I shut down wsjt-x and restarted when I returned. That is
when aI started getting the Hamlib error. I hadn’t changed
Here a few lines from mine. Win10 and running v2.6.0-rc2. Are you looking for
something in particular? I seem to get these dropped audio source alerts quite
a bit!
[SYSLOG][2022-07-22 03:26:29.383606][03:15:14.093551][warning] Detected dropped
audio source samples: -624 (-0.013 S)
Hi Mike,
On 7/22/22 10:37, Black Michael via wsjt-devel wrote:
> I'd appreciate if users could check their wsjtx_syslog.log file.
> For Windows users it will be in C:\Users\[username]\Appdata\WSJT-X
> For Linux users /[username]/.local/share/WSJT-X
>
> Should look like this and have one warning
I'd like to see some more detail
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
Mike,
A couple additional warnings but all seem to be working ok..
[SYSLOG][2022-07-22 19:08:02.659095][00:00:00.001682][info] Log Start
[SYSLOG][2022-07-22 19:08:02.659095][00:00:00.001767][info] WSJT-X
v2.6.0-rc2 994e3f by K1JT et al. - Program startup
[SYSLOG][2022-07-22
I had 11 audio warnings in 10 seconds today. Had the same or more on previous days. Also when using 2.5.4 I am running an Icom 7300 with a Dell windows 10 box.KD2RWCOn Jul 22, 2022 11:37 AM, Black Michael via wsjt-devel wrote:I'd appreciate if users could check their wsjtx_syslog.log file.
For
Thanks...
I have fixed the netrigctl errors which were left over debug stuff.
The error in get_vfo is a known one for Icom rigs --- that will remain an error
until Icom provides a way to determine the current vfo. A long-standing pet
peave of mine.
Mike W9MDB
On Friday, July 22,
Mike,
I renamed my old file since it was too large and then started the WSJT-X
program.
I am using Win 10, 64-bit, Radio=IC-7610, mode was FT8 on 15 meters.
Hope this helps.
73, Gene, K5PA
See file attached. Contents is listed below.
[SYSLOG][2022-07-22
On 22.7.2022 18.37, Black Michael via wsjt-devel wrote:
I'd appreciate if users could check their wsjtx_syslog.log file.
For Windows users it will be in C:\Users\[username]\Appdata\WSJT-X
For Linux users /[username]/.local/share/WSJT-X
Actually, under Linux it is in ~/.local/share/WSJT-X/*logs*
Have you tried raising the priority of WSJTX to real-time?
There's a great replacment for Task Manager called Process Hacker that give
complete control over processes and can remember across restarts.
https://processhacker.sourceforge.io
Mike W9MDB
On Friday, July 22, 2022 at
I'd appreciate if users could check their wsjtx_syslog.log file.
For Windows users it will be in C:\Users\[username]\Appdata\WSJT-X
For Linux users /[username]/.local/share/WSJT-X
Should look like this and have one warning possibly about dropped audio. If
you see any other warnings please
Hello,
I noticed a new undesired behavior here using the new WSJT-X
2.6.0-RC 2 with the latest Hamlib available by Github:
When I switch FROM any band TO 21MHz band, the rig
begins making a sort of band switching from previous band to the
21MHz one, without
Complied on SuSE Leap 15.4 and SuSE Linux Enterprise 15.4 with warnings,
no errors.
On 7/21/22 07:58, Joe Taylor via wsjt-devel wrote:
Dear WSJT-X Users,
We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc2 is
ready for download by beta testers. A list of its essential changes
As a diagnostic..
While sending CQ for example..
Reduce the transmit power,
by both audio and transmitter settings and see
if the phenomenon goes away at lower powers.
If with the output minimized the phenomenon
persists then it is probably not RFI related.
If you find a reduced output power
17 matches
Mail list logo