Re: [wsjt-devel] 2.2.0 RC1 Issues

[Black Michael via wsjt-devel]

There is a bug in DTR/RTS PTT in RC1 that will be fixed in the next release.
de Mike W9MDB

 

On Friday, May 15, 2020, 08:46:46 PM CDT, lgtngstk  
wrote:  
 
 Just to report, I am also having this issue as well.
On Wed, May 13, 2020 at 7:04 AM Bill Somerville  wrote:

  On 13/05/2020 00:37, David Tiller wrote:
  
 Dear devs, 
  I began using the latest release candidate today and love the early decodes, 
but I noticed a few things that seemed to be not working reliably under OSX. 
  My Setup: OSX 10.13.6, Icom 756PRO, and a RigExpert Standard. This setup 
works flawlessly with 2.1.2. 
  1) 2.20-RC1 does not remember the last band used on startup. It often starts 
on 160m and ends up on  2m, sometimes changing it while the RC banner is 
showing.
 2) PTT on TX is intermittent, as is the 'tune' function. Note that I do NOT 
use CAT control of the rig from WSJT-X (or anything else when testing this).
 3) Testing PTT sometimes works. The button turns red by itself and only 
actually keys the radio occasionally.
 
  Going into the Preferences/Radio menu tab immediately after startup gives me 
a red Test PTT button. With 2.1.2 I get a white button, as expected. See image, 
below. 
  
  I've made a video of the issues that can be downloaded from this folder link: 
  https://drive.google.com/open?id=1lRJIQFGZifH67zHoJUmajqDJiRrp43te 
  In case the listserv eats the link, it's: h t t p s:// drive_google_com / 
open ? id= 1lRJIQFGZifH67zHoJUmajqDJiRrp43te 
  sub '.' for '_' and remove spaces. 
  Thanks to all the devs for all their hard work! 
  
 
Hi David,
 
thanks for the issue report. Something is clearly not right. To help us 
diagnose this please open a terminal window and type the following command:
 /Applications/wsjtx.app/Contents/MacOS/rigctl-wsjtx -m 3027 -p 
/dev/cu.usbserial-141201 -P RTS -v -Z t pause 1 t pause 1 t 
Rreply with what gets printed please?
 
73
 Bill
 G4WJS.
 
 ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.2.0 RC1 Issues

[lgtngstk]

Just to report I am also having this issue as well.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.2.0 RC1 Issues

[lgtngstk]

Just to report, I am also having this issue as well.

On Wed, May 13, 2020 at 7:04 AM Bill Somerville 
wrote:

> On 13/05/2020 00:37, David Tiller wrote:
>
> Dear devs,
>
> I began using the latest release candidate today and love the early
> decodes, but I noticed a few things that seemed to be not working reliably
> under OSX.
>
> My Setup: OSX 10.13.6, Icom 756PRO, and a RigExpert Standard. This setup
> works flawlessly with 2.1.2.
>
> 1) 2.20-RC1 does not remember the last band used on startup. It often
> starts on 160m and ends up on  2m, sometimes changing it while the RC
> banner is showing.
> 2) PTT on TX is intermittent, as is the 'tune' function. Note that I do
> NOT use CAT control of the rig from WSJT-X (or anything else when testing
> this).
> 3) Testing PTT sometimes works. The button turns red by itself and only
> actually keys the radio occasionally.
>
> Going into the Preferences/Radio menu tab immediately after startup gives
> me a red Test PTT button. With 2.1.2 I get a white button, as expected. See
> image, below.
>
>
> I've made a video of the issues that can be downloaded from this folder
> link:
>
> https://drive.google.com/open?id=1lRJIQFGZifH67zHoJUmajqDJiRrp43te
>
> In case the listserv eats the link, it's:
> h t t p s:// drive_google_com / open ? id=
> 1lRJIQFGZifH67zHoJUmajqDJiRrp43te
>
> sub '.' for '_' and remove spaces.
>
> Thanks to all the devs for all their hard work!
>
> Hi David,
>
> thanks for the issue report. Something is clearly not right. To help us
> diagnose this please open a terminal window and type the following command:
>
> /Applications/wsjtx.app/Contents/MacOS/rigctl-wsjtx -m 3027 -p 
> /dev/cu.usbserial-141201 -P RTS -v -Z t pause 1 t pause 1 t
>
> Rreply with what gets printed please?
>
> 73
> Bill
> G4WJS.
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.2.0 RC1 Issues

[David Tiller]

Mike,

I gave it a go. I assume the 'master' branch is the one you want - I saw your 
commits :-)

I installed it in a local dir, not in /usr or /opt:

./configure --prefix=/Users/dtiller/hamlib-master-prefix 
--exec-prefix=/Users/dtiller/hamlib-master-eprefix

Here's the output:

WITH CACHE SET TO 0

dtiller$ ./rigctl -p /dev/cu.usbserial-141201 -P RTS -v -Z 
--set-conf=cache_timeout=0 t pause 1 t pause 1 t
2020-05-13:13:26:24.829615: rigctl, Hamlib 4.0~git May 13 2020 09:24:59
2020-05-13:13:26:24.829961: Report bugs to 


2020-05-13:13:26:24.829997: rig_init called
2020-05-13:13:26:24.830020: initrigs4_dummy: _init called
2020-05-13:13:26:24.830034: rig_register called
2020-05-13:13:26:24.830040: rig_register: rig_register (1)
2020-05-13:13:26:24.830051: rig_register called
2020-05-13:13:26:24.830057: rig_register: rig_register (2)
2020-05-13:13:26:24.830063: rig_register called
2020-05-13:13:26:24.830069: rig_register: rig_register (4)
2020-05-13:13:26:24.830075: rig_register called
2020-05-13:13:26:24.830081: rig_register: rig_register (5)
2020-05-13:13:26:24.830111: dummy_init called
2020-05-13:13:26:24.830142: rig_passband_normal called
2020-05-13:13:26:24.830148: rig_passband_normal called
2020-05-13:13:26:24.830166: rig_token_lookup called
2020-05-13:13:26:24.830172: rig_confparam_lookup called
2020-05-13:13:26:24.830182: rig_set_conf called
2020-05-13:13:26:24.830188: rig_confparam_lookup called
2020-05-13:13:26:24.830195: rig_set_conf: cache_timeout='0'
2020-05-13:13:26:24.830206: rig_set_cache_timeout_ms: called selection=0, ms=0
2020-05-13:13:26:24.830216: rig_open called
2020-05-13:13:26:24.830236: port_open called
2020-05-13:13:26:24.830244: ser_open called
2020-05-13:13:26:24.833249: ser_set_dtr called
2020-05-13:13:26:24.833262: ser_set_dtr: DTR=0
2020-05-13:13:26:24.833315: ser_set_rts called
2020-05-13:13:26:24.833322: ser_set_rts: RTS=0
2020-05-13:13:26:24.88: ser_close called
2020-05-13:13:26:24.833344: ser_close: no options for fd to restore
2020-05-13:13:26:24.835134: dummy_open called
2020-05-13:13:26:24.857629: rig_get_vfo called
2020-05-13:13:26:24.857666: elapsed_ms: start = 0,0
2020-05-13:13:26:24.857685: rig_get_vfo: cache check age=100ms
2020-05-13:13:26:24.857699: rig_get_vfo: cache miss age=100ms
2020-05-13:13:26:24.882744: dummy_get_vfo called: VFOA
2020-05-13:13:26:24.882764: elapsed_ms: start = 0,0
2020-05-13:13:26:24.882774: elapsed_ms: after gettime, start = 
1589376384,882772000
2020-05-13:13:26:24.882813: rig_set_parm called
2020-05-13:13:26:24.882826: rig_has_set_parm called
2020-05-13:13:26:24.882865: rig_setting2idx called
2020-05-13:13:26:24.882880: rig_strparm called
2020-05-13:13:26:24.882887: rig_strparm called
2020-05-13:13:26:24.882892: dummy_set_parm called: SCREENSAVER 0
Opened rig model 1, 'Dummy'
2020-05-13:13:26:24.882920: Backend version: 20200503.0, Status: Stable
2020-05-13:13:26:24.882928: rigctl_parse: called, interactive=0
2020-05-13:13:26:24.882939: rigctl_parse: debug1
2020-05-13:13:26:24.882945: rigctl_parse: debug5
2020-05-13:13:26:24.882950: rigctl_parse: debug10
2020-05-13:13:26:24.882958: rigctl_parse: vfo_mode=0
2020-05-13:13:26:24.882970: rig_get_ptt called
2020-05-13:13:26:24.882977: elapsed_ms: start = 0,0
2020-05-13:13:26:24.882983: rig_get_ptt: cache check age=100ms
2020-05-13:13:26:24.882989: rig_get_ptt: cache miss age=100ms
2020-05-13:13:26:24.907898: dummy_get_ptt called
2020-05-13:13:26:24.907924: elapsed_ms: start = 0,0
2020-05-13:13:26:24.907940: elapsed_ms: after gettime, start = 
1589376384,907937000
0
2020-05-13:13:26:24.907974: rigctl_parse: retcode=0
2020-05-13:13:26:24.907984: rigctl_parse: called, interactive=0
2020-05-13:13:26:24.908031: rigctl_parse: debug1
2020-05-13:13:26:24.908038: rigctl_parse: debug3
2020-05-13:13:26:24.908044: rigctl_parse: debug5
2020-05-13:13:26:24.908049: rigctl_parse: debug10
2020-05-13:13:26:24.908055: rigctl_parse: vfo_mode=0
2020-05-13:13:26:25.912536: rigctl_parse: retcode=0
2020-05-13:13:26:25.912560: rigctl_parse: called, interactive=0
2020-05-13:13:26:25.912568: rigctl_parse: debug1
2020-05-13:13:26:25.912574: rigctl_parse: debug5
2020-05-13:13:26:25.912580: rigctl_parse: debug10
2020-05-13:13:26:25.912586: rigctl_parse: vfo_mode=0
2020-05-13:13:26:25.912594: rig_get_ptt called
2020-05-13:13:26:25.912601: elapsed_ms: start = 1589376384,907937000
2020-05-13:13:26:25.912613: elapsed_ms: elapsed_secs=1004.67
2020-05-13:13:26:25.912623: rig_get_ptt: cache check age=1004ms
2020-05-13:13:26:25.912632: rig_get_ptt: cache miss age=1004ms
2020-05-13:13:26:25.936449: dummy_get_ptt called
2020-05-13:13:26:25.936474: elapsed_ms: start = 0,0
2020-05-13:13:26:25.936483: elapsed_ms: after gettime, start = 
1589376385,936481000
0
2020-05-13:13:26:25.936494: rigctl_parse: retcode=0
2020-05-13:13:26:25.936500: rigctl_parse: called, interactive=0
2020-05-13:13:26:25.936509: rigctl_parse: debug1
2020-05-13:13:26:25.936517: rigctl_parse: debug3
2020-05-13:13:26:25.936525: 

Re: [wsjt-devel] 2.2.0 RC1 Issues

[Bill Somerville]

On 13/05/2020 13:22, David Tiller wrote:

Thanks for the info, Bill and Mike!

I added the cache param and tried it with and without the -m parameter 
- with the -m 3027 it failed, without it the command 'worked', but DID 
NOT KEY THE RIG.


Hi David,

unfortunately it has not worked, the result is as before. It looks like 
this defect repair will have to wait for the next WSJT-X release. That 
should not be too long. I will make a test version up with the latest 
Hamlib fixes that Mike mentions, that should repair this regression, and 
send it to you for testing shortly.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.2.0 RC1 Issues

[Black Michael via wsjt-devel]

Are you able to compile hamlib?
de Mike W9MDB

 

On Wednesday, May 13, 2020, 07:48:25 AM CDT, David Tiller 
 wrote:  
 
 Thanks for the info, Bill and Mike!
I added the cache param and tried it with and without the -m parameter - with 
the -m 3027 it failed, without it the command 'worked', but DID NOT KEY THE RIG.
WITHOUT -m 3027
dtiller$ ./Applications/wsjtx.app/Contents/MacOS/rigctl-wsjtx -p 
/dev/cu.usbserial-141201 -P RTS -v -Z --set-conf=cache_timeout=0 t pause 1 
t pause 1 t2020-05-13:12:15:11.932273: rigctl, Hamlib 4.0~git May 10 2020 
14:25:012020-05-13:12:15:11.932609: Report bugs to 

2020-05-13:12:15:11.932630: rig_init called2020-05-13:12:15:11.932656: 
initrigs4_dummy: _init called2020-05-13:12:15:11.932670: rig_register 
called2020-05-13:12:15:11.932676: rig_register: rig_register 
(1)2020-05-13:12:15:11.932688: rig_register called2020-05-13:12:15:11.932694: 
rig_register: rig_register (2)2020-05-13:12:15:11.932700: rig_register 
called2020-05-13:12:15:11.932706: rig_register: rig_register 
(4)2020-05-13:12:15:11.932712: rig_register called2020-05-13:12:15:11.932717: 
rig_register: rig_register (5)2020-05-13:12:15:11.932749: dummy_init 
called2020-05-13:12:15:11.932783: rig_passband_normal 
called2020-05-13:12:15:11.932792: rig_passband_normal 
called2020-05-13:12:15:11.932811: rig_token_lookup 
called2020-05-13:12:15:11.932817: rig_confparam_lookup 
called2020-05-13:12:15:11.932827: rig_set_conf 
called2020-05-13:12:15:11.932835: rig_confparam_lookup 
called2020-05-13:12:15:11.932842: rig_set_conf: 
cache_timeout='0'2020-05-13:12:15:11.932854: rig_set_cache_timeout_ms: called 
selection=0, ms=02020-05-13:12:15:11.932863: rig_open 
called2020-05-13:12:15:11.932883: port_open called2020-05-13:12:15:11.932892: 
ser_open called2020-05-13:12:15:11.935101: ser_set_dtr 
called2020-05-13:12:15:11.935114: ser_set_dtr: DTR=02020-05-13:12:15:11.935158: 
ser_set_rts called2020-05-13:12:15:11.935165: ser_set_rts: 
RTS=02020-05-13:12:15:11.935181: ser_close called2020-05-13:12:15:11.935187: 
ser_close: no options for fd to restore2020-05-13:12:15:11.936673: dummy_open 
called2020-05-13:12:15:11.958970: rig_get_vfo called2020-05-13:12:15:11.959001: 
elapsed_ms: start = 0,02020-05-13:12:15:11.959026: rig_get_vfo: cache check 
age=100ms2020-05-13:12:15:11.959035: rig_get_vfo: cache miss 
age=100ms2020-05-13:12:15:11.980311: dummy_get_vfo called: 
VFOA2020-05-13:12:15:11.980359: elapsed_ms: start = 
0,02020-05-13:12:15:11.980372: elapsed_ms: after gettime, start = 
1589372111,9803690002020-05-13:12:15:11.980402: rig_set_parm 
called2020-05-13:12:15:11.980414: rig_has_set_parm 
called2020-05-13:12:15:11.980439: rig_setting2idx 
called2020-05-13:12:15:11.980453: rig_strparm called2020-05-13:12:15:11.980473: 
rig_strparm called2020-05-13:12:15:11.980490: dummy_set_parm called: 
SCREENSAVER 0Opened rig model 1, 'Dummy'2020-05-13:12:15:11.980613: Backend 
version: 20200503.0, Status: Stable2020-05-13:12:15:11.980645: rigctl_parse: 
called, interactive=02020-05-13:12:15:11.980671: rigctl_parse: 
debug12020-05-13:12:15:11.980681: rigctl_parse: 
debug52020-05-13:12:15:11.980691: rigctl_parse: 
debug102020-05-13:12:15:11.980703: rigctl_parse: 
vfo_mode=02020-05-13:12:15:11.980742: rig_get_ptt 
called2020-05-13:12:15:11.980757: elapsed_ms: start = 
0,02020-05-13:12:15:11.980770: rig_get_ptt: cache check 
age=100ms2020-05-13:12:15:11.980781: rig_get_ptt: cache miss 
age=100ms2020-05-13:12:15:11.980792: elapsed_ms: start = 
0,02020-05-13:12:15:11.980803: elapsed_ms: after gettime, start = 
1589372111,9808010002020-05-13:12:15:12.002440: dummy_get_ptt 
called02020-05-13:12:15:12.002496: rigctl_parse: 
retcode=02020-05-13:12:15:12.002517: rigctl_parse: called, 
interactive=02020-05-13:12:15:12.002608: rigctl_parse: 
debug12020-05-13:12:15:12.002639: rigctl_parse: 
debug32020-05-13:12:15:12.002656: rigctl_parse: 
debug52020-05-13:12:15:12.002682: rigctl_parse: 
debug102020-05-13:12:15:12.002698: rigctl_parse: 
vfo_mode=02020-05-13:12:15:13.006309: rigctl_parse: 
retcode=02020-05-13:12:15:13.006347: rigctl_parse: called, 
interactive=02020-05-13:12:15:13.006360: rigctl_parse: 
debug12020-05-13:12:15:13.006371: rigctl_parse: 
debug52020-05-13:12:15:13.006381: rigctl_parse: 
debug102020-05-13:12:15:13.006392: rigctl_parse: 
vfo_mode=02020-05-13:12:15:13.006404: rig_get_ptt 
called2020-05-13:12:15:13.006416: elapsed_ms: start = 
1589372111,9808010002020-05-13:12:15:13.006434: elapsed_ms: 
elapsed_secs=1025.622020-05-13:12:15:13.006447: rig_get_ptt: cache check 
age=1025ms2020-05-13:12:15:13.006457: rig_get_ptt: cache miss 
age=1025ms2020-05-13:12:15:13.006468: elapsed_ms: start = 
0,02020-05-13:12:15:13.006480: elapsed_ms: after gettime, start = 
1589372113,64770002020-05-13:12:15:13.029188: dummy_get_ptt 
called10242020-05-13:12:15:13.029229: rigctl_parse: 
retcode=02020-05-13:12:15:13.029242: rigctl_parse: called, 
interactive=02020-05-13:12:15:13.029256: rigctl_parse: 

Re: [wsjt-devel] 2.2.0 RC1 Issues

[David Tiller]

Thanks for the info, Bill and Mike!

I added the cache param and tried it with and without the -m parameter - with 
the -m 3027 it failed, without it the command 'worked', but DID NOT KEY THE RIG.

WITHOUT -m 3027

dtiller$ ./Applications/wsjtx.app/Contents/MacOS/rigctl-wsjtx -p 
/dev/cu.usbserial-141201 -P RTS -v -Z --set-conf=cache_timeout=0 t pause 1 
t pause 1 t
2020-05-13:12:15:11.932273: rigctl, Hamlib 4.0~git May 10 2020 14:25:01
2020-05-13:12:15:11.932609: Report bugs to 


2020-05-13:12:15:11.932630: rig_init called
2020-05-13:12:15:11.932656: initrigs4_dummy: _init called
2020-05-13:12:15:11.932670: rig_register called
2020-05-13:12:15:11.932676: rig_register: rig_register (1)
2020-05-13:12:15:11.932688: rig_register called
2020-05-13:12:15:11.932694: rig_register: rig_register (2)
2020-05-13:12:15:11.932700: rig_register called
2020-05-13:12:15:11.932706: rig_register: rig_register (4)
2020-05-13:12:15:11.932712: rig_register called
2020-05-13:12:15:11.932717: rig_register: rig_register (5)
2020-05-13:12:15:11.932749: dummy_init called
2020-05-13:12:15:11.932783: rig_passband_normal called
2020-05-13:12:15:11.932792: rig_passband_normal called
2020-05-13:12:15:11.932811: rig_token_lookup called
2020-05-13:12:15:11.932817: rig_confparam_lookup called
2020-05-13:12:15:11.932827: rig_set_conf called
2020-05-13:12:15:11.932835: rig_confparam_lookup called
2020-05-13:12:15:11.932842: rig_set_conf: cache_timeout='0'
2020-05-13:12:15:11.932854: rig_set_cache_timeout_ms: called selection=0, ms=0
2020-05-13:12:15:11.932863: rig_open called
2020-05-13:12:15:11.932883: port_open called
2020-05-13:12:15:11.932892: ser_open called
2020-05-13:12:15:11.935101: ser_set_dtr called
2020-05-13:12:15:11.935114: ser_set_dtr: DTR=0
2020-05-13:12:15:11.935158: ser_set_rts called
2020-05-13:12:15:11.935165: ser_set_rts: RTS=0
2020-05-13:12:15:11.935181: ser_close called
2020-05-13:12:15:11.935187: ser_close: no options for fd to restore
2020-05-13:12:15:11.936673: dummy_open called
2020-05-13:12:15:11.958970: rig_get_vfo called
2020-05-13:12:15:11.959001: elapsed_ms: start = 0,0
2020-05-13:12:15:11.959026: rig_get_vfo: cache check age=100ms
2020-05-13:12:15:11.959035: rig_get_vfo: cache miss age=100ms
2020-05-13:12:15:11.980311: dummy_get_vfo called: VFOA
2020-05-13:12:15:11.980359: elapsed_ms: start = 0,0
2020-05-13:12:15:11.980372: elapsed_ms: after gettime, start = 
1589372111,980369000
2020-05-13:12:15:11.980402: rig_set_parm called
2020-05-13:12:15:11.980414: rig_has_set_parm called
2020-05-13:12:15:11.980439: rig_setting2idx called
2020-05-13:12:15:11.980453: rig_strparm called
2020-05-13:12:15:11.980473: rig_strparm called
2020-05-13:12:15:11.980490: dummy_set_parm called: SCREENSAVER 0
Opened rig model 1, 'Dummy'
2020-05-13:12:15:11.980613: Backend version: 20200503.0, Status: Stable
2020-05-13:12:15:11.980645: rigctl_parse: called, interactive=0
2020-05-13:12:15:11.980671: rigctl_parse: debug1
2020-05-13:12:15:11.980681: rigctl_parse: debug5
2020-05-13:12:15:11.980691: rigctl_parse: debug10
2020-05-13:12:15:11.980703: rigctl_parse: vfo_mode=0
2020-05-13:12:15:11.980742: rig_get_ptt called
2020-05-13:12:15:11.980757: elapsed_ms: start = 0,0
2020-05-13:12:15:11.980770: rig_get_ptt: cache check age=100ms
2020-05-13:12:15:11.980781: rig_get_ptt: cache miss age=100ms
2020-05-13:12:15:11.980792: elapsed_ms: start = 0,0
2020-05-13:12:15:11.980803: elapsed_ms: after gettime, start = 
1589372111,980801000
2020-05-13:12:15:12.002440: dummy_get_ptt called
0
2020-05-13:12:15:12.002496: rigctl_parse: retcode=0
2020-05-13:12:15:12.002517: rigctl_parse: called, interactive=0
2020-05-13:12:15:12.002608: rigctl_parse: debug1
2020-05-13:12:15:12.002639: rigctl_parse: debug3
2020-05-13:12:15:12.002656: rigctl_parse: debug5
2020-05-13:12:15:12.002682: rigctl_parse: debug10
2020-05-13:12:15:12.002698: rigctl_parse: vfo_mode=0
2020-05-13:12:15:13.006309: rigctl_parse: retcode=0
2020-05-13:12:15:13.006347: rigctl_parse: called, interactive=0
2020-05-13:12:15:13.006360: rigctl_parse: debug1
2020-05-13:12:15:13.006371: rigctl_parse: debug5
2020-05-13:12:15:13.006381: rigctl_parse: debug10
2020-05-13:12:15:13.006392: rigctl_parse: vfo_mode=0
2020-05-13:12:15:13.006404: rig_get_ptt called
2020-05-13:12:15:13.006416: elapsed_ms: start = 1589372111,980801000
2020-05-13:12:15:13.006434: elapsed_ms: elapsed_secs=1025.62
2020-05-13:12:15:13.006447: rig_get_ptt: cache check age=1025ms
2020-05-13:12:15:13.006457: rig_get_ptt: cache miss age=1025ms
2020-05-13:12:15:13.006468: elapsed_ms: start = 0,0
2020-05-13:12:15:13.006480: elapsed_ms: after gettime, start = 
1589372113,6477000
2020-05-13:12:15:13.029188: dummy_get_ptt called
1024
2020-05-13:12:15:13.029229: rigctl_parse: retcode=0
2020-05-13:12:15:13.029242: rigctl_parse: called, interactive=0
2020-05-13:12:15:13.029256: rigctl_parse: debug1
2020-05-13:12:15:13.029266: rigctl_parse: debug3
2020-05-13:12:15:13.029277: rigctl_parse: debug5
2020-05-13:12:15:13.029287: 

Re: [wsjt-devel] 2.2.0 RC1 Issues

[Bill Somerville]

On 13/05/2020 12:37, David Tiller wrote:

Bill,

Thanks for the speedy reply!

I see that the command specifies a rig - like I said, I only use the 
given serial port for PTT, not for CAT commands. I'm not sure if that 
changes anything.
The CAT port is /dev/cu.usbserial-1412*00*, but I set the rig to None 
most of the time. I tried it with '-s 19200' also, but it didn't 
change anything.



Hi David,

apologies, my bad. Your second invocation without the '-m 3027' option 
is what I needed, thanks for working that out.


The trace output is useful. Please try Mike's suggestion, if that works 
we can provide a workaround for WSJT-X.


73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.2.0 RC1 Issues

[Bill Somerville]

On 13/05/2020 00:37, David Tiller wrote:

Dear devs,

I began using the latest release candidate today and love the early 
decodes, but I noticed a few things that seemed to be not working 
reliably under OSX.


My Setup: OSX 10.13.6, Icom 756PRO, and a RigExpert Standard. This 
setup works flawlessly with 2.1.2.


1) 2.20-RC1 does not remember the last band used on startup. It often 
starts on 160m and ends up on  2m, sometimes changing it while the RC 
banner is showing.
2) PTT on TX is intermittent, as is the 'tune' function. Note that I 
do NOT use CAT control of the rig from WSJT-X (or anything else when 
testing this).
3) Testing PTT sometimes works. The button turns red by itself and 
only actually keys the radio occasionally.


Going into the Preferences/Radio menu tab immediately after startup 
gives me a red Test PTT button. With 2.1.2 I get a white button, as 
expected. See image, below.



I've made a video of the issues that can be downloaded from this 
folder link:


https://drive.google.com/open?id=1lRJIQFGZifH67zHoJUmajqDJiRrp43te

In case the listserv eats the link, it's:
h t t p s:// drive_google_com / open ? id= 
1lRJIQFGZifH67zHoJUmajqDJiRrp43te


sub '.' for '_' and remove spaces.

Thanks to all the devs for all their hard work!


Hi David,

thanks for the issue report. Something is clearly not right. To help us 
diagnose this please open a terminal window and type the following command:


/Applications/wsjtx.app/Contents/MacOS/rigctl-wsjtx -m 3027 -p 
/dev/cu.usbserial-141201 -P RTS -v -Z t pause 1 t pause 1 t

Rreply with what gets printed please?

73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.2.0 RC1 Issues

[Ken Cox]

Installed [wsjt-devel] 2.2.0 RC1 on latest update of MacOs HiSierra with Icom 
IC7300. Only issue is with tune power level memory. Not sure I’m setting things 
properly. When all else fails, read the manual. Thanks for the effort everyone 
put into development of such a fine piece of software. Ken WA8OMR

> On May 12, 2020, at 7:37 PM, David Tiller  wrote:
> 
> Dear devs,
> 
> I began using the latest release candidate today and love the early decodes, 
> but I noticed a few things that seemed to be not working reliably under OSX.
> 
> My Setup: OSX 10.13.6, Icom 756PRO, and a RigExpert Standard. This setup 
> works flawlessly with 2.1.2.
> 
> 1) 2.20-RC1 does not remember the last band used on startup. It often starts 
> on 160m and ends up on  2m, sometimes changing it while the RC banner is 
> showing.
> 2) PTT on TX is intermittent, as is the 'tune' function. Note that I do NOT 
> use CAT control of the rig from WSJT-X (or anything else when testing this).
> 3) Testing PTT sometimes works. The button turns red by itself and only 
> actually keys the radio occasionally.
> 
> Going into the Preferences/Radio menu tab immediately after startup gives me 
> a red Test PTT button. With 2.1.2 I get a white button, as expected. See 
> image, below.
> 
> 
> I've made a video of the issues that can be downloaded from this folder link:
> 
> https://drive.google.com/open?id=1lRJIQFGZifH67zHoJUmajqDJiRrp43te 
> 
> 
> In case the listserv eats the link, it's:
> h t t p s:// drive_google_com / open ? id= 1lRJIQFGZifH67zHoJUmajqDJiRrp43te
> 
> sub '.' for '_' and remove spaces.
> 
> Thanks to all the devs for all their hard work!
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel