1. main@WSJTX.groups.io
  2. Messages
   Date   
Locked Rig control error #wsjt-x-crashing #Windows10 #FlexRadio

John Caulfield <johnradioham@...>
 

Windows 10, Flex 6400, Version 2.5.4 WSJT-X,
All works fine for a while (five minutes or so) then I get the Rig Control Error with the following detail:
Hamlib error: IO error
network.c(441):network_close return(0)
iofunc.c(361):port_close return(0)
rig.c(1047):rig_open return(-6) IO error
network.c(441):network_close return(0)
iofunc.c(361):port_close return(0)
iofunc.c(361):port_close return(0) while opening connection to rig

Only programs running are Flex SDR and WSJTX - no add-ins.
Ugraded to the most recent versin of WSJT-X in hopes that would fix it but same thing happened.
Any help would be greatly appreciated.
John K0FUZ
Locked WSJTX_LOG issues with 2 calls. #logging #WSJTX_config

Mike G8NSZ
 

H All,

I have an issue with, I think, WSJT-X not reading the log file caused by me removing, renaming, reinstalling the file into the log folder.

I changed my callsign when I operated from a holiday cottage in Scotland. So, I thought, I will copy and paste my G8 logfile to another location and rename it _G8. I then deleted that log from the folder using the delete command in the dropdown, then changed the callsign in settings to GM8. Once I returned home I did the same in reverse, so to speak, by saving the GM log as _GM and replacing the original in the log folder and renaming it as WSJTX_LOG. However, the programme does not appear to be reading the log as all the new call/new zone/new square colours which I know I have worked before are all there. Is that how it shows previously worked stations?

What did I do wrong, or can the programme not cope with what I have done? Many thanks.
73
Mike - G8NSZ
Locked New hits only (not new & unconfirmed) Alert #WSJTX_config

MikeMc -- KA5TDA
 

Is there anyway of getting just New hit alerts instead of new + unconfirmed?? DXCC is checked but I don't want to get notifications on every unconfirmed QSO.

Mike
Locked Re: Kenwood TS-2000 - no TX-NF in Versions above 2.3.1 #IssueReport #Kenwood #linux #Cat_RigControl #txaudio

Michael Black
 

Hamlib 4.5 is due Mar 1st.
For now you can compile the latest yourself and use rigctld from the latest version and have WSJT-X use Hamlib NET rigctl.
I think this problem was fixed.  At least I haven't heard any complaints recently.
http://n0nb.users.sourceforge.net/

Mike W9MDB

On Sunday, January 23, 2022, 08:53:55 AM CST, Stefan U. Hegner <db4st@...> wrote:

Hi there,

... 3 months later, now at WSJT-X 2.5.4 ...

Kenwood TS-2000 with back-panel NF-in does not send a signal, despite
active PTT via extra serial RTS. TX Moni also has no signal for playback.

Briefly again my setup, that works perfectly up to WSJT-X 2.3.1 on
Ubuntu 20.04 LTS:

  * rigctld (using the hamlib delivered with wstjtx) with "-m 2014"
  * wsjt-x uses net rigctl, second serial port with RTS for PTT

... any news on this or additonal ideas?

Or should I rather post this in parallel to the hamlib-list, as we are
moving from hamlib 4.2 to hamlib 4.5?

Current status-quo from Nov was:
Am 01.11.21 um 20:04 schrieb Stefan U. Hegner:
Am 01.11.21 um 19:58 schrieb Bill Somerville:
On 01/11/2021 18:53, Stefan U. Hegner wrote:
Am 01.11.21 um 19:17 schrieb Bill Somerville:
On 01/11/2021 18:00, Stefan U. Hegner wrote:

Up to WSJT-X 2.3.1 all works fine and as desired. However if I
upgrade to 2.4.x or 2.5.x I get the following problem:

Hitting PTT won't put any NF trough the TRX and hence send no HF
signal.
Hamlib is statically linked into WSJT-X in our pre-built Linux
packages, so you must re-build WSJT-X to change the Hamlib version.
Maybe I wasn't clear on this one: It's the hamlib rigctld that is
manually started and listens for commands from wsjtx via the net api.
the Hamlib linked into WSJT-X is involved as well as rigctld, it is
that which communicates with rigctld. I suspect the issue may have
been fixed already. Understood on not wanting to rebuild WSJT-X with
a more recent Hamlib version, I suggest you stay with WSJT-X v2.3.1
until a new version is available, you will not have long to wait.
That sounds like a plan.

Actually that was the plan after 2.4.1. - I waited for 2.5.1 ... and
as this was not yet fixed, I started asking my questions here.
Vy 73

Stefan.

--
Stefan U. Hegner    <db4st@...>
              * * *
DB4ST --- German Ham Radio Station
D-32584 Löhne ----- Locator JO42IE
              * * *
GPG-Key | C3CC 23A4 FBA8 622B 48AE
F-Print | 4F19 D0EE E39E ABDC 2BCE
Locked Kenwood TS-2000 - no TX-NF in Versions above 2.3.1 #IssueReport #Kenwood #linux #Cat_RigControl #txaudio

Stefan U. Hegner
 

Hi there,

... 3 months later, now at WSJT-X 2.5.4 ...

Kenwood TS-2000 with back-panel NF-in does not send a signal, despite
active PTT via extra serial RTS. TX Moni also has no signal for playback.

Briefly again my setup, that works perfectly up to WSJT-X 2.3.1 on
Ubuntu 20.04 LTS:

* rigctld (using the hamlib delivered with wstjtx) with "-m 2014"
* wsjt-x uses net rigctl, second serial port with RTS for PTT

... any news on this or additonal ideas?

Or should I rather post this in parallel to the hamlib-list, as we are
moving from hamlib 4.2 to hamlib 4.5?

Current status-quo from Nov was:
Am 01.11.21 um 20:04 schrieb Stefan U. Hegner:
Am 01.11.21 um 19:58 schrieb Bill Somerville:
On 01/11/2021 18:53, Stefan U. Hegner wrote:
Am 01.11.21 um 19:17 schrieb Bill Somerville:
On 01/11/2021 18:00, Stefan U. Hegner wrote:

Up to WSJT-X 2.3.1 all works fine and as desired. However if I
upgrade to 2.4.x or 2.5.x I get the following problem:

Hitting PTT won't put any NF trough the TRX and hence send no HF
signal.
Hamlib is statically linked into WSJT-X in our pre-built Linux
packages, so you must re-build WSJT-X to change the Hamlib version.
Maybe I wasn't clear on this one: It's the hamlib rigctld that is
manually started and listens for commands from wsjtx via the net api.
the Hamlib linked into WSJT-X is involved as well as rigctld, it is
that which communicates with rigctld. I suspect the issue may have
been fixed already. Understood on not wanting to rebuild WSJT-X with
a more recent Hamlib version, I suggest you stay with WSJT-X v2.3.1
until a new version is available, you will not have long to wait.
That sounds like a plan.

Actually that was the plan after 2.4.1. - I waited for 2.5.1 ... and
as this was not yet fixed, I started asking my questions here.
Vy 73

Stefan.

--
Stefan U. Hegner <db4st@...>
* * *
DB4ST --- German Ham Radio Station
D-32584 Löhne ----- Locator JO42IE
* * *
GPG-Key | C3CC 23A4 FBA8 622B 48AE
F-Print | 4F19 D0EE E39E ABDC 2BCE
Locked Re: Power amplifier RX/TX relay damage-high SWR -From Halt TX during Q65-60B TX #Q65

Reino Talarmo
 

Since arching can occur when a contact is made or broken, I was wondering if using the Halt TX button in the middle of a high power 60 sec TX happens too fast?
Hi Richard,

Unless you have a long latency in your audio string this should not be possible. Well, I assume that PTT signaling is initiated only after power down tapering at the end of power off.

73, Reino OH3mA
Locked Re: WSJTX Rus interface #WSJTX_config

Michael Black
 

Given that Bill Sommerville created the original and he was a Great Britain person you should use wsjtx_en_GB.ts
Mike W9MDB

On Saturday, January 22, 2022, 09:10:31 PM CST, Victor R3BB via groups.io <r3bb@...> wrote:

Hello! What should be taken as a basis
(template wsjtx_??.ts) for translating
the interface into Russian (wsjtx_ru.ts) ?
Victor (R3BB) 73!
Locked Power amplifier RX/TX relay damage-high SWR -From Halt TX during Q65-60B TX #Q65

G Richard Kreuter
 

I have had my Tajfun 1000 432MHz PA shutdown-zero power out-during TX of a string of EME Q65-60B CQ's. I had been running 425W out and seeing 2.2W REV. Antenna array tested 1.1SWR and 50 ohms. Tajfun memory showed shutdown due to high SWR. TX/RX relay was inspected, and pitting was found on the TX contact side. Since arching can occur when a contact is made or broken, I was wondering if using the Halt TX button in the middle of a high power 60 sec TX happens too fast?
Locked Re: Can't update Tx2 signal report #QSO_practices

Mike Koralewski K8VA
 

Gary,
I agree...it just doesn't make any sense to fret over SNR numbers. SURE they would be better IF the transmitting station was stronger into the receiving stations inherent noise level, or the noise level on each other's receiving end was lower.
But that's the challenge of ham radio. A completed contact is a completed contact.
73 Mike K8VA
Locked WSJTX Rus interface #WSJTX_config

Victor R3BB
 

Hello! What should be taken as a basis
(template wsjtx_??.ts) for translating
the interface into Russian (wsjtx_ru.ts) ?
Victor (R3BB) 73!
Locked Re: Two WSPR self decodes with 30-50 dB SNR delta #WSPR

Reino Talarmo
 

Hi Scott,
Is your mains frequency 60 Hz. If so, then another possibility is that your
WSPR transmitter DC voltage contains a bit 120 Hz brum and that amplitude
modulates your transmitter signal generating sidebands at 120 Hz difference.

You can check that by looking your signal at wsjt-x waterfall.
73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of
William Smith
Sent: 22. tammikuutata 2022 22:20
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Two WSPR self decodes with 30-50 dB SNR delta #WSPR

Rx overload, try turning down the RF gain on your 7300, or adding 20-30db
attenuation in the Rx antenna lead.

73, Willie N1JBJ

On Jan 22, 2022, at 2:36 PM, Scott Eckert via groups.io
<sbeckert@...> wrote:
I'm testing my .2W 17m WSPR transmitter using a local antenna and
receiving with my 7300. I'm running WSJT-X 2.5.4 and every decode period
shows two entries with 30-50 dB difference in SNR (e.g., one will be -13 and
the other +23. One was even +24 and -29) . The two decodes show about 130Hz
frequency delta. WSPR reporting seems normal. Any ideas on what's going on?
Thx. Scott
Locked Re: Two WSPR self decodes with 30-50 dB SNR delta #WSPR

William Smith <w_smith@...>
 

Rx overload, try turning down the RF gain on your 7300, or adding 20-30db attenuation in the Rx antenna lead.

73, Willie N1JBJ

On Jan 22, 2022, at 2:36 PM, Scott Eckert via groups.io <sbeckert@...> wrote:
I'm testing my .2W 17m WSPR transmitter using a local antenna and receiving with my 7300. I'm running WSJT-X 2.5.4 and every decode period shows two entries with 30-50 dB difference in SNR (e.g., one will be -13 and the other +23. One was even +24 and -29) . The two decodes show about 130Hz frequency delta. WSPR reporting seems normal. Any ideas on what's going on? Thx. Scott
Locked Two WSPR self decodes with 30-50 dB SNR delta #WSPR

Scott Eckert
 

I'm testing my .2W 17m WSPR transmitter using a local antenna and receiving with my 7300. I'm running WSJT-X 2.5.4 and every decode period shows two entries with 30-50 dB difference in SNR (e.g., one will be -13 and the other +23. One was even +24 and -29) . The two decodes show about 130Hz frequency delta. WSPR reporting seems normal. Any ideas on what's going on? Thx. Scott
Locked Re: Receive signal level with Signalink USB #signalink

MikeMc -- KA5TDA
 

If I remember correctly from the software, JTDX was programmed for stereo capability and WSJT is set for mono (usually left channel on most equipment).
Locked Re: WSJT-X crashes witrh error messages not understood #stopped_working

MikeMc -- KA5TDA
 

Stale locks, click yes remove them. The unique message means WSJT found another copy running when you tried to start it. Reboot the computer, Can't tell you about Windows 11, it's a whole new set of security issues. Start JTAlert first and then look in task manager and see if WSJT is running as a background process. If so you have check start WSJT in JTAlert (un-check it).

Mike
Locked Re: storing the wsjt-x_log.adi #logging

Dave Garber <ve3wej@...>
 

sounds like the udp got blanked or edited

Dave Garber
VE3WEJ / VE3IE

On Thu, Jan 20, 2022 at 2:15 PM Gary trock <Gtrockmd@...> wrote:

Since the windows 10 update, my JT Alert screen is blank, and LOG40M not
recording QSOs. No change in my settings. I can make QSOs using the WSJTx
window and manually record contacts. Any suggestions?
Gary N8GT
On Jan 20, 2022, at 10:53 AM, Roger <groups@...> wrote:

Having seen the devastation inflicted on my friend's machine by a
recent windows 10 update I think it would be foolhardy to move the file
anywhere else.

Roger
G#4HZA

On 20/01/2022 15:11, Michael Black via groups.io wrote:
I would agree this is a long overdue change that is needed. There are
workarounds as noted but that's not a really good solution for something
that just requires a textbox and a path browser. Very little code required.
Mike W9MDB
On Thursday, January 20, 2022, 03:23:24 AM CST, Panos <
sv1grn@...> wrote:
Hi, under my OS is Widows 10 64bit wsjt-x by default stores the adif
file in C:\Users\<username>\AppData\Local\WSJT-X. I wonder if the authors
can let the choice to us to select the directory we want? It'll be more
easy and convinient than other mentioned solutions 73
Locked Re: MacBook Pro with MacOS 11.6.2 Black Screen at boot after installing CP210x Macintosh OS VCP Driver v6 #macOS

Lynn Mears
 

No I’m not. FYI, my Mac is a 2016 13”dual core Intel. So not very recent either.

Lynn

On Jan 21, 2022, at 9:41 AM, Mike <m0aws@...> wrote:

Hi Lynn,

I'm running Big Sur, sadly my MacBook Pro is a 2016 model and not compatible with Monterey otherwise I would had upgraded.

I'm beginning to wonder if it's the Virtualbox USB driver that is causing a conflict.

Are you using Virtualbox or any other virtualisation software on your Mac?

Mike
M0AWS

On Fri, Jan 21, 2022 at 03:30 PM, Lynn Mears wrote:


FYI, I installed 6.0.2 about a week ago without any issues on a MacBook Pro
with Monterey 12.1 on it.

6.02 was released on Oct 26.

Lynn
K0CLM
On Jan 21, 2022, at 4:21 AM, K3JRZ <k3jrz.jeff@...> wrote:
I haven’t had any problems with the 6.0.1 since upgrading to those
after my
issue and no issues with Monterey yet nor with VMware Fusion. I’m in the
same boat as my iMac is my main computer too so I’m leaving well enough
alone for now.

Keep us informed of what Silicon Labs does for your issue.

Good luck & 73.

Jeff K3JRZ



On Fri, Jan 21, 2022 at 04:29 Mike <m0aws@...> wrote:

Hi Jeff,

V6.0.2 is the latest version but, I wouldn't install it yet just incase
you end up with the screen problems that I have experienced as it renders
your Mac unusable.
I got a reply from the Silicon Labs support asking for more info which
I've now provided.

My MacBook Pro is my main computer and I need it for a lot of other things
apart from radio and so I'm now thinking of using a PC for the radio stuff
rather than my Mac. I have two old PCs to hand which should be fine for
WSJT-X/FT8, I think I'll install Ubuntu Linux onto one of them and see if I
can get it working.

I use Virtualbox on my MacBook Pro so I can run a Windows VM for Eznec
Antenna design, I'm beginning to wonder if the USB driver/kernel extension
that Virtualbox installs is causing a conflict with the Silicon Labs VCP
driver. I'm aware that in the VCP driver release notes it's talks about not
using VMWare as its USB driver conflicts with the Silicon Labs driver, I'm
now wondering if the Virtualbox USB driver also conflicts even though it's
not detailed in the release notes.

Only way to prove this will be to uninstall Virtualbox from my MacBook Pro
and reinstall the Silicon Labs driver and see what happens. The only thing
putting me off doing this is having to reinstall MacOS all over again if it
bricks my MacBook again!

Best 73,

Mike.
M0AWS
http://m0aws.co.uk
Locked Re: WSJT-X crashes witrh error messages not understood #stopped_working

Gwen
 

Dick,

I'll leave others to answer the second set of problems, but those first problems (lock files/unique rig names) is a Windows problem, not WSJT-X.     I've had those pop up on Windows-10 --- both with and without WSJT-x running.
(( Which is why I dumped Microsoft for serious computer uses ))>>>>    The problem "resolves" by rebooting.

((BTW, I plan on staying with 2.4.4 as long as possible --- see too many complaints about the upgrade versions))

Gwen
KI5PXQ

On 1/21/22 6:52 PM, Dick McClain wrote:
WSJT-X version 2.5.3, JTAlert version 2.50.9 and Windows 11 with new PC

After re-starting PC and no programs running, I launch WSJT-X which starts as expected.
Then Launch JTAlert and get two error message windows:
1) WSJT-X Header followed by " Another instance may be running. Try to remove stale lock file? " I click "no".
2) WSJT-X Header followed by " Multiple instances must have unique rig names ". I click "no".

Then I make a couple of FT8 QSOs and log them as expected. Then a surprise ...
1) I answered a CQ
2) that station replied with my signal report
3) Within a second or two, WSJT-X window closed
4) attempt to re-launch WSJT-X fails (does not open)
5) Multiple error windows open as follows
a) WSJT-X Header followed by " Sub process error. Failed to close orphaned jt9 process " [but never had JT9 mode at any time]. I click "X" to close it.
b) WSJT-X Header followed by " Fatal Error. Sub process error " I click "X" to close window
6) More attempts to open QSJT-X fail with same errors
7) Checked Task Manager to verify no processes other than JTAlert
8) Did a re-start of PC and WSJT-X opens as expected but get following error windows
a) WSJT-X Header followed by " Another instance may be running. Try to remove stale lock file? ". I click "no".
b) WSJT-X Header followed by " Multiple instances must have unique rig names ". I click "no".

Then all works well for a while. At some point this sequence repeats and has done so many times.
I have no clue what the messages are telling me.

Hint: this trouble started after getting a new PC about a month ago. I have used WSJT-X & JTAlert for years without seeing this. Previous PC had Windows 10

Any suggestions are appreciated. Thank you and 73

Dick, KD4S
Locked Re: WSJT-X crashes witrh error messages not understood #stopped_working

JTAlert Support (VK3AMA)
 

On 22/01/2022 12:52 pm, Dick McClain wrote:
After re-starting PC and no programs running, I launch WSJT-X which starts as expected.
Then Launch JTAlert and get two error message windows:
1) WSJT-X Header followed by " Another instance may be running. Try to remove stale lock file? " I click "no".
2) WSJT-X Header followed by " Multiple instances must have unique rig names ". I click "no".
It would appear that you have JTAlert set to auto-start a copy of WSJT-X. Either turn that off or simply start JTAlert *without* first manually starting WSJTX.

de Laurie VK3AMA
Locked WSJT-X crashes witrh error messages not understood #stopped_working

Dick McClain
 

WSJT-X version 2.5.3, JTAlert version 2.50.9 and Windows 11 with new PC

After re-starting PC and no programs running, I launch WSJT-X which starts as expected.
Then Launch JTAlert and get two error message windows:
1) WSJT-X Header followed by " Another instance may be running. Try to remove stale lock file? " I click "no".
2) WSJT-X Header followed by " Multiple instances must have unique rig names ". I click "no".

Then I make a couple of FT8 QSOs and log them as expected. Then a surprise ...
1) I answered a CQ
2) that station replied with my signal report
3) Within a second or two, WSJT-X window closed
4) attempt to re-launch WSJT-X fails (does not open)
5) Multiple error windows open as follows
a) WSJT-X Header followed by " Sub process error. Failed to close orphaned jt9 process " [but never had JT9 mode at any time]. I click "X" to close it.
b) WSJT-X Header followed by " Fatal Error. Sub process error " I click "X" to close window
6) More attempts to open QSJT-X fail with same errors
7) Checked Task Manager to verify no processes other than JTAlert
8) Did a re-start of PC and WSJT-X opens as expected but get following error windows
a) WSJT-X Header followed by " Another instance may be running. Try to remove stale lock file? ". I click "no".
b) WSJT-X Header followed by " Multiple instances must have unique rig names ". I click "no".

Then all works well for a while. At some point this sequence repeats and has done so many times.
I have no clue what the messages are telling me.

Hint: this trouble started after getting a new PC about a month ago. I have used WSJT-X & JTAlert for years without seeing this. Previous PC had Windows 10

Any suggestions are appreciated. Thank you and 73

Dick, KD4S
11821 - 11840 of 43108