I ran your example and found that the code for the Flex radio is 236.
I have a TCP port configured for the radio on port 5002. Assuming the IP
address is 127.0.0.1, and copying your example, this is what I get. (Does the
-vvvvv mean “really verbose”?)
PS C:\wsjt\wsjtx_d\bin> ./rigctld-wsjtx.exe -m 136 -r 127.0.0.1:5002 -vvvvv
rigctld, Hamlib 3.2~git
Report bugs to <hamlib-develo...@lists.sourceforge.net>
rig_init called
yaesu: initrigs3_yaesu called
rig_register called
rig_register: rig_register (121)
rig_register called
rig_register: rig_register (127)
rig_register called
rig_register: rig_register (110)
rig_register called
rig_register: rig_register (105)
rig_register called
rig_register: rig_register (106)
rig_register called
rig_register: rig_register (107)
rig_register called
rig_register: rig_register (109)
rig_register called
rig_register: rig_register (120)
rig_register called
rig_register: rig_register (101)
rig_register called
rig_register: rig_register (122)
rig_register called
rig_register: rig_register (123)
rig_register called
rig_register: rig_register (111)
rig_register called
rig_register: rig_register (115)
rig_register called
rig_register: rig_register (113)
rig_register called
rig_register: rig_register (114)
rig_register called
rig_register: rig_register (128)
rig_register called
rig_register: rig_register (131)
rig_register called
rig_register: rig_register (116)
rig_register called
rig_register: rig_register (103)
rig_register called
rig_register: rig_register (124)
rig_register called
rig_register: rig_register (104)
rig_register called
rig_register: rig_register (125)
rig_register called
rig_register: rig_register (129)
rig_register called
rig_register: rig_register (132)
rig_register called
rig_register: rig_register (130)
rig_register called
rig_register: rig_register (117)
rig_register called
rig_register: rig_register (119)
rig_register called
rig_register: rig_register (118)
rig_register called
rig_register: rig_register (126)
rig_register called
rig_register: rig_register (133)
rig_register called
rig_register: rig_register (134)
rig_register called
rig_register: rig_register (135)
rig_register called
rig_register: rig_register (136)
ft891_init called, version 0.23.2
newcat_init called
rig_open called
port_open called
serial_open called
serial_open: Unable to open 127.0.0.1:5002 - No error
rig_open: error = IO error
PS C:\wsjt\wsjtx_d\bin>
I did all of this in PowerShell.
Dave Fisher / NX6D
________________________________
From: Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net>
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 default it connects to 127.0.0.1:4532 -vvvvv
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 -vvvvv
de Mike W9MDB
On Wednesday, October 11, 2017, 11:10:48 PM CDT, Phil Theis <p...@k3tuf.com>
wrote:
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-devel wrote:
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 -l
then
rigctld-wstx -m 346 -s 19200 -r COM2 -vvvvv
Then set up the wsjtx rig to Hamlib NET rigctl.I explained on an earlier email
how to do this.
See if you can repeat the problem. That will help tell if it's hamlib or
wsjt-x causing it.
The last group of lines should tell the story.
de Mike W9MDB
On Wednesday, October 11, 2017, 9:04:17 PM CDT, Ria Jairam
<rjai...@gmail.com><mailto:rjai...@gmail.com> wrote:
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 radio
has this problem.
Anyway either myself, Phil and others would be more than happy to help debug
any issues with flex radios connecting to WSJT-X or any software for that
matter.
73
Ria, N2RJ
On Wed, Oct 11, 2017 at 5:06 PM Dave
<quicks...@gmail.com<mailto:quicks...@gmail.com>> wrote:
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 when it freezes.
73 Dave W3DLQ
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
