Hello Saku,
Thanks for the info - and I will try what you have pointed out.
My shack PC has been running Vista-64 for a while - I have too much stuff
on it and I'll use it as long as it will last - but yes, it is getting
dated. I did look up some of the USB drivers today - circa 2013 - so I'm
pretty sure the WSJT-X code could not have been tested with those drivers.
And I don't think those drivers will be updateable either; so it's just a
matter of time now until they
are incompatible.
One way I've temporarily gotten around the issue is just to stop the
program; tune; and the start again - that seems to be working pretty well -
been working a lot of stations in Japan this evening too BTW. Worked a
station in Korea and New Zealand also. Saw one from China but they didn't
come back.
73's,
John
AJ6BC
On Thu, Jun 7, 2018 at 12:23 AM, Saku <oh...@sral.fi> wrote:
> John C. Westmoreland, P.E. kirjoitti 06.06.2018 klo 21:42:
>
> After operating and changing bands; I will use my tuner; and the program
> will either hang or will pop up a window saying the rig has become
> unresponsive. I can click 'retry' sometimes and it'll be ok - but a
> consistent issue that will happen is it will either become completely
> unresponsive - with TX stuck; or I will get an error message saying hamlib
> I/O has suffered an error, and TX is stuck.
>
>
> Hi!
>
> I have IC706 with LDG Z-100Plus. Auto tuning is set from rig's menu and
> control cable exists between rig and LDG. So it will start tuning process
> every time on first TX when band is changed. Normally that 1st TX is
> pressing "tune" button of wsjt-x after band change.
>
> It is completely normal getting wsjt-x prompt "rig not responding" 99% of
> the time.
>
> That is because rigctld does run to timeout because rig is not responding
> to cat commands during tuning. And LDG has (according to manual) 1,5 sec
> tail after the best match is set. Said according to manual, as sometimes I
> feel that the delay from LDG led showing ok to time it drops TX feels much
> longer.
>
> Answering "Retry" *after LDG has dropped rig's TX* will continue normal
> operation.
>
> That could, maybe, be fixed by setting rigctld timeout bigger. But that
> cannot be done via wsjt-x radio setup. Then rigctld must be started as
> separate command line process to get wanted parameters in use, and after
> that open the wsjt-x with setting radio/Hamlib Net rigctl/localhost:4532 to
> get access to rigctld.
>
> I have been too lazy to test this longer timeout, just accepted that I
> need to press "retry" after every tuning session.
>
> Os here is Fedora 27 linux.
> With my little experience from past years I wonder how you can stand
> Vista? Slowest OS I have never seen. I'm sure that it makes also a part of
> your problems. Not everything is coming from RF leaks as suspected here.
>
>
> --
> Saku
> OH1KH
>
>
>
>
> ------------------------------------------------------------
> ------------------
> 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
>
>
------------------------------------------------------------------------------
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
