OK, here’s a test using -m 236 (this time) on my Flex 6500 while it was 
listening to 21.074.  I get a lot of output from the program, then it appears 
to hang.  I waited a few minutes.

PS C:\wsjt\wsjtx_d\bin> ./rigctld-wsjtx.exe -m 236 -r 127.0.0.1:5002 -vvvvv
rigctld, Hamlib 3.2~git
Report bugs to <hamlib-develo...@lists.sourceforge.net>

rig_init called
initrigs3_kenwood called
rig_register called
rig_register: rig_register (213)
rig_register called
rig_register: rig_register (201)
rig_register called
rig_register: rig_register (225)
rig_register called
rig_register: rig_register (203)
rig_register called
rig_register: rig_register (204)
rig_register called
rig_register: rig_register (216)
rig_register called
rig_register: rig_register (224)
rig_register called
rig_register: rig_register (205)
rig_register called
rig_register: rig_register (207)
rig_register called
rig_register: rig_register (209)
rig_register called
rig_register: rig_register (210)
rig_register called
rig_register: rig_register (222)
rig_register called
rig_register: rig_register (214)
rig_register called
rig_register: rig_register (230)
rig_register called
rig_register: rig_register (221)
rig_register called
rig_register: rig_register (229)
rig_register called
rig_register: rig_register (238)
rig_register called
rig_register: rig_register (202)
rig_register called
rig_register: rig_register (211)
rig_register called
rig_register: rig_register (206)
rig_register called
rig_register: rig_register (208)
rig_register called
rig_register: rig_register (215)
rig_register called
rig_register: rig_register (226)
rig_register called
rig_register: rig_register (217)
rig_register called
rig_register: rig_register (233)
rig_register called
rig_register: rig_register (220)
rig_register called
rig_register: rig_register (223)
rig_register called
rig_register: rig_register (227)
rig_register called
rig_register: rig_register (234)
rig_register called
rig_register: rig_register (231)
rig_register called
rig_register: rig_register (239)
rig_register called
rig_register: rig_register (237)
rig_register called
rig_register: rig_register (228)
rig_register called
rig_register: rig_register (219)
rig_register called
rig_register: rig_register (232)
rig_register called
rig_register: rig_register (236)
rig_register called
rig_register: rig_register (240)
kenwood_init called
kenwood_init: if_len = 37
rig_open called
port_open called
network_open called
flexradio_open called
verify_flexradio_id called
kenwood_get_id called
kenwood_transaction called
kenwood_transaction: cmdstr = ID
network_flush called
write_block called
write_block(): TX 3 bytes
0000    49 44 3b                                            ID;
read_string called
read_string(): RX 6 characters
0000    49 44 39 30 35 3b                                   ID905;
verify_flexradio_id: Rig ID is ID905 (Flex 6500)
kenwood_get_trn called
kenwood_safe_transaction called
kenwood_transaction called
kenwood_transaction: cmdstr = AI
network_flush called
write_block called
write_block(): TX 3 bytes
0000    41 49 3b                                            AI;
read_string called
read_string(): RX 4 characters
0000    41 49 30 3b                                         AI0;
kenwood_set_trn called
kenwood_transaction called
kenwood_transaction: cmdstr = AI0
network_flush called
write_block called
write_block(): TX 4 bytes
0000    41 49 30 3b                                         AI0;
write_block called
write_block(): TX 3 bytes
0000    49 44 3b                                            ID;
read_string called
read_string(): RX 6 characters
0000    49 44 39 30 35 3b                                   ID905;
rig_get_vfo called
kenwood_get_vfo_if called
kenwood_get_if called
kenwood_safe_transaction called
kenwood_transaction called
kenwood_transaction: cmdstr = IF
network_flush called
write_block called
write_block(): TX 3 bytes
0000    49 46 3b                                            IF;
read_string called
read_string(): RX 38 characters
0000    49 46 30 30 30 32 31 30 37 34 30 30 30 30 30 31     IF00021074000001
0010    30 2b 30 30 30 30 30 30 30 30 30 30 30 39 30 30     0+00000000000900
0020    30 30 30 30 30 3b                                   00000;
Opened rig model 236, '6xxx'
rig_strstatus called
Backend version: 20130717, Status: Beta

<hangs here – no further output>

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

Reply via email to