000;
Opened rig model 236, '6xxx'
rig_strstatus called
Backend version: 20130717, Status: Beta
Dave Fisher / NX6D
From: Black Michael via wsjt-devel
Sent: Wednesday, October 11, 2017 9:19:16 PM
To: WSJT software development
Cc: Black Michael
Subject: Re
, 2017 7:01:44 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Stale Lock
WSJT-X hanging on exit definitely isn’t a SmartSDR problem. Any software should
timeout a TCP connection it can’t close instead of staying hung.
However this may be peculiar to Hamlib rather than WSJT-X. We are not
I ran it with the wrong rig number. Should have been 236. Ignore.
From: David Fisher
Sent: Wednesday, October 11, 2017 10:59:00 PM
To: Black Michael; WSJT software development
Subject: RE: [wsjt-devel] Stale Lock
I ran your example and found that the code for
f this in PowerShell.
Dave Fisher / NX6D
From: Black Michael via wsjt-devel
Sent: Wednesday, October 11, 2017 9:19:16 PM
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] Stale Lock
If you installed in the standard location:
By defa
It’s in the “bin” directory along side WSJT-x.
Dave / NX6D
From: Phil Theis
Sent: Wednesday, October 11, 2017 9:08:32 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Stale Lock
Where will I find rigctld-wsjtx?
Remember, the driver for Flex
If you installed in the standard location:
By default it connects to 127.0.0.1:4532 -v
If you need a different address or port then for example:
c:\wsjt\wsjt-x\rigctld-wsjtx.exe -m 136 -r 127.0.0.2:4533 -v
de Mike W9MDB
On Wednesday, October 11, 2017, 11:10:48 PM CDT, Phil Theis
wr
Where will I find rigctld-wsjtx?
Remember, the driver for Flex 6xxx doesn't use (or shouldn't use) CAT
com ports; it goes directly over the network via TCP.
Who wrote the original 6xxx driver, perhaps we can get info from them?
73,
Phil K3TUF
On 10/11/2017 11:51 PM, Black Michael via wsjt-
One or more of you needs to run rigctld-wsjtx to help debug this.
Do you know how to run rigctld-wsjtx?First you do this to get a list of the rig
numbers. 346 is the 746Pro
rigctld-wsjtx -lthenrigctld-wstx -m 346 -s 19200 -r COM2 -vThen set up the
wsjtx rig to Hamlib NET rigctl.I explained o
It's note "telnet" -- that's a specific TCP protocol on a specific port.
But yes...there is TCP capability built-in. I wrote an interface for FLRIg
that does TCP for example.And the Flex6xxx also does TCP.
de Mike W9MDB
On Wednesday, October 11, 2017, 9:07:31 PM CDT, Phil Theis
wrote:
Hamlib can do TCP connections to the CAT program. Technically telnet
is basically just a TCP stream.
73
Ria, N2RJ
On Wed, Oct 11, 2017 at 10:06 PM, Phil Theis wrote:
> I'm not familiar with hamlib, but are there any telnet facilities built in?
> The Flex API is a very easy protocol.
>
> 73,
>
>
I'm not familiar with hamlib, but are there any telnet facilities built
in? The Flex API is a very easy protocol.
73,
Phil K3TUF
On 10/11/2017 10:01 PM, Ria Jairam wrote:
WSJT-X hanging on exit definitely isn’t a SmartSDR problem. Any
software should timeout a TCP connection it can’t close i
WSJT-X hanging on exit definitely isn’t a SmartSDR problem. Any software
should timeout a TCP connection it can’t close instead of staying hung.
However this may be peculiar to Hamlib rather than WSJT-X. We are not the
only flex users having this issue and literally nothing else connected to
the r
The Flex API works fine, I use it all the time.
First I am confused on what to enter in the Server entry, when I enter
the IP and Port of the Radio server, it sees the client and I'd have to
use wireshark to determine what the program is doing to interrogate.
Phil K3TUF
On 10/11/2017 5:04 P
Sounds more like a problem with SmartSDR than WSJT-X. Maybe we should
raise the issue with Flex.
BTW. I said I killed the jte.exe entries. I should have said wsjtx.exe as
I just scroll down to the bottom of the lists and find up to four instances
listed depending how many slices I'm running whe
So am I. If I run two slices I get wo sale locks.
Paul –w4pgm
From: Ria Jairam [mailto:rjai...@gmail.com]
Sent: Wednesday, October 11, 2017 4:09 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Stale lock
For what it’s worth I’m also experiencing the same symptoms of Phil
Echo, echo, echo.. For what it’s worth I’m also experiencing the same
symptoms of Phil and Ria. I’m also using a flex radio with the ports set to
TCP. Echo off.
Thought it was just me. I just kill the one or two jt9.exe with task manager
and restart the slices.
Dave W3DLQ
-
wasn't jt9 it was wsjt.exe which I stopped and got working again.
Tried Exit and that worked on restart
Tried the X again, and now that is working.
Anomaly I guess
Phil K3TUF
On 10/11/2017 4:10 PM, Black Michael via wsjt-devel wrote:
That should work. If you get the lock error check to see
Can you run rigctld-wsjtx and use Hamlib NET rigctl for the rig in WSJT-X and
see if the problem persists with the TCP ports then?
de Mike W9MDB
On Wednesday, October 11, 2017, 3:11:16 PM CDT, Ria Jairam
wrote:
For what it’s worth I’m also experiencing the same symptoms of Phil and
That should work. If you get the lock error check to see if jt9.exe is still
running in task manager.The you can kill it and answer the lock dialog with
Retry and it should work.
Next question is why isn't jt9.exe being terminated correctly?
Try renaming your WSJT-X.ini file and start WSJT-X wit
For what it’s worth I’m also experiencing the same symptoms of Phil and I’m
also using a flex radio with the ports set to TCP. When I change it to
TS2000 and use regular CAT ports the problem goes away.
73
Ria, N2RJ
On Wed, Oct 11, 2017 at 4:03 PM Phil Theis wrote:
> What is normal? I click on t
What is normal? I click on the X in the upper right.
Phil K3TUF
On 10/11/2017 3:53 PM, Black Michael via wsjt-devel wrote:
That usually indicates jt9.exe is still running.
Is WSJT-X crashing on you? That most always leaves jt9.exe running
and you can't remove the lock file until it's killed
That usually indicates jt9.exe is still running.Is WSJT-X crashing on you?
That most always leaves jt9.exe running and you can't remove the lock file
until it's killed in task manager.Are you exiting WSJT-X normally?
de Mike W9MDB
On Wednesday, October 11, 2017, 2:05:03 PM CDT, Phil Theis
With RC2 I keep getting the stale lock error and have to restart the
computer to get going again.
Also can't get the Flex 6xxx to convey frequency; I always resort to
CAT, which works fine.
Phil K3TUF
--
Check out th
23 matches
Mail list logo
